SDK vs SoftDevice compatibility

RE: SDK vs SoftDevice compatibility

awneil — Mon, 13 Apr 2015 09:31:11 GMT

" I find the easiest way is to copy all custom code from your application into an example project in the new SDK"

Yes; that looks like the way to go.

Thanks.

RE: SDK vs SoftDevice compatibility

Stefan Birnir Sverrisson — Mon, 13 Apr 2015 07:34:18 GMT

There is not documentation on how to port an application from one major SDK version to another. By major SDK version I mean from e.g. SDK 5.x.x to SDK 6.x.x or from SDK 6.x.x to SDK 7.x.x. I find the easiest way is to copy all custom code from your application into an example project in the new SDK, i.e. SDK 7.2.0 in your case.

You can see what has changed in the new SDK version by looking at the SDK release notes

RE: SDK vs SoftDevice compatibility

awneil — Wed, 08 Apr 2015 15:19:46 GMT

None of those documents says anything at all about taking an existing Keil project and updating it to use a newer SDK version.

Is it possible?

Is it documented anywhere?

Might I just as well start again from scratch with a "clean" new Project for the new SDK?

RE: SDK vs SoftDevice compatibility

Stefan Birnir Sverrisson — Tue, 07 Apr 2015 11:55:19 GMT

use the nRF51_SDK_7.2.0_cf547b5.zip. You can unzip it wherever you like. All project files in the SDK have relative path to files within the zip file.

RE: SDK vs SoftDevice compatibility

awneil — Tue, 07 Apr 2015 11:39:47 GMT

There are two zip files: nRF51_SDK_7.2.0_cf547b5.zip; nRF51_SDK_7.2.0_cf547b5_packs.zip

Do I use both?

To where should they be unzipped?

RE: SDK vs SoftDevice compatibility

Stefan Birnir Sverrisson — Tue, 07 Apr 2015 11:05:20 GMT

I guess the migration guide is referring to the migration document inside the softdevice zip file that you download from the website.

I find the safest way to go between SDK's is to use the SDK zip file without msi file installation. From SDK 7, the msi installation file is not available anyway.

RE: SDK vs SoftDevice compatibility

awneil — Tue, 07 Apr 2015 10:25:40 GMT

The Migration Guide refers to an "S310 migration document" and says, "This is available in the (sic) SoftDevice folder" - but which "SoftDevice folder" is that?

The Migration Guide doesn't mention if any special precautions are needed to ensure that installing the new SDK doesn't interfere with an older SDK installation.

RE: SDK vs SoftDevice compatibility

awneil — Tue, 07 Apr 2015 08:23:47 GMT

And any help on the associated question of how to update an existing project to new SDK & SoftDevice versions...?

RE: SDK vs SoftDevice compatibility

awneil — Tue, 07 Apr 2015 08:04:39 GMT

Ah, OK - that link is under 51822, but the document does cover both 51822 & 51422.

So, if I'm reading that correctly, the v2 SoftDevice is not compatible with SDK v8.

I would need SDK v7.2.0 and SoftDevice v2.0.1.

And none of this is going to work on my EK kits (PCA10001/3) - I am going to have to replace them with an nRF51-DK Development Kit?

RE: SDK vs SoftDevice compatibility

awneil — Tue, 07 Apr 2015 07:52:13 GMT

That's for nRF51822 - where is the equivalent for nRF51422 ?

RE: SDK vs SoftDevice compatibility

Stefan Birnir Sverrisson — Tue, 07 Apr 2015 07:39:43 GMT

To see compatibility of different things, check the nRF51 compatibility matrix.

Update 7.4.2015 More detailed information for nRF51422 is in the PCN-093 v1.1 document, page 3. For migration from rev2 to rev3, look at the nRF51422 migration document nWP-022.

To use a new SDK with older boards should work fine, and we provide documentation for how to do that. This thread also shows where exactly to change the compiler define in Keil.

What the nRF51 compatibility matrix contains is the components that have be tested together by Nordic and that is what we recommend to customers to go into production with. If you use components that are outside the compatibility matrix, you would need to perform more extensive testing on your own.