eclipse + yagarto + openocd + amontec jtag tiny+lpc2368 prob

Hi to all, as suggest to me by tcomins I insert this line in the open ocd cmd file:

flash bank lpc2000 0x00000000 0x20000 0 0 0 lpc2000_v2 14746 calc_checksum

and then i insert this lines in the gdb commmand tad inside eclipse:

target remote localhost:3333

monitor reset halt

monitor sleep 500

monitor poll

monitor soft_reset_halt

load

break main

continue

info breakpoints

but I’m not able to enter in debug mode, and these are messages present in the eclipse console tab:

target remote localhost:3333

0x7fffe13e in ?? ()

monitor reset halt

JTAG tap: lpc2368.cpu tap/device found: 0x4f1f0f0f (Manufacturer: 0x787, Part: 0xf1f0, Version: 0x4)

srst pulls trst - can not reset into halted mode. Issuing halt after reset.

target state: halted

target halted in Thumb state due to debug-request, current mode: Supervisor

cpsr: 0xa00000f3 pc: 0x7fffe140

monitor sleep 500

monitor poll

target state: halted

target halted in Thumb state due to debug-request, current mode: Supervisor

cpsr: 0xa00000f3 pc: 0x7fffe140

monitor soft_reset_halt

requesting target halt and executing a soft reset

target state: halted

target halted in ARM state due to debug-request, current mode: Supervisor

cpsr: 0xa00000d3 pc: 0x00000000

load

Loading section prog, size 0x27a37 lma 0x2a4

Ignoring packet error, continuing…

Ignoring packet error, continuing…

Loading section .data, size 0x220 lma 0x27cdc

Ignoring packet error, continuing…

Error erasing flash with vFlashErase packet

Breakpoint 1 at 0x534: file main.c, line 121.

break main

Note: automatically using hardware breakpoints for read-only addresses.

continue

Warning:

Cannot insert hardware breakpoint 1.

Could not insert hardware breakpoints:

You may have requested too many hardware breakpoints/watchpoints.

Num Type Disp Enb Address What

1 breakpoint keep y 0x00000534 in main at main.c:121

info breakpoints

Cannot access memory at address 0x7fffe142

WHAT IS WRONG?

THNKS

Hi,

No solution yet but I’m having a similar problem using:

eclipse

yagarto

openocd

olimex jtag usb tiny

olimex lpc-e2468

The “command tab inside eclipse” for me holds the following:

target remote localhost:3333
monitor reset init
monitor sleep 500
#monitor poll
monitor soft_reset_halt
monitor mww 0xE01FC040 0x0002
monitor mdw 0xE01FC040

# needed for gdb 6.8 and higher
set mem inaccessible-by-default off

load
break main
continue

With the corresponding console output when I’m trying to enter debug mode:

JTAG tap: lpc2294.cpu tap/device found: 0x4f1f0f0f (Manufacturer: 0x787, Part: 0xf1f0, Version: 0x4)
JTAG Tap/device matched
srst pulls trst - can not reset into halted mode. Issuing halt after reset.
target state: halted
target halted in ARM state due to debug-request, current mode: System
cpsr: 0x000000df pc: 0x00000208
requesting target halt and executing a soft reset
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0x00000000
1500 kHz
monitor sleep 500
monitor soft_reset_halt
requesting target halt and executing a soft reset
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0x00000000
monitor mww 0xE01FC040 0x0002
monitor mdw 0xE01FC040
0xe01fc040: 00000002 
set mem inaccessible-by-default off
load
Error erasing flash with vFlashErase packet
break main
Breakpoint 1 at 0x1e2: file main.c, line 98.
continue
Note: automatically using hardware breakpoints for read-only addresses.
Warning:
Cannot insert hardware breakpoint 1.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.

I think it might be something to do with my openocd configuration (which I basically copied from a different project). Something to do with the following line, perhaps:

flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v2 0 4000 calc_checksum

I’m not sure, I’m new to ARM programming.

Any help is greatly appreciated, and I’ll report in as I continue working on it.

PS - I should add that after this point eclipse says that it “cannot execute due to errors” and the console repeats the message about breakpoints, ad nauseum.