12-15-2020, 05:12 PM
Hey @Pine I was indeed successful. Have only tested with a single Sopine but I have stored both U-Boot and iPXE in the SPI flash, and I have chainloaded iPXE. I've then tried to chain http://boot.alpinelinux.org/boot.ipxe (without HTTPS*), but failed to boot: requests are going over the wire though, and kernel images are being downloaded. Something else failed in the boot process.
When you say "unresponsive", what do you mean? There's a well-known issue with iPXE and U-Boot, in which iPXE tries to put the processor to sleep -- and relies on an interrupt to wake it up as needed (2sec timer, or keyboard input) -- but U-Boot has no interrupt support, so the processor never wakes up again. If you see the iPXE banner, and then it's unresponsive, then that's probably the bug. To fix, search for NAP_NULL in this page and follow the instructions:
https://u-boot.readthedocs.io/en/v2020.1....html#ipxe
If it's something else, you'll need to be more precise -- I'm not sure I understood what problem you are seeing.
* due to imcompatible crypto between iPXE and that website's config -- whole different story.
When you say "unresponsive", what do you mean? There's a well-known issue with iPXE and U-Boot, in which iPXE tries to put the processor to sleep -- and relies on an interrupt to wake it up as needed (2sec timer, or keyboard input) -- but U-Boot has no interrupt support, so the processor never wakes up again. If you see the iPXE banner, and then it's unresponsive, then that's probably the bug. To fix, search for NAP_NULL in this page and follow the instructions:
https://u-boot.readthedocs.io/en/v2020.1....html#ipxe
If it's something else, you'll need to be more precise -- I'm not sure I understood what problem you are seeing.
* due to imcompatible crypto between iPXE and that website's config -- whole different story.