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

SDKV12 sdk_config.h "master" ?

Hello. I have a question and a request for Nordic developers.

It is really super-helpful that in SDKV12 you converted to having a master sdk_config.h that contains what seems to be 100% of all sdk config parameters. This is terrific.

What has been making conversion from SDK11 a bit more challenging for me, however, is the fact that I can't seem to find a "master" sdk_config.h that contains 100% of all parameters. It has been a trial and error process that involves scanning the sdk_config.h's contained within the various examples, which seem to have differing subsets of sdk_config.h.

Furthermore, in at least one case I was stumped by the fact that there were no sdk_config.h's at all, in any of the examples, that had a parameter that turned out to be necessary and should have been in there: APP_GPIOTE_ENABLED.

I don't know what other developers do, but what I would like to be able to do each time a new SDK is released is this:

  1. Go into a subfolder of /documentation that contains the "master" sdk_config.h for that release
  2. Diff it against the "master" sdk_config for the previous release.
  3. Manually upgrade my own sdk_config.h's based upon what I find.

I say this because given the number of parameters it can be tricky and error-prone to propagate an app's config parameters from one release to another. If the Nordic devs would maintain the sdk_config.h in a "readily diff-able" manner, it would really help 3rd party devs in sdk transitions.

Thanks for your consideration.

Parents
  • +1 for this also I've so far noticed that not all options of given module are included in example configuration. For example NRF_LOG module has option to define log output colors only for some levels only whereas code of that module allows to configure them for all levels. Another thing is pin definitions for TWI, SPI, etc. Those used to be defined in nrf_drv_config.h but are absent from sdk_config.h

Reply
  • +1 for this also I've so far noticed that not all options of given module are included in example configuration. For example NRF_LOG module has option to define log output colors only for some levels only whereas code of that module allows to configure them for all levels. Another thing is pin definitions for TWI, SPI, etc. Those used to be defined in nrf_drv_config.h but are absent from sdk_config.h

Children
No Data
Related