Print

[Confusticated]

If your dreamplug stops booting off SD\SDHC ) and you get errors like this

arvell>> usb reset
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 4 USB Device(s) found
       scanning bus for storage devices... Device NOT ready
   Request Sense returned 02 3A 00
1 Storage Device(s) found
Marvell>> usb storage
  Device 0: Vendor: Generic  Rev: 9909 Prod: STORAGE DEVICE
            Type: Removable Hard Disk
            Capacity: not available
Marvell>> fatls usb 0
Device NOT ready
   Request Sense returned 02 3A 00
** Can't read from device 0 **

** Unable to use usb 0:1 for fatls **

Marvell>> usb reset
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... failed to set default configuration len 0, status 20
4 USB Device(s) found
       scanning bus for storage devices... EHCI timed out on TD - token=0x80008c80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
error in inquiry
0 Storage Device(s) found
Marvell>>

It may be caused by bad connections on the flying lead from the SD Card Board to the main Plug Board.
Take it apart and give them a 'wiggle', you have nothing to loose.

[kanpa]

It may be caused by bad connections on the flying lead from the SD Card Board to the main Plug Board.

No, it is not.

It's an u-boot timing issue, just verified it with the manufacturer.

The resolution for it is to flash a fixed u-boot.

[Confusticated]

It may be caused by bad connections on the flying lead from the SD Card Board to the main Plug Board.

No, it is not.

It's an u-boot timing issue, just verified it with the manufacturer.

The resolution for it is to flash a fixed u-boot.

That may be your issue, but it certainly wasn't mine

[kanpa]

That may be your issue, but it certainly wasn't mine.

You cannot accertain that it was not you issue, UNLESS it was happening repeatedly on EVERY reboot UNTIL you cleaned the leads (that, however was not mentioned in your previous post).

Please bear with me for a while:

- the log output you provided is EXACTLY the output of the timing issue the manufacturer confirmed,
- the issue occurs randomly (nondeterministically, if you will) every tens/hundreds of reboots, so your opening of the dreamplug and cleaning the leads was, IMO, the same workaround of the problem as I employed: disconnecting the mains and repowering the plug. Then you're good for another XX or XXX reboots.

I would simply prefer finding a piece of information about a faulty uboot before I had read your post. "You have nothing to loose" and "wiggle them a bit" did not provide useful for over a thousand of dreamplug units my organization purchased, that's all.

Cheers.

[Confusticated]

over a thousand of dreamplug units my organization purchased

That's good to hear, I look forward to reading more of your posts sharing the wealth of experience that you have surely gained.

[kanpa]

Listen, as far as I am concerned, it's perfectly fine if you find this particular u-boot error description boring and/or funny/generally uninteresting. Why the sarcasm though?

I did not find information about this particular uboot issue on the forum, the only mention that, in my opinion, was connected with it - was your post. I do think that, given how similar your log was compared to mine - it is highly unlikely that it was dirty leads or need of 'wiggling' them and not this particular uboot error.

Why would you try to discredit something that was admitted by the manufacturer? I am merely giving you and forum readers facts.

I do apologize if you felt somehow threatened by my posts, it was never my intention.
Cheers.

That's EOT from me, will provide further info when the patch from the manufacturer will prove itself.

[Confusticated]

Why the sarcasm though?

Sarcasm ? I am serious (or I never would have bothered starting this thread), it is through 'sharing' that strong 'community's are built.

[misterTi]

I take it apart to make a backup of the sd card. Same thing happened. Card was not found, controller was. I reopened it and replaced the card a few times and voila! It was working again.
Thanks Confusticated