No JTAG port on rev 1.3 board vie mini-usb?

[ken.walker@secglobe.net]

Hello, I am getting this error with my latest batch of plugs:

Code:

./runme.sh
 **** Preparing environment variables file ...
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 453:
   
 **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplug

And in /var/log/messages I get the following etnries:

Code:

Sep 18 10:56:24 ken-lx kernel: usb 5-1: new full speed USB device using uhci_hcd and address 7
Sep 18 10:56:24 ken-lx kernel: usb 5-1: New USB device found, idVendor=0403, idProduct=6010
Sep 18 10:56:24 ken-lx kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 18 10:56:24 ken-lx kernel: usb 5-1: Product: Dual RS232
Sep 18 10:56:24 ken-lx kernel: usb 5-1: Manufacturer: FTDI
Sep 18 10:56:24 ken-lx kernel: usb 5-1: configuration #1 chosen from 1 choice
Sep 18 10:56:24 ken-lx kernel: ftdi_sio 5-1:1.0: FTDI USB Serial Device converter detected
Sep 18 10:56:24 ken-lx kernel: usb 5-1: Detected FT2232C
Sep 18 10:56:24 ken-lx kernel: usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB1
Sep 18 10:56:24 ken-lx kernel: ftdi_sio 5-1:1.1: FTDI USB Serial Device converter detected
Sep 18 10:56:24 ken-lx kernel: usb 5-1: Detected FT2232C
Sep 18 10:56:24 ken-lx kernel: usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB2

However, on my other (older) plugs, I would get these entries:

Code:

Sep 16 15:50:02 ken-lx kernel: usb 5-1: new full speed USB device using uhci_hcd and address 21
Sep 16 15:50:02 ken-lx kernel: usb 5-1: New USB device found, idVendor=9e88, idProduct=9e8f
Sep 16 15:50:02 ken-lx kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 16 15:50:02 ken-lx kernel: usb 5-1: Product: SheevaPlug JTAGKey FT2232D B
Sep 16 15:50:02 ken-lx kernel: usb 5-1: Manufacturer: FTDI
Sep 16 15:50:02 ken-lx kernel: usb 5-1: SerialNumber: FTSA8DK3
Sep 16 15:50:02 ken-lx kernel: usb 5-1: configuration #1 chosen from 1 choice
Sep 16 15:50:02 ken-lx kernel: usb 5-1: Ignoring serial port reserved for JTAG
Sep 16 15:50:02 ken-lx kernel: ftdi_sio 5-1:1.1: FTDI USB Serial Device converter detected
Sep 16 15:50:02 ken-lx kernel: usb 5-1: Detected FT2232C
Sep 16 15:50:02 ken-lx kernel: usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB1

You can clearly see that one of the 2 serial ports was reserver for JTAG. Has anyone else run accross this yet?
And if so, how does one now JTAG the plug?

Thanks,
Ken

[superpat]

Hi Ken,

The new (v1.3) plugs report their USB details differently to the earlier versions, the usb device is found but it is not automatically associated to the ftdi driver. 

It is necessary to change the connection details see :-

http://plugcomputer.org/plugforum/index.php?topic=2.0

and read the threads especially #5 onwards

cheers

Edit re-reading your post, I may be wrong, since your log file does show the ftdi device,  when I first connected to my new Plug, dmesg on the host showed the usb device, but never picked u the ftdi driver,  Patrick

[ken.walker@secglobe.net]

Actually after looking at my post above, it *looks like* perhaps a step was missed in manufacturing where the eeprom on the FTDI chip isn't getting reporgrammed with the SheevaPlug ID and vendor ID.

I know FTDI has a windows program to allow manufacturers to change the eeprom on an installed chip. I wonder if this is what is missing.

Ken

[Reedy]

There has been a change of vendor id/whatever it is

http://plugcomputer.org/plugwiki/index.php/SheevaPlug_Installer#Troubleshooting

http://plugcomputer.org/plugwiki/index.php/SheevaPlug_Installer#Important_Note_for_Newer_Plugs_.287.2F30.2F09ish.29

You're getting that issue, seemingly

Also, installer 1.0 is out,  but there are some issues... Partially related to the above, but fixed for some people


http://plugcomputer.org/plugforum/index.php?topic=717.0

[dvbuser]

I have two Sheeva Plugs (both Rev 1.3)  and ordered at the same time.

I am currently using a Windows client to access the JTAG port.

Problem is, the JTAG works on one of the plugs, but not the other!

I'm guessing this is the same issue as above, as Windows isn't able to detect the JTAG port, just the USB Composite Device.

Based on Ken's log messages, I think I'm expericing the same thing, where the working plug detects two SheevaPlug JTAGKey devices, however the other plug just shows another USB Composite Device.

Any ideas how to get this working in Windows?

Thanks

[JiriH]

Currently I have no Sheeva plugged in, but what I remember:
Try to open "Computer management" dialog and in Device manager locate Composite Device related to sheeva. Open "Properties" dialog and on one of tabs, there is checkbox with something like "Load VCP..." Select this checkbox, press Apply or Close then disconnect sheeva and connect again. This procedure definitelly helped me on Windows to recognize USB serial ports. I think it is related to missing info in eeprom stated some posts earlier.

[dvbuser]

Thanks for the feedback, I can't see the VCP option when the Composite Device is displayed. The VCP option does appear if I force an incorrect Serial Driver. I guess if you have it working, what Serial Driver are you using?

As you can see in the attached images, its the Vendor, Product and Serial Number ids that have changed.

Any ways to get around this?

I'm guessing there must be a way to manipulate the .inf file.

Also tried using FT Prog to change the details on the EEPROM, but this didn't work!

Any advice/guidance would be much appreciated.

[prafulla]

yes this is problem with some sheevaplug, configuration eeprom fir FT2232D is not programmed
you can use "modprobe ftdi_sio vendor=0x0403 product=0x6010" to get this working on Linux host

best way is to program the vendor id/product id, you can get thr tool from ftdi to update eeprom

Regards...
Prafulla . .