Hi, > Am 17.01.2024 um 16:07 schrieb Ivan T. Ivanov <iiva...@suse.de>: > > On 01-12 14:10, Jens Maus wrote: >> >> Hi Ivan, >> >> first of all, thanks for the updated rpi5 patchset. However, I am unable to >> reproduce that it is actually working as you suggest. Could you please >> quickly elaborate on your test environment and the test config.txt for the >> RaspberryPi5? Here I have compiled U-Boot 2024.01 with your patches applied >> and using the „rpi_arm64_defconfig“, put the u-boot.bin file on the sd card >> and then added „kernel=u-boot.bin“ to the config.txt file. The environment I >> am using is a buildroot-based system which boots nicely with the default >> RaspberryPi boot loader and a RaspberryPi5. However, as soon as I replace >> the „kernel=Image“ line with „kernel=u-boot.bin“ the system stalls and there >> is no HDMI output (nor any console output) with the u-boot 2024.01 version >> and your patches applied. >> > > Yes, I am using rpi_arm64_defconfig for building the U-Boot. > And as I wrote in the cover letter I am using openSUSE Tumbleweed > image[1], [2]. Once you copy image to uSD card mount EFI uSD > partition and copy new u-boot.bin over existing one. That > it is. Just make sure you clearly sync, unmount the card. > You can find config.txt file in the EFI partition.
That’s in fact exactly what I was also trying in addition to get u-boot running with your patches in my own buildroot-based environment. So I was also exactly using this Tumbleweed rpi4 image and simply replaced the u-boot.bin file with my own build version which I built with your patches applied and using the rpi_arm64_defconfig as the build config. However, there is still no output on any of the HDMI ports. Haven’t tried to see if there is any serial output on the special UART debug port of the rpi5. Should there be any output at all? Best Regards, Jens -- Jens Maus, Dresden/Germany http://jens-maus.de/
