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?

[jev]

The pin settings NRF_SPI_DRV_MISO_PULLUP_CFG for SPI are not part of the sdk_config.h as available in this master configuration file. Neither is NRF_BLE_GATT_ENABLED. The log macro's for NRF_SORTLIST_* are missing. Just to name a few, I didn't check everything.

A closely related request: would it be possible to update the examples to use sdk_config files directly derived from the delivered master copy?

The reason for this request is that it would enable a simple diff between master- and example sdk_config.h to provide a quick overview of the modifications done to get the example up and running. Makes it so much easier to re-use the illustrated functionality!

Just to illustrate the problem I ran into... I wrote a small diff tool that checks differences based on identifiers (a tool like winmerge finds 391 different blocks with changes in it).

My tool found 617 differences, 606 symbols are missing from the sdk_config.h in blinky (examples/peripheral/blinky/pca10040/blank/config), 4 are not in the master at all and only 7 have actually been changed from the default. Note that this tool was written in a couple of hours and thus may contain bugs, but the ones I checked seem to confirm said figures.

Please note, I'm not here to sound all negative and such. It's great to have an SDK as complete as this that is actually useful and you guys are doing a terrific job helping us where necessary!