Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 6 Dec 2023 11:02:41 -0800
From:      bob prohaska <fbsd@www.zefox.net>
To:        Bob Bishop <rb@gid.co.uk>
Cc:        "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: RPi2 USB boot problems, maybe hardware?
Message-ID:  <ZXDFUZVpPY/x/OXa@www.zefox.net>
In-Reply-To: <A06B3439-F423-42DE-BC8B-104276C2EFBA@gid.co.uk>
References:  <ZXCfBAxWoGNuDyuZ@www.zefox.net> <A06B3439-F423-42DE-BC8B-104276C2EFBA@gid.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 06, 2023 at 04:37:39PM +0000, Bob Bishop wrote:
> Hi,
> 
> > On 6 Dec 2023, at 16:19, bob prohaska <fbsd@www.zefox.net> wrote:
> > 
> > Since a recent build/install cycle a Pi2 v1.1 (armv7) has stopped
> > booting stable/14.
> > [ ... ]
> > The failure to enumerate more USB devices seems odd.
> > [ ... ]
> > 
> > Thanks for reading, any suggestions appreciated!
> 
> Check your power supplies.

With the machine up, running and idling I see 5.06 volts.
When shutdown -r is issued on the console the voltage
rises to 5.13 with the red power LED on steadily. 

Meanwhile, the Pi reports

root@www:~ # shutdown -r now
Shutdown NOW!
shutdown: [pid 1420]
root@www:~ #                                                 Stopping apache24.
Waiting for PIDS: 1093.
Stopping cron.
Waiting for PIDS: 1078.
Stopping sshd.
Waiting for PIDS: 1075.
Stopping devd.
Waiting for PIDS: 774.
Writing entropy file: .
Writing early boot entropy file: .
.
Terminated
Dec  6 10:40:25 www syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop... 
Syncing disks, vnodes remaining... 0 0 done
All buffers synced.
Swap device da0s2b removed.
Uptime: 2h35m33s
Resetting system ... 

U-Boot 2023.07.02 (Aug 25 2023 - 05:50:16 +0000)

DRAM:  948 MiB
RPI 2 Model B (0xa21041)
Core:  75 devices, 12 uclasses, devicetree: board
MMC:   mmc@7e300000: 1
Loading Environment from FAT... ** Bad device specification mmc 0 **
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
Bus usb@7e980000: USB DWC2
scanning bus usb@7e980000 for devices... cannot reset port 1!?
1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
MMC Device 0 not found
no mmc device at slot 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
No EFI system partition
No EFI system partition
Failed to persist EFI variables
BootOrder not defined
EFI boot manager: Cannot load any image
MMC Device 2 not found
no mmc device at slot 2

Device 0: unknown device
No ethernet found.
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
Retrieving file: pxelinux.cfg/000000
No ethernet found.
Retrieving file: pxelinux.cfg/00000
No ethernet found.
Retrieving file: pxelinux.cfg/0000
No ethernet found.
Retrieving file: pxelinux.cfg/000
No ethernet found.
Retrieving file: pxelinux.cfg/00
No ethernet found.
Retrieving file: pxelinux.cfg/0
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-bcm283x-rpi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-bcm283x
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.
U-Boot> 

usb info reports only the hub:
U-Boot> usb info
1: Hub,  USB Revision 1.10
 -  U-Boot Root Hub 
 - Class: Hub
 - PacketSize: 8  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 0.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 2 Interval 255ms

U-Boot> 

This doesn't look like a power supply problem to me. 
The Pi gets far enough to spin up the disk, find 
u-boot and run it. Only then does it run into trouble.

The error messages that are presented are always so.
Perhaps they're symptoms of some other, underlying,
problems?

Thanks for reading!

bob prohaska




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZXDFUZVpPY/x/OXa>