Did my SheevaPlug arrive broken?

[edmc]

I'm trying to install the FTDI Virtual COM Port ("VCP") drivers on my Vista PC as per the XP instructions to no avail.  No matter what I do, Vista just insists it cannot "start" any driver I attach to the device.

Google-ing around, I've certainly tracked down several versions of the FTCI VCP driver set... all with different installation instructions.

But each document I found referred to OEM variances in the VendorID/ProductID settings reported and suggested I check to see what the SheevaPlug happens to be sending.  FTDI has conveniently hosted the "USBView" tool from Microsoft that can be used to report what your Windows PC is seeing on its various USB bus/ports.

Much to my surprise, USBView reports the following for my SheevaPlug:

  In the Navigation Panel on the left, it says:

    "[!] [Port6] DeviceFailedEnumeration : Unknown Device"

  Clicking on this item in the Navigation Panel causes the Detail Panel on the right to report:

    Device Descriptor:
    bcdUSB:             0x0000
    bDeviceClass:         0x00
    bDeviceSubClass:      0x00
    bDeviceProtocol:      0x00
    bMaxPacketSize0:      0x00 (0)
    idVendor:           0x0000
    idProduct:          0x0000
    bcdDevice:          0x0000
    iManufacturer:        0x00
    iProduct:             0x00
    iSerialNumber:        0x00
    bNumConfigurations:   0x00

    ConnectionStatus: DeviceFailedEnumeration
    Current Config Value: 0x00
    Device Bus Speed:     Low
    Device Address:       0x00
    Open Pipes:              0

I was expecting, maybe, the idVendor/idProduct to not match the values in the FTDI-supplied .inf file values (0x0403 & 0x60?? respectively).  What I didn't expect to see was an obviously non-responding USB device :-(.

I should also comment that - as far as lights go - only the green one closest to the power plug end of the SheevaPlug is ever lighted now.  When I first plugged in the SheevaPlug, I could have sworn the other light came on brightly as well (and, indeed, may have been flashing), but I had to leave for dinner at that very moment.  Upon my return, only the lone green light nearest the power plug end ever lights no matter what I do.

Suggestions?  Similar experiences?

[nicenguy]

Have you tried to use the driver from the CD?  You can also fetch it under resource --> download from openplug.org site

[edmc]

Have you tried to use the driver from the CD?  You can also fetch it under resource --> download from openplug.org site

Windows Vista Device Manager doesn't understand the device at all.  As USBView shows, the device(s) isn't enumerating.  Kind of hard to install a driver when it can't attach to any device.

I have an email into GlobalScale asking them to address the problem or exchange my failed device - no response for 48 hours unfortunately.

The drivers, btw, are also available for download from both Marvell's and GlobalScale's sites.

[edmc]

It would be very helpful to me that one or more people simply attempt to run USBView on their Windows systems  and post how their device responds immediately after power-up/connection.

For a link to this helpful tool, see this FTDI site.

I just spoke with my contact @ GlobalScale that graciously offered to overnight/exchange-ship a replacement, but it would be good to cross-verify my current device is actually unusual :-)

[edmc]

Bump... Can nobody out there run USBView for me and post their response?

I'm sure there are USBView equivalents for Linux & MacOS out there as well.

Anyone?

[moshiach]

This is from a working plug attached to a linux computer.

Code:

SheevaPlug JTAGKey FT2232D B
Manufacturer: FTDI
Serial Number: FTS03NTS
Speed: 12Mb/s (full)
USB Version:  2.00
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 8
Number of Configurations: 1
Vendor Id: 9e88
Product Id: 9e8f
Revision Number:  5.00

Config Number: 1
Number of Interfaces: 2
Attributes: 80
MaxPower Needed: 100mA

Interface Number: 0
Name: ftdi_sio
Alternate Number: 0
Class: ff(vend.)
Sub Class: ff
Protocol: ff
Number of Endpoints: 2

Endpoint Address: 81
Direction: in
Attribute: 2
Type: Bulk
Max Packet Size: 64
Interval: 0ms

Endpoint Address: 02
Direction: out
Attribute: 2
Type: Bulk
Max Packet Size: 64
Interval: 0ms

Interface Number: 1
Name: ftdi_sio
Alternate Number: 0
Class: ff(vend.)
Sub Class: ff
Protocol: ff
Number of Endpoints: 2

Endpoint Address: 83
Direction: in
Attribute: 2
Type: Bulk
Max Packet Size: 64
Interval: 0ms

Endpoint Address: 04
Direction: out
Attribute: 2
Type: Bulk
Max Packet Size: 64
Interval: 0ms

The fact that you aren't seeing a product ID or vendor ID  pretty much points to a likely dead plug.   Unless you just don't have the windows usb serial drivers installed properly.

