Migration to SDK 8.1 from SDK 6.1 File Structure Issues

[Dave_couling]

Hi all,

Due to the updates file structure introduces in SDK 7.0 I'm trying to figure our where everything has been scrambled to. Here are the items I'm struggling with

1. The SDK is only tested with nRF51422 as evident with nrf51422_xxac_s110 mentioned in the example Makefiles. Can I simply overwrite these to nRF51822_xxaa_s110?

2. Do I have to used the new Advertising module? I had developed my own on SDK 6.1. Was hoping to port it over, but want to make sure there are no underlying reliance on this module/issues.

3. Is the new project based nrf_drv_config.h used to set each individual peripheral setting? I ask because my board has a 32MHz crystal which I normal setup the settings for with: NRF_CLOCK->XTALFREQ &= 0xFFFFFF00;

However if this is now supposed to be set in nrf_drv_config.h?

5. There are alot more compiler and softdevice files integrated into this SDK. I'm using Eclipse to simply compile my application and flash/debug it separately from the SoftDevice is that still possible? Does this new CMSIS affect this?

[Hung Bui]

Hi Dave,

1. Yes, because there is no difference between nRF51422 and nRF51822 when you use them with Bluetooth stack.

2. No, you don't have to. The SDK is created as reference code. You can choose to not to use any module. Just to make sure you update the API header files of the new S110 v8.0 and match the API call in your code with any new API introduced.

3. Yes, you can set it in nrf_drv_config.h, but then you would need to use the clock driver, and call nrf_drv_clock_init(). I would suggest if you don't plan to use any other feature of the clock driver, you can simply keep your code to just calling NRF_CLOCK->XTALFREQ &= 0xFFFFFF00; to set the clock.

4. The softdevice is pre-compiled. I don't see any problem that you compile your code using Eclipse.

[Dave_couling]

I've tried simply getting the example gcc projects to compiler, however they all return the following error:

make: *** [all] Error 2

I'm so confused as all my toolchains work fine with SDK6.1. Has anyone been able to migrate to SDK8.1 and found this error?