Memory warnings in SES v3.24

RE: Memory warnings in SES v3.24

RichieJH — Mon, 24 Jul 2017 09:42:06 GMT

Thanks as always RK

RE: Memory warnings in SES v3.24

RK — Mon, 24 Jul 2017 05:49:30 GMT

I'm sure it's picking up the memory map, 200525f8 is just the start of SRAM (and it seems wrong because the start of RAM is 20000000). The actual place used to put the code is usually passed in via a macro (as you have now done).

The memory map defines the layout of the chip to build the linker file and should represent the actual layout of the chip, other macros control where you actually place the start of sections.

RE: Memory warnings in SES v3.24

RichieJH — Mon, 24 Jul 2017 05:20:06 GMT

OK, so I seem to be passing in 0x20002ffa8. I then set a Section Placement Macro of 0x200025f8 which gets rid of the message. But how is SES picking up the wrong RAM? How can I double check that SES is accepting the Memory Map (I do select use this Memory Map in SES)?

RE: Memory warnings in SES v3.24

RK — Sun, 23 Jul 2017 22:52:51 GMT

SES isn't suggesting anything, this has nothing to do with the IDE at all. What you're seeing is the warnings built into the SDK which check RAM set against RAM actually required on enable and print out any differences.

So go put a debug in there and find out what you're actually sending in, what it's actually returning and then work out what SES setting needs to be changed. It's in the softdevice enable code somewhere, should take all of 10 seconds to find.