Search the Community

@Gunjan Gupta I only used the Armbian-Config to see what the Boot Environment was set to and to see if the correct boot device was set by Armbina-Install. It turned out that Armbian-Install had set the UUID of the SD-Card as the boot device. I will try to add a UART Serial port to the board and see what I can come up with.

Sorry but I am confused about this part. Why did you had to modify the UUID yourself? Armbian install has the option to install bootloader to emmc. Not sure if you used it, but if not try using the same. It generally helps to see the serial console logs when troubleshooting boot issues, so if you can share them that will make it easier for people to help you out.

Hey guys, I have been fiddling with this for days now. I think I have to give up. I am able to boot from an sd-card that has the built on it that @pixdrift whipped up the other day. It boot flawlessly. In the terminal is was able to start armbian-install and move the content of the sd over to the internal emmc. That finished without errors. i then went ahead and opened the armbian-config from the emmc and modified the boot environment to make sure it has the correct boot drive UUID. Everything look good but I will still not boot from EMMC. Any help with this would be appreciated. BTW everything in this built seems to be working as long as I boot from SD-Card. Ethernet, Wifi all the USB port ... everything works great except the part with moving it to emmc.

AFAIK rk3128 is not supported in the mainline armbian code, perhaps some forks may exist but I doubt a lot they do.

I tried the latest 6.8 kernel edge on my Rock 5A and noticed the CSI camera interface doesnt exist. Is there any plan or time schedule to fix that? I saw it's marked "TODO" on https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md . So in 6.9 perhaps? (A LOT of other stuff works remarkably well though, great work!)

