GuruPlug JTAG WinXP Drivers

[fabio70mi]

Hello,
GuruPlug JTAG I/F is not recognized from standard FTDI drivers on WXP ( http://www.ftdichip.com/Drivers/CDM/CDM20602.zip )

So reading http://www.ftdichip.com/Documents/AppNotes/AN_107_AdvancedDriverOptions_AN_000073.pdf I added the following lines to .inf driver installation files and it worked fine:

FTDIBUS.INF

[FtdiHw]
%USB\VID_9E88&PID_9E8F&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_9E88&PID_9E8F&MI_00
%USB\VID_9E88&PID_9E8F&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_9E88&PID_9E8F&MI_01

[FtdiHw.NTamd64]
%USB\VID_9E88&PID_9E8F&MI_00.DeviceDesc%=FtdiBus.NTamd64,USB\VID_9E88&PID_9E8F&MI_00
%USB\VID_9E88&PID_9E8F&MI_01.DeviceDesc%=FtdiBus.NTamd64,USB\VID_9E88&PID_9E8F&MI_01

[Strings]
USB\VID_9E88&PID_9E8F.DeviceDesc="SheevaPlug JTAGKey FT2232D B"
USB\VID_9E88&PID_9E8F&MI_00.DeviceDesc="SheevaPlug JTAGKey FT2232D B Port A"
USB\VID_9E88&PID_9E8F&MI_01.DeviceDesc="SheevaPlug JTAGKey FT2232D B Port B"


FTDIPORT.INF

[FtdiHw]
%VID_9E88&PID_9E8F.DeviceDesc%=FtdiPort2232.NT,FTDIBUS\COMPORT&VID_9E88&PID_9E8F

[FtdiHw.NTamd64]
%VID_9E88&PID_9E8F.DeviceDesc%=FtdiPort2232.NTamd64,FTDIBUS\COMPORT&VID_9E88&PID_9E8F

[Strings]
VID_9E88&PID_9E8F.DeviceDesc="SheevaPlug JTAGKey FT2232D B Serial Port"

[light]

I created an account just to tell you that I love you.

[tkteun]

Why is it that all the assholes using those FTDI chip just HAVE to change the vid/pid in this thing...

It's not that difficult to just change the description and leave the vid/pid intact for all the drivers in the world to just work, especially since the FT2232 is the only chip on this board and is just used for it's intended purposes...

[guidol]

Why is it that all the assholes using those FTDI chip just HAVE to change the vid/pid in this thing...

Some time ago Marvell itself did got the correct package for the sheevaplug (which should also work for ftdi from the guruplug) at
http://www.marvell.com/files/products/embedded_processors/developer/kirkwood/SheevaPlug_Host_SWsupportPackageWindowsHost.zip
(but this link is also on the page http://plugcomputer.org/plugwiki/index.php/Serial_terminal_program)

But now its gone and it isnt in the downloads of the GlobaleScaleTechnologies WebPage.

I got this file downloaded some time ago....but is it allowed to be uploaded to any storage here?

[phampson]

http://www.plugcomputer.org/index.php/us/resources/downloads?func=select&id=13

It seems that globalscope are letting plugcomputer host the files. The drivers for windows can be found in the drivers directory. I downloaded from here and it worked a treat.

If your intending on using Esai as your installer then the following link points to everything you need. Including distributions of ubuntu, debian (squeeze/lenny) etc which work with there installer.

http://sourceforge.net/projects/esia/files/

Paul

[guidol]

http://www.plugcomputer.org/index.php/us/resources/downloads?func=select&id=13
It seems that globalscope are letting plugcomputer host the files. The drivers for windows can be found in the drivers directory. I downloaded from here and it worked a treat.

I thought they were in the tools/driver directory, but I only could see the sheevaplug-installer
there :-(

[phampson]

Sorry my bad there are in the sheevaplug software & design information directory

[guidol]

Sorry my bad there are in the sheevaplug software & design information directory

No Problem :-)
ahh here :
plugcomputer.org : SheevaPlug Software & Design Information - Revision 1.2
http://www.plugcomputer.org/index.php/us/resources/downloads?func=select&id=10

SheevaPlug_Host_SWsupportPackageWindowsHost1.2.zip
http://www.plugcomputer.org/index.php/us/resources/downloads?func=fileinfo&id=44

[lyzby]

Well--over an hour from the time I plugged in the mini usb cable and got the error message, "SheevaPlug JTAGKey FT2232D B"  driver missing until I found this thread and the solution.  It had been quite a while since I had used the usb cable, and the thing that I can think of which would have changed things was installing a new u-boot and Martin Michlmayr's Debian on USB thumb drive.  And the drivers from the FTDI site didn't work. 

Kudos to those who posted the solution.  Bad karma for those who created the problem.