04-02-2019, 07:13 PM
(This post was last modified: 04-02-2019, 07:16 PM by SirRyanTheGeek.)
(04-02-2019, 06:47 PM)t4_4t Wrote: > but how to does one access the "u-boot console"?
Access is via "uart".
Using this method, you get the output as shown in the #1 post above, and you can control it.
For example, access from other PCs using the following items.
https://www.pine64.org/?product=padi-serial-console
The "u-boot" currently released for "rock64" does not provide any other way to control "u-boot".
The "boot-method" depends on the distribution (eg Ayufan/Armbian etc).
So you should clearly indicate which image you are considering using.
Otherwise, you will not get a useful response for you.
Well darn. Don't have one of those little things :-(
So far I was settling on Ayufan's Bionic release.
Is there a way like on the Raspberry Pi where I can put something like the bootloader "bootcode.bin" and an empty file called "TIMEOUT" onto a microSD which tells the Pi to hang tight for about 20 seconds to let things "spin up" that may be attached, and THEN boot? I do this on the Pi and it works 100% of the time. Sure it wastes a microSD, but having it reliably boot is worth it.
I flashed the SPI so it will do a USB boot - but sadly that method is inadequate when it doesn't allow for time for any attached bootable devices to always be discovered. Seems like it somewhat defeats the purpose of allowing to boot from USB - which is why you needed to do your workaround it seems.