Deutsch English Français Italiano |
<vrug9a$3679p$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Chris Townley <news@cct-net.co.uk> Newsgroups: comp.sys.raspberry-pi Subject: Re: Pi2 bootcode.bin puzzle Date: Tue, 25 Mar 2025 14:57:45 +0000 Organization: A noiseless patient Spider Lines: 97 Message-ID: <vrug9a$3679p$1@dont-email.me> References: <vrufnd$3hlnn$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Tue, 25 Mar 2025 15:57:47 +0100 (CET) Injection-Info: dont-email.me; posting-host="b9cef43af2efd21014715f5e7cfa18e9"; logging-data="3349817"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19InT3SxpMindxz8sHJLaF/GaUBwkfOMCk=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:Nz9XG53MC8/evQ6VoGUt3Dba+5o= In-Reply-To: <vrufnd$3hlnn$1@dont-email.me> Content-Language: en-GB On 25/03/2025 14:48, bp@www.zefox.net wrote: > Twice now a Paspberry Pi 2 v1.1 using the bootcode.bin-only > method to boot from usb mass storage has abruptly > stopped finding the mass storage device, or so it seems. > > The machines are actually running freebsd, but the failures > are seemingly too early in the boot process to get anywhere > close to freebsd files. > > In both cases, the failures occurred "out of the blue" during > a normal reboot with no change to the system. I've monitored > power supply voltage during boot, it stays above 5.2 volts, > measured via one of the usb ports, on both powered hub and Pi2. > > Here's a transcript: > > > > Raspberry Pi Bootcode > > Found SD card, config.txt = 0, start.elf = 0, recovery.elf = 0, timeout = 0 > Trying USB > Set address 4 > Num devices = 1, addr = 4 > get_config_descriptor 41 bytes > Initialise hub > Found 5 ports, multi_tt = 1 > Setting interface 0 > Enabling PORT POWER on port 1 > Enabling PORT POWER on port 2 > Enabling PORT POWER on port 3 > Enabling PORT POWER on port 4 > Enabling PORT POWER on port 5 > Waiting for devices to respond to reset > Found device on port 1 > Found highspeed device > Set address 5 > Num devices = 2, addr = 5 > get_config_descriptor 39 bytes > device class = 255 > Device found: type = Ethernet adapter, addr = 5 > Found device on port 3 > Found highspeed device > Set address 6 > Num devices = 3, addr = 6 > get_config_descriptor 41 bytes > device class = 9 > Hub device found at addr 6, enumerating HUB > Initialise hub > Found 4 ports, multi_tt = 1 > Setting interface 0 > Enabling PORT POWER on port 1 > Enabling PORT POWER on port 2 > Enabling PORT POWER on port 3 > Enabling PORT POWER on port 4 > Waiting for devices to respond to reset > Found device on port 3 > Ignoring low speed device > Found device on port 2 > Ignoring low speed device > Found device on port 4 > Ignoring low speed device > Found device on port 4 > Device failed to respond to reset > Trying booting from Ethernet device addr 5 > > At this point the Pi goes into a netboot loop. It doesn't seem to > activate the disk drive apart from one blink of the activity LED. > > The Pi still boots from a Bookworm microSD, so > it doesn't look like a broken Pi2. I've been > using the version of bootcode.bin linked at > https://github.com/raspberrypi/firmware/blob/master/boot/bootcode.bin > from the page at > https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#raspberry- > pi-boot-modes > but didn't change anything betwen working and not. > > I notice that the narrative at that page is somewhat tangled. > > In one, and so far only one, instance the Pi booted sucessfully > during a sequence of tests while makeing and re-making USB connections. > That led me to suspect a loose plug, but multiple repetitions, moving > all plugs, didn't repeat the success. > > Can bootcode.bin pick up any parameters (other than noting the > presence of a timeout file) from any files placed on the microSD? > > Thanks for reading, > > bob prohaska > Have tried another known good USB cable? -- Chris