Problem with U-boot | Configuration Signature not being checked while booting

[Mark Kettenis]

> From: Moiz Imtiaz <moizimtiaz1 at gmail.com>
> Date: Sat, 11 Sep 2021 23:19:05 +0500
> 
> Hi Simon,
> 
> Thanks for the reply.  I already followed the steps mentioned in
> "doc/uImage.FIT/beaglebone_vboot.txt".
> 
> >I wonder if rpi is not using the devicetree compiled with U-Boot, but
> instead one provided by the earlier-stage firmware?
> 
> Not sure, but seems like this is the case. I checked and there isn't any
> dtb or dts for rpi4 (bcm2711-rpi-4-b) in arc/arm/dts in u-boot. I tried to
> add the dtb and other dts dtsi
> <https://github.com/raspberrypi/linux/tree/rpi-5.10.y/arch/arm64/boot/dts/broadcom>files
> from the raspberry pi Linux and compile them with CONFIG_OF_SEPARATE and
> CONFIG_OF_EMBED (one at a time) *but it couldn't even boot the U-Boot and
> it would just give a blank screen*. I wonder why there isn't any device
> tree in the U-boot repo for RPI4. Is U-boot control FDT not supported by
> RPI4?

The issue with the rpi4 is that the addresses of devices move around
based on the version of the Raspberry Pi firmware you're using.  And
possibly on the amount of memory on the board as well.  So U-Boot
pretty much has to use the device tree passed by the firmware since
the device tree in the U-Boot tree would be wrong for many
combinations of firmware and hardware.

Simon, this sort of thing is exactly the reason why I think the idea
of having all U-Boot configuration information in a single device tree
with the hardware description doesn't work everywhere.