usb did not recognized..

[y23]

My flash drive is "not recognized" but it *is* visible by linux'





lsusb -vvv

Code:

  Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp.
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               2.00
   bDeviceClass            0 (Defined at Interface level)
   bDeviceSubClass         0
   bDeviceProtocol         0
   bMaxPacketSize0        64
   idVendor           0x058f Alcor Micro Corp.
   idProduct          0x6387
   bcdDevice            1.41
   iManufacturer           1 JetFlash
   iProduct                2 Mass Storage Device
   iSerial                 3 R1XXXXXX
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
{snip}


cat /proc/bus/usb/devices

Code:

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=058f ProdID=6387 Rev= 1.41
S:  Manufacturer=JetFlash
S:  Product=Mass Storage Device
S:  SerialNumber=R1XXXXX
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms


LED blinks normally, windows does ding ding ding, linux does not assign a /dev/sda1 node.

Is there really no software that can read-out the contents?


(I can run linux-live-cds, windows xp, dos, various laptops available. We are here on great Barrier Island, only 12Volt, and 14k4 modem Internet access, have mercy. pictures from here are (here and here)

[pepe]

Hi,

I am afraid there is no SW able to read out contents. The memory needs to be desoldered, read, and LBA space reassembled, then files logically recovered. There's no magic for this one, sorry.

pepe

[y23]

Hi,

I am afraid there is no SW able to read out contents. The memory needs to be desoldered, read, and LBA space reassembled, then files logically recovered. There's no magic for this one, sorry.

pepe

Thanks for the reply, thanks for the matter-of-fact...

Please excuse my amateur terminology..

So, the process that corrupted the memory got through the controller into the memory.

I had booted a mini-Windows-XP "from the stick" .. what can have happened?

• A voltage spike?
• Bad bytes that the controller-chip passed into the memory?
• The controller chip has a bug?
• The memory itself failed?

No wild bit of code that can "get through" and do something?

For example, I would be happy with a list of files. (I forgot whether important files were on it).

The manufacturer has a special analysis programme, maybe?

cheeeerio from New Zealand...

[pepe]

manufacturer surely has some reformat utility (not available publicly), but u would loose the data.
'i would be happy with a list of files': If u could get a list of files, u could get everything else too (mostly)..

[bigal.nz]

I had a flash disk that when inserted in windows said not formatted, in Linux it gave a buffer IO error in dmesg.

After checking all the caps and resistors as ok, I decided to hold the memory chip (NAND?) very firmly on the PCB when I inserted it, and it worked and I got all the data off. Not very scientific, but something easy to try if anyone has the same problem.

How were you checking the oscillator? With a scope?

-Al

[cakedi]

part above jpg

[fzabkar]

Without osc, the controller can't make USB link, so the windows can't sense at all something is plugger in or not.
So, if the windows says the device is unknown, usually the flash content is corrupted of flash chip is dead.

Janos

See the following article.

USB in a NutShell:
http://www.beyondlogic.org/usbnutshell/usb2.htm

If you read the section entitled "Speed Identification", it suggests that a pullup resistor is used to signal when a USB device has been attached to a port. The author writes that "some devices have this resistor built into its silicon, which can be turned on and off under firmware control, others require an external resistor." This means that USB drives using an external resistor will always be detected, although not properly recognised, even if the oscillator is dead. OTOH, those drives with a resistor that is switched in and out of circuit by the firmware will not be detected if the oscillator fails, assuming the resistor is open in the reset state.

BTW, I can't see any pullup resistors in the OP's photos. Instead they are probably implemented in the silicon.