(08-03-2023, 12:31 PM)tophneal Wrote: ...
So I'm curious now if anyone else has had this or a similar issue when trying to install tow-boot through SD installer or writing directly to mtd0 from within a booted OS. I'd raise it as an issue on the Github, but I want to be sure I haven't overlooked any potential solutions and I know @samueldr has indicated he isn't able to be as active in maintaining/troubleshooting as before.
Not what you asked, but pine64-pinephonePro-2022.07-006 worked fine for me on my PPP. 35Mb spi.installer.img was dd'd to a tatty old SD on my RPro64 then that booted fine on my PPP and I could do the install.
Same RK3399 ...
FWIW my SDcard looks like (on the RPro64)
Code:
$ lsblk
...
mmcblk1 179:96 0 3.7G 0 disk
├─mmcblk1p1 179:97 0 12M 0 part
└─mmcblk1p2 179:98 0 22M 0 part /run/media/chris/57f8f4bc-abf4-655f-bf67-946fc0f9f25b
Are you sure you have the correct bits held/flicked/switched to get your PBP booting from the SDcard?
On the basis there isn't that much difference between the boards would be tempted to at least try the PPP and/or RPro64 Tow-Boots - at least you should get to the Tow-Boot menu, whether you actually flash is another call. But would eliminate that the PBP download is a duffer.
- ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Arch (6.2 kernel, Openbox desktop) for general purpose daily PC.
- PinePhone Pro Explorer Edition, daily driver, rk2aw & U-boot on SPI, Arch/SXMO & Arch/phosh on eMMC
- PinePhone BraveHeart now v1.2b 3/32Gb, Tow-boot with Arch/SXMO on eMMC