issue realted to start address of hex

RE: issue realted to start address of hex

mobi — Mon, 06 Jul 2015 13:26:38 GMT

Only this get removed "Pattern RTT_Syscalls_KEIL.o(RO) only matches removed unused sections." If uncheck "Use MicroLib" option... Reset of the warnings are still there...

RE: issue realted to start address of hex

Petter Myhre — Mon, 06 Jul 2015 11:05:50 GMT

I'm not sure, but from this it seems some code as been optimized away. Does unchecking "Use MicroLIB" change anything?

RE: issue realted to start address of hex

michael — Mon, 06 Jul 2015 07:50:30 GMT

mobi, you should adjust your IRAM1 settings as mentioned by John DeWitt above. See also the documentation for the S110 Softdevice, look for the chapter "Memory resource map and usage". Further you might want to try to rename your current scatter file and let µVision regenerate it.

RE: issue realted to start address of hex

mobi — Sun, 05 Jul 2015 10:31:28 GMT

thanks... I also read that on the softdevice API specification for more clarity.

Please any help, I was able to flash hex to desired address 0x16000 after marking the option use Memory Layout from the target Layout. I also flashed the soft device. But the application is not running any more... See the edit portion of the question.

RE: issue realted to start address of hex

wlgrd — Sat, 04 Jul 2015 21:54:53 GMT

the softdevice takes care of that.

RE: issue realted to start address of hex

mobi — Sat, 04 Jul 2015 09:00:17 GMT

One more quick question based on my M0 knowledge on the same lines, since my code is at 0x16000 the vector table has to be at 0x0 of our application.so how this will work ? does softdevice has its own vector table which initates a jump to our application vector table or Noridc M0 takes care of this and automatically jumps to application start of application "0x16000" ?

RE: issue realted to start address of hex

mobi — Sat, 04 Jul 2015 08:51:39 GMT

Please see the edit in my question after using option use memory layout from Target Dialog

RE: issue realted to start address of hex

michael — Thu, 02 Jul 2015 16:00:05 GMT

I had a similiar problem long time ago. In my case the "Use Memory Layout from Target Dialog" in the Linker tab got unchecked. You might also want to check the content of your scatter (.sct) file, if it agrees with your settings.

RE: issue realted to start address of hex

John — Thu, 02 Jul 2015 13:28:07 GMT

These may not be relevant to @mobi's problem, but shouldn't the Xtal(MHz) be 16.0 and the IRAM1 settings start at 0x20002000 with a size of 0x2000 (or whatever his version of the SD leaves for the app?).

RE: issue realted to start address of hex

Petter Myhre — Thu, 02 Jul 2015 13:04:12 GMT

Are you able to flash through Keil? Could you upload the hex file so I can have a look at it?