On Saturday, February 17th, 2024 at 1:55 PM, Jojan <jjva...@yahoo.com> wrote:
> For RPi 5B you need bcm2712 device tree . RPi4 uses 2711. > So the e rpi_arm64_confi does not work for RPi5 > Which config target did you build or did you modify rpi_arm64_config? If so, can you share the diff? You mentioned modifying "the config" in your message below. > Also make sure that you have the changes discussed here.[GIT PULL] rpi: > updates for v2024.04 (mail-archive.com) I built from the master branch of the github mirror. That should have these changes incorporate, no? https://github.com/u-boot/u-boot/commits/master/ > Iwas able to get the git > (https://source.denx.de/u-boot/custodians/u-boot-raspberrypi.git > tags/rpi-next-2024.04) > > and modify the config to get 2712 dts file, and able to get u-boot. > [GIT PULL] rpi: updates for v2024.04 > > > > > > > > On Saturday, February 17, 2024 at 08:36:22 AM PST, John > <therealgray...@proton.me> wrote: > > > I am running Arch ARM on a RPi4B and also on a RPi5B. My RPi4B can boot the > vanilla kernel package (linux-aarch64) with the latest uboot-raspberrypi > (2024.04-rc2) just fine. Yet, if I take that uSD card and place it in my > RPi5B, it does not boot. I only see the "U-Boot" submarine logo in the upper > right of the screen/no debug output. Any thoughts are appreciated. > > I built u-boot like this: > > unset CFLAGS > unset CXXFLAGS > unset CPPFLAGS > > make rpi_arm64_config > echo 'CONFIG_IDENT_STRING=" Arch Linux ARM"' >> .config > make EXTRAVERSION=-2024.04rc2
