Welcome! Log In Create A New Profile

Advanced

errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"

Posted by huge 
Forum List Message List New Topic
huge
errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 05, 2017 07:02PM
I'm trying to upgrade to the new uBoot (and rootfs) on my Pogoplug V4, previously on an older Debian kernel/rootfs & older uBoot. This is the first time I've been upgrading uBoot from something older than the 2016 release, so I had to go through the extra "step 8" nandwrite. I'm hoping that's the source of my (hopefully simple) problem.

I have been booting from a Sandisk SD card, but I installed the latest rootfs on a USB stick and then went through the uBoot-install steps on the V4 before shutdown, eject SD card & power-up with only USB stick installed. [And I tried a second USB stick in case the first one was bad] I have netconsole set up but not serial. Here are my log from boot attempt and then my printenv output.


boot log: 
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed
Card did not respond to voltage select!
mmc_init: -95, time 11
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **

no IDE devices available
Card did not respond to voltage select!
mmc_init: -95, time 10
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: ide_preinit failed
device ide 0:1
** Bad device ide 0 **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Card did not respond to voltage select!
mmc_init: -95, time 11
device mmc 0:1
Card did not respond to voltage select!
mmc_init: -95, time 10
Card did not respond to voltage select!
mmc_init: -95, time 11
** Bad device mmc 0 **
device mmc 1:1
MMC Device 1 not found
MMC Device 1 not found
** Bad device mmc 1 **
device mmc 2:1
MMC Device 2 not found
MMC Device 2 not found
** Bad device mmc 2 **
device mmc 3:1
MMC Device 3 not found
MMC Device 3 not found
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!



and printenv... 
Pogov4> printenv
printenv
arcNumber=3960
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb mmc ide
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:25:31:05:EA:F4
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.222.164
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
ncip=192.168.222.165
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.222.165
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 3310/131068 bytes
Pogov4>


Just to make sure it wasn't choking on mmc/SD or IDE/SATA attempts, I reset devices to just usb & tried again... Fewer errors but same result:
Pogov4> printenv devices
printenv devices
devices=usb ide mmc
Pogov4> setenv devices usb
setenv devices usb
Pogov4> saveenv
saveenv
Saving Environment to NAND...
Erasing NAND...
Erasing at 0xc0000 -- 100% complete.
Writing to NAND... OK
Pogov4> boot
boot
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!



Side question - on the V4 does it matter whether I plug a USB stick into the top or bottom slot for booting? I've been trying both, but does it make a difference (as with the E02)?
Reply Quote
rayknight
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 05, 2017 08:46PM
Please post a log showing how you are creating the file system on the USB stick.
Reply Quote
bodhi
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 05, 2017 08:50PM
huge,

> Card did not respond to voltage select!
> mmc_init: -95, time 11

This is OK. Don't worry about it if you are not booting from SD card.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
bodhi
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 05, 2017 08:55PM
huge,

But your bootlog showed it is not OK with the USB drive: 

scanning usb for storage devices... 0 Storage Device(s) found
So the USB drive is not recognized by u-boot.

If this is the Pogo V4 (not Pogo Mobile) then you must use the top USB slot. If it is the Pogo Mobile then it should be OK for the USB drive to be plugged in either USB slots in the back.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
huge
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 05, 2017 09:39PM
bodhi Wrote:
-------------------------------------------------------
> huge,
>
> But your bootlog showed it is not OK with the USB
> drive:
>
> 
> scanning usb for storage devices... 0 Storage
> Device(s) found
>
> So the USB drive is not recognized by u-boot.
>
> If this is the Pogo V4 (not Pogo Mobile) then you
> must use the top USB slot. If it is the Pogo
> Mobile then it should be OK for the USB drive to
> be plugged in either USB slots in the back.

lol ... this might be my only chance EVER to correct you on something (unless you were just having a laugh) ... the Mobile only has one USB slot.

But more seriously ... this is a V4 (not Mobile) V4-A3-01 with two USB3.0 (allegedly) slots in the back. I just tried again making sure to put the stick in the top slot, and I've tried it with 2 different USB sticks - one of them is a SanDisk but they're both old, and it wouldn't completely shock me if they were both problematic, but I thought with your new uBoot and the EHCI patch that was less likely to be a problem (look at me pretending like I know what I'm talking about).