I believe this question goes to @rpardini as maintainer of patches for Rockchip series in the `build` repo: I'm trying connect camera to Orange Pi 3B (yes, it boots from community support on edge kernels), but spent 2h digging to find no drivers for CSI2 from Rockchip's fork are ported to patches for recent kernels (for example: https://github.com/armbian/linux-rockchip/blob/rk-5.10-rkr6/drivers/phy/rockchip/phy-rockchip-csi2-dphy.c and corresponding device trees to instantiate these drivers). This is a little chicken egg problem as I need recent kernels to have access to open source GPU drivers - they're not present on 5.10 based original system images for OrangePi 3B. I created a DT overlay for imx219 camera, but it cannot work as right references don't exist on Armbian yet. I could help with porting these, but I need to know the procedure - that's some amount of drivers I can figure out based on `compatible = ` entries from Rockchip's device trees. I probably need to get them built with 6.6 and 6.7, then generate patches with these and PR changes. Any more hints appreciated. I'm interested in having both MIPI CSI2 and GPU working on these boards for now: OrangePi 3B (that one I have on my desk) Radxa Zero 3E Radxa Zero 3W Thank you. How you can live with forum not supporting humanly Markdown?

Hi, After running armbian-install on S905x device it stopped booting. USB Burning Tool doesn't recognize the device, nothing. After connecting to UART it looks like install script has overwritten the original u-boot. That's the boot log from UART connection without sd card: GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 104174 BL2 Built : 11:58:42, May 27 2017. gxl gc3c9a84 - xiaobo.gu@droid05 set vcck to 1120 mv set vddee to 1000 mv Board ID = 1 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 912MHz - PASS Rank0: 1024MB(auto)-2T-13 Rank1: 1024MB(auto)-2T-13 DataBus test pass! AddrBus test pass! -s Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000 New fip structure! Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600 Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400 Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x000af000 NOTICE: BL3-1: v1.0(release):3348978 NOTICE: BL3-1: Built : 15:44:01, May 12 2017 [BL31]: GXL CPU setup! mpu_config_enable:ok [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07] OPS=0x82 8f bb f0 da ba 22 d2 cf 1 b0 31 f4 [0.359461 Inits done] secure task start! high task start! low task start! ERROR: Error initializing runtime service opteed_fast <debug_uart> U-Boot 2022.07-armbian (Nov 25 2023 - 12:50:42 +0000) libretech-cc Model: Libre Computer AML-S905X-CC SoC: Amlogic Meson GXL (S905X) Revision 21:b (82:2) DRAM: 2 GiB Core: 169 devices, 27 uclasses, devicetree: separate MMC: mmc@72000: 0, mmc@74000: 1 Loading Environment from nowhere... OK In: serial Out: serial Err: serial [BL31]: tee size: 0 [BL31]: tee size: 0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1: Armbian Retrieving file: /uInitrd ** File not found /uInitrd ** Skipping Armbian for failure retrieving initrd SCRIPT FAILED: continuing... Found U-Boot script /boot/boot.scr 8147 bytes read in 1 ms (7.8 MiB/s) ## Executing script at 08000000 U-boot default fdtfile: amlogic/meson-gxl-s905x-libretech-cc.dtb Current variant: Current fdtfile after armbianEnv: amlogic/meson-gxl-s905x-libretech-cc.dtb Mainline bootargs: root=/dev/mmcblk1p1 rootwait rootfstype=ext4 splash=verbose c onsole=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ub ootpart=d27dbd06-01 libata.force=noncq usb-storage.quirks= cgroup_enable=memo ry swapaccount=1 22783841 bytes read in 500 ms (43.5 MiB/s) 27433472 bytes read in 601 ms (43.5 MiB/s) 40228 bytes read in 4 ms (9.6 MiB/s) Failed to load '/boot/dtb/amlogic/overlay/-fixup.scr' ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 22783777 Bytes = 21.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7a982000, end 7bf3c721 ... OK Loading Device Tree to 000000007a90f000, end 000000007a981fff ... OK "Synchronous Abort" handler, esr 0x96000004 elr: 00000000010656ec lr : 0000000001055038 (reloc) elr: 000000007dfb46ec lr : 000000007dfa4038 x0 : e14b4287a666c25d x1 : 000000007dfbc290 x2 : 0000000000000010 x3 : 000000007bf54e10 x4 : 0000000000000000 x5 : e14b4287a666c25d x6 : 0000000001000000 x7 : 0000000000000000 x8 : 0000000000000007 x9 : 0000000000000000 x10: 0000000000000178 x11: 000000007bf40eec x12: 00000000000000a4 x13: 000000007bf40ea8 x14: 000000007a90f000 x15: 0000000000000020 x16: 000000007df5946c x17: 0000000000000000 x18: 000000007bf4cdb0 x19: 000000007af41040 x20: 000000007df4fb18 x21: 000000007dfbc290 x22: 0000000000001000 x23: 000000007bf54d60 x24: 000000007dfdacb8 x25: 0000000001000000 x26: 0000000000000000 x27: 0000000001000000 x28: 0000000000001000 x29: 000000007bf40ea0 Code: eb04005f 54000061 52800000 14000006 (386468a3) Resetting CPU ... resetting ... bl31 reboot reason: 0xd bl31 reboot reason: 0x0 system cmd 1. And with sd card GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 103545 BL2 Built : 11:58:42, May 27 2017. gxl gc3c9a84 - xiaobo.gu@droid05 set vcck to 1120 mv set vddee to 1000 mv Board ID = 1 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 912MHz - PASS Rank0: 1024MB(auto)-2T-13 Rank1: 1024MB(auto)-2T-13 DataBus test pass! AddrBus test pass! -s Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000 New fip structure! Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600 Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400 Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x000af000 NOTICE: BL3-1: v1.0(release):3348978 NOTICE: BL3-1: Built : 15:44:01, May 12 2017 [BL31]: GXL CPU setup! mpu_config_enable:ok [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07] OPS=0x82 8f bb f0 da ba 22 d2 cf 1 b0 31 f4 [0.358822 Inits done] secure task start! high task start! low task start! ERROR: Error initializing runtime service opteed_fast <debug_uart> U-Boot 2022.07-armbian (Nov 25 2023 - 12:50:42 +0000) libretech-cc Model: Libre Computer AML-S905X-CC SoC: Amlogic Meson GXL (S905X) Revision 21:b (82:2) DRAM: 2 GiB Core: 169 devices, 27 uclasses, devicetree: separate MMC: mmc@72000: 0, mmc@74000: 1 Loading Environment from nowhere... OK In: serial Out: serial Err: serial [BL31]: tee size: 0 [BL31]: tee size: 0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1: Armbian Retrieving file: /uInitrd Retrieving file: /Image append: root=UUID=a6cf29bd-49ae-4d3b-bf22-800408ae1fba rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles Retrieving file: /dtb/amlogic/meson-gxl-s905x-p212.dtb Moving Image from 0x8080000 to 0x8200000, end=9cd0000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 22783777 Bytes = 21.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 08008000 Booting using the fdt blob at 0x8008000 Loading Ramdisk to 7a982000, end 7bf3c721 ... OK Loading Device Tree to 000000007a975000, end 000000007a98169c ... OK "Synchronous Abort" handler, esr 0x96000004 elr: 00000000010656ec lr : 0000000001055038 (reloc) elr: 000000007dfb46ec lr : 000000007dfa4038 x0 : e14b4287a666c25d x1 : 000000007dfbc290 x2 : 0000000000000010 x3 : 000000007bf54e10 x4 : 0000000000000000 x5 : e14b4287a666c25d x6 : 0000000001000000 x7 : 0000000000000000 x8 : 0000000000000007 x9 : 0000000000000000 x10: 0000000000000188 x11: 000000007bf409ec x12: 00000000000000b4 x13: 000000007bf409a8 x14: 000000007a975000 x15: 0000000000000020 x16: 000000007df7a768 x17: 0000000000000000 x18: 000000007bf4cdb0 x19: 000000007af41040 x20: 000000007df4fb18 x21: 000000007dfbc290 x22: 0000000000001000 x23: 000000007bf54d60 x24: 000000007dfdacb8 x25: 0000000001000000 x26: 0000000000000000 x27: 0000000001000000 x28: 0000000000001000 x29: 000000007bf409a0 Code: eb04005f 54000061 52800000 14000006 (386468a3) Resetting CPU ... resetting ... bl31 reboot reason: 0xd bl31 reboot reason: 0x0 system cmd 1. Is there any way to restore original firmware?

Yes, you can obviously reinstall the boot completely instead of backing up what you have on your system. This is great info in the thread! I opted for a backup rather than a reinstall. Not only may, I have learned it is more of a rule than an exception. This an example with the opi5 img: Model: Loopback device (loopback) Disk /dev/loop0: 7315MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 16,8MB 285MB 268MB fat16 bootfs bls_boot 2 285MB 7315MB 7030MB ext4 rootfs Witch is the reason I do a dd of the entire boot sector (including any existing boot partitions if they exist) in the initial backup, sup-sequential backups, I just mount both partitions (if there is a boot partition) on the img and backs up the entire file system.

I got this on a nano pi and have WordPress on it and use it as a backup and I back it up with WP Synchro. MariaDB Database Server MariaDB version 10.5.21 But it gets all sort of errors like this: 1 Error(s) during migration: Migration aborted, due to a SQL query failing. See WP Synchro log (found in menu "Logs") for specific information about the query that failed. The specific error from database server was: "Unknown collation: 'utf8mb4_0900_ai_ci'". That means that the charset/collation used is not supported by the target database engine. The table charset/collations needs to be changed into a supported charset/collation for the target database or excluded from migration. See documentation on wpsynchro.com for further help. 1 Error(s) during migration: Table 'wordpress.wpsyntmp_65b643f7cbd44' doesn't exist 1 Error(s) during migration: Table 'wordpress.wpsyntmp_65b643f7cc1c2' doesn't exist 3 Error(s) during migration: Table 'wordpress.wpsyntmp_65b643f7cc396' doesn't exist Table 'wordpress.wpsyntmp_65b643f7cc396' doesn't exist Table 'wordpress.wpsyntmp_65b643f7cc396' doesn't exist I can click on RESUME MIGRATION and that's how I got the errors here but it can keep going and I did that one time before took me over a hour to click on the RESUME MIGRATION over and over. Then at the end WordPress said error in database. Have another Debian on a old i386 and I got MySQL install on it. by putting this one line in /etc/apt/sources.list: deb http://ftp.de.debian.org/debian bookworm main contrib non-free non-free-firmware Then could do a apt update and apt install mysql-server. That worked but it don't on this arm armbian for the nano pi. I know with MySQL I don't get any error with the WP Synchro. Looked and I guess no way to install the MySQL on it. Or can't they update the MariaDB to be 100% computable with MySQL? root@nanopi-dock:~# apt install mysql-server Reading package lists... Done Building dependency tree... Done Reading state information... Done Package mysql-server is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'mysql-server' has no installation candidate root@nanopi-dock:~# -Raymond Day

I checked my image. In the minicom console (BPI-M3 -UART -> FTD232 -> USB - Host Linux), in the SSH session, and on the monitor screen connected via HDMI, I see the same greeting pictures: ____ ____ _ __ __ _____ | __ )| _ \(_) | \/ |___ / | _ \| |_) | | | |\/| | |_ \ | |_) | __/| | | | | |___) | |____/|_| |_| |_| |_|____/ Welcome to Armbian 23.10 Bookworm with Linux 6.4.10 No end-user support: built from trunk & unsupported (bookworm) userspace! System load: 1% Up time: 4 min Memory usage: 6% of 1.96G IP: 192.168.100.101 CPU temp: 46�°C Usage of /: 6% of 15G leo@bananapim3:~$ dmesg | grep -i hdmi [ 0.000000] Kernel command line: root=UUID=41970142-87ec-4b91-8231-1b55ee68d69f rootwait rootfstype=ext4 splash=verbose console=ttyS0,115200 console=1 [ 0.084376] platform 1ee0000.hdmi: Fixed dependency cycle(s) with /soc/lcd-controller@1c0d000/ports/port@1/endpoint@1 [ 0.086788] platform connector: Fixed dependency cycle(s) with /soc/hdmi@1ee0000/ports/port@1/endpoint [ 2.327031] sun8i-dw-hdmi 1ee0000.hdmi: supply hvcc not found, using dummy regulator [ 2.327713] sun8i-dw-hdmi 1ee0000.hdmi: Detected HDMI TX controller v1.32a with HDCP (sun8i_dw_hdmi_phy) [ 2.328344] sun8i-dw-hdmi 1ee0000.hdmi: EVENT=plugin [ 2.328730] sun8i-dw-hdmi 1ee0000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.329389] sun4i-drm display-engine: bound 1ee0000.hdmi (ops 0xc0baecbc) [ 2.330594] sun8i-dw-hdmi 1ee0000.hdmi: read_hpd result: 1 [ 43.228319] sun8i-dw-hdmi 1ee0000.hdmi: EVENT=plugin [ 44.121951] sun8i-dw-hdmi 1ee0000.hdmi: EVENT=plugin Observation: My monitor is very smart. He thinks he has correctly identified the entrance from the three possible ones. But he was wrong. I had to press the button with my hand to switch the mode and see the command prompt for entering the password.

