On Tue, 18 Nov 2025, at 12:18, jslee wrote: > On Tue, 18 Nov 2025, at 06:30, Glen Gunsalus wrote: >> As I mentioned before, this seems to be a problem with u-boot not >> initializing >> things, but I'm a novice here. That's why I resorted to misc. > > Crystal previously and very helpfully (thankyou!) shared a link on this > list to their page about getting arm64 devices running. Not exactly the > same devices, but the same concepts apply here. > > In particular it emphasized the importance of having the correct device > tree file
eg. see the history of the device tree file for this product in the Linux kernel tree https://github.com/torvalds/linux/commits/master/arch/arm64/boot/dts/rockchip/rk3528-radxa-e20c.dts and note: 1. it didn't always include eMMC (or ethernet) support 2. the most recent revision enables eMMC "HS200" HS200, according to Google, is an eMMC operating mode that uses a higher clock speed (200MHz vs 50MHz for “HS” mode) _and also a lower operating voltage_ https://adaptivesupport.amd.com/s/article/69368?language=en_US not sure if this HS200 mode requires corresponding OS kernel changes/support or not. I'll explore further when my little babby computers arrive next week. John