I can just install the new rootfs & kernel on my SD card, but I'm guessing whatever is causing this problem with the USB port will cause me more problems when I try to connect my external HD's to the USB ports.

Is it clear, or is there any way to know, whether the message 
scanning usb for storage devices... 0 Storage Device(s) found
means that it's choking on my USB stick, or failing to properly communicate with the USB port?

Related question - If I take a Sandisk USB stick that is right now successfully booting a Pogo-Mobile, should it work to boot a Pogo-V4?

Thank you
-huge
Reply Quote
bodhi
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 05, 2017 11:12PM
huge,

> lol ... this might be my only chance EVER to
> correct you on something (unless you were just
> having a laugh) ... the Mobile only has one USB
> slot.

Right :)

> > I can just install the new rootfs & kernel on my
> SD card, but I'm guessing whatever is causing this
> problem with the USB port will cause me more
> problems when I try to connect my external HD's to
> the USB ports.

It should be less of a problem with USB HDD on all USB ports. The top port (USB 2.0) must be used for rootfs on this box.

> Is it clear

Yes it is clear.

> means that it's choking on my USB stick, or
> failing to properly communicate with the USB port?
>

It is choking on your USB stick only. The port is fine.

>
> Related question - If I take a Sandisk USB stick
> that is right now successfully booting a
> Pogo-Mobile, should it work to boot a Pogo-V4?

It should boot without changing anything. Of course, it would be better if you clone it to a different USB to use for this box, and change the IP addr and hostname.

It is good to try this Sandisk test to prove to yourself that this USB drive is either not good, or the partition you've created for rootfs on this drive was not good.

Further thought: since you have that Sandisk USB that boots perfectly on the Pogo Mobile, you could use this as your reference rootfs, and clone it to any other type of disk drive (USB, SD, HDD) to boot a different Kirkwood box. There is no need to go through the procedure with a new rootfs again, ever. See the Wiki thread;

Quote

http://forum.doozan.com/read.php?2,23630

Backup and Cloning rootfs

CrashPlan 4.3.0
Backup/Restore rootfs using tar command
Adjust udev rules after cloning rootfs
Stock Pogoplug rootfs
How to clone a rootfs from one Kirkwood box to another: Step 1 and Step 2
How to clone SATA rootfs to USB rootfs

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/05/2017 11:17PM by bodhi.
Reply Quote
bodhi
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 05, 2017 11:22PM
Ok I've corrected that link in the Wiki. 

How to clone a rootfs from one Kirkwood box to another: Step 1

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/05/2017 11:33PM by bodhi.
Reply Quote
huge
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 06, 2017 01:04PM
bodhi Wrote:
-------------------------------------------------------
> > means that it's choking on my USB stick, or
> > failing to properly communicate with the USB
> port?
> >
>
> It is choking on your USB stick only. The port is
> fine.
>

It looks like either there is something wrong with the port or (maybe more likely?) something going wrong with uBoot's attempt to access the port. See log below

> >
> > Related question - If I take a Sandisk USB
> stick
> > that is right now successfully booting a
> > Pogo-Mobile, should it work to boot a Pogo-V4?
>
> It should boot without changing anything. Of
> course, it would be better if you clone it to a
> different USB to use for this box, and change the
> IP addr and hostname.
>
> It is good to try this Sandisk test to prove to
> yourself that this USB drive is either not good,
> or the partition you've created for rootfs on this
> drive was not good.
>
> Further thought: since you have that Sandisk USB
> that boots perfectly on the Pogo Mobile, you could
> use this as your reference rootfs, and clone it to
> any other type of disk drive (USB, SD, HDD) to
> boot a different Kirkwood box. There is no need to
> go through the procedure with a new rootfs again,
> ever. See the Wiki thread;
>
>
Quote

> http://forum.doozan.com/read.php?2,23630
>
> How to clone a rootfs from one Kirkwood box to
> another: Step 1 and Step 2
> How to clone SATA rootfs to USB rootfs

Thanks for the cloning link - I've been doing that sort of haphazardly.




OK, so when I boot my V4 from the mmc/SD slot, everything seems to work fine, and once booted I can use both USB slots to access USB sticks & external hard drives.

