-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where to add/fix boot targets? #51
Comments
@MichaelZhuxx Any ideas? I'd love to be able to use the board without a |
Cross-linking a similar report on the other repo: starfive-tech/VisionFive2#67 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Generic boot, i.e. scanning through all defined boot targets for bootable partitions, is currently broken. The relevant part of the default/embedded U-Boot environment looks like this:
So as long as there is not
uEnv.txt
on a 3rd partition with a FAT filesystem, it tries themmc0
target. It looks like it would setdevnum
to0
, but actually it doesn't, as the syntax is wrong. So it remains at default value1
, which is the SD card.Since last U-Boot update, with NVMe support added, as fast as any NVMe card is attached, it sets
devnum
to0
correctly, aiming to boot from NVMe device 0. However, there is nonvme0
boot target, so it again tries to boot frommmc0
. As nowdevnum
is0
, which is the eMMC slot, it does not boot from SD card anymore as it used to prior to the U-Boot update.Basically what we want, for generic boot support, is this:
mmc0
boot command now does really setdevnum
to0
with the correctsetenv
command (devnum=0
is incorrect syntax).mmc1
SD card boot command added.nvme0
NVMe boot command added.I wanted to fix/add those environment variables, but I cannot find them. Neither
boot_targets
, norbootcmd_mmc0
is defined here: https://github.com/MichaIng/u-boot/blob/JH7110_VisionFive2_devel/include/configs/starfive-visionfive2.hWould if work if we add them here to the end of the
CONFIG_EXTRA_ENV_SETTINGS
variable, just in caseBOOTENV
orBOOTENV_SF
sets them, where ever those are defined?The text was updated successfully, but these errors were encountered: