I had U-boot all nicely configured, so that I could easily switch between
DVI and the 4.3" LCD by entering one command at the boot prompt. I just
popped in a different uSD card with a different image, and suddenly it's not
working. The "bootcmd" mini-script in my NAND environment uses the "mmc
rescan" command to initialize it, which now doesn't work. Instead, it
expects an "mmc init" command. If I put the other uSD card back in, "mmc
rescan" works. This suggests that the NAND U-boot is successfully chaining
to an updated U-boot from one of the cards, but is failing to do this from
the other one. The boot output is identical, but there is a five second
timeout in the one that's failing.
I gather from Googling that "init" is old and "rescan" is new. I don't know
what demented individual abolished "init" when "rescan" was added, but I'm
trying to figure out how to fix this. As far as I can tell, I don't need the
U-boot on the uSD card at all, because the NAND version still boots Linux
just fine. So should I just get rid of the "boot" partition? (Will that
work?) Or should I try to find an old version of U-boot to put in my "boot"
partition so that it matches the NAND version? (Ugh.) Or is there a (safe)
way to update the version in NAND so that it matches what I've been putting
on my uSD cards? Or should I put a more complicated "bootcmd" mini-script
into my environment that tries both "init" and "rescan"?
Any advice? Has anyone else come up against this?
Ciao, Paul D. DeRocco