tpou

I am currently attempting to compile a device tree overlay, in connection with an OPi Zero 2. But my questions here are of rather general nature (with regards to DT compiling), so I posted it here. ------- Goal: Creating a DT overlay to enable certain hardware currently not working on the board: wifi and HDMI output. Alternatively, compiling a "full" .dtb file for the board, replacing the one currently used during boot. For completeness: In the below I experimented starting from the Armbian_22.08.7_Orangepizero2_bullseye_edge_5.19.16.img.xz image, 406585908 bytes. uname -a: "Linux orangepizero2 5.19.16-sunxi64 #22.08.6 SMP Tue Oct 18 06:56:22 UTC 2022 aarch64 GNU/Linux" Boot-up (at times shaky), UART and USB (via type A socket) is working with this image. ------- I have tried to assemble a dts file, to be made into an overlay, from snippets seen at https://github.com/jernejsk/linux-1/commit/e7222b1f0dfde22a3b60de7f3add6599fd942e84 But this runs into errors, as references are missing, in this case for example "reg_aldo2". I can look at the complete file, https://github.com/jernejsk/linux-1/blob/e7222b1f0dfde22a3b60de7f3add6599fd942e84/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts and see that it includes #include "sun50i-h616.dtsi", which I can copy from the tree. Further I can make additional code additions that all missing references are resolvable. Nevertheless, even then errors (or to be exact: warnings) remain that look as if the resulting .dtbo will not be functional. Thus: What is the typical workflow in compiling overlays? 1. How much of existing code needs to be included? (I also tried, as alternative to above, to decompile the existing dtb and use it as included file in my compilation - is this a reasonable avenue?) 2. What are negligible warnings? 3. If I compiled something resulting in an erroreous .dtbo, could it be harmful to the hardware? (Or asked differently: tinkering with what parts of the device tree is potentially damaging to the board?) ------- Example warnings: sun50i-h616.dtsi:109.6-1009.4: Warning (unit_address_vs_reg): /soc: node has a reg or ranges property, but no unit name also defined at orangepi-zero2_wifi_and_hdmi.dts:61.13-81.11 sun50i-h616.dtsi:375.21-395.5: Warning (avoid_unnecessary_addr_size): /soc/mmc@4021000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property also defined at orangepi-zero2_wifi_and_hdmi.dts:63.25-79.15 Thanks to the knowledgable.

@ALIGMSTEN Hello, you mentioned you had to "power cycle" [to make it successfully boot], near Aug 10, for this board. Can you write with which board version you are working with. (silk-screened in white on the board, something like v1.x, in same text body as the OrangePi logo)

@TheOWL: You said "2: I use the newest image , display nothing on screen. But i have an older version image. It display to screen by Micro-HDMI perfect." Which older version was it, on which HDMI output worked? (I observed non-working HDMI-output, or say exactly: nothing displayed on the monitor, as well for Armbian 22.08 bullseye.)

Hello, I have an OrangePi Zero H2 which until recently was running almost flawlessly with the Armbian_5.38_Debian_stretch_4_14_14 image. When I did a kernel upgrade using "apt-get dist-upgrade" (because I had earlier the error message ~"failed to Load Kernel Modules", and dist-upgrade was recommended), and this dist-upgrade failed inbetween (probably because of power consumption), the SD card was left in unbootable state. (error msg see below [1]) I concluded that the /boot directory was corrupted, so from a new installation of Armbian_5.38_Debian_stretch_4_14_14 made elsewhere I copied all the /boot directory over to my SD card. This made the (first) SD card again bootable in the first stages, but it now will not continue after "starting version 232". Is there a way to make the installation still working by copying parts of a fresh new installation of Armbian_5.38_Debian_stretch_4_14_14 over? I am asking because of the many changes made on the SD card in course of time. (Such rescue method could be of general interest.) Thanks (I have meanwhile a new power supply.) [1] ... Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 206 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 241 bytes read in 167 ms (1000 Bytes/s) 5400639 bytes read in 643 ms (8 MiB/s) 6972808 bytes read in 811 ms (8.2 MiB/s) Found mainline kernel configuration ** File not found /boot/dtb/sun8i-h2-plus-orangepi-zero.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ** File not found /boot/dtb/overlay/sun8i-h3-analog-codec.dtbo ** ** File not found /boot/dtb/overlay/sun8i-h3-usbhost2.dtbo ** ** File not found /boot/dtb/overlay/sun8i-h3-usbhost3.dtbo ** ** File not found /boot/dtb/overlay/sun8i-h3-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5400575 Bytes = 5.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... Device 0: Vendor: Generic Rev: 8.07 Prod: Flash Disk Type: Removable Hard Disk Capacity: 30200.0 MB = 29.4 GB (61849600 x 512) ... is now current device Scanning usb 0:1... _sun8i_emac_eth_init: Timeout missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-42-80-86-76-5c *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 *** ERROR: `serverip' not set