Cant boot
-
Pi 4
PSU tried 5V3A and 5V6A
Retropie version 4.7.1
Built from a Surface Pro 7, tried Raspberry Pi Imager and Etcher, same results
USB devices connected: had some controllers but pulled just in case. Just keyboard and mouse.
I've tried deleting all volumes on disk part and trying over. Did not work.
I have tried a 32GB and 128GB microSD card. Both give me the same results.Any tips?
More info: red light is consistent on. doesn't seem to be an issue with the pi itself. God I hope not, I bought it over a year ago and it sat in the box so I can't return or exchange it at this point.
-
If you insert the sdcard back into your PC, do you see the
boot
partition with the files there (config.txt
,cmdline.txt
, etc.) ? -
@mitu yes, both txt files are there.
-
figure ill add a bit more info so here's the status of the 32GB boot media i made
and the txt files present in the boot partition
-
Looks like the image was written correctly on the sdcard, so that's not the problem here. Haven't seen this error yet, assuming it's not the power source, you could try updating the Pi's boot EEPROM first and try again.
-
and the txt files present in the boot partition
what i find a bit odd in the image you posted is that bootcode.bin and COPYING.linux both have file extensions ... but cmdline and config are both missing the .txt extension :/
they should look like config.txt and cmdline.txt
-
@dreamcastkid said in Cant boot:
they should look like config.txt and cmdline.txt
Windows 10, by default, hides extensions for known file types. If you look at the 3rd column, you'll see they're labeled 'Text Document' and the file type icon is a text file.
-
I tried the EEPROM thing. It didn't really change how the pi behaves.
I'm assuming that the flashing green light and the green screen on display means it's completed successfully. If I put the SD card in after power it on though I do get some concerning error messages.
VL805 EEPROM is up to date
recover4.elf not found (6)
recovery.elf not found (6)
start4.elf not found (6)
Firmware not found
ERROR 00000004Not sure how relevant this is. Either way, after the whole green screen thing I tried the retropi image and its giving me the same errors in the initial post.
I was concerned that my microSD reader/writer was defective as it was having some issues, but I'm trying today on a new device that is writing smoothly. No differences.
At this point I'm thinking it's the pi itself. No blinking red light error codes though.
-
Update: It seems to be working.
I more or less tried everything exactly the same way I've been trying it so far, but with one minor difference.
I tried using the download and flash option from Raspberry Pi Imager, rather than the local image from the download page. I'll have to mess around with it a bit more later but for now I think its been resolved.
-
Windows 10, by default, hides extensions for known file types. If you look at the 3rd column, you'll see they're labeled 'Text Document' and the file type icon is a text file.
oh, ok ... i'm using Windows 7 and have that setting Off because it make renaming files and extensions a pain.
-
@kitaek27 Glad you got it working.
One advantage when using the Raspberry Pi Image is that you don't need to download the image, the program will do it for you and automatically check the image file against its checksum.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.