On a Rock 5B, I installed Armbian 23.11 Bookworm CLI via a SD card and now trying to setup boot via the NVMe drive. I followed the instructions on https://www.armbian.com/rock-5b/ to create a partition on the NVMe drive, format it, then tried `armbian-install` to boot from SPI. However armbian-install does not list the option to "Boot from SPI". It shows only the following options: 1 Boot from SD - system on SATA, USB, or NVMe 5 Install/Update the bootloader on SD/eMMC I then noticed I do not have a SPI device. /dev/mtdblock0 doesn't exist as well as "cat /proc/mtd" is empty. # ls /dev/mtd* ls: cannot access '/dev/mtd*': No such file or directory # cat /proc/mtd dev: size erasesize name # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk1 179:0 0 29.7G 0 disk ├─mmcblk1p1 179:1 0 256M 0 part /boot └─mmcblk1p2 179:2 0 29.2G 0 part /var/log.hdd / zram0 251:0 0 7.7G 0 disk [SWAP] zram1 251:1 0 50M 0 disk /var/log zram2 251:2 0 0B 0 disk nvme0n1 259:0 0 3.7T 0 disk └─nvme0n1p1 259:1 0 10G 0 part # dmesg | grep -i spi [ 0.000000] GICv3: 480 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.679958] spi spi0.0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/regulators/dcdc-reg7 [ 0.679996] spi spi0.0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/dvs3-null-pins [ 0.680004] spi spi0.0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/dvs2-null-pins [ 0.680011] spi spi0.0: Fixed dependency cycle(s) with /spi@feb20000/pmic@0/dvs1-null-pins Is there something I need to do such as specifying a dtoverlay to enable SPI? Thanks in advance for your help.

