10-17-2017, 09:53 AM
Which Pine64 OS distributions use the newer SPL (secondary program loader), and not just fall back on the older boot0 code?
I'm tracking the Fedora ARM team's efforts as they are nearing the point of releasing support for the Pine64+. They have had preliminary builds that I've wanted to test. However, these new builds require using a serial console (uart) to view the boot process, and access a login prompt. I can successfully watch many of the Pine64 distros boot over the serial console. But most of these distros use the legacy boot0 code. Fedora is using the newer ATF (ARM Trusted Firmware) / SPL/U-Boot code.
See here for details:
https://github.com/u-boot/u-boot/blob/ma...ME.sunxi64
When I try to boot the Fedora distribution, I see absolutely nothing on the serial console. I know the OS is booting, because I can later pull the microSD card from the Pine, and view the log files on another computer. In troubleshooting, I'm attempting to rule out all the variables I can. As I mentioned, I can view text on the serial console for distributions that use the legacy boot0 code. I'd like to locate other distributions that don't use boot0, so I can attempt to boot them and see if the serial console works for me on those.
Forgive me if I've used the wrong terms for some of this technology. School me if necessary! :-)
I'm tracking the Fedora ARM team's efforts as they are nearing the point of releasing support for the Pine64+. They have had preliminary builds that I've wanted to test. However, these new builds require using a serial console (uart) to view the boot process, and access a login prompt. I can successfully watch many of the Pine64 distros boot over the serial console. But most of these distros use the legacy boot0 code. Fedora is using the newer ATF (ARM Trusted Firmware) / SPL/U-Boot code.
See here for details:
https://github.com/u-boot/u-boot/blob/ma...ME.sunxi64
When I try to boot the Fedora distribution, I see absolutely nothing on the serial console. I know the OS is booting, because I can later pull the microSD card from the Pine, and view the log files on another computer. In troubleshooting, I'm attempting to rule out all the variables I can. As I mentioned, I can view text on the serial console for distributions that use the legacy boot0 code. I'd like to locate other distributions that don't use boot0, so I can attempt to boot them and see if the serial console works for me on those.
Forgive me if I've used the wrong terms for some of this technology. School me if necessary! :-)