This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Maybe a few couple SDK bug reports

I'm looking at the 5.2 SDK and I have noticed a few minor things that may be bugs or might be my mistake but here goes:

  1. In the GCC linker scripts, I was carefully reviewing what changed from the last SDK. Most of the changes were standardizing the format from decimal to their equivalent hecadecimal. For example "Length = 208K" was replaced with "Length = 0x34000" which is mathematically identical. However one caught my eye as not being identical. In "gcc_nrf51_s210_xxaa.ld" line 49, RAM length was changed from 13K to 0x3700 which is not mathematically equivalent. That may have been intentional but all the other changes I checked were replacing decimal notation with equivalent hex.

  2. The GCC linker scripts lack the linker scripts for S310 soft device. Trivial to make your own but should probably be part of SDK.

Parents
  • Hi David,

    You're right. However, the linker script given with SDK v5.1.0 has a bug, where it was not updated to the latest S210 release (the binary downloadable from our site). The linker script is now updated with origin 0x20000900, length 0x3700, which adds up to 0x20004000 (16kB RAM)

    1. Yes, I will input a feature request on this. We're still not 100% GCC compatible, but it is in the SDK teams back log.

    Best regards Håkon

Reply
  • Hi David,

    You're right. However, the linker script given with SDK v5.1.0 has a bug, where it was not updated to the latest S210 release (the binary downloadable from our site). The linker script is now updated with origin 0x20000900, length 0x3700, which adds up to 0x20004000 (16kB RAM)

    1. Yes, I will input a feature request on this. We're still not 100% GCC compatible, but it is in the SDK teams back log.

    Best regards Håkon

Children
No Data
Related