JTAG issues on BeagleBone Black

I’m trying to connect a Bus Blaster v3c 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. 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 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.

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?

JTAG is used here all the time. But we use higher in JTAG devices and CCS for debugging. Only JTAG component is one connector. Voltage is 3.3V.

Gerald

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

By "components" I meant the BBB, the JTAG interface and the system
running the software debugger/toolchain.

Right now I'm not sure if:
1) I messed up soldering the header onto the BBB -- don't think so,
looks perfect under magnification.
2) Whether the issue is with my Bus Blaster v3c. The
instructions/adapter I'm using are for the Flyswatter2 but it uses an
identical ARM20 pinout to the BusBlaster.
3) Related to my particular OpenOCD/libusb/Linux install.

Hence I was wondering if there was someone local to me using the
Flyswatter2 JTAG with the BBB, according to the Tincan tools site,
it works, at least using OpenOCD 0.7

I'm aware that there are more expensive JTAG tools available.

JTAG is used here all the time. But we use higher in JTAG devices and
CCS
for debugging. Only JTAG component is one connector. Voltage is 3.3V.

By "components" I meant the BBB, the JTAG interface and the system
running the software debugger/toolchain.

Right now I'm not sure if:
1) I messed up soldering the header onto the BBB -- don't think so,
looks perfect under magnification.
2) Whether the issue is with my Bus Blaster v3c. The
instructions/adapter I'm using are for the Flyswatter2 but it uses an
identical ARM20 pinout to the BusBlaster.
3) Related to my particular OpenOCD/libusb/Linux install.

Hence I was wondering if there was someone local to me using the
Flyswatter2 JTAG with the BBB, according to the Tincan tools site,
it works, at least using OpenOCD 0.7

I'm aware that there are more expensive JTAG tools available.

BTW, I can connect the USB100V2 and USB560M directly to the BBB JTAG, but
the Lauterbach JTAG connector is an ARM20 format so I used the following
adapter from TinCan:

ARM20cTI20 - cTI 20-pin JTAG Adapter Board

Regards,
John

BTW, I can connect the USB100V2 and USB560M directly to the BBB JTAG, but
the Lauterbach JTAG connector is an ARM20 format so I used the following
adapter from TinCan:

ARM20cTI20 - cTI 20-pin JTAG Adapter Board

That is the exact adapter I'm using. I attached the header/cable
to the BBB exactly as shown here:

https://www.tincantools.com/w/images/thumb/f/f5/black_P2_zoom2.jpg/634px-black_P2_zoom2.jpg
http://www.tincantools.com/w/images/3/3b/ARM20cTI20_ribbon_cable.jpg

I can get the Bus Blaster v3c (JTAG adapter) to work with my Panda
Board ES [ti14] using OpenOCD 0.8 but I'm having no luck with the BBB
(see first post).

Re: your previous message, yes, better research on my end before
purchasing the Bus Blaster would have been smart. It's "community
supported" but "I can't get this working" questions seem to go
unanswered on their forum. I should have got
http://www.blackhawk-dsp.com/products/USB100v2D.aspx as it appears to
include everything I needed for the Panda Board and BBB. With the
cost of the Bus Blaster plus the Tincan adapters I've probably spent
more and it doesn't work for the hardware I have. Stupid.