Closed kkettinger closed 1 year ago
The first thing to try is to use a minimum layers setup and a basic image. Does that work out of the box?
I found out that one RPI was defective, i've applied too high voltage on one pin (12V). It still boots fine without U-Boot. It can be closed, sorry for the issue.
How come they were both working with Raspbian though?
My best guess is the UART is faulty and interrupts the boot process in u-boot by spitting out random chars, which u-boot picks up and enters the prompt (U-Boot>). Do you know what raspbian is using as bootloader? I think it might be grub, but i'm not sure.
Got it. I think they use the rpi bootloader directly (but I could be wrong).
I'm building an image with yocto and meta-raspberrypi, which worked fine until I built the last image.
On one RPI it boots fine, but on the other I get this error at boot:![grafik](https://user-images.githubusercontent.com/83078716/214288024-fbc41347-b9b3-43cf-be89-95966de599a9.png)
This is the boot process on the working RPI:![grafik](https://user-images.githubusercontent.com/83078716/214289634-d80c001c-8030-482a-85fa-f73ff98d696e.png)
It seems that something is getting into the u-boot console and writing random stuff into it, preventing it from booting. No peripherals are connected.
Raspbian works fine on both Raspberries.
Here is the build configuration: