Problem rebooting into ALARM

[LavaChild]

Code: Select all

Marvell>> help usb
usb - USB sub-system

Usage:
usb reset - reset (rescan) USB controller
usb stop [f]  - stop USB [f]=force stop
usb tree  - show USB device tree
usb info [dev] - show available USB devices
usb storage  - show details of USB storage devices
usb dev [dev] - show or set current USB storage device
usb part [dev] - print partition table of one or all USB storage devices
usb read addr blk# cnt - read `cnt' blocks starting at block `blk#'
    to memory address `addr'
usb write addr blk# cnt - write `cnt' blocks starting at block `blk#'
    from me


So this tells me what 'usb reset' does... But I still don't understand what you mean by 'doubling the usb reset command'.

I really am out of my depth at this point but trying my best to hang on... I'd be very grateful if you could give further advice. Thanks.

EDIT:

Issuing a 'usb reset' gives me:

Code: Select all

Marvell>> usb reset
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found


EDIT2:

I do think we're onto something here. If I 'feel' the HDD I can physically feel it start to spin up when I issue usb reset. The issue is by the time it's really spun up the output '0 Storage Device(s)' is already displayed. I hope this might help...

EDIT3:

I have been playing with 'rootdelay' (and usb_rootdelay) and they certainly do not seem to be in seconds (e.g., 10 does not wait 10 seconds!) however it does seem, though I cannot be certain, that there are *tiny* changes in the time it 'usb reset' takes. Irrespective of this the drive always spins up as soon as the '0 Storage Device(s)' is shown. It's almost as if the device only spins up after the 'usb reset', though in fairness it may be that changing 'rootdelay' is not actually changing anything at all. I really don't know!

[WarheadsSE]

Great, now run that command a second time.

Also, this may be "out of your depth" but it will only become familiar if you try it. Manuals suck for actual knowledge You're learning why, not what

[LavaChild]

Thanks for your help. I do appreciate that this is making a positive learning experience and knowing now that I can access UBoot (and interact - on Windows) is very reassuring.

Back to the troubleshooting:

By 'run that command a second time' do you mean the 'usb reboot'? In which case, I tried (issued immediately after the output for the first command had finished) and the output was the same. What is odd (though I do not know if this is correct behaviour or not) is that after the drive spins up it then spins back down again...

[WarheadsSE]

E.g.

Code: Select all

Marvell >> usb reset
...
Marvell >> usb reset

If the output is still the same then

Code: Select all

Marvell >> usb tree

[LavaChild]

I believe I tried that but still '0 Storage Device(s)'. I did at one point do a 'usb tree' but don't have the output any longer.

Unfortunately I will be unable to investigate this further until sometime in the middle of next week now however I am very keen to continue debugging this and work to a solution. At the next available opportunity I will execute the all of the commands as in your last message and will post the output.

I'd like to quickly thank you for all of your prompt help and I hope you'll be able to continue to assist me when I can come back to this problem I'm slowly but surely learning and I do believe this is an interesting learning process. (Certainly I'm having much better luck than I ever did with a GuruPlug!).

[LavaChild]

I've finally had another chance to look at this. Output of usb reset, usb reset, usb tree, usb info below:

Code: Select all

Marvell>> usb reset
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
Marvell>> usb reset
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
Marvell>> usb tree

Device Tree:
  1  Hub (480 Mb/s, 0mA)
  |  u-boot EHCI Host Controller
  |
  +-2  Hub (480 Mb/s, 100mA)
    |   USB2.0 Hub
    |
    +-0  See Interface (480 Mb/s, 0mA)

Marvell>> usb info
1: Hub,  USB Revision 2.0
 - u-boot EHCI Host Controller
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Hub,  USB Revision 2.0
 -  USB2.0 Hub
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x05e3  Product 0x0608 Version 9.1
   Configuration: 1
   - Interfaces: 1 Self Powered Remote Wakeup 100mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms

   Configuration: 0
   - Interfaces: 0 Bus Powered 0mA


Any suggestions on what to try next?

Thank you!

EDIT: Incase there is value in this information, here is the UBoot log from a cold boot, which boots into ALARM:

Code: Select all

U-Boot 2010.09 (Oct 23 2010 - 11:51:16)
Marvell-PinkPogo by Jeff Doozan
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        727
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             716
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2861420 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.1.10-8-ARCH
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861356 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...


And, for completeness, here is the output of usb reset, usb tree, usb info, boot from a cold boot, which does not boot into ALARM (it would suggest that interrupting the boot process and issuing the usb commands before boot has caused the HDD to disappear?):

Code: Select all

Marvell>> usb reset
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Marvell>> usb tree

Device Tree:
  1  Hub (480 Mb/s, 0mA)
  |  u-boot EHCI Host Controller
  |
  +-2  Hub (480 Mb/s, 100mA)
    |   USB2.0 Hub
    |
    +-3  Mass Storage (480 Mb/s, 2mA)
         Super Top    USB 2.0  SATA BRIDGE    M6116A016V20

Marvell>> usb info
1: Hub,  USB Revision 2.0
 - u-boot EHCI Host Controller
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Hub,  USB Revision 2.0
 -  USB2.0 Hub
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x05e3  Product 0x0608 Version 9.1
   Configuration: 1
   - Interfaces: 1 Self Powered Remote Wakeup 100mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms

3: Mass Storage,  USB Revision 2.0
 - Super Top    USB 2.0  SATA BRIDGE    M6116A016V20
 - Class: (from Interface) Mass Storage
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x14cd  Product 0x6116 Version 2.0
   Configuration: 1
   - Interfaces: 1 Self Powered 2mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 2
     - Class Mass Storage, Transp. SCSI, Bulk only
     - Endpoint 1 In Bulk MaxPacket 512
     - Endpoint 2 Out Bulk MaxPacket 512

Marvell>> boot
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        727
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             716
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: .......  read_nand_cached: error reading nand off 0x13b2a00 s
ize 8192 bytes
. done.
read_nand_cached: error reading nand off 0x13b1600 size 8192 bytes
off = 0x13b128c magic 0x1985 type 0xe002 node.totlen = 2431
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...


[LavaChild]

Any advice?

WarheadsSE, you've been a great help so far... What would you suggest next?

[WarheadsSE]

My apologies, but for the moment I am scratching my head on this.

[LavaChild]

I know it's a serious problem when the Guru is stumped too! Not sure I've got much chance myself, in this case... In the meantime please do post an update if you have any ideas - Thank you!

[regder]

Just so you know, you're not alone! I have the same problem booting into a usb flash drive. Software restart goes into Pogoplug, hardware restart goes into Alarm.

Haven't had time to delve into it though