Error reading MMC when trying to use MMC as rootfs

[No-0n3]

Hi!

Changed the bootargs for booting linux on orangecrab board in the dts so I could boot into a persistent filesystem on SDcard with ext4. I Can boot from the filesystem when booting from ram. I get this error log when booting from the litexmmc driver until a kernel panic. There is also a strange memory overlap between reserved memory and opensbi memory regions that the boot complains about.

I've built this linux image with buildroot LTS version 2024.02.10, latest stable LTS version.

Board: OrangeCrab 0.2.1 85F

Have attached a complete log when booting, genimage.cfg and dts.

I would like some help in how I can boot with the sd card and solve the problem with the mmc.

term.log

dts.txt

genimage.txt

[enjoy-digital]

Hello @No-0n3,

The rootfs itself seems to mount correctly:

VFS: Mounted root (ext4 filesystem) readonly on device 179:2.

The later panic is a consequence of repeated LiteX MMC timeouts while /sbin/init is being read/executed from the SD card. The first failures are around CMD12/CMD13, then CMD23 and recovery failures, so this looks like an SD-mode transfer robustness issue under sustained rootfs traffic rather than an ext4/genimage problem.

Please also regenerate the DTB with the current tree using:

./make.py --board=orange_crab --rootfs=mmcblk0p2

The attached DTS still contains linux,initrd-start/end, which is why Linux tries to unpack an invalid initrd. Current master omits those entries for mmcblk0p2.

The OpenSBI reserved-memory overlap warning looks separate and does not explain the MMC I/O errors.

A useful next test would be a conservative LiteX MMC driver change that disables multi-block/CMD23 traffic, or limits requests to single-block transfers. That may be slower, but should help confirm whether the issue is the multi-block SD transfer path.