But when I take the SanDisk USB stick that successfully boots my Mobile, plug it into the V4 and try to boot, I see a very brief blink from the activity light on the USB stick when I power up the V4 and then no light (this is not normal - normally it would be blinking showing that uBoot was trying to talk to it) and then I get the following in netconsole: 
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Card did not respond to voltage select!
mmc_init: -95, time 11
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **
Card did not respond to voltage select!
mmc_init: -95, time 11
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device mmc
Card did not respond to voltage select!
mmc_init: -95, time 11
device mmc 0:1
Card did not respond to voltage select!
mmc_init: -95, time 11
Card did not respond to voltage select!
mmc_init: -95, time 10
** Bad device mmc 0 **
device mmc 1:1
MMC Device 1 not found
MMC Device 1 not found
** Bad device mmc 1 **
device mmc 2:1
MMC Device 2 not found
MMC Device 2 not found
** Bad device mmc 2 **
device mmc 3:1
MMC Device 3 not found
MMC Device 3 not found
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Pogov4>

The same happens with 2 other USB sticks that should have valid rootfs on them.

If I then try to access the USB ports from the Pogov4> prompt, it fails similarly - with either the top or bottom port, and with external USB hard drives: 
Pogov4> usb reset
usb reset
resetting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Pogov4>
Pogov4> usb storage
usb storage
No storage devices, perhaps not 'usb start'ed..?
Pogov4> usb start
usb start
Pogov4> usb reset
usb reset
resetting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Pogov4> usb info
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

Pogov4> usb storage
usb storage
No storage devices, perhaps not 'usb start'ed..?
Pogov4>


It's possible that I haven't booted this V4 from a USB stick in well over a year. Ultimately I don't need to boot from the USB slots as long as they work for external hard drives. But it's worrisome in case of emergencies that I can't plug in a USB stick and boot from it.

Does it make sense that the uBoot system is somehow failing to access the USB ports? Should I go through the process again of installing uBoot after booting from my SD card?

Thanks
Reply Quote
huge
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 06, 2017 02:00PM
Perhaps should have posted printenv output: 
root@debian:~# fw_printenv
arcNumber=3960
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:25:31:05:EA:F4
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.222.164
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.222.168
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15
ncip=192.168.222.165
devices=usb ide mmc
root@debian:~#
Reply Quote
bodhi
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 06, 2017 02:27PM
huge,

> OK, so when I boot my V4 from the mmc/SD slot,
> everything seems to work fine, and once booted I
> can use both USB slots to access USB sticks &
> external hard drives.


This is good. But we want to know: you can use the top USB slot in Debian?


>
> It's possible that I haven't booted this V4 from a
> USB stick in well over a year. Ultimately I don't
> need to boot from the USB slots as long as they
> work for external hard drives. But it's worrisome
> in case of emergencies that I can't plug in a USB
> stick and boot from it.
>

With netconsole or serial console, even with the SD slot failure, you can still boot from network. So no worry.


> Does it make sense that the uBoot system is
> somehow failing to access the USB ports? Should I
> go through the process again of installing uBoot
> after booting from my SD card?
>

Not needed. If the USB 2.0 slot is working in Debian, then it's a different issue. If it does not work in Debian, then I would say it's the HW problem.

I spoke too soon previously! your tests above indicated that u-boot can only see the hub. But not seeing the drive at all. Do you have a USB BT dongle or an extra USB keyboard that you can try?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/06/2017 02:28PM by bodhi.
Reply Quote
huge
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 06, 2017 05:35PM
bodhi Wrote:
-------------------------------------------------------
> you can use the top USB slot in Debian?
>

