Does the R2S image actually boot into the kernel, or does it fail at the bootloader already? I wonder whether we’d only need the R2S Plus device tree built with the kernel, or a new U-Boot build as well.
How is that friendly-debian → dietpi conversion working for you? @MichaIng had previously indicated that those were perhaps not the best starting point. But perhaps they can be used to pinpoint whatever needs to be done to make the armbian version work?
Working quite well, had to disable overlay filesystem though, otherwise the converter cannot find boot partition (cannot remember the exact message) and fails.
LANs got detected, CPU temp is working. Did not need anything else, so cannot comment on other things.
I was going through some SD cards and R2S and R2S Plus devices this last weekend and I think I found that I was able to get an RS2 Plus to boot up to a semi-working state with an SD card that I had used in a R2S with a usb wifi configured. wifi on the R2S Plus wasn’t working, but didn’t try to resolve yet. So when I have time I will try to revisit that path and see if I can get it fully working.