How to identify SDK version?

RE: How to identify SDK version?

awneil — Mon, 13 Apr 2015 09:27:54 GMT

"I will convey this feedback internally"

What was the outcome?

RE: How to identify SDK version?

awneil — Mon, 13 Apr 2015 09:27:20 GMT

"Identifying the SDK could be accomplished if Nordic were to include something like SDK_ID.h that defined some constants like a version string and also some binary #defines for the maj.min.rev codes"

Yes - that would be great!

RE: How to identify SDK version?

Balaji Srinivasan — Tue, 13 May 2014 06:56:12 GMT

Dan and Gerry,

I will convey this feedback internally. Thank you for your suggestion. :-)

Cheers, Balaji

RE: How to identify SDK version?

Gerry Ortoli — Tue, 13 May 2014 06:46:53 GMT

Balaji:

Thanks for the quick response.

Best, Gerry

RE: How to identify SDK version?

Dan Danknick — Tue, 13 May 2014 04:29:48 GMT

There is certainly a way to identify the SoftDevice loaded into the chip. nRFgo Studio reads some address and, for example, reports that value 0x0049 is the signature for the S110_nRF51822_6.0.0 SoftDevice. I do not know what address this is.

There is also a hardware ID located somewhere that uniquely identifies the silicon - nWP-018 discloses a number of codes in Table 1.

Identifying the SDK could be accomplished if Nordic were to include something like SDK_ID.h that defined some constants like a version string and also some binary #defines for the maj.min.rev codes. If you added it you could at least grep the version string in the binary.

I think these are development related issues but still, shaving days and making things easier for the devs is always a good thing.

Dan

RE: How to identify SDK version?

Balaji Srinivasan — Mon, 12 May 2014 10:34:14 GMT

Hi there,

@. It seems to run OK but I'm uncomfortable with that difference.

Did you also compare the .uvproj files? It could be that the compiler/linker options are different.

@Do the hex or axf files contain an SDK "signature"?

Unfortunately, there is no way to find out the SDK version from the axf file,

@I believe that the Keil & J-Link software versions are not as important. Are these good assumptions or should I be looking at those differences as well?

Keil version is also important. A different compiler (in this case armcc) version may or may not have an impact on the final hex file. The J-Link software versions are not important.

Cheers, Balaji