Hi I am trying to debug my code (size 0~0x20000) which is located in DDR memory. The ESRAM is much too small for it.
Below is the scatter file I am using to link it all together. The system startup code is located in eNVM (address 0) using ESRAM for its stack.
My main will be in the DDR which starts at 0xA0000000. I put the heap and all other data structures in there too. The map looks correct to me.
The problems I am having are:
1) When using uVision ULINK2, I click on load and I immediately get a "error 129: MapMem - map size truncated to 128MB" yet it continues to load the software into what I hope is eNVM and DDR
So I do not know what this error is trying to tell me.
2) After the load completes, I click on Start Debug Session and it gets to about 19% and then hangs up.
I have been able to debug my bootloader code (which is smaller) using both eNVM and DDR already so I know it will work. My main code is much bigger, obviously, but outside of that I don't understand why the uVision/ULINK2 is hanging up.
I would really appreciate any help or ideas you might have on what might be wrong
Steve
LR_IROM1 0x00000000 0x40000 { ; load region size_region ER_RO 0x00000000 0x40000 ; load address = execution address { *.o (RESET, +First) *(InRoot$$Sections) startup_m2sxxx.o (+RO) system_m2sxxx.o (+RO) sys_config.o (+RO) low_level_init.o (+RO) } RAM_EXEC 0xA0000000 0x30000 { * (+RO) }
STACKS 0x20000000 UNINIT { startup_m2sxxx.o (STACK) }
; MDDR_RAM 0xA0000000 0x1FFFFFFF ER_RW 0xA0030000 0x1FFFFFFF { * (+RW +ZI) * (HEAP) } }
I just wanted to add one more piece of information. Right now I am trying to load the software onto the smartfusion2 development kit board. It has plenty of DDR on board as well as the Cortex M3 ARM processor we are using.
The real hardware is still fabrication.
I noticed that the formatting of the scatter file is messed up. Here is is in a more readable form:
FLASH_LOAD 0x00000000 0x00080000 { ; load region size_region
ER_RO 0x00000000 0x80000 ; load address = execution address
{
*.o (RESET, +First)
*(InRoot$$Sections)
startup_m2sxxx.o (+RO)
system_m2sxxx.o (+RO)
sys_config.o (+RO)
low_level_init.o (+RO)
retarget.o (+RO)
}
ER_RW 0x20000000 0x8000
system_m2sxxx.o (.data)
retarget.o (.data)
retarget.o (.bss)
* (+RW +ZI)
STACKS 0x20001000 UNINIT
startup_m2sxxx.o (STACK)
; MDDR_RAM 0xA0000000 0x20000000
ER_DDR 0xA0000000 0x20000000 ; RW data DDR
* (+RO)
* (HEAP)
Observe the "Tips for Posting Messages" and the use of the PRE tags
Ok thank you. I will review it for next time
I have seen my question about error 129 asked many times in this forum as well as a few other places and not once was there a response to this issue which is disappointing. So I cannot get any clues from other people's responses because there have not been any.
I really need your help in trying to figure this out. I cannot debug any of my code if I cannot get it loaded with ulink2.
One additional piece of information that may be important is that the start up code is in C and the main code is C++. C++ uses a lot more ram
"C++ uses a lot more ram"
That depends on your use of STL and similar and your coding style.
The language itself doesn't really have much difference in amount of RAM needed.
I agree. I just thought that it might have some bearing on this issue since I have absolutely no idea what is causing it.
do you know what this error 129 means? This is day 3 I have been working on this and cannot figure out what is causing it.
There is little information out there about this.
You need to ask Keil, but it sounds like the Keil tools can't support more than 128MB of memory (maybe they keep some bitmap) and you seem to have 1GB of RAM.