From: Tony Jones <t...@tonyjones.com> Reply-To: <beagleboard@googlegroups.com> Date: Wednesday, May 21, 2014 at 12:35 PM To: <beagleboard@googlegroups.com> Subject: [beagleboard] Re: JTAG issues on BeagleBone Black
> Anyone? Am I the only person with a BBB and JTAG? > > Is there anyone in the Portland (Oregon) Metro area who has a Flyswatter2 > and/or a BBB (with JTAG connector) soldered on who'd be willing to spend 30 > minutes swapping components to see if the issue is my BBB, my JTAG or my > OpenOCD/libusb/Linux install? I have used BBB with USB100V2, Blackhawk USB560M, Ronetix and Lauterbach and they all work fine. I have seen several users on this forum bag their heads against the wall trying to use Flyswatter but no one has ever claimed to have got it working. The USB100V2 is less than $100, which is about an hour of your time so you may want to reconsider going down this path. Regards, John > > On Friday, May 16, 2014 3:23:23 PM UTC-7, Tony Jones wrote: >> I'm trying to connect a Bus Blaster v3c >> <http://dangerousprototypes.com/docs/Bus_Blaster_v3_design_overview> to a >> Beagle Bone Black. I'm seeing identical output to the AM335X problem >> posted here: https://forum.sparkfun.com/viewtopic.php?f=18&t=35490 >> >> I'm using OpenOCD 0.8. TDO is always 1, if I ground it, OpenOCD reports >> "JTAG scan chain interrogation failed: all zeros". TCK is constantly >> changing. >> >> I'm using the Tincan Tools ARM20 to cTI20 adapter >> <http://www.tincantools.com/JTAG/ARM20CTI20.html> . The Bus Blaster uses >> the same ARM20 pinout as the Tincan Flyswatter. I've verified via >> continuity that everything is correct wiring/adapter wise >> >> The Tincan instructions for using the adapter >> <http://www.tincantools.com/wiki/Flyswatter2_BeagleBone_Black_How_To> with >> their JTAG interface are pretty straight forward, I used their config as a >> starting point (FYI: I see the same output using the openocd supplied >> am335x.cfg) >> >> $ openocd -f ./ti_beaglebone_with_fs2.cfg -c init -c "reset init" >> Open On-Chip Debugger 0.8.0 (2014-05-12-14:07) >> 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: 100 kHz >> Warn : target name is deprecated use: 'cortex_a' >> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain >> connect_deassert_srst >> Info : clock speed 100 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: am335x.jrc: IR capture error; saw 0x3f not 0x01 >> Warn : Bypassing JTAG setup events due to errors >> 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: am335x.jrc: IR capture error; saw 0x3f not 0x01 >> Warn : Bypassing JTAG setup events due to errors >> >> >> Tips/suggestions welcomed. I'm out of ideas. > -- > 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 beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
