Re: Unexpected RPi5 Behavior with Saved U-Boot Environment

On 21/04/25 12:15, Peter Robinson wrote: Hi Mauro, We recently started using U-Boot on various Raspberry Pi 5 boards with different hardware configurations. While testing, Simon noticed unusual boot failures, such as the kernel failing to boot with no output or U-Boot reporting: "ERROR: Did no

Re: Unexpected RPi5 Behavior with Saved U-Boot Environment

On 27/03/25 17:31, Richard Weinberger wrote: On Donnerstag, 27. März 2025 17:24 Mauro Salvini wrote: could be related tho this [1]? I sent this patch some years ago but was never accepted in u-boot tree. But meta-rpi uses it in u-boot recipe [2]. Uh, good point! In our initial experiments we

Re: Unexpected RPi5 Behavior with Saved U-Boot Environment

On 27/03/25 16:54, Richard Weinberger wrote: Hi! We recently started using U-Boot on various Raspberry Pi 5 boards with different hardware configurations. While testing, Simon noticed unusual boot failures, such as the kernel failing to boot with no output or U-Boot reporting: "ERROR: Did not f

Re: [PATCH] rpi: always set fdt_addr with firmware-provided FDT address

Hi Matthias, On 29/09/21 13:41, Matthias Brugger wrote: Hi Mauro, On 29/09/2021 12:14, Mauro Salvini wrote: Hi Matthias On 15/09/21 13:16, mbrugger at suse.com (Matthias Brugger) wrote: Hi Mauro, On 07/06/2021 11:27, Mauro Salvini wrote: On 12/05/21 14:39, Mauro Salvini wrote: Raspberry

Re: [PATCH] rpi: always set fdt_addr with firmware-provided FDT address

Hi Matthias On 15/09/21 13:16, mbrugger at suse.com (Matthias Brugger) wrote: Hi Mauro, On 07/06/2021 11:27, Mauro Salvini wrote: On 12/05/21 14:39, Mauro Salvini wrote: Raspberry firmware prepares the FDT blob in memory at an address that depends on both the memory size and the blob size [1

Re: U-boot integration in the bootloader process of Rasperry Pi CM4

eded because bootm/bootz/booti u-boot commands needs different image formats (image headers, offsets, etc.) regards -- Mauro Best, Anthony Arrascue On Wed, Jul 7, 2021 at 2:15 PM Mauro Salvini <mailto:m.salv...@koansoftware.com>> wrote: On 07/07/21 10:05, Anthony Arra

Re: U-boot integration in the bootloader process of Rasperry Pi CM4

h for your help! [1] https://andrei.gherzan.ro/linux/uboot-on-rpi/ -- Mauro Salvini | KOAN sas | Bergamo - Italia embedded software engineering Phone: +39 035-255235 http://KoanSoftware.com

Re: [PATCH] rpi: always set fdt_addr with firmware-provided FDT address

On 12/05/21 14:39, Mauro Salvini wrote: Raspberry firmware prepares the FDT blob in memory at an address that depends on both the memory size and the blob size [1]. After commit ade243a211d6 ("rpi: passthrough of the firmware provided FDT blob") this FDT is passed to kernel throug

[PATCH] rpi: always set fdt_addr with firmware-provided FDT address

ion always overwrite fdt_addr value. [1] https://www.raspberrypi.org/forums//viewtopic.php?f=107&t=134018 Signed-off-by: Mauro Salvini Cc: Cédric Schieli Cc: Matthias Brugger --- board/raspberrypi/rpi/rpi.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/board/raspberrypi/rpi/rpi.c b/board/r

Boot does not work when changing default dts

Hi, I also wrote on RPI forums [1] to discuss about this problem. I'm using a CM4 module on CMIO board, with an image built by Yocto (dunfell version) and containing u-boot version 2020.01. When I add some overlays via config.txt file, or I change the original Linux dts and rebuild its dtb,