• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 91 subscribers
  • Views 674 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 285484
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to upgrade sdk_config.h from SDK16.0.0 to SDK17.1.0?

TilakL

Hej!

Upgrading from SDK16.0.0 to SDK17.1.0,concerning sdk_config.h in my application: I worry that some new options could have been introduced while some old ones might have been depreciated or removed. I have not come across any documentation for these changes in the sdk_config.h. Is it safe to assume there are no changes in sdk_config.h going from SDK16.0.0 to SDK17.1.0?

Moreover, executing CMSIS_CONFIG_TOOL := $(SDK_ROOT)/external_tools/cmsisconfig/CMSIS_Configuration_Wizard.jar
gives an error for my application sdk_config.h: "Unable to parse file: java.lang.NullPointerException". While I view and edit the bootloader's sdk_config.h without any errors. Is parsing error a cause of worry even though my application compiles.

Also, in this link: infocenter.nordicsemi.com/.../sdk_config.html
what does "Keeping the full configuration file should be helpful when migrating to new SDK versions." mean?

How should one go about upgrading the sdk_config.h for my application?

Thanks,
Tilak

  • +1

    Hi Tilak, 

    We have a migration guide here that you can follow. It's not a very big change from SDK v16.0 to SDK v17.0.2 (and to SDK v17.1) as far as I can see.

    Regarding the sdk_config.h, I am not aware of any modification needed. Did you base your application on an example ? If you do I would suggest to do a comparison between the sdk_config.h in SDK v16 and SDK v17 of the same example. From that you know what you need to add to your own sdk_config.h. I usually use the Compare tool in Notepadd++ application for the purpose. 

    For example here is some of the changes I can find when doing comparison in Notepad++: 


    I have seen the issue "sdk_config.h: "Unable to parse file" before it's usually due to invalid syntax in the sdk_config.h file, or sometime with a wrong end of line symbol. If you do a compare (to the example you based your sdk_config.h on )you can also find where the potential bug is. 

    Regarding the  "Keeping the full configuration file should be helpful when migrating to new SDK versions." , my understanding is that if you keep the full configuration file, then when we migrate to new SDK you can use the same full sdk_config.h on the new SDK with minimum change. And even if there is any change , you can easily modify it if it's based on the same full sdk_config.h that we included in most of our examples via the compare tool. 

  • 0

    Thank you very much Hung Bui, Your suggestion is clear and seems to be the only way to go. BTW, my application's SDK appears to have grown to 11k lines (with comments). Thanks

Related
Terms of service