Philip Couling

@SteeMan Thanks. no I did not. I was just compiling one with that now. Using this post as a reference point. I also made a mistake above (which I will delete and re-post if this all works) as I accidently put the dts files in arch/arm/boot/dts instead of arch/arm64/boot/dts/rockchip/.

Nope. Still missing something. When I mount the first partition of the image /dtb/ still has no rk3566-rock-3c.dtb Definitely missing something.

@Endian Warning... this didn't work Yeah I think so... AFAIK they are mostly independent of kernel version. The syntax could theoretically change between Kernel or driver versions. But the theory of them is that it's easier to keep them stable as abstract text... at least that's what I read somewhere. So here's what I tried: Start creating a kernel patch... ./compile.sh CREATE_PATCHES=yes BOARD=rock-3c BRANCH=current kernel-patch Pull the DTS files from Radxa's kernel 4.19. Think dts files might be compatible across major kernel versions. Notes these are NOT the ones I linked above which was u-boot DTS, not Linux DTS cd arch/arm/boot/dts sudo curl -O https://raw.githubusercontent.com/radxa/kernel/stable-4.19-rock3/arch/arm64/boot/dts/rockchip/rk3566.dtsi sudo curl -O https://raw.githubusercontent.com/radxa/kernel/stable-4.19-rock3/arch/arm64/boot/dts/rockchip/rk3566-rock-3c-camera.dtsi sudo curl -O https://raw.githubusercontent.com/radxa/kernel/stable-4.19-rock3/arch/arm64/boot/dts/rockchip/rk3566-rock-3c.dts Copy the created patch file in place sudo cp output/patch/kernel-rockchip64-current.patch patch/kernel/rockchip64-current ./compile.sh Compiling...

That would make some sense since the latest Radxa release uses the somewhat antiquated 4.19 Kernel. Looks like we need different DTS files for linux vs u-boot: https://stackoverflow.com/a/30801701/453851

Hmmm, no. I tried to add this manually, creating a patch with this command: ./compile.sh CREATE_PATCHES=yes BOARD=rock-3c BRANCH=current uboot-patch But when I looked the file rk3566-rock-3c.dts is already present. AFAIK It gets brought in here: [🌱] Fetching SHA1 of 'branch' 'refs/heads/stable-4.19-rock3' [ https://github.com/radxa/u-boot.git ] So I guess there needs to be something else get the dtb file compiled. Not found it yet.

The important error message there, I think, is: ** Unable to read file /dtb/rockchip/rk3566-rock-3c.dtb ** I am not an Armbian expert. But this sounds like you need to get hold of a dts file and put it in the right place so that it will be built as a dtb file and included in the image. I think the DTS file you need is this one: https://github.com/radxa/u-boot/blob/next-dev/arch/arm/dts/rk3566-rock-3c.dts

Same problem here. I'll add a note that Radxa official images likewise do not boot each other's board. IE you can't use the official 3a image on the 3c board.

Could someone point me to a guide / how to / existing build script to create a bootloader image for the Radxa Rock-3a? Context... I'm trying to get a Radxa Rock3c to boot with a modern (6x) Linux kernel. This has the Rockchip rx3566 unlike the Radxa Rock3a which has the rx3568 (supported by Armbian). This is my first time working with u-boot, so I'm trying to follow Rockchip's own guide (here). Sadly that guide seems to be a rather cryptic, poorly translated, and file names don't appear to mach anything I can find. Radxa's own binaries (here) don't seem to know about the rk3566 or rk3568: I get errors when I use mkimage. But other distributions (Armbian and Alpine) have ready built mkimage that does know about rk3568 not rk3566. (Okay!). So my plan is to see if I can use mkimage from Armbian along with rk3566 binaries from Radxa's own repo. Even if I swing across to using the Rock3a I'll still want to be able to re-build the boot loader... so any information here is useful. I'm currently stuck on how to configure / build "spl/u-boot-spl.bin" provided by u-boot source code. I don't see good instructions on that. Long story short... Armbian developers managed to make u-boot boot a Radxa Rock3a with a 6.x kernel. How did they do it. [i don't mind reading source code, I just need to understand which bits were the Armbian customisations / configurations]

Is there any support for Rock 3 C (RK3566)? I've tried booting from the Rock 3 A image, but no joy. It looks like the Rock 3A was RK3568 so I wonder if using another device tree overlay for RK3566 might otherwise work?