How to query SD140 version from application code?

RE: How to query SD140 version from application code?

Simonr — Thu, 10 Oct 2019 07:43:18 GMT

What Keith is saying is correct, you'll have to read the FWID and "translate" it into the SoftDevice version they represent, this is done in the nRFConnect for desktop Programmer app, whereupon SoftDevice detection, it prints the FWID and SoftDevice version, I.E "SoftDevice detected, id 0x87 (S130 v2.0.1)". I'm not 100% sure, but I think you should be able to find the source code for this here.

Best regards,

Simon

RE: How to query SD140 version from application code?

Keith Brafford — Wed, 09 Oct 2019 23:14:04 GMT

It looks like we need to do it ourselves. The original answer did suggest this strategy. This is pretty lame, but I guess it saves them bytes?

The list of what firmware ID maps to which softdevice version is not public. What you can do however, is to flash all the different versions of softdevices that are possible to reside on your chips and see what firmware ID those return and you can obtain the mapping yourself

...also...

About a year ago we started printing the FWID in the SoftDevice release notes. In SDK 15 you will find those in <sdk folder>/components/softdevice/<sxxx>/doc/, where <sxxx> is the particular SoftDevice (e.g. s132, s140, etc.)

RE: How to query SD140 version from application code?

t_prachar — Wed, 09 Oct 2019 23:02:56 GMT

My question isn't how to get the magic byte, but rather how to identify *which* version is running. The answer would be in the form such as 6.0.0 which is how Nordic publishes the versions and names the hex files. I don't see any hex file published by Nordic named SD140_0xA9.

RE: How to query SD140 version from application code?

Keith Brafford — Wed, 09 Oct 2019 22:56:42 GMT

It looks like you can use nrfjprog to read memory (the "memrd" option) at location 0x0000300C and look for the value 0xA9

nrfjprog --family NRF52 --memrd 0x0000300C

https://devzone.nordicsemi.com/f/nordic-q-a/1171/how-do-i-access-softdevice-version-string

So from your application code I suspect you can do something like this:

#define SD140_VAL_600 0xA9
#define SD132_VAL_601 0xB7

int verify_sd_is_good(uint8_t sd_sanity_value)
{
  uint32_t *addr_loc = 0x0000300C;

  return ((*addr_loc) & 0x000000FF) == sd_sanity_value;
}