Skip to main content
Topic: Difficulty getting v3 working with openocd/urjtag (Read 2405 times) previous topic - next topic

Difficulty getting v3 working with openocd/urjtag

I must be doing something wrong here:

I'm using libftdi.  Primarily as the openocd page said "ftdi interface driver got extensive testing and is now recommended over the old ft2232 implementation"

Originally libftdi 0.2 but I just recompiled 1.1 (no difference).

URJTAG built from latest sources
Code: [Select]
$ ./configure
...
...
jtag is now configured for

  Detected libusb      : yes
  Detected libftdi    : yes
  Detected libftd2xx  : no
  Detected inpout32    : no
  Build SVF player    : yes
  Build BSDL subsystem : yes
  Bus drivers          : au1500 avr32 bcm1250 bf526_ezkit bf527_ezkit bf533_stamp bf533_ezkit bf537_stamp bf537_ezkit bf538f_ezkit bf548_ezkit bf561_ezkit bscoach ejtag ejtag_dma fjmem ixp425 jopcyc h7202 lh7a400 mpc5200 mpc824x ppc405ep ppc440gx_ebc8 prototype pxa2x0 pxa27x s3c4510 sa1110 sh7727 sh7750r sh7751r sharc_21065L slsup3 tx4925 zefant_xs3
  Cable drivers        : arcom byteblaster dlc5 ea253 ei012 ft2232 igloo jlink keithkoep lattice mpcbdm triton usbblaster wiggler xpc
  Lowlevel drivers    : direct ftdi ppdev

# /usr/local/bin/jtag

UrJTAG 0.10 #1502
Copyright (C) 2002, 2003 ETC s.r.o.
Copyright (C) 2007, 2008, 2009 Kolja Waschk and the respective authors

UrJTAG is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
There is absolutely no warranty for UrJTAG.

WARNING: UrJTAG may damage your hardware!
Type "quit" to exit, "help" for help.

jtag> cable jtagkey
Couldn't connect to suitable USB device.
Error: Cable connection failed!

I get further if I select "cable flyswatter"

Code: [Select]
jtag> cable Flyswatter
Connected to libftdi driver.
jtag> detect
{hangs}


OPENOCD

Plug bus blaster into USB,  following appears in dmesg

Code: [Select]
2014-05-08T20:22:58.069126-07:00 linux-wyem kernel: [26393.442943] usb 1-4: new high-speed USB device number 14 using ehci_hcd
2014-05-08T20:22:58.183167-07:00 linux-wyem kernel: [26393.557739] usb 1-4: New USB device found, idVendor=0403, idProduct=6010
2014-05-08T20:22:58.183183-07:00 linux-wyem kernel: [26393.557745] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
2014-05-08T20:22:58.183186-07:00 linux-wyem kernel: [26393.557748] usb 1-4: Product: Dual RS232-HS
2014-05-08T20:22:58.183188-07:00 linux-wyem kernel: [26393.557751] usb 1-4: Manufacturer: FTDI
2014-05-08T20:22:58.184145-07:00 linux-wyem kernel: [26393.558121] ftdi_sio 1-4:1.0: FTDI USB Serial Device converter detected
2014-05-08T20:22:58.184157-07:00 linux-wyem kernel: [26393.558155] usb 1-4: Detected FT2232H
2014-05-08T20:22:58.184159-07:00 linux-wyem kernel: [26393.558158] usb 1-4: Number of endpoints 2
2014-05-08T20:22:58.184161-07:00 linux-wyem kernel: [26393.558160] usb 1-4: Endpoint 1 MaxPacketSize 512
2014-05-08T20:22:58.184162-07:00 linux-wyem kernel: [26393.558163] usb 1-4: Endpoint 2 MaxPacketSize 512
2014-05-08T20:22:58.184164-07:00 linux-wyem kernel: [26393.558165] usb 1-4: Setting MaxPacketSize 512
2014-05-08T20:22:58.184167-07:00 linux-wyem kernel: [26393.558574] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB0
2014-05-08T20:22:58.184169-07:00 linux-wyem kernel: [26393.558737] ftdi_sio 1-4:1.1: FTDI USB Serial Device converter detected
2014-05-08T20:22:58.184181-07:00 linux-wyem kernel: [26393.558770] usb 1-4: Detected FT2232H
2014-05-08T20:22:58.184183-07:00 linux-wyem kernel: [26393.558773] usb 1-4: Number of endpoints 2
2014-05-08T20:22:58.184184-07:00 linux-wyem kernel: [26393.558776] usb 1-4: Endpoint 1 MaxPacketSize 512
2014-05-08T20:22:58.184185-07:00 linux-wyem kernel: [26393.558778] usb 1-4: Endpoint 2 MaxPacketSize 512
2014-05-08T20:22:58.184186-07:00 linux-wyem kernel: [26393.558781] usb 1-4: Setting MaxPacketSize 512
2014-05-08T20:22:58.185107-07:00 linux-wyem kernel: [26393.559047] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB1
2014-05-08T20:22:58.186620-07:00 linux-wyem mtp-probe: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4"
2014-05-08T20:22:58.187311-07:00 linux-wyem mtp-probe: bus: 1, device: 14 was not an MTP device

Code: [Select]
 # openocd -f interface/ftdi/dp_busblaster.cfg -f board/ti_pandaboard.cfg
Open On-Chip Debugger 0.8.0 (2014-05-08-18:36)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
RCLK - adaptive
Using dbgbase = 0x80000000
force hard breakpoints
trst_only separate trst_push_pull
Info : RCLK (adaptive clock speed)
{hangs}

following new lines in dmesg
Code: [Select]
2014-05-08T20:23:35.886091-07:00 linux-wyem kernel: [26431.242155] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
2014-05-08T20:23:35.886105-07:00 linux-wyem kernel: [26431.242173] ftdi_sio 1-4:1.0: device disconnected


Any suggestions?    I connected to a Panda board using the Tincantools ARM20->TI14 adapter.  I see it mentioned in these instructions:  http://dangerousprototypes.com/docs/Bus ... nOCD_guide  ("Alternative: ARM20TI14 JTAG adapter board including a ribbon cable")