Compatibility table for nRF51422

[Nestor Matas]

Is there any compatibility table for nRF51 series chips with revisions, softdevice versions and SDK versions?

I have some custom boards with a module that contains a nRF51422 CEAA A0 (0x0031) and although I can reprogram the softdevice downloading the S310 or the S210, I have issues when trying to run ANT examples from the 5.2.0 SDK. The issues include hardfaults that occur when opening the ANT channel.

Will I be able to use softdevice 310 if I go back to SDK 4.2.2,?

I'm using Keil 5.10, SDK 5.2.0, SD310 1.0.0

[Stefan Birnir Sverrisson]

Hi

Here is the migration guide for the nRF51422. Look at table 1 in this document to realize compatibility with different softdevices and SDK's.

You will not be able to go back to older SDK version than v5.1.0 with the new flashable S310 softdevice, as stated in the table.

[Nestor Matas]

Thanks for the guide Stefan.

As far as I can see, the table says that the chip I'm using: CEAAA0 (0x0031), can only use SDK 4.x.x so that rules out the use of S310 but the table also says that I can't use S210, so, what softdevice can I use then?

When reading the chip as it comes from the factory from nRFgo Studio, it informs of having something in the region 0 with a size of 48Kb (what is compatible with the size of S210) but the firmware id is 0xffff. What version of the softdevice is that?

Thanks

[Nestor Matas]

I've tried using SDK 4.4.2 but I always get a NRF_ERROR_SVC_HANDLER_MISSING when calling sd_ant_channel_open. It happens with all the ANT examples.

To recap:

• nRF51422 CEAAA0
• SDK 4.4.2
• Softdevice unknown with a 48kb footprint and a 0xffff firmware signature

and

• nRF51422 CEAAA0
• SDK 4.4.2
• Softdevice S210 3.0.0-3.beta with 0x004b signature

Both cases I get a NRF_ERROR_SVC_HANDLER_MISSING when calling sd_ant_channel_open.

As this error is usually due to wrong version of softdevice, where can I find a previous version of the S210 to test it with every version until I find the right one? In the web site there is only the last version available.

Thanks!

[Stefan Birnir Sverrisson]

Hi

The CEAAA0 chip is preprogrammed with the S210 v2.0 and should be compatible with the nRF51422 SDK v4.4.2. Preprogrammed means that the softdevice can not be replaced or erased. In order to program a new S210/S310 softdevice, you need to get a hold of the latest version of the nRF51422, for CEAA it is the CEAAB0 chip.

Can you please confirm that the chip you are having is the CEAAA0, by reading the chip markings on the chip itself. If you can program the device it is the CEAAB0 chip, according to my cookbooks. Also, the former preprogrammed S210 softdevice had 40kB footprint while the new S210 v3.0.0 has a 48kB footprint.

It may well be possible that nRFgo Studio does not directly recognize the softdevice on the CEAA chip.

The former S210 softdevices (prior to v3.0.0) were preprogrammed in production to previous nRF51422 versions. S210 softdevices prior to version 3.0.0 were only available on the nRF51422 chip as preprogrammed.

We do not recommend to start new development with the CEAAA0 as there is currently a newer major release now available for the S210, i.e. v3.0.0.

[Nestor Matas]

I'm not able to read the markings on the chip as it comes inside a module. I will destroy it if I take apart the shielding. The nRFgo Studio says it is a CEAA A0 (0x0031) Using nrfjprog procedure I read 004B0031 at 0x1000005C, so it says it's a CEAAA0 too.

I know you don't recommend using this old chip, but it's all I have. 10 protos with this, and I'm not sure when the manufacturer will send me more with new chipsets.

What I don't understand is that if I erase the chip and download a new softdevice, nrfgo studio will tell me that the new sd is actually the one i've downloaded. If it is a CEAAA0 that shouldn't be possible, right?