12:11 <Kwiboo> warpme: I thought there was an issue loading FIT from emmc on my Radxa Zero 3W using generic-rk3568 but turned out to not work because I had been using boot partition as source for FIT last time I tested, that prevented it from loading FIT from normal user partition :-)

12:12 <Kwiboo> so yes, emmc seem to work using generic-rk3568 u-boot target, just re-confirmed using the build artifact from https://github.com/Kwiboo/u-boot-build/actions/runs/8010106826

12:16 <warpme> Kwiboo: thx. I still have more generic issue with my non-working emmc: can't see it at all on my zero3w. How emmc dt fragment looks in your working kernel?

12:27 <Kwiboo> warpme: just tested starting latest openSUSE Tumbleweed aarch64 network install snapshot and its kernel find the emmc: mmc0: new HS200 MMC card at address 0001

12:27 <Kwiboo> DT is very bare bone, only contains sdhci and sdmmc node: https://github.com/Kwiboo/u-boot-rockchip/blob/rk35xx-2024.04/arch/arm/dts/rk3568-generic.dts

12:46 <warpme> hmm - even with your's sdhci fragment - still on emmc (https://gist.github.com/warpme/6b6778651c0fe7132e5428efc9e29542)

12:46 <warpme> on->no

12:53 <Kwiboo> CONFIG_MMC_SDHCI_OF_DWCMSHC=y is enabled in kernel?

12:59 <warpme> argh - was not :-( My bad! Let me recompile....

13:36 <warpme> Kwiboo: qll have it now :-) Having your expertise: if i want to have boot from emmc - can i simply go with "echo 0 > /sys/block/${emmc_dev}boot0/force_ro" then write idbloader.img & u-boot.itb to ${emmc_dev}boot0 or some extra actions are needed?

13:48 <Kwiboo> warpme: you would write to it same as for sd-card: "dd if=u-boot-rockchip.bin of=/dev/${emmc_dev} bs=32k seek=1 conv=fsync"

13:51 <Kwiboo> the boot0/1 partitions is not read/used by bootrom/u-boot, only the normal "user partition"

13:52 <Kwiboo> I did play around with being able to save part of u-boot in a boot partition in https://patchwork.ozlabs.org/patch/1894243/ but please do not try to use that :-)