combining sdk_config.h files with CMSIS

[Bret Foreman]

I want to combine code that uses both the libuarte library and the spi library.

When I look at the sdk_config.h file of the libuart example with CMSIS, I see this:

When I look at the sdk_config.h file of the SPI example with CMSIS, I see this:

Note that the SPI example has an entire "Application" branch of settings that is not contained in the libuarte example. 

You might imagine that the SPI example is a superset of the libuarte example, but that's not the case. There are many settings in the sdk_config.h for the libuarte example that don't exist in the SPI example.

How do I use CMSIS to "drag" the settings I need from one project to another such that I can combine the functionality of the two examples?

[Kenneth]

Hello,

You will unfortunately have to open the sdk_config.h in a text editor, and copy and paste from one file to the other. The sdk_config.h should be pretty human readable, but I can admit it's not ideal. If you were to switch to the nRF Connect SDK you would avoid this kind of problems.

Kenneth

[Bret Foreman]

I'll try it with the nRF Connect SDK. The problem with that SDK is that the hex file loader doesn't work with my PCA10040 DK board. You have to use the command line tool to flash the board each time you change anything.

[Bret Foreman]

BTW, I've tried to edit the sdk_config.h file and that doesn't work. There are a bunch of CMSIS flags in the comments of the file and there's no document that describes what those flags do. In my experience, editing the file in any way breaks the CMSIS parser and there's no way to fix it.