(08-08-2022, 07:00 PM)wdt Wrote: armbian uses boot.txt, run thru a simple compiler to make boot.scr
This is one of the things uboot looks for
While the kernel has to be configured to use nvme, 1st uboot has to find it (and be able to read it)

(08-09-2022, 07:20 PM)wdt Wrote: OK, I'll try to describe how the boot works
Please note: ALL? (nearly) images contain the 1st 16M, ie a mbr and a uboot package (2 or 3 files, in right place)
The boot rom searches  SPI, emmc, SD for signature of idbloader
It is assumed that if there is an idbloader that there will be a uboot @8M on same media
Then uboot takes control,  alters search order (& adds to it, ex, usb)
uboot is looking, in partitions for boot.scr, extlinux/extlinux.conf or aarch64.efi
The first one of those it finds, then it loads it and follows the config within
So... the path to kernel and initrd and dtb must be correct for a succesfull boot
Also note... uboot doesn't know if it is a 1 or 2 partition setup (and knows nothing about mount setup)
so it looks for boot/boot.scr AND boot.scr  (it considers where it finds the config file to be /)
Of course, after initrd all this changes, but uboot has done its job by then and exited
I hope this was useful
-----more--
I think the idea of armbianENV.txt is that it is included (referenced) in boot.scr and doesn't need compiling,
but I don't know much about armbian........
----more explaination---
if there is a uboot on emmc, that is the one that will be used,
any uboot on SD will be IGNORED
when you install armbian to emmc, the uboot on emmc will be overwritten by uboot in image
this is the same as uboot on SD
armbians uboot does NOT work, you have proved this, I don't know why
uboot ONLY searches for the config files, all paths to kernel, initrd, dtb are in config file
when uboot loads the config file, then it knows the path to load kernel etc

(08-10-2022, 01:06 PM)wdt Wrote: OK, I see you said you have usb -> emmc adapter
make an image of present emmc, maybe on usb key on pbp
dd if=/dev/emmc of=/mnt/sda/emmc.img bs=1M status=progress
(if you don't have a big enough key, pipeline thru gzip,, as so
dd if=dev/emmc bs=1M|gzip >someplace, usb key,,emmc.gz)
Then, with adapter you easily restore any screw-up,
that is I am assuming you have another computer?
Then do a install (of armbian) on emmc,,,DO NOT shut it off
until you ALSO install pcm uboot to emmc (as last step before reboot)
See, with a partition copy install, fstab, boot.scr and probably the initrd need to be adjusted
Because those are all set for the SD
---
BTW,,,pbp reboot is flakey, do a shut off, reboot often hangs

(08-01-2022, 12:15 AM)geokon Wrote: I had trouble installing it the conventional way to the emmc - where you copy the compressed system image to the emmc.

(08-15-2022, 07:17 PM)TRS-80 Wrote:

(08-01-2022, 12:15 AM)geokon Wrote: I had trouble installing it the conventional way to the emmc - where you copy the compressed system image to the emmc.

The 'conventional way' (on Armbian) would be to use the nand-sata-install tool (which, IIRC, may also be available from armbian-config (not sure)).

Different SBCs boot in all different ways, which is part of the problem with them.  This is all very different from x86 you may be used to.

Having said all of the above, some other people were also reporting this issue at Armbian forums (Werner gives a clue in that thread about how it works), so maybe something went wrong.  I do believe it used to work at some point.

Edit: I just realized you are probably the same calinb from the thread I linked.  Keep up the good work, and I hope to be able to help you some more very soon (just need to pick up my new PBP from post office in a couple days).