meta-raspberrypi icon indicating copy to clipboard operation
meta-raspberrypi copied to clipboard

No display output on a Raspberry Pi 0W - honister

Open sm-oralnum opened this issue 3 years ago • 13 comments

I do am building image on a raspberry pi zero w. After flashing the image on the raspberry, i don get anything on the screen. I am doing this the honister branch. I had the gatesgarth branch and it was working perfectly. I tried many thing but i can't get to work. i have literally the same code on a raspberry pi zero w 2 and it works perfectly. I am only changing the name of the machine (raspberrypi0-wifi ) to get to work. Do you have an idea why ? I have the sensation that it is booting because the green led is flashing but i don't have anything on the screen.

sm-oralnum avatar Feb 22 '22 14:02 sm-oralnum

Please set up an SSH/serial connection and debug the services a bit at runtime. Just to understand, on honister if you build your image for 0w2 you get display output but you don't get any if you build it for 0w, right?

agherzan avatar Feb 22 '22 16:02 agherzan

Also, please improve the issue title - you can see how non-descriptive it is.

agherzan avatar Feb 22 '22 16:02 agherzan

it is booting because the green led is flashing but i don't have anything on the screen.

Please set up an SSH/serial connection and debug the services a bit at runtime. Just to understand, on honister if you build your image for 0w2 you get display output but you don't get any if you build it for 0w, right?

yeah, i don't have any display on a 0w

sm-oralnum avatar Feb 22 '22 16:02 sm-oralnum

@sm-oralnum In that case try to attach a serial console to the board and check if it boots. Are you using uboot?

agherzan avatar Feb 23 '22 10:02 agherzan

@sm-oralnum In that case try to attach a serial console to the board and check if it boots. Are you using uboot?

with the last commit ( migrating to 5.10.83), i did a pull request. Now i have a hdmi display. But i have please wait : booting and it it is blocked there without advancing. Do you have an idea why it is doing that ?

sm-oralnum avatar Feb 24 '22 13:02 sm-oralnum

It sounds like the kernel image is not valid/available.

agherzan avatar Feb 24 '22 23:02 agherzan

Reference in n Do you have a solution to this ?

sm-oralnum avatar Feb 28 '22 14:02 sm-oralnum

@sm-oralnum I don't know what is going on to be able to provide a solution. You will need to debug it a bit.

agherzan avatar Feb 28 '22 15:02 agherzan

@sm-oralnum I don't know what is going on to be able to provide a solution. You will need to debug it a bit.

I know now that i can have a normal boot if i don't add bluetooth or wifi recipes. Do you have an idea why ?

sm-oralnum avatar Mar 01 '22 11:03 sm-oralnum

Without seeing some serial logs it's very hard to say. It sounds like the kernel panics with those devices enabled.

Are you saying that without BT/WiFi firmware the boot proceeds and you get console logs on HDMI?

agherzan avatar Mar 01 '22 11:03 agherzan

Without BT/WIFI I don't have console logs but the boot proceeds.

sm-oralnum avatar Mar 01 '22 12:03 sm-oralnum

OK. Attach a serial please and come back with logs.

agherzan avatar Mar 01 '22 14:03 agherzan

i have nothing to attach a serial consol. I did find that i have a problem when i add packagegroup-base and packagegroup-base-bluetooth to the image with CORE_IMAGE_EXTRA_INSTALL. Do you have an idea how i can have the boot logs ? I have the same system with the raspberry pi zero w 2 and i have the logs. It is only with the raspberry pi zero that i don't have the logs. When i eliminated the recipes one by one, i found out that when i add packagegroup-base and packagegroup-base-bluetooth, i got blocked on the boot.

sm-oralnum avatar Mar 01 '22 14:03 sm-oralnum