armlink error | developer.brewmp.com armlink error | developer.brewmp.com

Developer

armlink error

Forums:

I am getting the following error after linking with BREW. Could any body suggest how to optimize RAM?
----------------------------------------------------------------------
armlink -elf -map -info sizes,totals,veneers -list CC1M.map -symbols -symdefs CC
1M.sym -scatter 1792_512.scl -noremove -o CC1M.elf "C:\ads101\LIB"/armlib/c_t__u
n.l -VIA ~tmplib.bak -VIA ~tmpobj.bak
Error: L6221E: Execution region APP_RAM overlaps with Execution region BB_RAM.
Not enough information to produce a SYMDEFs file.
Finished: 1 information, 0 warning and 1 error messages.
----------------------------------------------------------------------------

Hi:
You shouldn't need a scatter-loading description file. Just use the simple memory map. On ADS1.2, my RO base address is 0x8000 and I've set the -rwpi and -ropi linker options (I use the CodeWarrior IDE as opposed to the command line, but the settings should still be the same). I haven't had a problem running BREW code on a phone using these settings.
As for whether this is optimal or not, I have no idea. Is there a specific reason you need to map out memory at a low level?
If you haven't already done so, I suggest you take a look at a couple of the ARM makefiles included with the examples provided in the SDK. I believe the settings used in them are specifically for ADS 1.0.1.
regards,
Murray
PS: here's the linker command line generated by codewarrior:
-remove (dbg) -map -symbols -first AEEMod_Load -rwpi -ropi

Hi:
You shouldn't need a scatter-loading description file. Just use the simple memory map. On ADS1.2, my RO base address is 0x8000 and I've set the -rwpi and -ropi linker options (I use the CodeWarrior IDE as opposed to the command line, but the settings should still be the same). I haven't had a problem running BREW code on a phone using these settings.
As for whether this is optimal or not, I have no idea. Is there a specific reason you need to map out memory at a low level?
If you haven't already done so, I suggest you take a look at a couple of the ARM makefiles included with the examples provided in the SDK. I believe the settings used in them are specifically for ADS 1.0.1.
regards,
Murray
PS: here's the linker command line generated by codewarrior:
-remove (dbg) -map -symbols -first AEEMod_Load -rwpi -ropi

Thanks for your suggestions.
The problem was that the total RAM area was exceeding our old system resources. I could build it after increasing the RAM area allocation, which is supported by new development platform.

Thanks for your suggestions.
The problem was that the total RAM area was exceeding our old system resources. I could build it after increasing the RAM area allocation, which is supported by new development platform.