with the 0.4.0 and latest openocd, I can't recognize the CPU ID, but can't halt
it.
the log is:
$ telnet localhost 4444
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> halt
Halt timed out, wake up GDB.
invalid mode value encountered 0
cpsr contains invalid mode value - communication failure
Command handler execution failed
in procedure 'halt'
> reset halt
JTAG tap: pxa920.cpu tap/device found: 0x0c9203d3 (mfg: 0x1e9, part: 0xc920,
ver: 0x0)
timed out while waiting for target halted
TARGET: pxa920.cpu - Not halted
Command handler execution failed
in procedure 'reset'
> halt
Halt timed out, wake up GDB.
timed out while waiting for target halted
Command handler execution failed
in procedure 'halt'
invalid mode value encountered 0
cpsr contains invalid mode value - communication failure
Polling target failed, GDB will be halted. Polling again in 100ms
Polling succeeded again
the configuration file is:
# Marvell PXA920
jtag_khz 1000
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
} else {
set _CHIPNAME pxa920
}
if { [info exists ENDIAN] } {
set _ENDIAN $ENDIAN
} else {
set _ENDIAN little
}
# IDs for all currently known pxa920 chips
if { [info exists CPUTAPID_PXA920 ] } {
set _CPUTAPID_PXA920 $CPUTAPID_PXA920
} else {
set _CPUTAPID_PXA920 0x0c9203d3
}
# set jtag_nsrst_delay to the delay introduced by your reset circuit
# the rest of the needed delays are built into the openocd program
jtag_nsrst_delay 260
reset_config trst_and_srst
# set the jtag_ntrst_delay to the delay introduced by a reset circuit
# the rest of the needed delays are built into the openocd program
jtag_ntrst_delay 250
set _TARGETNAME $_CHIPNAME.cpu
jtag newtap $_CHIPNAME cpu -irlen 11 -ircapture 0x1 -irmask 0x7f \
-expected-id $_CPUTAPID_PXA920
target create $_TARGETNAME arm966e -endian $_ENDIAN \
-chain-position $_TARGETNAME -variant arm946
# work area in internal RAM.
$_TARGETNAME configure -work-area-phys 0xD100A000 -work-area-size 0x20000
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
