Hi, I tried booting a Raspi 4 with a Leap 15.3 USB stick following the instructions on https://en.opensuse.org/HCL:AArch64_EFI which unfortunately did not work. Any other resources to look for in order to get it running? Thx Axel
On Fri, May 28, 2021 at 12:00:41PM +0200, Axel Braun wrote:
Hi,
I tried booting a Raspi 4 with a Leap 15.3 USB stick following the instructions on https://en.opensuse.org/HCL:AArch64_EFI which unfortunately did not work.
How did it fail? Thanks Michal
Am Freitag, 28. Mai 2021, 12:28:43 CEST schrieb Michal Suchánek:
On Fri, May 28, 2021 at 12:00:41PM +0200, Axel Braun wrote:
Hi,
I tried booting a Raspi 4 with a Leap 15.3 USB stick following the instructions on https://en.opensuse.org/HCL:AArch64_EFI which unfortunately did not work.
How did it fail?
It booted from the inserted SD card (w/o card it did just nothing) I interrupted at the uboot prompt, and then? Thx Axel
On Fri, May 28, 2021 at 12:41:00PM +0200, Axel Braun wrote:
Am Freitag, 28. Mai 2021, 12:28:43 CEST schrieb Michal Suchánek:
On Fri, May 28, 2021 at 12:00:41PM +0200, Axel Braun wrote:
Hi,
I tried booting a Raspi 4 with a Leap 15.3 USB stick following the instructions on https://en.opensuse.org/HCL:AArch64_EFI which unfortunately did not work.
How did it fail?
It booted from the inserted SD card (w/o card it did just nothing) I interrupted at the uboot prompt, and then?
Then you should be able to execute the bootscript from the environment which loads the system from USB like run bootcmd_usb0 where the 'run' command executes command list from environment variable and 'bootcmd_usb0' is a command list predefined in the default environment. Random (unofficial) document that lists u-boot commands is here: https://www.digi.com/resources/documentation/digidocs/PDFs/90000852.pdf Note that the availability of commands depents on compiled-in features. There might be an official u-boot manual but it is notoriously hard to find. In case of problems you might want to use the usb command to determine if your storage device has been detected (or if you happen to have more than one in which case you may need to specify number other than 0 in the above). HTH Michal
The RPi4 can boot from USB if the RPi firmware is up to date.
Check if you need to update your firmware, I had to.
Best,
Alex
________________________________
From: Axel Braun
Hello Michal, Am Freitag, 28. Mai 2021, 13:07:55 CEST schrieb Michal Suchánek:
On Fri, May 28, 2021 at 12:41:00PM +0200, Axel Braun wrote:
Am Freitag, 28. Mai 2021, 12:28:43 CEST schrieb Michal Suchánek:
On Fri, May 28, 2021 at 12:00:41PM +0200, Axel Braun wrote:
Hi,
I tried booting a Raspi 4 with a Leap 15.3 USB stick following the instructions on https://en.opensuse.org/HCL:AArch64_EFI which unfortunately did not work.
How did it fail?
It booted from the inserted SD card (w/o card it did just nothing) I interrupted at the uboot prompt, and then?
Then you should be able to execute the bootscript from the environment which loads the system from USB like
run bootcmd_usb0
where the 'run' command executes command list from environment variable and 'bootcmd_usb0' is a command list predefined in the default environment.
Random (unofficial) document that lists u-boot commands is here:
https://www.digi.com/resources/documentation/digidocs/PDFs/90000852.pdf
Note that the availability of commands depents on compiled-in features.
There might be an official u-boot manual but it is notoriously hard to find.
In case of problems you might want to use the usb command to determine if your storage device has been detected (or if you happen to have more than one in which case you may need to specify number other than 0 in the above).
Yes, I could spot the device and partition, but struggeling with the correct boot command: fatload usb <dev>[:partition] <loadAddress> <bootfilename> -> what is the bootfilename it is looking for? when running run bootcmd usb0 (where the USB stick sits) it still boots into the SD-Card @Alexandre - thanks for the hint with the firmware - I updated successful, however the USB stick was not selected at boot. Cheers Axel
On Fri, May 28, 2021 at 02:45:18PM +0200, Axel Braun wrote:
Hello Michal,
Am Freitag, 28. Mai 2021, 13:07:55 CEST schrieb Michal Suchánek:
On Fri, May 28, 2021 at 12:41:00PM +0200, Axel Braun wrote:
Am Freitag, 28. Mai 2021, 12:28:43 CEST schrieb Michal Suchánek:
On Fri, May 28, 2021 at 12:00:41PM +0200, Axel Braun wrote:
Hi,
I tried booting a Raspi 4 with a Leap 15.3 USB stick following the instructions on https://en.opensuse.org/HCL:AArch64_EFI which unfortunately did not work.
How did it fail?
It booted from the inserted SD card (w/o card it did just nothing) I interrupted at the uboot prompt, and then?
Then you should be able to execute the bootscript from the environment which loads the system from USB like
run bootcmd_usb0
where the 'run' command executes command list from environment variable and 'bootcmd_usb0' is a command list predefined in the default environment.
Random (unofficial) document that lists u-boot commands is here:
https://www.digi.com/resources/documentation/digidocs/PDFs/90000852.pdf
Note that the availability of commands depents on compiled-in features.
There might be an official u-boot manual but it is notoriously hard to find.
In case of problems you might want to use the usb command to determine if your storage device has been detected (or if you happen to have more than one in which case you may need to specify number other than 0 in the above).
Yes, I could spot the device and partition, but struggeling with the correct boot command: fatload usb <dev>[:partition] <loadAddress> <bootfilename> -> what is the bootfilename it is looking for? It's a command that loads a file into memory, nothing else.
You can then specify the addres to one of the boot* family of commands to execute it. You can also use multiple files (kernel, ramdisk, devicetree) and then you need to pass their addresses to the boot* command correctly. The command lists predefined in the environment use some load addresses that were picked by the maintainer in the board configuration to not conflict with the board hardware. Thanks Michal
when running run bootcmd usb0 (where the USB stick sits) it still boots into the SD-Card
@Alexandre - thanks for the hint with the firmware - I updated successful, however the USB stick was not selected at boot.
Cheers Axel
Am Freitag, 28. Mai 2021, 15:46:20 CEST schrieben Sie: ....
Yes, I could spot the device and partition, but struggeling with the correct boot command: fatload usb <dev>[:partition] <loadAddress> <bootfilename> -> what is the bootfilename it is looking for?
It's a command that loads a file into memory, nothing else.
You can then specify the addres to one of the boot* family of commands to execute it. You can also use multiple files (kernel, ramdisk, devicetree) and then you need to pass their addresses to the boot* command correctly.
The command lists predefined in the environment use some load addresses that were picked by the maintainer in the board configuration to not conflict with the board hardware.
OK....the manual was not really...easy to spot what to do. Finally it worked with usb reset run bootcmd_usb0 Thanks for the help Axel
On Fri, May 28, 2021 at 04:24:59PM +0200, Axel Braun wrote:
Am Freitag, 28. Mai 2021, 15:46:20 CEST schrieben Sie:
....
Yes, I could spot the device and partition, but struggeling with the correct boot command: fatload usb <dev>[:partition] <loadAddress> <bootfilename> -> what is the bootfilename it is looking for?
It's a command that loads a file into memory, nothing else.
You can then specify the addres to one of the boot* family of commands to execute it. You can also use multiple files (kernel, ramdisk, devicetree) and then you need to pass their addresses to the boot* command correctly.
The command lists predefined in the environment use some load addresses that were picked by the maintainer in the board configuration to not conflict with the board hardware.
OK....the manual was not really...easy to spot what to do. Finally it worked with
usb reset run bootcmd_usb0
You probably should not need 'usb reset'. If you do that's something that should be fixed (if the u-boot you are using comes from openSUSE). Please report a bug. Thanks Michal
Am Freitag, 28. Mai 2021, 16:34:02 CEST schrieb Michal Suchánek:
OK....the manual was not really...easy to spot what to do. Finally it worked with
usb reset run bootcmd_usb0
You probably should not need 'usb reset'. If you do that's something that should be fixed (if the u-boot you are using comes from openSUSE).
Tested again, works as well w/o usb reset! Thanks Axel
participants (3)
-
Alexandre Vicenzi -
Axel Braun -
Michal Suchánek