12-18-2024, 08:17 AM
(This post was last modified: 12-18-2024, 08:18 AM by ethical_haquer.)
(12-18-2024, 05:13 AM)dukla2000 Wrote:I was under the impression that rk2aw was a loader for boot-loaders.(12-17-2024, 04:59 PM)ethical_haquer Wrote: I tried using it with U-Boot, but U-Boot couldn't find the pmOS installation I have on the eMMC.
...
rk2aw includes its own flavour of uboot (as does Tow-Boot): I had problems with pmOS and rk2aw as pmOS wasn't happy to have its boot directory in the same partition as /. So if I did a "default" pmOS where /boot had its own partition, and didn't bother with extlinux stuff, rk2aw happily picked up the EFI hooks and it loaded fine. However it kept randomly rebooting so I went with arch.
(12-17-2024, 04:59 PM)ethical_haquer Wrote: ...I am perplexed as to why you would want to? Both Tow-Boot & rk2aw are "facilitators" between the board startup firmware and (their own flavour of) uboot. As such they flash LEDs, make disks available over USB and give some options which is your OS of choice for the day. I prefer rk2aw as it (better) supports multiple OSs on each disk.
I'm just surprised that no one has tried using Tow-Boot with rk2aw before. It should be possible, seeing as Tow-Boot is based off U-Boot.
When you flash rk2aw to the SPI and there are no boot-loaders present on the SPI, eMMC, and microSD, rk2aw won't do anything.
And I was able to flash Tow-Boot to the microSD, and rk2aw to the SPI, and it worked. rk2aw would start up, and after pressing the power key Tow-Boot would load pmOS.
But that was not ideal, as having Tow-Boot on the microSD made it so I couldn't test out other installations easily.
How do you like Arch on the PPP?