I just want to add a few comments to this whole dtb overlay discussion. First I want to thank all of you involved in this discussion. You all have different view points and I think are tackling a very difficult problem to which there is no perfect solution. What comes out of this discussion should be applied to the other soc families as well, as they all suffer from some form of this issue as there is no standard in place that works for all use cases well. From what I have seen, good minds are thinking this through and I expect a good result to follow. The reason I am commenting at all, is because in my role as forum moderator, the basic question: "How do I enable feature x on my board" is one of, if not the most commonly asked question by end users of the forum. And when the answer is 'just write a dtb overlay', you have lost 95% of those users as they do not have the skills/knowledge to do that. The status of the dtb overlay's across Armbian supported and community maintained boards is poor. There is no standardization from family to family or board to board. And no testing of what does exist to ensure that it works. Now I'm not saying that all of this needs to be solved in what comes out of this design discussion. I'm just saying from my perspective as a moderator that this is an area that can use some attention, and in doing so, please try to make the end result usable by the typical end user of an sbc, trying to do common things. I realize also that I'm saying this when I only use these boards as servers and don't personally need any of the functionality the overlays provide. But as a forum moderator, I see the mismatch between what is being done and some common use cases that end users are looking for.

I booted the RC from 1/20/2024, set the ftdfile to rc3588s-orangepi-5b.dtb in armbianEnv.txt, and rebooted: no wifi or bluetooth. The hci0 and wlan0 devices are not present. They both work on the Linux 5.10 kernel. My armbianEnv.txt: -------------------------- verbosity=1 bootlogo=true overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588s-orangepi-5b.dtb rootdev=UUID=38eb4cb5-0503-4a0a-900f-7a5167517a20 rootfstype=ext4 overlays=sata1 sata2 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

@pixdrift I built an image for the zero3 from your repository and I am not having any difficulties with the overlays. If you think it is the overlays that are causing your boot problems you can try putting your system drive on another machine and removing the overlays line in: sysadmin@orangepizero3:~$ more /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun50i-orangepizero2-3 rootdev=UUID=8b58b731-6024-4fbe-bd3e-c784b3b9a449 rootfstype=ext4 overlays=i2c3 ir otg-host spi1-cs0-spidev uart5 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Armbian-config creates and modifies this line when you enable/disable overlays. If that resolves the problem try adding overlays one at a time. I would suggest this order: i2c3 ir spi1-cs0-spidev uart5 otg-host

Dear Community, I want to build a custom FirmWare for Banana Pi M2 Berry, im currently using the BPI-M2-Ultra Firmware, cuz no BPI-M2-Berry FirmWare exist. What do I need for building for my SBC(BPI-M2-Berry) ? I want to use my SBC as a LTE-Router/ Mesh-Repeater and want to pre-install some necessary packages, the device need. I want to build a Dashboard for Administrate the Device. Maybe I'll use electron + reactjs, or would it be better to use php for it? Greetz BlackLeakz

Unreleased open hardware board in CM4 footprint https://www.crowdsupply.com/ov-tech-gmbh/pi-mx8-module - SOC: NXP i.MX 8M Plus - NXP guarantees production of the chip for 10 years. - 4x A53 cores at up to 1.8 GHz / 1x M7 core at up to 700 MHz - 1 GB/2 GB/4 GB/8 GB LPDDR4 system memory - Vivante GC7000UL GPU - Gigabit Ethernet PHY supporting IEEE 1588v2 and SyncE - PCIe Gen3 1x1 Interface - Optional eMMC with 8 GB/16 GB/32 GB - Optional 2.4 GHz & 5 GHz Wi-Fi + Bluetooth 5.2 (Murata LBEE5PK2BC) - Optional Coral Edge TPU connected via PCIe - Two CSI-2 interfaces, one with 4-lane and one 2-lane width Some open hardware carrier boards exist such as Twisted fields CanBUS/ Robotics Piunora Camera, Qwiic, Arduino pinout Jkiv Gigabit, uSD Will cluster RobertLukan dual camera, 40 pin header Wiretrustee SATA/ NAS Mirko PC 2x HDMI, 2x Camera, M.2, uSD, 40pin tkircher camera, Qwiic, M.2, HDMI, uSD Others I plan to use this thread to document the hardware and other related efforts to support IMX8 hardware, intending to add Armbian support for this board. So far I have found: - https://github.com/Joshua-Riek/ubuntu-apalis-imx8 - https://github.com/TechNexion-customization/ubuntu-tn-imx/tree/master?tab=readme-ov-file#technexion-ubuntu-lts-image-builder

Ok, i do have one, but not a vim4. I have a vim 3. But armbian doesnt install on a vim3 as far as i can tell. No applicable or verified instructions exist for installing it there. I would like a working vim board with armbian. So maybe a vim4 is my only choice. I have not seen the screen work outside of android that came with it. On an edge V or vim 3 with any mainline distro. But it is expected to work? I will have to buy a vim4 to try.

