On Sat, 4 Jan 2014, Bill Traynor wrote: > On Sat, Jan 4, 2014 at 10:11 PM, Robert P. J. Day <[email protected]> > wrote: > > On Sat, 4 Jan 2014, Bill Traynor wrote: > > > >> On Sat, Jan 4, 2014 at 6:34 PM, Robert P. J. Day <[email protected]> > >> wrote: > >> > > >> > 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: > >> > > >> > http://elinux.org/Flyswatter2_Beagleboard_XM_How_To > >> > > >> > 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 > >> > confusing. > >> > >> Yes, PIC4 and 5 are slightly confusing and incorrect. > >> > >> > > >> > 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 > >> > http://openocd.sourceforge.net/doc/doxygen/bugs.html > >> > 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 > >> > # > >> > > >> > "Unknown target type cortex_a"? > >> > > >> > if i go to line 144 of the config file, sure enough, i find: > >> > > >> > target create $_TARGETNAME cortex_a -chain-position $_CHIPNAME.dap > >> > ^^^^^^^^ > >> > > >> > should that instead say "cortex_a8"? is this really a bug in openocd? > >> > has anyone else tried this? > >> > >> Yes, and it used to work. Did the cfg file get patched for cortex_a. > >> > >> I'd also recommend NOT using the distros OpenOCD, but rather using the > >> latest version in OpenOCDs Git repo. > > > > i just tried to build openocd from the git repo and, when all was > > said and done, i was right back where i started -- with openocd > > complaining about an unknown target type of "cortex_a". > > > > i'll try this again tomorrow after a good night's sleep, but i would > > be interested in whether anyone else can get this to work on 64-bit > > fedora 20 to talk to the beagleboard xm. > > > > more tomorrow ... > > I'll give it a try as well tomorrow, or Monday.
i'm going to give this another shot but here's the fundamental problem as i see it. over at elinux.org, there are a number of patches to earlier openocd ostensibly to add support for the flyswatter2 and the bb-xm, one of those patches being the file amdm37x.cfg as seen here: http://elinux.org/images/9/95/Amdm37x.cfg whose most important line seems to be 144: target create $_TARGETNAME cortex_a8 -chain-position $_CHIPNAME.dap where you can see the reference to "cortex_a8", not just "cortex_a". however, i checked out the git repo for openocd from sourceforge and you can see the latest commit to that very file here: http://sourceforge.net/p/openocd/code/ci/d9ba56c295f057e716519a798bf9cdb4898c24f4/tree/tcl/target/amdm37x.cfg?diff=ca45e700b1c57caca2ef08e665e3c7e3e02ac8d3 which *renames* "cortex_a8" *back* to "cortex_a". so what's going on? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
