if it works on a LPC2106 then it's got to work on the LPC2124, too.
I have no idea what Eclipse does while that "launching" progress bar runs -
that's one of the reasons why I don't use it, it hides what's
happening.
What you could try to check:
- Jumper settings. If P0.14 is low then the LPC is going to enter bootloader
mode, and your application wont be started
- Try without Eclipse. Use the telnet interface at first, to verify
everything's working as expected. If your application doesn't operate
properly (like no LED blinking), issue a "halt", and see what PC is reported,
the current mode the uC is in and so on. You can display all ARM registers
using the "armv4_5 reg" command. There's even a disassembler available
using
the "armv4_5 disassemble " command.
Regards,
Dominic
On Wednesday 16 May 2007 00:51:35 Richard wrote: > I finally have Open OCD (Running through eclipse)
functioning on an
> IAR Kickstart board (LPC2106). Yea!
>
> I am unable to get it to run on a Keil board, the MCB2100 (LPC2124).
>
> The debugger APPEARS to program the micro but then it just hangs while
> the "launching" progress bar runs, forever.
>
> The console output when I start the debugger:
>
> (gdb) target state: halted
> target halted in ARM state due to debug request, current mode: Abort
> cpsr: 0x600000d7 pc: 0x000002ec
> flash 'lpc2000' found at 0x00000000
> erased sectors 0 through 0 on flash bank 0 in 0s 641043us
> wrote file main.bin to flash bank 0 at offset 0x00000000 in 0s 656678us
> requesting target halt and executing a soft reset
> force hardware breakpoints enabled
>
> *********************************
> *****The CFG file I am using:****
> *********************************
>
> #daemon configuration
> telnet_port 4444
> gdb_port 3333
>
> #interface
> interface ft2232
> ft2232_device_desc "Olimex OpenOCD JTAG A"
> ft2232_layout "olimex-jtag"
> ft2232_vid_pid 0x15BA 0x0003
> jtag_speed 10
>
> #use combined on interfaces or targets that can't set TRST/SRST
separately
> reset_config trst_and_srst separate
>
> #jtag scan chain
> #format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
> jtag_device 4 0x1 0xf 0xe
>
> #target configuration
> daemon_startup reset
>
> #target
> #target arm7tdmi
> target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4
> run_and_halt_time 0 30
>
> #target_script 0 reset oocd_flash2138.script
> working_area 0 0x40000000 0x40000 nobackup
>
> #flash configuration
> flash bank lpc2000 0x0 0x40000 0 0 lpc2000_v1 0 14765 calc_checksum
>
> # For more information about the configuration files, take a look at:
> # http://openfacts.berlios.de/index-en.phtml?title=Open+On-Chip+Debugger
> Thanks for the help
>
> Rich
--- In l..., "Richard" wrote: >
> I finally have Open OCD (Running through eclipse) functioning on an
> IAR Kickstart board (LPC2106). Yea!
>
> I am unable to get it to run on a Keil board, the MCB2100 (LPC2124).
>
> The debugger APPEARS to program the micro but then it just hangs while
> the "launching" progress bar runs, forever.
I fear you've got the same problem with Eclipse that I have (see
Message #24330, though with JVM 1.6 the reported error code is
different). I have got no responses so far.
Also, asking more detailed in the Eclipse support newsgroups, I also
got no responses.
It seems to me that the combination Eclipse/CDT/GDB/OpenOCD is really
unstable. Here, it very often hangs when uploading the application
code to the target. I often have to shutdown and restart eclipse
several times (!) before it finally enters debug mode correctly.
I didn't yet find out how to trace this error, and noone else seemed
to know something about it yet, at least I couldn't find anything
related and I got no responses to my questions. I wonder if it's
possible to do serious software development with such unstable tools
at all.
Problem is, that since it's a combination of various different tools,
it's hard to find out which one is misbehaving, or at which interface
the problems occur/begin.
Tilmann
Reply by Richard●May 15, 20072007-05-15
I finally have Open OCD (Running through eclipse) functioning on an
IAR Kickstart board (LPC2106). Yea!
I am unable to get it to run on a Keil board, the MCB2100 (LPC2124).
The debugger APPEARS to program the micro but then it just hangs while
the "launching" progress bar runs, forever.
The console output when I start the debugger:
(gdb) target state: halted
target halted in ARM state due to debug request, current mode: Abort
cpsr: 0x600000d7 pc: 0x000002ec
flash 'lpc2000' found at 0x00000000
erased sectors 0 through 0 on flash bank 0 in 0s 641043us
wrote file main.bin to flash bank 0 at offset 0x00000000 in 0s 656678us
requesting target halt and executing a soft reset
force hardware breakpoints enabled
*********************************
*****The CFG file I am using:****
*********************************
