On Tue, May 23, 2023 at 1:16 PM Stefan Wahren <stefan.wah...@i2se.com> wrote:
> Because we stuck in this discussion, can you please provide more > information to reproduce this issue? > > What is the exact behavior based on debug UART and LED when Linux fails > to start from eMMC (timeout, SoC lockup, ...)? > Kernel says: sdhost-bcm2835 3f202000.mmc: loaded - DMA enabled (>1) Waiting for root device /dev/mmcblk0p3... sdhost-bcm2835 3f202000.mmc: sdhost_busy_irq: intmask 00000410 Other boot messages continue, but the rootfs is never found so eventually it hangs. > > Does your boot setup (U-Boot) based on Device tree (Mainline or RPF) or > EFI? > > DT mainline with some aliases and __overrides__ for the firmware to set up uart and watchdog. > Which Raspberry firmware version are you using? > Buildroot default, 3f20b832b27cd730deb6419b570f31a98167eef6 (Jan 17, 2022) > What settings of config.txt do you use? > arm_64bit=1 gpu_freq=250 gpu_mem=16 device_tree=bcm2837-rpi-cm3-io3.dtb dtoverlay=uart1,txd1_pin=32,rxd1_pin=33 dtparam=uart0=off dtparam=watchdog kernel=u-boot.bin > > Are you able to reproduce this issue on other RPi variants? > I found the issue on the CM3 and CM3+. In addition I tested the RPi 1 Model A and it is NOT affected. Thanks