I think a read through this sort of explains things.
If you put a usb tty serial console on the radxa zero as in documentation/rs102 at master · radxa/documentation · GitHub
You can see uboot is loading but failing so its software but confused to how to progress with uboot.sd.boot.bin and which and what tree of u-boot we should use.
I have a 512mb and the same and its all non eMMC versions prob due to the closed source binary blobs of Amlogic that Baylibre and others have done so much great work reverse engineering.
I purchased a 2gb so I can have I can have a comparison and awaiting delivery but expecting that maybe someone will hack a solution.
You have mainline u-boot with U-Boot for Amlogic SEI510 (S905X2) — Das U-Boot unknown version documentation as apart from ethernet the s905x2 is near identical to s905y2
As opposed to GitHub - angerman/meson64-tools and pretty sure someone will sort it out soon as has been accomplished on other amlogic boards or it will be eMMC only.
At a guess the current uboot uses the version from 2015.01 and has a custom eMMC partition format based on NAND and when flashing SD its why we are getting messages on corrupt partitions.
So just downloading u-boot.bin.sd.bin and using DD is not going to work with a custom partition format maybe?
@sven posted the console info in this thread
or there is a an error in the u-boot dts config for the SD card that is correct in the mainline kernel?
@jack ?
I haven’t done much as still waiting for a eMMC version but have to say I am mighty confused on what u-boot or sources should be used?
Isn’t blx_fix.sh supposed to cut and compress the binaries so they do fit in the reserved memory area?
@mara might get it cracked with a slackware minimal image but is still waiting for a board.