Same issue. Mine is also a similar g12a device. I tested from 23.8.1 - 23.11.1 and all have problems. But works fine on my gxl device. G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:0;READ:0;0.0; bl2_stage_init 0x01 bl2_stage_init 0x81 hw id: 0x0000 - pwm id 0x01 bl2_stage_init 0xc1 bl2_stage_init 0x02 L0:00000000 L1:00000703 L2:00008267 L3:04000000 S1:00000000 B2:00002000 B1:e0f83180 TE: 96329 BL2 Built : 14:02:05, Nov 23 2020. g12a g966c864 - gongwei.chen@droid11-sz Board ID = 1 Set cpu clk to 24M Set clk81 to 24M CPU clk: 1200 MHz Set clk81 to 166.6M eMMC boot @ 0 sw8 s board id: 1 Load FIP HDR DDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0 fw parse done PIEI prepare done 00000000 emmc switch 1 ok ddr saved addr:00016000 Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0 00000000 emmc switch 0 ok fastboot data verify result: 255 Cfg max: 12, cur: 1. Board id: 255. Force loop cfg LPDDR4 probe LPDDR4_PHY_V_0_1_22-Built : 15:59:30, May 25 2020. g12a gb6bfa83 - gongwei.chen@droid11-sz ddr clk to 1176MHz dmc_version 0000 Check phy result INFO : End of CA training INFO : End of initialization INFO : Training has run successfully! Check phy result INFO : End of initialization INFO : End of read enable training INFO : End of fine write leveling INFO : End of read dq deskew training INFO : End of MPR read delay center optimization INFO : End of Write leveling coarse delay INFO : End of read delay center optimization INFO : Training has run successfully! Check phy result INFO : End of initialization INFO : End of MPR read delay center optimization INFO : End of write delay center optimization INFO : End of read delay center optimization INFO : End of max read latency training INFO : Training has run successfully! 1D training succeed Check phy result INFO : End of initialization INFO : End of 2D read delay Voltage center optimization INFO : End of 2D read delay Voltage center optimization INFO : End of 2D write delay Voltage center optimization INFO : End of 2D write delay Voltage center optimization INFO : Training has run successfully! soc_vref_reg_value 0x 00000024 00000024 00000026 00000025 00000024 00000027 00000026 00000025 00000024 00000025 00000025 00000024 00000026 00000025 00000025 00000026 00000025 00000027 00000027 00000024 00000026 dram_vref_reg_value 0x 00000060 2D training succeed auto size-- 65535DDR cs0 size: 1024MB DDR cs1 size: 1024MB DMC_DDR_CTRL: 00e0001bDDR size: 2048MB cs0 DataBus test pass cs1 DataBus test pass cs0 AddrBus test pass cs1 AddrBus test pass non-sec scramble use zero key ddr scramble enabled 100bdlr_step_size ps== 447 result report boot times 1Enable ddr reg access 00000000 emmc switch 3 ok Authentication key not yet programmed get rpmb counter error 0x00000007 00000000 emmc switch 0 ok Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0 Load BL3X from eMMC, src: 0x00078200, des: 0x01768000, size: 0x000dac00, part: 0 BL33 CHK: 0x000000ff ADDR 017a7170 Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 1 00000000 emmc switch 1 ok Load BL3X from eMMC, src: 0x00078200, des: 0x01768000, size: 0x000dac00, part: 1 0.0;M3 CHK:0;cm4_sp_mode 0 [Image: g12a_v1.1.3394-7d43064d5 2020-05-07 15:37:06 gongwei.chen@droid11-sz] OPS=0x70 ring efuse init 28 0c 70 00 01 15 11 00 00 09 35 38 39 41 48 50 [1.072094 Inits done] secure task start! high task start! low task start! boot bl31 NOTICE: BL31: v1.3(release):079690f10 NOTICE: BL31: Built : 16:11:33, Nov 8 2021 NOTICE: BL31: G12A normal boot! NOTICE: BL31: BL33 decompress pass ERROR: Error initializing runtime service opteed_fast U-Boot 2015.01 (Dec 30 2021 - 18:08:05) DRAM: 2 GiB Relocation Offset is: 76e3b000 mmu cfg end: 0x80000000 mmu cfg end: 0x80000000 spi_post_bind(spifc): req_seq = 0 register usb cfg[0][1] = 0000000077f387e8 NAND: get_sys_clk_rate_mtd() 292, clock setting 200! bus cycle0: 6,timing: 7 NAND device id: 0 ff ff ff ff ff No NAND device found!!! nand init failed: -6 get_sys_clk_rate_mtd() 292, clock setting 200! bus cycle0: 6,timing: 7 NAND device id: 0 ff ff ff ff ff No NAND device found!!! nand init failed: -6 MMC: aml_priv->desc_buf = 0x0000000073e2bd90 aml_priv->desc_buf = 0x0000000073e2e0d0 SDIO Port B: 0, SDIO Port 😄 1 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, cmd->cmdarg=0x1aa, status=0x1ff2800 emmc/sd response timeout, cmd55, cmd->cmdarg=0x0, status=0x1ff2800 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 40000000 [set_emmc_calc_fixed_adj][875]find fixed adj_delay=20 init_part() 297: PART_TYPE_AML [mmc_init] mmc init success Amlogic multi-dtb tool GZIP format, decompress... Multi dtb detected Multi dtb tool version: v2 . Support 3 dtbs. aml_dt soc: g12a platform: u212 variant: 2g dtb 0 soc: g12a plat: u212 vari: 1g dtb 1 soc: g12a plat: u212 vari: 2g dtb 2 soc: sm1 plat: ac213 vari: 2g Find match dtb: 1 start dts,buffer=0000000073e30920,dt_addr=0000000073e30920 get_partition_from_dts() 92: ret 0 Amlogic multi-dtb tool Single dtb detected parts: 18 00: logo 0000000000800000 1 01: recovery 0000000001800000 1 02: misc 0000000000800000 1 03: dtbo 0000000000800000 1 04: cri_data 0000000000800000 2 05: param 0000000001000000 2 06: boot 0000000001000000 1 set has_boot_slot = 0 07: rsv 0000000001000000 1 08: metadata 0000000001000000 1 09: vbmeta 0000000000200000 1 10: tee 0000000002000000 1 11: vendor 0000000014000000 1 12: odm 0000000008000000 1 13: system 0000000050000000 1 14: product 0000000008000000 1 15: cache 0000000040000000 2 16: backup 0000000040000000 2 17: data ffffffffffffffff 4 init_part() 297: PART_TYPE_AML eMMC/TSD partition table have been checked OK! crc32_s:0x1577dad == storage crc_pattern:0x1577dad!!! crc32_s:0xee152b83 == storage crc_pattern:0xee152b83!!! crc32_s:0x79f50f07 == storage crc_pattern:0x79f50f07!!! mmc env offset: 0x47400000 In: serial Out: serial Err: serial board_late_init: boardid = 0x1 reboot_mode=normal [store]To run cmd[emmc dtb_read 0x1000000 0x40000] _verify_dtb_checksum()-3476: calc eef30c2, store eef30c2 _verify_dtb_checksum()-3476: calc eef30c2, store eef30c2 dtb_read()-3691: total valid 2 update_old_dtb()-3672: do nothing Amlogic multi-dtb tool GZIP format, decompress... Multi dtb detected Multi dtb tool version: v2 . Support 3 dtbs. aml_dt soc: g12a platform: u212 variant: 2g dtb 0 soc: g12a plat: u212 vari: 1g dtb 1 soc: g12a plat: u212 vari: 2g dtb 2 soc: sm1 plat: ac213 vari: 2g Find match dtb: 1 amlkey_init() enter! [EFUSE_MSG]keynum is 4 vpu: driver version: v20190313 vpu: detect chip type: 8 vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz) vpu: clk_level in dts: 7 vpu: vpu_power_on vpu: set_vpu_clk vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100) vpu: set_vpu_clk finish vpu: vpu_module_init_config vpp: vpp_init vpp: vpp osd2 matrix rgb2yuv.............. hdr_func 4, hdr_process_select 0x1 cvbs: cpuid:0x28 vdac_gsw_init: 0x0 cvbs: find clk_path: 0x0 cvbs: find performance_pal config cvbs: find performance_ntsc config hpd_state=0 do_hpd_detect: hdmimode=1080p60hz do_hpd_detect: colorattribute=rgb,8bit Saving Environment to aml-storage... mmc env offset: 0x47400000 Writing to MMC(1)... done aml_config_dtb 633 aml_config_dtb 663 co_phase = <0x00000003> caps2 = "??"_CAP2_HS200" status = "disabled" status = "okay" Net: dwmac.ff3f0000amlkey_init() enter! amlkey_init() 71: already init! [EFUSE_MSG]keynum is 4 wipe_data=successful wipe_cache=successful upgrade_step=2 reboot_mode:::: normal ext4logoLoadCmd=ext4load mmc 1:${logoPart} ${logoLoadAddr} ${ext4LogoPath} 6220854 bytes read in 180 ms (33 MiB/s) [imgread]load bmp from ext4 part okay bmp pixel: 24 [OSD]load fb addr from dts:/meson-fb [OSD]set initrd_high: 0x7f800000 [OSD]fb_addr for logo: 0x7f800000 [OSD]load fb addr from dts:/meson-fb [OSD]fb_addr for logo: 0x7f800000 [OSD]VPP_OFIFO_SIZE:0xfff01fff [CANVAS]canvas init [CANVAS]addr=0x7f800000 width=5760, height=2160 [OSD]osd_hw.free_dst_data: 0,719,0,575 [OSD]osd1_update_disp_freescale_enable vpp: vpp_matrix_update: 2 cvbs_performance_enhancement cvbs_config_hdmipll_g12a cvbs_set_vid2_clk vdac_enable: 1, module_sel:0x8 hdr_packet vpp: hdr_policy = 1 vpp: Rx hdr_info.hdr_sup_eotf_smpte_st_2084 = 0 amlkey_init() enter! amlkey_init() 71: already init! [EFUSE_MSG]keynum is 4 [KM]Error:f[key_manage_query_size]L515:key[oemkey] not programed yet Command: bcb uboot-command Start read misc partition datas! BCB hasn't any datas,exit! time_out = 7a120 key[0] = b8471420 key[1] = b847ff00 key[2] = 6699dd22 key[3] = 66994cb3 irkey - irkey <timeout> <key1> ...<keyN> - maximum value of N: 10 Usage: irkey - No additional help available. Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 card out (Re)start USB... USB0: USB3.0 XHCI init start Register 3000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... init_part() 282: PART_TYPE_DOS 1 Storage Device(s) found reading s905_autoscript 537 bytes read in 23 ms (22.5 KiB/s) ## Executing script at 01020000 start amlogic old u-boot ## Error: "bootfromsd" not defined card out ** Bad device mmc 0 ** reading boot_android ** Unable to read file boot_android ** card out ** Bad device mmc 0 ** reading u-boot.ext 740080 bytes read in 68 ms (10.4 MiB/s) ## Starting application at 0x01000000 ... U-Boot 2015.01-dirty (Aug 14 2020 - 19:56:34) DRAM: 2 GiB Relocation Offset is: 76eec000 spi_post_bind(spifc): req_seq = 0 register usb cfg[0][1] = 0000000077f83f48 MMC: aml_priv->desc_buf = 0x0000000073edc7c0 aml_priv->desc_buf = 0x0000000073edeb00 SDIO Port 😄 0, SDIO Port B: 1 Using default environment In: serial Out: serial Err: serial vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters vpu: driver version: v20190313 vpu: detect chip type: 8 vpu: clk_level default: 7(666667000Hz), max: 7(666667000Hz) vpu: clk_level = 7 vpu: vpu_power_on vpu: set_vpu_clk vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100) vpu: set_vpu_clk finish vpu: vpu_module_init_config vpp: vpp_init vpp: g12a/b osd1 matrix rgb2yuv .............. vpp: g12a/b osd2 matrix rgb2yuv.............. vpp: g12a/b osd3 matrix rgb2yuv.............. cvbs: cpuid:0x28 cvbs_config_hdmipll_g12a cvbs_set_vid2_clk co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x1, tx-dly 0, clock 40000000 aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x2000 [mmc_startup] mmc refix success [mmc_init] mmc init success Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** movi: not registered partition name, logo movi - Read/write command from/to SD/MMC for ODROID board Usage: movi <read|write> <partition|sector> <offset> <address> [<length>] - <read|write> the command to access the storage - <offset> the offset from the start of given partiton in lba - <address> the memory address to load/store from/to the storage device - [<length>] the size of the block to read/write in bytes - all parameters must be hexa-decimal only [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]set initrd_high: 0x3d800000 [OSD]fb_addr for logo: 0x3d800000 [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]fb_addr for logo: 0x3d800000 [OSD]VPP_OFIFO_SIZE:0xfff01fff [CANVAS]canvas init [CANVAS]addr=0x3d800000 width=5760, height=2160 cvbs: outputmode[1080p60hz] is invalid vpp: vpp_matrix_update: 2 set hdmitx VIC = 16 config HPLL = 5940000 frac_rate = 1 HPLL: 0x3b3a04f7 HPLL: 0x1b3a04f7 HPLLv1: 0xdb3a04f7 config HPLL done j = 6 vid_clk_div = 1 hdmitx phy setting done hdmitx: set enc for VIC: 16 enc_vpu_bridge_reset[1319] rx version is 1.4 or below div=10 Net: dwmac.ff3f0000MACADDR:02:00:00:11:15:01(from chipid) Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 (Re)start USB... USB0: USB3.0 XHCI init start Register 3000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf reading /extlinux/extlinux.conf 532 bytes read in 29 ms (17.6 KiB/s) 1: Armbian Retrieving file: /uInitrd reading /uInitrd 15122788 bytes read in 878 ms (16.4 MiB/s) Retrieving file: /Image reading /Image 27433472 bytes read in 1579 ms (16.6 MiB/s) append: root=UUID=b134c113-5cbe-4ccc-ab4a-6c24dde01dd3 rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymous Retrieving file: /dtb/amlogic/meson-g12a-u200.dtb reading /dtb/amlogic/meson-g12a-u200.dtb 72240 bytes read in 43 ms (1.6 MiB/s) [rsvmem] get fdtaddr NULL! rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed ## Loading init Ramdisk from Legacy Image at 03080000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15122724 Bytes = 14.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK active_slot is <NULL> Unknown command 'store' - try 'help' No dtbo patitions found load dtb from 0x1000000 ...... ERROR: Did not find a cmdline Flattened Device Tree load dtb from 0x0 ...... ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... ** Bad device usb 1 ** ** Bad device usb 2 ** ** Bad device usb 3 ** card out ** Bad device mmc 1 ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** odroidn2#

