On Thu, 22 Aug 2019 07:44:00 -0700 (PDT), Larry Klein
<
kleinl...@gmail.com> declaimed the
following:
>
>Did something change over the years when I was not paying attention? I have
>googled this subject and have not gotten any results that say anything
>about this. If its now only a EXT4 partition, what do I have to change in
>my board to get it to boot this new image?
Well, first off, have you tried holding down the boot-select button
when applying power to the board?
And yes, a lot has changed... The "FAT" partition is now a virtual
read-only system mounted by the OS only so that the device shows up when
connecting via USB. Second, instead of having the kernel load device tree
overlays, u-Boot now loads them. So part of what you see happening is that
the board/eMMC old u-Boot is trying to load a kernel but is not handling
device tree settings, and the kernel that comes off the SD card tries to
run but does not have a device tree set up for it.
You may need to find an IoT image (or even smaller -- console only
image, since the odds are that a unit with Angstrom on it may be a 2GB
eMMC), write it to the SD card, convert the card to a flasher, boot with
the Boot select button held down, and let it flash that image to the eMMC.
With luck, that will install a u-Boot that handles device tree set-up (and
the applicable device tree files). Also [I believe this is how it works],
newer u-Boot images, while loading from eMMC will detect the SD card and
automatically complete booting from the SD card -- no more using the boot
select button.
The alternative is some cryptic command that basically wipes out the
initial part of the eMMC so there is nothing found in it from which to
boot, and it then relies upon the SD card u-Boot to complete booting.
--
Wulfraed Dennis Lee Bieber AF6VN
wlf...@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/