If you have the uboot image (uboot.img OR u-boot.itb) then, to find out,
strings <uboot> |grep _targets replacing <uboot> with whatever is appropriate
mmc0 is emmc, mmc1 is SD
OR using dd, rip 4M out of some block device starting 8M in (and writing to some tmp file)
what you want is
strings uboot.img |grep _targets
boot_targets=mmc1 usb0 mmc0 pxe dhcp
(this from mrfixit bsp uboot,, no nvme)
Of course there has to be the boot files in "correct" place, one of,,,, boot.scr, extlinux.conf, aarch64.efi
and their configuration has to be correct too
--------after a little more thought----
Maybe for the OP, easiest would be to rename the boot files and see what happens,, ie
cd /boot/extlinux ; mv extlinux.conf extlinux.conf.good ;reboot (reboot is a little flakey, might need a shutdown)
Obviously with SD card in
strings <uboot> |grep _targets replacing <uboot> with whatever is appropriate
mmc0 is emmc, mmc1 is SD
OR using dd, rip 4M out of some block device starting 8M in (and writing to some tmp file)
what you want is
strings uboot.img |grep _targets
boot_targets=mmc1 usb0 mmc0 pxe dhcp
(this from mrfixit bsp uboot,, no nvme)
Of course there has to be the boot files in "correct" place, one of,,,, boot.scr, extlinux.conf, aarch64.efi
and their configuration has to be correct too
--------after a little more thought----
Maybe for the OP, easiest would be to rename the boot files and see what happens,, ie
cd /boot/extlinux ; mv extlinux.conf extlinux.conf.good ;reboot (reboot is a little flakey, might need a shutdown)
Obviously with SD card in