The situation with the overlays is more confusing than I originally anticipated. I assumed that the zero2 overlays would have been in good working order. I should know better than to assume anything! Would someone with an orangepizero2 please test the overlay function to see what works and does not. Use armbian-config -> System -> Hardware and turn on all options. Reboot and check the console boot log to see which overlays load or fail. It looks like the bigtreetech-cb1board created the overlay for sun50i-h616 (/kernel/archive/sunxi-6.7/patches.armbian/arm64-dts-overlay-sun50i-h616-bigtreetech-cb1.patch). However not all SBCs that use the h616 SOC implement the same features. The current sun50i-h616 overlays have implementations for ws8212, tft3, mcp and light, none of which exist on orangepizero2/3. The spi overlays might work as well as the ir. There is no overlay to enable i2c3 or add host function to usbotg. New SBCs that use the h618 SOC will probably implement different features than the zero2/3. The zero2 (h616) and the zero3 (h618) implement the same i/o features. My current thoughts are to implement a new set of overlays for the orangepizero2/3, which have identical i/o. Then both boards then need to be pointed to the new overlays with an overlay_prefix in the board config. I would start with the overlays from the Zunlong distribution for orangepizero3. I would appreciate feedback before I go charging off in the wrong direction (again).

Yes, u-boot-s905x-s912 is correct for an s905w based board. Your original post said u-boot-s905x2-s912 which doesn't exist

This does not change the current boot order and requires additional hardware. Hardware used in my testing: BananaPi BPI-CM4IO Baseboard with BPI-CM4 Module Mini PCI-E PCI Express to SATA 3.0 Dual Ports Adapter Converter Hard Drive Extension Card https://a.co/d/0G679qW Kingston 120GB A400 SATA 3 2.5" Internal SSD https://a.co/d/fB2qf3r External power supply for Hard Drive 2.5" 3.5" https://www.ebay.com/itm/114620135743 bananapi: ~ $ lspci 00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01) 01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) bananapi: ~ $ sudo blkid /dev/mmcblk1p1: LABEL="EMMC" UUID="67ea5c62-c9cb-498e-91ff-3e60d71bd1ab" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="0a8751c2-01" /dev/sda2: LABEL="ROOTFS" UUID="39d23eae-ba3a-4b28-acba-8f45ff8eed1c" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="e6053ca6-02" /dev/sda1: LABEL="BOOT" UUID="d540a625-98a8-4c73-a5a3-7a905d5bbb98" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e6053ca6-01" /dev/zram0: UUID="ee6d34f4-fda2-4207-8dc9-b8a4b83cd759" TYPE="swap" bananapi: ~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 111.8G 0 disk ├─sda1 8:1 0 508M 0 part /boot └─sda2 8:2 0 111.3G 0 part / mmcblk1 179:0 0 14.6G 0 disk └─mmcblk1p1 179:1 0 14.6G 0 part mmcblk1boot0 179:32 0 4M 1 disk mmcblk1boot1 179:64 0 4M 1 disk zram0 253:0 0 1G 0 disk [SWAP] Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

