Lpc2000

Hmm...so I guess no one's willing to help me out here :)
Anyway I did a little googling and came across some threads saying
something about loading a flash programming script into the RAM first
and then loading the image you want to execute...so I'm still puzzled,
why does the image (axf) generated using ADS with Keil uVision3 work
with AXD?


--- In lpc2000@...m, "Shahzeb Ihsan" <snakeskin172@...> wrote:
>
> Hi,
> 
> I compiled a small example using ADS compilers with Keil uVision3 for
> LPC2148, set to be downloaded into the flash and debugged from there.
> The compiled *.axf image ran fine with ULINK. Also when I loaded this
> image into AXD, it ran fine (with OpenICE32 A900), as long as I gave
> it the correct path to the source files.
> 
> So, I decided to take the source files and combine them into an ARM
> Developer Suite (CodeWarrior) project. But even when I used the same
> RO/RW base and entry point settings as in Keil for ADS, I couldn't get
> the image to run. Debugging the firmware from the RAM was a breeze,
> but I can't seem to get the right assembler/compiler/linker settings
> for debugging it from the flash.
> 
> Even though in both cases (uVision3 and CodeWarrior) the same compiler
> was used - the *axf file generated using uVision3 runs fine with AXD,
> but the one generated using CodeWarrior doesn't. Any help would be
> appreciated.
> 
> The following settings were used for different modes:
> 
> Debugging from RAM:
> RO base:     0x40000000
> RW base:     0x40000700
> Entry Point: 0x40000000
> 
> Debugging from FLASH:
> RO base:     0x00000000
> RW base:     0x40000000
> Entry Point: 0x00000000
> 
> Regards
> --Shahzeb
>