• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 8 replies
  • Subscribers 65 subscribers
  • Views 4930 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 126058
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SDK_config.h inconsistencies

jev

I just replaced SDK 14.0 with the shiny new SDK 14.1 in my project. My project uses components from the SDK, but I don't use the exact same structure. Once again, it won't compile out of the box. sigh

Okay, here's the question. I assumed ~\nRF5_SDK_14.1.0_1dda907\config\sdk_config.h to be a typical "master" from which the sdk_config.h files used in the examples are derived. No such luck. I expected this master not to be that different from, for example, from ~\nRF5_SDK_14.1.0_1dda907\examples\peripheral\blinky\pca10040\blank\config\sdk_config.h.

Wrong. It is next to impossible to compare the differences in these two using an automated tool.

Is there another "master" that is being used for creation of the examples?

How can I compare the sdk_config.h from my project (that started life using SDK 13) with the changes required in SDK 14.1?

Parents
  • 0

    Yes, there seems to be some room for improvment in the sdk_folder\config\sdk_config.h file.

    For BLE application, you can also consider the sdk_config.h in the ble_app_template project to also be a kind of master config file.

    would it be possible to update the examples to use sdk_config files directly derived from the delivered master copy?

    Could be possible, but care must be taken when merging so that the master sdk_config defines don’t overwrite any of the defines set in the example sdk_config.

  • 0 in reply to Sigurd

    Can a single sdk_config file that has all possible macros definitions ?

    (1) be provided ?

    (2) an identical sdk_config file be inserted in all examples - so it is easy for customers to merge different examples to make their projects easily. 

    What we have now is scrambled sdk macros spread in different examples. [This means example projects does not have all the sdk_config parameters which defeats the purpose of having and sdk_config. altogether].

    A huge amount of time is wasted just trying to identify and getting a working sdk_config file. This can be avoided with a single sdk_config that has all parameters. 

Reply
  • 0 in reply to Sigurd

    Can a single sdk_config file that has all possible macros definitions ?

    (1) be provided ?

    (2) an identical sdk_config file be inserted in all examples - so it is easy for customers to merge different examples to make their projects easily. 

    What we have now is scrambled sdk macros spread in different examples. [This means example projects does not have all the sdk_config parameters which defeats the purpose of having and sdk_config. altogether].

    A huge amount of time is wasted just trying to identify and getting a working sdk_config file. This can be avoided with a single sdk_config that has all parameters. 

Children
Related

core_v2_widget.Hide()