Yes. Following is with two rootfs USB sticks plugged in (after booting from mmc/SDcard: 
root@debian:~#
root@debian:~#
root@debian:~# fdisk -l
Disk /dev/mtdblock0: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock2: 32 MiB, 33554432 bytes, 65536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock3: 91 MiB, 95420416 bytes, 186368 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0: 7.4 GiB, 7948206080 bytes, 15523840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6e97044e

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1 *     2048 15523839 15521792  7.4G 83 Linux
root@debian:~#
root@debian:~#
root@debian:~# fdisk -l
Disk /dev/mtdblock0: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock2: 32 MiB, 33554432 bytes, 65536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock3: 91 MiB, 95420416 bytes, 186368 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0: 7.4 GiB, 7948206080 bytes, 15523840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6e97044e

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1 *     2048 15523839 15521792  7.4G 83 Linux


Disk /dev/sda: 3.7 GiB, 4004511744 bytes, 7821312 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb51507e4

Device     Boot Start     End Sectors  Size Id Type
/dev/sda1  *     2048 7821311 7819264  3.7G 83 Linux


Disk /dev/sdb: 3.8 GiB, 4051697152 bytes, 7913471 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x31948f83

Device     Boot Start     End Sectors  Size Id Type
/dev/sdb1  *     2048 7913470 7911423  3.8G 83 Linux
root@debian:~#
root@debian:~# mount /dev/sda1 /media/sda1
root@debian:~# mount /dev/sdb1 /media/sdb1
mount: mount point /media/sdb1 does not exist
root@debian:~# mkdir /media/sdb1
root@debian:~# mount /dev/sdb1 /media/sdb1
root@debian:~#
root@debian:~#
root@debian:~# ls -lh /media/sda1
total 96K
drwxr-xr-x 21 root root 4.0K Nov  5 16:19 .
drwxr-xr-x  4 root root 4.0K Nov  6 15:18 ..
drwxr-xr-x  2 root root 4.0K Jul 23 17:12 bin
drwxr-xr-x  3 root root 4.0K Dec 31  1969 boot
drwxr-xr-x  5 root root 4.0K Feb 24  2012 dev
drwxr-xr-x 57 root root 4.0K Dec 31  1969 etc
drwxr-xr-x  2 root root 4.0K Jan 22  2012 home
drwxr-xr-x 14 root root 4.0K Jul 20 01:55 lib
drwx------  2 root root  16K Feb 24  2012 lost+found
drwxr-xr-x  2 root root 4.0K Feb 24  2012 media
drwxr-xr-x  2 root root 4.0K Feb 10  2015 mnt
drwxr-xr-x  2 root root 4.0K Feb 24  2012 opt
drwxr-xr-x  2 root root 4.0K Jan 22  2012 proc
drwx------  5 root root 4.0K Jul 23 18:49 root
drwxr-xr-x  2 root root 4.0K Feb  7  2013 run
drwxr-xr-x  2 root root 4.0K Jul 23 17:12 sbin
drwxr-xr-x  2 root root 4.0K Feb 24  2012 srv
drwxr-xr-x  2 root root 4.0K Dec 31  2010 sys
drwxrwxrwt  2 root root 4.0K Dec 31  1969 tmp
drwxr-xr-x 10 root root 4.0K Feb 24  2012 usr
drwxr-xr-x 11 root root 4.0K Dec 31  1969 var
root@debian:~# ls -lh /media/sdb1
total 96K
drwxr-xr-x 21 root root 4.0K Nov  6 09:51 .
drwxr-xr-x  4 root root 4.0K Nov  6 15:18 ..
drwxr-xr-x  2 root root 4.0K Jul 23 17:12 bin
drwxr-xr-x  3 root root 4.0K Dec 31  1969 boot
drwxr-xr-x  5 root root 4.0K Feb 24  2012 dev
drwxr-xr-x 57 root root 4.0K Dec 31  1969 etc
drwxr-xr-x  2 root root 4.0K Jan 22  2012 home
drwxr-xr-x 14 root root 4.0K Jul 20 01:55 lib
drwx------  2 root root  16K Feb 24  2012 lost+found
drwxr-xr-x  2 root root 4.0K Feb 24  2012 media
drwxr-xr-x  2 root root 4.0K Feb 10  2015 mnt
drwxr-xr-x  2 root root 4.0K Feb 24  2012 opt
drwxr-xr-x  2 root root 4.0K Jan 22  2012 proc
drwx------  5 root root 4.0K Jul 23 18:49 root
drwxr-xr-x  2 root root 4.0K Feb  7  2013 run
drwxr-xr-x  2 root root 4.0K Jul 23 17:12 sbin
drwxr-xr-x  2 root root 4.0K Feb 24  2012 srv
drwxr-xr-x  2 root root 4.0K Dec 31  2010 sys
drwxrwxrwt  2 root root 4.0K Dec 31  1969 tmp
drwxr-xr-x 10 root root 4.0K Feb 24  2012 usr
drwxr-xr-x 11 root root 4.0K Dec 31  1969 var
root@debian:~#



> > it's worrisome
> > in case of emergencies that I can't plug in a
> > USB stick and boot from it.
> >
>
> With netconsole or serial console, even with the
> SD slot failure, you can still boot from network.
> So no worry.
>

Boot from the network!!?! Wow, I should have figured that out a week ago ... lol.

>
> > Does it make sense that the uBoot system is
> > somehow failing to access the USB ports? Should
> > I go through the process again of installing
> > uBoot after booting from my SD card?
> >
>
> Not needed. If the USB 2.0 slot is working in
> Debian, then it's a different issue. If it does
> not work in Debian, then I would say it's the HW
> problem.
>
> I spoke too soon previously! your tests above
> indicated that u-boot can only see the hub. But
> not seeing the drive at all. Do you have a USB BT
> dongle or an extra USB keyboard that you can try?

Yes, I have both ... should I just plug a USB keyboard in and see if the PogoV4> prompt responds to it or do I have to do something with envs to get it to look for a keyboard? I'll just try it - what could go wrong?
Reply Quote
bodhi
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 06, 2017 06:33PM
Nothing will go wrong! Keyboard will tell if this device is enumerated. Execute 

usb start

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/06/2017 06:35PM by bodhi.
Reply Quote
huge
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 06, 2017 09:26PM
bodhi Wrote:
-------------------------------------------------------
> Nothing will go wrong! Keyboard will tell if this
> device is enumerated. Execute
>
> 
usb start

Sadly the results of various USB commands are all unpromising (with the USB stick plugged in to the top port and a keyboard in the bottom, after failing to boot from the USB stick). It certainly does look like it's seeing the hub but not anything plugged into it...
Pogov4> usb start
usb start
Pogov4> usb reset
usb reset
resetting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Pogov4> usb stop
usb stop
stopping USB..
Pogov4> usb start
usb start
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Pogov4> usb info
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

Pogov4> usb part
usb part
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
Pogov4>


Is there a way to debug/trace what is happening successfully in Debian but not in uBoot?

This is probably a dumb question but is there any reason to try rolling back to an older uBoot?


[Edit: I don't *need* to fix this. You've helped me so much with other problems (where I would be dead in the water without your help) that I don't want to take up more of your time with something that I can easily work around. That said, if you're curious to see what's wrong and have suggestions for what I should try, I'm happy to keep exploring it.]



Edited 1 time(s). Last edit at 11/06/2017 10:29PM by huge.
Reply Quote
bodhi
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 07, 2017 12:18AM
hughe,

Quote

This is probably a dumb question but is there any reason to try rolling back to an older uBoot?

That's not a dumb question :) But there is no good reason to flash older u-boot at all.

Remember, we are only interested in the top port, which is USB 2.0. The rear ports are USB 3.0 ports so they will not work during u-boot booting.

The fact that it is OK in Debian to use the top port for the USB drive, then the only explanation is because of your USB drive. Which model and capacity is this drive? also in Debian, what is the output of: 

lsusb -v

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
huge
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 07, 2017 02:03AM
ARRRGGHHH ...
Well, I'm glad I got my fun little moment of pointing out to you that the Mobile only had one USB port, not two ... I've been messing around with my 3 Mobiles so much that I completely forgot that my V4 had a pop-off top with a USB (& SATA) port. Like I said, it's been just sitting there running off of an SD card for well over a year.

It boots fine off the same USB stick that boots the Mobile. Of course.

Sorry to have wasted your time, and mine, mostly yours... Every time I do something stupid with these things I learn a lot getting them running again, but that doesn't stop me feeling bad about ensnaring you with a non-existent problem.
Reply Quote
bodhi
Re: errors on new uBoot "Card did not respond to voltage select", "Bad device usb 0"
November 07, 2017 03:20AM
huge Wrote:
-------------------------------------------------------
> ARRRGGHHH ...
> Well, I'm glad I got my fun little moment of
> pointing out to you that the Mobile only had one
> USB port, not two ... I've been messing around
> with my 3 Mobiles so much that I completely forgot
> that my V4 had a pop-off top with a USB (& SATA)
> port. Like I said, it's been just sitting there
> running off of an SD card for well over a year.
>
> It boots fine off the same USB stick that boots
> the Mobile. Of course.
>
> Sorry to have wasted your time, and mine, mostly
> yours... Every time I do something stupid with
> these things I learn a lot getting them running
> again, but that doesn't stop me feeling bad about
> ensnaring you with a non-existent problem.

:)) it's ok. That happens often, mixing one plug with another.

There was no time wasted with you at all. To me, wasted time is when I tried to help people who are not following instruction and did not provide info that I asked for.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: