OleksandrK

The NanoPi R3S contains a hardware clock (HYM8563) with the possibility to connect a backup battery. However, the current kernel adds this clock as an additional one (RTC1). I tried to create a device tree overlay, but it does not work. As I understand it, this is because the default Rockchip clock is not included in the device tree. So, if I understand correctly, the only way to make the HYM8563 the default clock is to build the kernel with this option enabled. Please consider changing the default kernel options to make the HYM8563 the default RTC. If there’s another way to make the HYM8563 the default RTC, please advise.

Hi everyone, and thanks a lot for the help. I found the solution: the problem was Windows 11 on my laptop. After writing the Armbian image, if the SD card stays inserted, it becomes corrupted within a few seconds. This happens only with Armbian and only with R3S images. I have no idea why. So, to get a proper SD card, I need quick hands to remove it immediately after the writing finishes (no matter which software is used to write).

OK. So solution is to properly writing SD. Armbian_25.5.2_Nanopi-r3s-lts_bookworm_current_6.12.34_minimal and the same result Armbian_25.5.2_Nanopi-r3s-lts_noble_current_6.12.34.

Yes I tried. With no result. I even tried to write (decompressed) image by "gnome disks" graphic tool on Debian. With no result also. Board behaves like no system on SD (blink red led and no activity led on ethernets, except one on WAN). So the question is: if to insert properly recorded Armbian SD to x86 Debian, system have to recognize partition and read content of it, right?

Yes, validation always succsess. I tried even different SD cards (brand new Sandisk). After Armbian fails to boot I write stock friendlyelec image by the same tool and stock image always properly boot

I know this sounds strange, but I cannot get any of the images to boot. I have an R3S non-LTS + SD card. It works well with the stock images from FriendlyElec, but none of the Armbian images I tried will boot. I tried different tools to write the SD (BalenaEtcher, USBImager, Rufus), but nothing changed. When I tried to read the SD card with Armbian on my x86 laptop running Debian, the system didn’t recognize any proper partitions (maybe that’s normal, maybe not—I don’t know). But when I write an Armbian image for Allwinner NanoPi, the partitions are detected correctly. And finally, I can’t connect to the debug UART, so I can’t get any logs. I feel the solution should be simple, but I need help with this.