Vanilla mainline Debian 11 (Bullseye) on the RockPro64
10-04-2021, 05:23 PM
I Understood.
Now, type in the following command and run it.
If there are no typos, you will be given 10 seconds to interrupt the boot process from the next boot.
(You only need to press the key within 10 seconds, so you don't need to keep pressing the key, which makes the operation easier.
Please be very careful when executing the "saveenv" command.
If an unintended environment variable is changed due to a typo, etc., and "saveenv" is executed in that state, it will result in a bad situation.
--- U-BOOT ---
Switching the "bootloader" itself is quite simple, just copying a few files and creating a text file of about 20 lines.
Copying the files is a familiar "bash" process, so there is no problem.
If you make a mistake, shell will report the error to you and you can try again as many times as you like.
The difficulty is in creating text files, typos are not tolerated.
Even if there is a mistake in the text, no one will report it to you.
And the only way to know if there is a mistake is at boot time.
In short, it is very inefficient.
If you have an environment where you can copy and paste text and write it back to the target media, then you don't have to worry about it.
Can you prepare such an environment ?
Please think about it before next time.
Now, type in the following command and run it.
If there are no typos, you will be given 10 seconds to interrupt the boot process from the next boot.
(You only need to press the key within 10 seconds, so you don't need to keep pressing the key, which makes the operation easier.
Please be very careful when executing the "saveenv" command.
If an unintended environment variable is changed due to a typo, etc., and "saveenv" is executed in that state, it will result in a bad situation.
--- U-BOOT ---
Code:
Hit any key to stop autoboot: 0
=> printenv bootdelay
bootdelay=0
=> setenv bootdelay 10
=> printenv bootdelay
bootdelay=10
=>saveenv
Saving Environment to SPIFlash... Erasing SPI flash...Writing to SPI flash...done
OK
=>resetSwitching the "bootloader" itself is quite simple, just copying a few files and creating a text file of about 20 lines.
Copying the files is a familiar "bash" process, so there is no problem.
If you make a mistake, shell will report the error to you and you can try again as many times as you like.
The difficulty is in creating text files, typos are not tolerated.
Even if there is a mistake in the text, no one will report it to you.
And the only way to know if there is a mistake is at boot time.
In short, it is very inefficient.
If you have an environment where you can copy and paste text and write it back to the target media, then you don't have to worry about it.
Can you prepare such an environment ?
Please think about it before next time.