This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Warnings in RTE_Components when using packs

I am trying to set up an environment based on CMSIS Packs. However, when using some components from nRF_Libraries, these lines get added to RTE_Components.h:

#define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS=4>nrf_drv_gpiote
#define GPIOTE_ENABLED=1>.
  #define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS=1>.

Since I use RTE_Components.h in most of my own files, I am flooded with compiler warnings regarding these definitions:

C:\Data\Projects\HGBLE\application\arm\RTE\RTE_Components.h(13): warning:  #2775-D: white space is required between the macro name "GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS" and its replacement text
  #define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS=4>nrf_drv_gpiote
C:\Data\Projects\HGBLE\application\arm\RTE\RTE_Components.h(14): warning:  #2775-D: white space is required between the macro name "GPIOTE_ENABLED" and its replacement text
  #define GPIOTE_ENABLED=1>.
C:\Data\Projects\HGBLE\application\arm\RTE\RTE_Components.h(15): warning:  #2775-D: white space is required between the macro name "GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS" and its replacement text
    #define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS=1>.
C:\Data\Projects\HGBLE\application\arm\RTE\RTE_Components.h(15): warning:  #47-D: incompatible redefinition of macro "GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS" (declared at line 13)
    #define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS=1>.

Is this an expected behaviour? What can I do to silence these compiler warnings?

Parents
  • They are coming from NordicSemiconductor.nRF_Libraries.pdsc (line 394, app_button component definition) and NordicSemiconductor.nRF_Drivers.pdsc (line 835/836, nrf_drv_gpiote component definition). I could edit these in my installation, but that would mean editing them on the local machine of each developer and break compatibility.

    I am aware that there is already a problem when these two components are used together in the latest SDK versions, but I'm not sure this particular problem with CMSIS packs is known too.

Reply
  • They are coming from NordicSemiconductor.nRF_Libraries.pdsc (line 394, app_button component definition) and NordicSemiconductor.nRF_Drivers.pdsc (line 835/836, nrf_drv_gpiote component definition). I could edit these in my installation, but that would mean editing them on the local machine of each developer and break compatibility.

    I am aware that there is already a problem when these two components are used together in the latest SDK versions, but I'm not sure this particular problem with CMSIS packs is known too.

Children
No Data
Related