@KrzyPacu Start by copying your original dtb into tm16xx-display folder: cd tm16xx-display cp meson-sm1-x96-air-gbit.dtb original.dtb # or alternatively run: make extract-dtb Then, assuming the corresponding device tree source overlay in the "devices" subfolder is "x96-max-1gbit.dtso", build the updated dtb: make x96-max-1gbit.dtb # <-- same name as the dtso file in devices subfolder but with dtb extension Finally, replace the original dtb of your boot path with the updated one (first keep a copy of your original dtb somewhere else, just in case) and reboot: cp release/x96-max-1gbit.dtb /boot/dtb/{YOUR_DTB_PATH}.dtb reboot

$ make meson-sm1-x96-air-gbit_mod.dtb ORIGINAL_DTB=meson-sm1-x96-air-gbit.dtb make: *** No rules for object execution 'meson-sm1-x96-air-gbit_mod.dtb'. Stop. https://github.com/jefflessard/tm16xx-display/blob/main/README.md#configure-the-device-tree I can't do option 1 because I don't have the "/boot/armbianEnv.txt" file . Where do I add the entry "user_overlays=tm16xx"

Hi @KrzyPacu I can only provide basic instructions without any support regarding loading overlays. It's not supported on every device (and I personally don't own a device which supports this). You can always search for other posts on device tree overlay for your device if you absolutely want to use overlays. Though, you can easily embed the device tree overlay into your dtb instead. This is what I do personally. You can check instructions of Option 2: Create an updated dtb at : https://github.com/jefflessard/tm16xx-display/blob/main/README.md#configure-the-device-tree

I am trying to run this driver on Vontar X3 Armbian 25.8.0-trunk.163 bookworm. I stopped at the point "Edit /boot/armbianEnv.txt to load the overlay" because I do not have the armbianEnv.txt file. What should I do next to add the generated file "hk1-x3.dtbo" to my device tree file "meson-sm1-x96-air-gbit.dtb"?

armbianmonitor logs: https://paste.armbian.com/rolisaboru I’m running Armbian 25.2 on a Banana Pi BPI-M4-Zero (Allwinner sun50i-h618). EMAC1 (ethernet@5030000) with its internal PHY never comes up: sunxi-gmac 5030000.ethernet end0: renamed from eth0 … No PHY found! … phy init again… No PHY found! … phy init failed So far I have tried: 1. Directly patching full.dts Enabled /soc/ethernet@5030000 (status = “okay”) Added phy-mode = "rmii", pinctrl-0 = <&rmii_pins>, phy-handle, phy-supply etc. Defined a simple ethernet-phy@0 under MDIO. Recompiled to sun50i-h618-bananapi-m4-zero.dtb and rebooted. 2. User overlay (.dts → .dtbo) Created fragments to: Turn on /soc/ethernet@5030000/mdio Inject an ethernet-phy@0 node Enable EMAC1, assign RMII pins, MDIO and PHY handle Compiled with dtc -@ and loaded via user_overlays=bpi-m4z-eth in armbianEnv.txt. 3. Following Armbian build PR #6617 Tried the patch for H618’s internal AC300 PHY from https://github.com/armbian/build/pull/6617 No change: PHY still not detected, no power-up. 4. Troubleshooting notes Overlay apply errors: FDT_ERR_NOTFOUND dtc compile errors on duplicate or missing phandle references Verified pinctrl entries (rmii-pins) and alias names match base DTS I’ve collected a full hardware/software report via armbianmonitor—see the logs here: https://paste.armbian.com/rolisaboru What I’m looking for A known-good snippet of device-tree (base DTS or overlay) that brings up the internal EMAC1 PHY on sun50i-h618 Advice on any missing power-or-clock settings or MFD nodes required for the AC300 PHY Confirmation whether additional kernel/config patches are needed Thanks in advance for any pointers!