Sunday, July 5, 2015

Phase 1: openocd woes

encountered some problems getting openocd + jtag interface up and running. the ftdi driver has superceeded the ft2232 but the latter at least produces a connection ... example:


using recently upgraded 0.9.0 (openocd)
***using "interface ft2232" script
openocd_ft2232
Open On-Chip Debugger 0.9.0 (2015-07-05-17:44)
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 10 kHz
adapter_nsrst_delay: 1000
jtag_ntrst_delay: 1000
cortex_m reset_config sysresetreq
cortex_m reset_config sysresetreq
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Info : max TCK change to: 30000 kHz
Info : clock speed 10 kHz
Info : inter: 0.000102, inter2: 0.000102 end: 0.069985
Info : JTAG tap: lpc1788.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)
Info : inter: 0.000163, inter2: 0.000163 end: 0.001911
Info : inter: 0.000134, inter2: 0.000134 end: 0.033913
Info : inter: 0.000154, inter2: 0.000154 end: 0.017895
Info : inter: 0.000180, inter2: 0.000180 end: 0.057936
Info : inter: 0.000155, inter2: 0.000155 end: 0.031909
Info : inter: 0.000160, inter2: 0.000160 end: 0.019909
Info : inter: 0.000102, inter2: 0.000102 end: 0.023956
Info : inter: 0.000063, inter2: 0.000063 end: 0.019930
Info : inter: 0.000063, inter2: 0.000064 end: 0.019930
Info : inter: 0.000092, inter2: 0.000092 end: 0.019954
Info : inter: 0.000166, inter2: 0.000167 end: 0.020112
Info : inter: 0.000122, inter2: 0.000122 end: 0.019744
Info : inter: 0.000076, inter2: 0.000076 end: 0.019959
Info : inter: 0.000050, inter2: 0.000050 end: 0.019932
Info : inter: 0.000041, inter2: 0.000041 end: 0.019923
Info : inter: 0.000067, inter2: 0.000068 end: 0.023947
Info : inter: 0.000042, inter2: 0.000042 end: 0.019936
Info : inter: 0.000160, inter2: 0.000160 end: 0.019910
Info : inter: 0.000060, inter2: 0.000060 end: 0.019952
Info : inter: 0.000143, inter2: 0.000143 end: 0.019890
Info : lpc1788.cpu: hardware has 6 breakpoints, 4 watchpoints

arm-linux-gnueabi-gdb ./app.out produces
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x1fff0080 msp: 0x10001ffc
inter: 0.000265, inter2: 0.000266 end: 0.019667
inter: 0.000043, inter2: 0.000043 end: 0.019801
(gdb) load
Loading section .data, size 0xe0 lma 0x10000000
Loading section .text, size 0x1ca8 lma 0x100000e0
Start address 0x10000f49, load size 7560
Ignoring packet error, continuing...
Reply contains invalid hex digit 79



***using "interface ftdi" script
at least this turns on the BILED segment i chose in "data" argument to ftdi_layout
openocd_ftdi
Open On-Chip Debugger 0.9.0 (2015-07-05-17:44)
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
adapter speed: 10 kHz
adapter_nsrst_delay: 1000
jtag_ntrst_delay: 1000
cortex_m reset_config sysresetreq
cortex_m reset_config sysresetreq
Info : clock speed 10 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: lpc1788.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction

Need to resolve this before going forward. And for now I think it best I stick to using the ftdi interface



now that I have moved and settled into a new place. attaching an updated picture of a section of the lab. parts are still in bins inside the closets


No comments:

Post a Comment