Samuel Dionne-Riel

Oh, in the case where there's a valid U-Boot on SPI, manually erasing that install first would help. From Linux using `/dev/mtd0` I guess would work. Otherwise `sf erase 0x0...

@crlena: which disk image did you flash to the SD card? When booting, you can start "spamming" presses of ESC or CTRL+C to break into the boot menu. Does selecting...

Odd. What *exact* command are you using to write the spi installer to the SD card? Given it's seemingly starting Tow-Boot (assuemd from the *esc/ctrl-c* message), it seems that at...

Assuming your SD card reader indeed is `/dev/mmcblk1`, it is looking fine. The important parts are probably done correctly, that is syncing the storage media. Do you have access to...

I wouldn't call this a solution, ideally we'd be able to dig into *why* this failed. But eh, t works. Anyone having similar issues (Tow-Boot starts from SD, but it...

I guess this could be a general troubleshooting step. I expect troubles like these could happen with any hardware, so trying this as an additional troubleshooting step is relatively painless...

One of the goals I want to work towards, I think you know, is a firmware interface, e.g. a "BIOS menu". Part of the options I always assumed would be...

> I hadn't even considered other boards - I guess I'd assumed if they weren't in a similar situation of having firmware loaded+altered DTBs that we would just let the...

+1, anyway we need a list of "supported" devices, and a way to provide per-device information, not unlike what Mobile NixOS automatically does.

Relatively relevant: ``` ~/tmp/u-boot/u-boot $ nix-shell ~/Projects/Tow-Boot/Tow-Boot -A pine64-pineA64LTS.config.Tow-Boot.outputs.firmware ``` This can be used to have a shell with the required environment.