following up on my earlier post on JTAG debugging, i dug into my
supplies and found my flyswatter 2 and associated cables and started
following the instructions here:
and ran into a couple issues.
the first is that, if you look at the photos on that page, there's a
discrepancy between pics 4 and 5, as pic 4 shows the 10-pin ribbon
cable being connected, then suddenly that cable has vanished in pic 5,
and is replaced by the serial cable in pic 6, which is kind of
the bigger issue is an apparent bug in openocd. there is an openocd
package for fedora 20, which i installed with yum -- it's version
0.7.0, which appears to be the latest version. if i then connect the
USB cable and run the appropriate openocd command, i get:
# openocd -f interface/flyswatter2.cfg -f board/ti_beagleboard_xm.cfg -c init -c "reset init"
Open On-Chip Debugger 0.7.0 (2013-09-07-16:51)
Licensed under GNU GPL v2
For bug reports, read
Info : only one transport option; autoselect 'jtag'
adapter speed: 10 kHz
Warn : dm37x.dsp: huge IR length 38
Runtime Error: embedded:startup.tcl:20: Unknown target type cortex_a,
try one of arm7tdmi, arm9tdmi, arm920t, arm720t, arm966e, arm946e,
arm926ejs, fa526, feroceon, dragonite, xscale, cortex_m, cortex_a8,
cortex_r4, arm11, mips_m4k, avr, dsp563xx, dsp5680xx, testee,
avr32_ap7k, or hla_target
in procedure 'script'
at file "embedded:startup.tcl", line 58
at file "/usr/share/openocd/scripts/board/ti_beagleboard_xm.cfg", line 5
in procedure 'target' called at file "/usr/share/openocd/scripts/target/amdm37x.cfg", line 144
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 20