Hello Kevin,

I am using openocd debugger with an lpc2468 in an olimex board to.

I am using the openocd release 0.1.0 now, but for some time i was
using the trunk. I have some strange behaviors too. Some times after
flashing a program I can not get more access over the jtag if I made a
hardware reset or a "monitor reset" but until then works. After a
reset or a "monitor reset" command I can not get more contact and I
get the error:

arn : Tap/Device does not have IDCODE
Error: JTAG tap: lpc2468.cpu             got: 0x00000000 (mfg: 0x000,
part: 0x0000, ver: 0x0)
Error: JTAG tap: lpc2468.cpu expected 1 of 1: 0x4f1f0f0f (mfg: 0x787,
part: 0xf1f0, ver: 0x4)
Error: trying to validate configured JTAG chain anyway...
Error: unknown EmbeddedICE version (comms ctrl: 0x00000070)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Warn : DBGACK set while target was in unknown state. Reset or initialize target.
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Warn : DBGACK set while target was in unknown state. Reset or initialize target.
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure

and so one, the last 3 lines are repeted every x time again and again.

Every time that I have this problem I flash back a start example using
the serial interface and lpc21isp-1.64 software or flash manager from
windows to load an other software and then i can use the debugger
again.

I have no idea where is the problem, but I am sure is not a problem
regarding security flag of the lpc since the value on the position
0x1fc (i dont remember if this or which posistion) but is not
protected. So is an other issue.

I am using the cfg file attached to the mail.

Best Regards,
Mariano.-

On Fri, Mar 13, 2009 at 1:31 PM, Kevin Townsend <[email protected]> wrote:
> I was able to make some progress on this, but I'm sure there are some major
> problems with the configuration (it seems a lot has changed since I made the
> previous configuration file for build 717!)
>
> I'm a bit lost, though, why the board can not reset (it times out, see below),
> and the command "arm7_9 force_hw_bkpts enable" is in the documentation as 
> valid,
> so I don't really understand why it's throwing an exception.
>
> For reference sake, here is the output when I start the debugging process.  
> I'll
> include my config files afterwards:
>
> ______________________________________________________________________
> OUTPUT
> ______________________________________________________________________
>
> source .gdbinit
> target remote 127.0.0.1:3333
> Load$$ER_FLASH$$Base () at
> E:\MicroFrameworkPK_v3_0\DeviceCode\cores rm\AssemblyCode 
> rm\GNU_S\FirstEntry.s:102
> 102         msr     cpsr_c, #PSR_MODE_SYSTEM    @ go into System mode, 
> interrupts
> off
> Current language:  auto; currently asm
> monitor reset
> JTAG tap: lpc2478.cpu tap/device found: 0x4f1f0f0f (Manufacturer: 0x787, Part:
> 0xf1f0, Version: 0x4)
> JTAG Tap/device matched
>
> monitor sleep 500
>
> monitor poll
> target state: running
>
> monitor soft_reset_halt
> requesting target halt and executing a soft reset
> Failed to halt CPU after 1 sec
>
> monitor arm7_9 force_hw_bkpts enable
> invalid command name "arm7_9_force_hw_bkpts"
> called at file "command.c", line 456
> called at file "embedded:startup.tcl", line 89
> called at file "embedded:startup.tcl", line 93
> break PreStackEntry
> Breakpoint 1 at 0x4: file
> E:\MicroFrameworkPK_v3_0\DeviceCode\cores rm\AssemblyCode 
> rm\GNU_S\FirstEntry.s,
> line 110.
> load
> Load failed
> 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.
>
> ______________________________________________________________________
>
> Config Settings
> ______________________________________________________________________
>
> #ARM-USB-OCD
>
> #interface
> interface ft2232
> ft2232_device_desc "Olimex OpenOCD JTAG A"
> ft2232_layout olimex-jtag
> ft2232_vid_pid 0x15ba 0x0003
>
> -----------------------------------
>
> #LPC2478
>
> if { [info exists CHIPNAME] } {
>   set  _CHIPNAME $CHIPNAME
> } else {
>   set  _CHIPNAME lpc2478
> }
>
> if { [info exists ENDIAN] } {
>   set  _ENDIAN $ENDIAN
> } else {
>   set  _ENDIAN little
> }
>
> if { [info exists CPUTAPID ] } {
>   set _CPUTAPID $CPUTAPID
> } else {
>  # force an error till we get a good number
>   #set _CPUTAPID 0xffffffff
>   set _CPUTAPID 0x4f1f0f0f
> }
>
> #daemon configuration
> telnet_port 4444
> gdb_port 3333
> tcl_port 6666
>
> # GDB can also flash my flash
> gdb_memory_map enable
> gdb_flash_program enable
>
> #jtag speed (this may need to be adjusted to get openocd to work)
> jtag_speed 3
>
> #delays on reset lines
> jtag_nsrst_delay 200
> jtag_ntrst_delay 200
>
> #use combined on interfaces or targets that can't set TRST/SRST separately
> reset_config trst_and_srst srst_pulls_trst
>
> #jtag scan chain
> jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id
> $_CPUTAPID
>
> set _TARGETNAME [format "%s.cpu" $_CHIPNAME]
> target create $_TARGETNAME arm7tdmi -endian $_ENDIAN -chain-position
> $_TARGETNAME -variant arm7tdmi-s_r4
> $_TARGETNAME configure -work-area-virt 0 -work-area-phys 0x40000000
> -work-area-size 0x4000 -work-area-backup 0
>
> #flash configuration
> #flash bank lpc2000 <base> <size> 0 0 <target#> <variant>
> flash bank lpc2000 0x0 0x4000 0 0 0 lpc2000_v2 14765 calc_checksum
>
> # For more information about the configuration files, take a look at:
> # openocd.texi
>
> ______________________________________________________________________
>
> Commands Issued in Debug Configuration (Eclipse + Zylin)
> ______________________________________________________________________
>
> target remote 127.0.0.1:3333
> monitor reset
> monitor sleep 500
> monitor poll
> monitor soft_reset_halt
> monitor arm7_9 force_hw_bkpts enable
> break PreStackEntry
> load
> continue
> _______________________________________________
> Openocd-development mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/openocd-development
>

Attachment: lpc2468.cfg
Description: Binary data

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to