On 2026-01-30, Peng Fan wrote: > On Thu, Jan 29, 2026 at 05:46:43PM -0800, Vagrant Cascadian wrote: >>Thanks for adding support for rk3588 MNT Reform2! >> >>I tried using u-boot 2026.01 with the rk3588 MNT Reform2, but it only >>gets as far as SPL, and then fails: >> >> U-Boot SPL 2026.01 (Jan 01 1970 - 00:00:01 +0000) >> Trying to boot from MMC1 >> mmc_load_image_raw_sector: mmc block read error >> Error: -38 >> SPL: Unsupported Boot Device! >> SPL: failed to boot from all boot devices >> ### ERROR ### Please RESET the board ### >> >>I *think* MMC1 is eMMC, which I currently have blanked, as recovering >>from a failed install on eMMC is trickier. >> >>The vendor u-boot works fine on either eMMC or SD. >> >>Any suggestions to get it to support booting off SD card? > > Please check whether you have this patch in your tree: > > commit c4f5b1d4b037beeb538cf6dee0a16cd196539273 > Revert "mmc: mmc-uclass: Use max-frequency from device tree with default > handling" > > This reverts commit aebb523a23818a8ee4199c9532b51e3d4020696f.
Thanks for the suggestion! Just tested with v2026.04-rc1, which appears to contain both if I am reading this right:: git describe --contains c4f5b1d4b037beeb538cf6dee0a16cd196539273 v2026.04-rc1~56^2 git describe --contains aebb523a23818a8ee4199c9532b51e3d4020696f v2026.04-rc1~52^2~23^2~7 But the behavior was about the same: U-Boot SPL 2026.04-rc1 (Jan 01 1970 - 00:00:01 +0000) Trying to boot from MMC1 mmc_load_image_raw_sector: mmc block read error Error: -38 SPL: Unsupported Boot Device! SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### There are 63 commits since v2026.04-rc1 currently on master, but nothing immediately leaps out as relevent to my untrained eyes... :) I could test the initial commit it was introduced in and if it works, bisect from there (looks to bee about 600 commits between introduction of the platform and v2026.01)... live well, vagrant
signature.asc
Description: PGP signature
