Rpi4 No Boot SD Card Problem
Joined: 2012-Mar-11 Sun 8:19 am
Location: South Holland, The Netherlands
RE: STICKY: IS YOUR PI NOT BOOTING? (THE BOOT PROBLEMS STICKY)
Postby mahjongg » 2019-Jun-26 Wed 5:39 am
This information is written especially for the RPI 4B.
Currently (end of august 2016) there seems to be an issue with some 32GB cards that expresses itself with that the boot aborts. The four raspberry’s appear followed by a short burst of text, then the system halts. This issue is being investigated, see this thread: https://www.raspberrypi.org/forums/view … 8&t=248968 in the mean time, if you have this exact problem, I would suggest using a 16GB card
Firstly, the new RPI4 will ONLY boot the version of raspbian that was released at its time of launch (or later) Rasbian Buster, it won’t boot any older versions!
Unlike previous Raspberry PI’s the RPI4B boots with the use of code from a built in EEPROM, that means it can use more complex boot code with more flexibility, and the ability to add new features.
consequently when the new bootcode doesn’t detect a valid start.elf file on the SD-card it will blink the activity LED, four times with an interval between the four blinks, (bootcode.bin is no longer used, and is ignored when it exists on the SD-card).
Its very-very unlikely the EEPROM content is corrupted, but to check if this the case, unplug everything from the Raspberry Pi 4, including the SD card, and then turn the power back on.
If the green LED blinks with a repeating four blink pattern then the bootloader is running correctly, and indicating that start.elf has not been found.
Not blinking four times with nothing but the power connected (and no SD-card) implies that the bootloader is not working correctly and should be reinstalled using recovery.bin. see https://www.raspberrypi.org/documentati … teeprom.md
if after recovery your PI still doesn’t blink the ACT LED, then you can assume you somehow managed to blow up your PI, The common pitfalls sticky in beginners, (post #27) describes things that can lead to the destruction of your RPI, for example changing breadboard wiring without turning the RPI off first.
So unlike other RPI’s blinking the ACT LED (in a regular pattern) now doesn’t mean the SD-card is detected and is booting, instead it means the EEPROM code cannot find the SD-card (start.elf).
LED warning flash codes
If a Pi fails to boot for some reason, or has to shut down, in many cases an LED will be flashed a specific number of times to indicate what happened. The LED will blink for a number of long flashes (0 or more), then short flashes, to indicate the exact status. In most cases, the pattern will repeat after a 2 second gap.
led blink warnings.PNG
led blink warnings.PNG (23.97 KiB) Viewed 37078 times
if the ACT LED blinks in a regular four blink pattern, it cannot find bootcode (start.elf)
if the ACT LED blinks in an irregular pattern then booting has started.
If the ACT LED doesn’t blink, then the EEPROM code might be corrupted, try again without anything connected to make sure.
As always, if the PWR LED goes of (blinks) you have an unfit power supply/power cable.
If you don’t get a picture out of your HDMI monitor you might want to try it with the primary HDMI port, which is the one located near the USB-C power port.
Also, for first use start with software that is known to work, that is the latest version of
Raspbian (Buster) freshly downloaded from here: https://www.raspberrypi.org/downloads/raspbian/ and imaged with Etcher.
Other older Raspbian images are probably incompatible, and other OS’s (Ubuntu’s) are probably not yet updated for the RPI4. that will come later.
Booting from USB is worked on, (new Boot EEPROM code update) and older methods may not work.
In fact the boot code is still being worked on, and bugs might exist, so if you have trouble booting try to remove all USB devices. Reports are in that some wireless USB keyboards prevent booting.