I'm having trouble debuging the blinky example on my lpc2138 (MCB2130 board) The program is compiled from Eclipse using the arm-elf-gcc compiler with a startup.s file which comes from a blinky example for the MCB2100 board, which has a LPC2129. When debuging it seems as if the program gets stuck either around address 0x00000240 or around 0x7FFFD2A2, the first being an flash memory address and the second being the RAM boot block. It could also be the RAM.ld linker script that's causing the problem, since it's also taken from a MCB2100 blinky example. Does anyone have a startup.s and Ram.ld for the MCB2130 board for GNU? Or even better, does anyone know what's causing the problem, and how it's fixed? Best Regards Søren Hansen Mjølner Informatics A/S Denmark
Thanks for the link - I'll try that first thing. Does the ULINK and uVision use some kind of alternatet JTAG protocol for debugging the LPC2138? When I try to use the RAVEN OCDemon with OCDRemote and arm-elf-gdb, I get a lot of "SW breakpoint at 0x[address]: unable to write breakpoint: Target bus error" messages Best Regards Søren Hansen
ULINK uses the Embedded ICE to set breakpoints (when it cannot write into the memory). Reinhard