I'm assuming this is as typo, since that file doesn't exist.

armbianmonitor can not upload for whatever reason so here is the output from armbianmonitor -U armbianmonitor.log bruno@orangepione:~$ less /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=2f506a90-a24d-4930-a5bb-8d61ce45629a rootfstype=ext4 overlays=usbhost0 usbhost1 usbhost2 usbhost3 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

I think the overlay files for zero2 and zero3 can be the same as the hardware layout is identical. Zero2w is different. I have put together and tested 3 overlay files, - enable i2c3 - enable spi1 and create spidev - change usbotg to host I could use the i2c3 and spi1 overlays to fix the PH5 duplication if it will not be done in sun50i-h616.dtsi. Usb2 and 3 are already enabled and work without further changes. I am still looking into uart5 to determine what is required. Ir is another item to look at. Then there is sound which has output on the header. But since sound is not yet working that will have to wait. All these overlays currently exist in the Zunlong image. After @Gunjan Gupta showed me how to build an overlay I am now able to reverse engineer the Zunlong dtbos and create dts/dtbo for Armbian.

I *think* some pins / IOs etc are disabled in dts, in part as these days pins has multiple (alternate) functions (e.g. gpio / i2c / uart / spi / usb etc). I'm not too sure if say the same pin is enabled for gpio and i2c that if they'd conflict with each other as in that in practice it would only be one of the function i2c or gpio that is valid. the device tree compiler dtc has become pretty common and used these days it shouldn't be too difficult for anyone to edit the dts file (e.g. change that status from 'disabled' to 'okay' and re-compile that into its dtb file, then reboot. some non-armbian examples are like: https://mjoldfield.com/atelier/2017/03/rpi-devicetree.html ^ in fact even without the dts file, it is possible to take the dtb file and convert that to a dts file, make the edits and recompile that back to the edited dtb file. other examples: https://www.udoo.org/forum/threads/manually-editing-device-tree-dts-files.21600/ https://www.emcraft.com/som/vf6/controlling-gpio-from-linux dtsi are includes, so that those common things get included as common templates, and the differences changes are updated in the final dts file for the board. I think boot loaders like uboot may be possible to choose different dts/dtb file etc on the boot prompt command line, but I'm not sure how nor have i tried that. more interesting reading about device tree, https://elinux.org/images/a/a3/Elce2013-petazzoni-devicetree-for-dummies.pdf it is invented originally for the beagle bone black, in fact it exist earlier, subsequent to that these days device tree has become a linux standard practice especially for single board computers. Computers used to have standard features e.g. drives, keyboard, mouse, usb and that practically they are 'all the same'. then came single board computers 'revolution' and there are 'capes' and FPGAs (hardware is software ! change the program and hardware changes !), and that GPIO pins are pin-muxed, so today hardware is *configurable*. e.g. if you place a led on a board, it can be physically wired to any of the gpio pins, and you can further wire it as LOW = ON (sink), or HIGH = ON (source). but that as an 'alternate' function e.g. a led, you may even configure PWM and blink patterns and/or events for the leds. that that is still a gpio pin, but that the function changes by simple virtue of the context. it is a led. https://elinux.org/images/1/19/Dynamic-dt-keynote-v3.pdf https://cdn-learn.adafruit.com/downloads/pdf/introduction-to-the-beaglebone-black-device-tree.pdf https://elinux.org/images/e/e2/Engaging_Device_Trees_0.pdf https://ofitselfso.com/BeagleNotes/AboutTheDeviceTree.pdf https://elinux.org/Device_Tree_Usage