Okay, so my pi won't boot from SD card (or anything really) but this is different. First, I tried updating the EEPROM with USB boot support through recovery. But the ACT led stayed on eternally, and I do mean eternally (I waited for 4 hours and it was still on). Rebooting it changed nothing, 3 long flashes and 1 short flash. Which was weird because I could not find that LED sequence anywhere. (which I found out today was a SPI EEPROM error https://www.raspberrypi.com/documentati ... lash-codes)
Now that wouldn't be a issue because I remember enabling USB boot, except for reasons explained later on that wouldn't exactly work.
For a bit of context, back in 2021 I was frantically swapping the SD card between my laptop and the rpi because I had broken fstab and was trying to fix it. Later that day, I was running Kodi and next day when I put power through it finally stopped booting. (I can't exactly remember if it was after restarting on the same day or next day)
My first suspect is that the problem was the SD card, but using another SD card didn't work either. Second suspect is that the microSD card slot was broken (it wasn't), which was the theory I ran with for like an year before investigating further
Note that, months before the rpi was already showing signs of failure, first of all the wireless module was pretty weird (it would completely stop working for 15 minutes if I downloaded OR uploaded too much data (like around 30-50MB)) and second of all sometimes it failed to boot, though I could just cycle the power and it would boot. (not for much longer though)
Last year, I found out it was possible to boot the rpi from USB-C (through this post: viewtopic.php?t=278537) and that gave me a slight glimmer of hope I could get this rpi to a functional state again, grounding the pin in question worked and I managed to get it to USB host mode. However after pushing the recovery bootcode through usbboot, it gave the same result as using a recovery SD card. (3 long flashes, 1 short flash)
Even after trying the embedded rpi imager on usbboot it gave the same result, and no HDMI output. (also the EEPROM version is from before HDMI diagnostics was on stable)
Now, while the wireless module is rusty (probably due to the fact I had the cooler on the wrong side for 1 year, whoops) nothing else seems to be so I don't think that's related.
I'm posting this here because at this point, I have no idea what to do.
A few options I thought of were:
- Using a external EEPROM programmer to try flashing a ROM properly (not gonna happen, that thing is WAAAY too tiny)
- debugging with a UART serial (gonna need an adapter for that, and it also looks like the EEPROM won't output anything unless specified on the configuration)
At least the first stage bootloader seems to be working, but not the second?
Now that wouldn't be a issue because I remember enabling USB boot, except for reasons explained later on that wouldn't exactly work.
For a bit of context, back in 2021 I was frantically swapping the SD card between my laptop and the rpi because I had broken fstab and was trying to fix it. Later that day, I was running Kodi and next day when I put power through it finally stopped booting. (I can't exactly remember if it was after restarting on the same day or next day)
My first suspect is that the problem was the SD card, but using another SD card didn't work either. Second suspect is that the microSD card slot was broken (it wasn't), which was the theory I ran with for like an year before investigating further
Note that, months before the rpi was already showing signs of failure, first of all the wireless module was pretty weird (it would completely stop working for 15 minutes if I downloaded OR uploaded too much data (like around 30-50MB)) and second of all sometimes it failed to boot, though I could just cycle the power and it would boot. (not for much longer though)
Last year, I found out it was possible to boot the rpi from USB-C (through this post: viewtopic.php?t=278537) and that gave me a slight glimmer of hope I could get this rpi to a functional state again, grounding the pin in question worked and I managed to get it to USB host mode. However after pushing the recovery bootcode through usbboot, it gave the same result as using a recovery SD card. (3 long flashes, 1 short flash)
Even after trying the embedded rpi imager on usbboot it gave the same result, and no HDMI output. (also the EEPROM version is from before HDMI diagnostics was on stable)
Now, while the wireless module is rusty (probably due to the fact I had the cooler on the wrong side for 1 year, whoops) nothing else seems to be so I don't think that's related.
I'm posting this here because at this point, I have no idea what to do.
A few options I thought of were:
- Using a external EEPROM programmer to try flashing a ROM properly (not gonna happen, that thing is WAAAY too tiny)
- debugging with a UART serial (gonna need an adapter for that, and it also looks like the EEPROM won't output anything unless specified on the configuration)
At least the first stage bootloader seems to be working, but not the second?
Statistics: Posted by nicejs — Wed Feb 28, 2024 9:02 pm