Z572 <zhengjun...@iscas.ac.cn> writes: > hello!, can you try boot from mmc1, and do setenv and saveenv on mmc1 > uboot, then reset and boot from mmc2?
Hi! Sorry for not mentioning that. Those setenv + saveenv commands were run with MMC1 (SPI) boot selected, not MMC2. I confirmed the printenv fdtfile output matched starfive/jh7110-starfive-visionfive-2-v1.3b.dtb on both MMC1 and MMC2. However, I ran the commands again just now and suddenly it can boot from MMC2. I have no idea idea what could have happened (Originally entered from MMC1, no typos, and printenv matched the expected values after rebooting), but it boots now. Very strange, but seemingly the issue is resolved. I wonder if anyone else will encounter it in the future. Thanks! -- Take it easy, Richard Sent Making my computer weirder one commit at a time.
