noinit section of RAM not working after SDK16 update

RE: noinit section of RAM not working after SDK16 update

Vidar Berg — Wed, 11 May 2022 09:19:23 GMT

Thanks for the update. Yes, the stack grows down and it usually starts at the top of RAM (i.e. 0x20004000 if using the 52832).

I'm afraid I don't have an explanation as to why you didn't experience the issue with SDK15.2.0. You may compare the *.map file from the bootloader builds and see if the STACK area is covering the same address range in both versions.

RE: noinit section of RAM not working after SDK16 update

JasonGeo — Wed, 11 May 2022 09:09:34 GMT

Thanks Vidar, that's indeed the problem!

But I do not understand why does it work with SDK15.2 previously without having to reduce the size of the RAM section in bootloader ld file?

Also does the call stack always starts at the highest address in the allocated RAM section and goes down?

RE: noinit section of RAM not working after SDK16 update

Vidar Berg — Wed, 11 May 2022 06:12:30 GMT

Hello,

The bootloader call stack appears to overlap with your noninit section in the application. Maybe you forgot to reduce the size of the RAM section when you updated to the new SDK?

RAM (rwx) : ORIGIN = 0x200057b8, LENGTH = 0x3a848 - 0x40

Edit: Forgot to add that there weren't any relevant between version 16 and 17. At least, none that I can think of.

RE: noinit section of RAM not working after SDK16 update

JasonGeo — Wed, 11 May 2022 05:27:28 GMT

I also verified from the map file that the memory is allocated for the noinit section variable.