[edmc]

This is from a working plug attached to a linux computer.
...
Vendor Id: 9e88
Product Id: 9e8f
...
The fact that you aren't seeing a product ID or vendor ID  pretty much points to a likely dead plug.   Unless you just don't have the windows usb serial drivers installed properly.

Thanks for posting... and the advice.  Re the "usb serial drivers", it's actually a Windows/Vista thing that it needs to see a VendorID/ProductID to know which driver to install.  Since my SheevaPlug isn't reporting correctly, Windows/Vista doesn't know which driver to select to talk to it.

GlobalScale is shipping me a new device & I'll return this one.  I guess its comforting to think that nobody else's arrived dead.

[edmc]

Just wanted to close this thread out proper.  Indeed, my SheevaPlug was bad - and I'm suspecting
others SheevaPlugs that fail are due to similar defects.  Mine would only light up one of the LEDs,
never the 2nd one.

Just received my replacement from GlobalScale and it powered up perfectly.  Installing the drivers
in Vista went perfect... only slightly different than the WinXP process documented.

And for any that are interested, here is the output from USBView for my new/functioning Plug:

  Device Descriptor:
  bcdUSB:             0x0200
  bDeviceClass:         0x00
  bDeviceSubClass:      0x00
  bDeviceProtocol:      0x00
  bMaxPacketSize0:      0x08 (
  idVendor:           0x9E88
  idProduct:          0x9E8F
  bcdDevice:          0x0500
  iManufacturer:        0x01
  iProduct:             0x02
  iSerialNumber:        0x03
  bNumConfigurations:   0x01

  ConnectionStatus: DeviceConnected
  Current Config Value: 0x01
  Device Bus Speed:     Full
  Device Address:       0x02
  Open Pipes:              4

  Endpoint Descriptor:
  bEndpointAddress:     0x81  IN
  Transfer Type:        Bulk
  wMaxPacketSize:     0x0040 (64)
  bInterval:            0x00

  Endpoint Descriptor:
  bEndpointAddress:     0x02  OUT
  Transfer Type:        Bulk
  wMaxPacketSize:     0x0040 (64)
  bInterval:            0x00

  Endpoint Descriptor:
  bEndpointAddress:     0x83  IN
  Transfer Type:        Bulk
  wMaxPacketSize:     0x0040 (64)
  bInterval:            0x00

  Endpoint Descriptor:
  bEndpointAddress:     0x04  OUT
  Transfer Type:        Bulk
  wMaxPacketSize:     0x0040 (64)
  bInterval:            0x00

Equivalent to the report in moshiach's reply earlier...

[hiroshi]

I got my SheevaPlug today and was very excited (I ordered it 7 weeks ago!)   Sadly I have the same exact FTDI driver problem 

Here is my USBView output from a Vista Business PC:

======
Device Descriptor:
bcdUSB:             0x0000
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x00 (0)
idVendor:           0x0000
idProduct:          0x0000
bcdDevice:          0x0000
iManufacturer:        0x00
iProduct:             0x00
iSerialNumber:        0x00
bNumConfigurations:   0x00

ConnectionStatus: DeviceFailedEnumeration
Current Config Value: 0x00
Device Bus Speed:     Low
Device Address:       0x00
Open Pipes:              0
============

3 different PCs gave me the same result:  a Vista Business desktop,  a XP Sony laptop, and a Compaq desktop running CentOS 5 (used minicom on this.)

btw,  the unit works OK thru TCP/SSH.  I copied the filesystem to a SDHC card (runs faster and easier to clone.) that's when I discovered the console problem!   Needless to say I'm very disappointed now

Did anyone else encounter this issue or have a solution short of requesting a replacement unit?

Thanks!

P.S.   thanks to edmc for the original detailed post.

[restamp]

Probably a long shot, but the Plug is notorious for requiring a mini-connector that is a bit longer than the standard specifies in order to make a good connection.  See:

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

Since it doesn't appear to be recognizing your Plug at all, I wonder if this may be the problem.

[mgillespie]

Saw similar things myself, the way the PCB is fitted and the hole for the miniUSB was not a great fit, and the plastic case was getting int the way of the miniusb connector, making a very crappy connection.   A stong wind in the wrong connection would result in the thing disconnecting (bit of an exageration there perhaps...)

Make sure that lead is pushed all the way in and making a nice connection...

[birdman]

FWIW:  My connector seemed to be slightly lose, so I just bit it (the mini-USB connector on the cable) to bend the top flange down slightly.,  It then fitted snugly and I've had no problems at all.

[rbgray]

I switched to another USB cable which fit securely and then it worked fine.