I installed your Debian stable minimalist image on my R5S (housed in its black metal box), added an NVMe disk (WD Blue SN5000), I boot into it and let sit idle for a few hours and `sensors` tells me: % sensors nvme-pci-22100 Adapter: PCI adapter Composite: +66.8 C (low = -40.1 C, high = +89.8 C) (cr...

How do I upgrade my Debian install when a new kernel is released?
I can install `linux-image-arm64` just fine, but that puts the kernel only inside `/boot` where it's not used AFAICT when booting (instead the kernel used for boot seems to be hardcoded to the one in `/dev/mmcblk2p4`).

I installed the Debian image on my machine. AFAICT the boot options are passed to the kernel via a device tree overlay stored in the "dtbo" partition (a.k.a /dev/mmcblk2p3). This is a binary format not fit for editing: # hexdump -C /dev/mmcblk2p3 00000000 d7 b7 ab 1e 00 00 05 80 00 00 00 2...

AFAICT, mmcblk2boot0 and mmcblk2boot1 are both empty (hexdump says they contain just NULL bytes).
Can we install U-Boot in there?

I'm trying to build U-Boot (from git.denx.de/u-boot.git). I basically did `make nanopi-r5s-rk3568_defconfig; make` and I'm getting the following message at the end: Image 'simple-bin' is missing external blobs and is non-functional: rockchip-tpl atf-bl31 /binman/simple-bin/mkimage/rockchip-tpl (rock...

Where's the boot information? Things like: - How to build U-Boot - How to install it (how it's found, in which order various devices are tried to find the cmd.boot file, ...). - What's supported by the U-Boot build (is it supposed to show something on HDMI, if not why not? Does it support USB keyboa...

I can't find anywhere in the wiki where the boot process is described. All I see is explanations of how to take someone else's premade image and maybe how to tweak it, but I'm looking for documentation about how it works, so as to know what are the constraints on eMMC or uSD partitioning, for exampl...