#HA Yellow Not Booting – Solid Green D5 LED

1 messages · Page 1 of 1 (latest)

granite bramble
#

Hi!

I'm having trouble getting my new HA Yellow to boot properly. The green D5 LED keeps blinking, but nothing else seems to happen.

I'm using a CM5 (no eMMC) with 16GB RAM, along with a Samsung EVO SSD. I flashed an older USB drive using the Raspberry Pi Imager, but when I plug it in, the activity light stays solid green and the system doesn’t seem to start.

Has anyone experienced this before or have any suggestions?

Thanks in advance for your help

gusty igloo
#

Is the CM4 fully inserted in its sockets?
I can also see no USB stick on your image.

#

And are you sure you are using a CM4 and not a CM5?

granite bramble
#

It's a CM5, sorry 🙂

gusty igloo
#

That explains it. CM5 does not support the USB installer method.
You can either flash the OS (not the installer) to the NVMe directly with a USB adapter or use the Yellow with rpiboot.

granite bramble
#

Ah I see

#

Thanks, I will let you know the results 🙂

#

Appreciate!

granite bramble
#

Hmmm. I did change the jumper to usb and pushed the usb recovery button prior to plug in the power

#

Stays in the waiting state

gusty igloo
#

Hold the button when powering it up.

granite bramble
#

Ah, it did work. Caveat was that usb c cable was already plugged in

granite bramble
#

I don't think RPIboot did what it had to do. I saw that it ran yesterday, but it didn't pop up in my Raspberry Pi Imager.

When i connect HA Yellow to my PC via USB-c, it doesn't get recognized in USB mode. When it is in UART-mode I see a unknown device popping up in the Device Manager

gusty igloo
#

Rpiboot needs to be used with the mass storage option to show the NVMe.
rpiboot -d mass-storage-gadget64

granite bramble
#

That doesn't work. I've set my JP1 to USB. If it is set to UART I hear a bleep in Windows. If it is set to USB I don't hear that bleep.

gusty igloo
#

UART is the serial console discovered in Windows.

#

It needs to be in USB position and in recovery mode by using the button. If it really doesn't work with rpiboot or rpiboot -d mass-storage-gadget64, using a NVMe to USB adapter is likely the easiest way to flash the OS to it.

granite bramble
#

It is on USB position. Setting it to UART gives me a device in device manager. So can I assume my hardware is not defect then?

gusty igloo
#

As I said, the device discovered in UART mode is the serial console (just missing the driver) and absolutely expected behavior.

granite bramble
#

Okay, good to know 🙂

#

Also, i plugged in my ZPI-7 and the leds do work. So I think I'll have to go the nvme adapter route

gusty igloo
#

It is the easiest way. Rpiboot is a bit tricky sometimes.

granite bramble
#

I was scared that my CM5 was not positioned well, but that is not the case I think

gusty igloo
#

It might be. You can apply some slight pressure on the heatsink (while holding it, so it doesn't bend).

granite bramble
#

It worked! so i fixed this by apply some light pressure on the heatsink and making sure the ssd was installed properly. I didn't have to rpiboot anymore, It got detected by windows straight away!

#

Thank you @gusty igloo . Really appreciate your help!

#

So, I have an 16gb model. But HA only detects 8gb of ram
https://github.com/home-assistant/operating-system/pull/4045

Looks like this issue has been fixed, but Home Assistant OS hasn't been updated since April. Will I be able to update HA OS once I've setup everything?

GitHub

U-Boot defconfig used for Yellow checks only 4 DRAM banks, however, CM5 with 16 GB has the memory spread across 8 banks. Add a patch (submitted upstream) to the defconfig to get access to the whole...

gusty igloo
#

The HAOS update has not been rolled out yet. It will show up like every other HA update.