Search the Community

I noticed that the Cubie a5e would reboot when anything that draws moderate power (>100mA) was connected to the USB3 port. Thought it was my power supply or USB cable, but after changing that out and doing some testing, I have determined that the reboot problem doesn't happen with the Radxa Bullseye image, only with the Armbian Trixie. I haven't had a chance to test older Armbian builds to see if it broke somewhere along the way, but that's what I'll do next. Armbian boot (26.2.0 trunk 385): U-Boot SPL 2026.01_armbian-2026.01-S127a-P96c6-H560c-Va7f1-B2eb2-R448a (Feb 03 2026 - 12:13:55 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.13.0(debug):armbian NOTICE: BL31: Built : 12:13:32, Feb 3 2026 NOTICE: BL31: Detected Allwinner A523 SoC (1890) NOTICE: BL31: Found U-Boot DTB at 0xa0c06a8, model: Radxa Cubie A5E INFO: Configuring SPC Controller INFO: BL31: Platform setup done INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: Maximum SPI INTID supported: 287 INFO: BL31: Initializing runtime services INFO: BL31: cortex_a55: CPU workaround for erratum 1530923 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 ns16550_serial serial@2500000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2026.01_armbian-2026.01-S127a-P96c6-H560c-Va7f1-B2eb2-R448a (Feb 03 2026 - 12:13:55 +0000) Allwinner Technology CPU: Allwinner A523 (SUN55I) Model: Radxa Cubie A5E DRAM: 2 GiB sunxi_set_gate: (CLK#35) unhandled Core: 88 devices, 25 uclasses, devicetree: separate WDT: Not starting watchdog@2050000 MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In: serial@2500000 Out: serial@2500000 Err: serial@2500000 Net: eth0: ethernet@4500000 starting USB... sun4i_usb_phy phy@4100400: External vbus detected, not enabling our own vbus USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 Bus usb@4101000: 1 USB Device(s) found Bus usb@4101400: 1 USB Device(s) found Bus usb@4200000: 1 USB Device(s) found Bus usb@4200400: 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 PCIe: Acquiring resources... PCIe: All resources acquired. Starting power-on sequence... PCIe: Toggling external device reset (PERST#)... PCIe: Hardware power-on sequence successful. PCIe: Disabling DBI write protection... PCIe: DBI region: 0x04800000-0x04c80000 PCIe: IO region: 0x21000000-0x22000000 PCIe: MEM region: 0x22000000-0x30000000 PCIe: CFG region: 0x20000000-0x21000000 PCIe: Lanes: 1, Max Speed: Gen2 Link Status: 0x00000004 RDLH_LINK_UP: 0 SMLH_LINK_UP: 0 LINK_SPEED: 0 LINK_WIDTH: 0 Link Status: 0x00000004 RDLH_LINK_UP: 0 SMLH_LINK_UP: 0 LINK_SPEED: 0 LINK_WIDTH: 0 Link Status: 0x00000017 RDLH_LINK_UP: 1 SMLH_LINK_UP: 1 LINK_SPEED: 0 LINK_WIDTH: 0 pcie link up success PCIe: Link active at Gen2 Device 0: Vendor: 0x1e0f Rev: 10410105 Prod: X06PD8L0QUM1 Type: Hard Disk Capacity: 244198.3 MB = 238.4 GB (500118192 x 512) ... is now current device Scanning nvme 0:1... Found U-Boot script /boot.scr 4641 bytes read in 0 ms ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from nvme 263 bytes read in 0 ms Load fdt: /dtb/allwinner/sun55i-a527-cubie-a5e.dtb 37110 bytes read in 1 ms (35.4 MiB/s) Working FDT set to 4fa00000 Failed to load '/dtb/allwinner/overlay/sun55i-a527-fixup.scr' 16552556 bytes read in 55 ms (287 MiB/s) 39950848 bytes read in 102 ms (373.5 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x42900000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16552492 Bytes = 15.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 49036000, end 49fff22c ... OK Loading Device Tree to 0000000048fc4000, end 0000000049035fff ... OK Working FDT set to 48fc4000 Starting kernel ... Armbian_community 26.2.0-trunk.385 Trixie ttyS0 radxa-cubie-a5e login: Radxa Bookworm Boot: [207]HELLO! BOOT0 is starting! [210]BOOT0 commit : 33d8db429a-dirty [214]periph0 has been enabled [218]set pll end [219]PL gpio voltage : 3.3V [224]PMU: AXP2202 [229]PMU: AXP1530 [234]power mode:33, sys_vol:920 [239]vaild para:1 select dram para0 [242]dram_para[0]:0x4b0 [245]dram_para[1]:0x8 [247]dram_para[2]:0x7070707 [250]dram_para[3]:0xd0d0d0d [253]dram_para[4]:0xe0e [256]dram_para[5]:0x84848484 [259]dram_para[6]:0x310a [262]dram_para[7]:0x10001000 [265]dram_para[8]:0x0 [267]dram_para[9]:0x34 [270]dram_para[10]:0x1b [272]dram_para[11]:0x33 [275]dram_para[12]:0x3 [277]dram_para[13]:0x0 [280]dram_para[14]:0x0 [282]dram_para[15]:0x4 [285]dram_para[16]:0x72 [287]dram_para[17]:0x0 [290]dram_para[18]:0xe [292]dram_para[19]:0x0 [295]dram_para[20]:0x0 [297]dram_para[21]:0x26 [300]dram_para[22]:0x80808080 [303]dram_para[23]:0x6060606 [306]dram_para[24]:0x1f0b0503 [309]dram_para[25]:0x0 [312]dram_para[26]:0x3a000000 [315]dram_para[27]:0x802f3333 [318]dram_para[28]:0xc0c0bbbf [321]dram_para[29]:0x35352f31 [325]dram_para[30]:0xc64 [327]dram_para[31]:0x48484848 [331]board init ok [353]enable_jtag [355]card no is 0 [357]sdcard 0 line count 4 [360][mmc]: mmc driver ver 2023-03-24 16:23 [370][mmc]: Wrong media type 0x0 [374][mmc]: ***Try SD card 0*** [395][mmc]: HSSDR52/SDR25 4 bit [398][mmc]: 50000000 Hz [401][mmc]: 60906 MB [403][mmc]: ***SD/MMC 0 init OK!!!*** [414]DRAM BOOT DRIVE INFO: V0.67 [419]DRAM_VCC set to 1100 mv [545]DRAM retraining ten [671]DRAM retraining ten [689][AUTO DEBUG]32bit,1 ranks training success! [718]Soft Training Version: T2.0 [7773][SOFT TRAINING] CLK=1200M Stable memtest pass [7778]DRAM CLK =1200 MHZ [7781]DRAM Type =8 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [7792]phy_dfs_clk1 = 800M [8078]phy_dfs_clk2 = 400M [8169]phy_dfs_clk3 = 150M [8290]phy_dfs_clk0 = 1200M [8293]DRAM MDFS VERSION INFO: V0.660 [8298]DRAM MDFS time =38892 ns [8301]DRAM SIZE =2048 MBytes, para1 = 310a, para2 = 8000000, tpr13 = 6465 [8329]DRAM simple test OK. [8332]dram size =2048 [8339]nsi init 2023-2-23 [8343]error:bad magic. [8463]Loading boot-pkg Succeed(index=1). [8467]Entry_name = u-boot [8476]Entry_name = monitor [8480]Entry_name = scp [8484]Entry_name = dtb [8487]mmc not para [8489]Jump to second Boot. NOTICE: BL31: OP-TEE 32bit detected NOTICE: BL31: U-BOOT 32bit detected NOTICE: BL31: v2.5(debug):a6e1826c1 NOTICE: BL31: Built : 10:10:43, Mar 28 2025 NOTICE: BL31: No DTB found. nsi init ok 2022-11-08 ERROR: Error initializing runtime service opteed_fast U-Boot 2018.07-11-boot-aw2501-g4f803d1684e-dirty (Dec 05 2025 - 10:08:58 +0000) Allwinner Technology [08.641]CPU: Allwinner Family [08.644]Model: Radxa Cubie A5E I2C: ready [08.655]DRAM: 2 GiB [08.659]Relocation Offset is: 75e60000 [08.721]secure enable bit: 0 [08.725]PMU: AXP2202 [08.753][AXP2202] comm status : 0x0 = 0x20, 0x1 = 0x90 [08.758][AXP2202] onoff status: 0x20 = 0x4, 0x21 = 0x0 [08.763][AXP2202] reboot/charge status: 0xf0 = 0x0 [08.768]PMU: AXP1530 [08.771]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=600Mhz [08.777]gic: sec monitor mode SPI ALL: ready [08.782]flash init start [08.785]workmode = 0,storage type = 1 [08.788][mmc]: mmc driver ver uboot2018:2024-10-18 9:01:00 -- uboot2018:2025-03-28 10:03:00 [08.796][mmc]: get sdc_type fail and use default host:tm1. [08.802][mmc]: can't find node "mmc0",will add new node [08.807][mmc]: fdt err returned <no error> [08.811][mmc]: Using default timing para [08.814][mmc]: SUNXI SDMMC Controller Version:0x50500 [08.843][mmc]: card_caps:0x3000000a [08.846][mmc]: host_caps:0x3000003f [08.851]sunxi flash init ok get value error [08.860]Loading Environment from SUNXI_FLASH... OK [08.867]No ethernet found. [08.877]Fail to get de's irq! [08.915]NOT support bridge yet [08.918]Warn: no find panel or bridge [08.921]hdmi@5520000 disconnected [08.924]drm hdmi get mode: 1920x1080@60Hz hdmi@5520000: use force output detailed mode clock 148500 kHz, flags[5] H: 1920 2008 2052 2200 V: 1080 1084 1089 1125 bus_format: 0 [09.134]the secure storage item0 copy0 magic is bad [09.148]the secure storage item0 copy1 magic is bad [09.152]usb burn from boot delay time 0 weak:otg_phy_config [09.163]usb prepare ok [09.466]overtime [09.471]do_burn_from_boot usb : no usb exist cann't get the boot_base from the env [09.494]update part info [09.498]update bootcmd pcie link up success PCIe speed of Gen2 [09.908]change working_fdt 0xbbe0fe18 to 0xbbddfe18 get value error [09.914][mmc]: get sunxi-mmc0 string failed [09.918]The storage not support sample function [09.924]## error: update_fdt_dram_para_from_bootpara : FDT_ERR_NOTFOUND ret 0 [09.935]chip id : 0x0000ff10 0x00004824 0x0000d710 0x00001d96 [09.940]chip id : 0x0000ff10 0x00004824 0x0000d710 0x00001d96 [09.946]Could not find nodeoffset for used ext pmu:reg-axp1530 [09.951]update dts curr_device:0 Device: SUNXI SD/MMC Manufacturer ID: 3 OEM: 5344 Name: SR64G Bus Speed: 50000000 Mode : SD High Speed (50MHz) Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 59.5 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes Hit any key to stop autoboot: 0 starting USB... USB0: start sunxi USB-DRD... config usb clk ok sunxi USB-DRD init ok... USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found USB1: start sunxi USB1-Host... config usb clk ok sunxi USB1-Host init ok... USB EHCI 1.00 scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: device type unknown ... is now current device ** Bad device usb 0 ** ** Bad device usb 0 ** mmc0 is current device Scanning mmc 0:2... Scanning mmc 0:3... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000) 1323 bytes read in 7 ms (184.6 KiB/s) U-Boot menu 1: Debian GNU/Linux 11 (bullseye) 5.15.147-13-aw2501 2: Debian GNU/Linux 11 (bullseye) 5.15.147-13-aw2501 (rescue target) Enter choice: 1: Debian GNU/Linux 11 (bullseye) 5.15.147-13-aw2501 Retrieving file: /boot/initrd.img-5.15.147-13-aw2501 ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000) 7060674 bytes read in 300 ms (22.4 MiB/s) Retrieving file: /boot/vmlinuz-5.15.147-13-aw2501 ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000) 20992512 bytes read in 877 ms (22.8 MiB/s) append: root=UUID=9645203c-b680-44b6-8b18-068d9e110402 console=ttyAS0,115200n8 rootwait clk_ignore_unused mac_addr=08:ef:6c:c7:8b:ad mac1_addr=08:ef:6c:c7:8b:ac quiet splash loglevel=4 rw earlycon consoleblank=0 console=tty1 coherent_pool=2M irqchip.gicv3_pseudo_nmi=0 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 kasan=off Retrieving file: /usr/lib/linux-image-5.15.147-13-aw2501/allwinner/sun55i-a527-cubie-a5e.dtb ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000) 161015 bytes read in 18 ms (8.5 MiB/s) get value error [16.446]The storage not support sample function ret 0 [16.563]update dts stop sunxi USB-DRD ok... stop sunxi USB1-Host ok... Loading Ramdisk to 49944000, end 49fffcc2 ... OK ERROR: reserving fdt memory region failed (addr=bbed0000 size=7e9000) [16.598]Starting kernel ... [16.601]total: 16601 ms [16.603][mmc]: MMC Device 2 not found [16.606][mmc]: mmc 2 not find, so not exit NOTICE: [SCP] :wait arisc ready.... NOTICE: [SCP] :arisc version: [364dad9bcd34230512f015ab5c6cefa12bd238d0] NOTICE: [SCP] :arisc startup ready NOTICE: [SCP] :arisc startup notify message feedback NOTICE: [SCP] :sunxi-arisc driver is starting NOTICE: BL3-1: Next image address = 0x40200000 NOTICE: BL3-1: Next image spsr = 0x3c5 [ 0.071969] AW BSP version: caee29fcb3, 2025-12-09 07:23:49, RadxaOS SDK [ 0.140107] sunxi:twi_sunxi-2502000.twi0:[ERR]: pinctrl_get failed [ 0.140127] sunxi:twi_sunxi-2502000.twi0:[ERR]: TWI failed to get resource [ 0.143734] sunxi:axp2101-6-0036:[ERR]: Unable to match OF ID [ 0.310164] sunxi:ccu_ddr:[ERR]: dram_clk:1200 [ 0.310191] sunxi:ccu_ddr:[ERR]: dram_div:0x1f0b0503 [ 0.310832] sunxi:pin-2000000.pinctrl:[ERR]: unknown pin [ 0.310842] sunxi:pin-2000000.pinctrl:[ERR]: unknown pin [ 0.310886] sunxi:pin-2000000.pinctrl:[ERR]: unknown pin [ 0.310892] sunxi:pin-2000000.pinctrl:[ERR]: unknown pin [ 0.311482] sunxi:sunxi_uart-uart0:[ERR]: uart0 error to get fifo size property [ 0.386566] NSI_PMU 2020000.nsi-controller: no topo process for clk path type:0 [ 0.394816] no topo process for topo type:0 [ 0.402846] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: Could not get mbus clock [ 0.411011] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: Could not get store clock [ 0.419251] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: Could not get msi_lite clock [ 0.457791] sunxi:sunxi_mmc_host-4020000.sdmmc:[ERR]: Could not get mbus clock [ 0.466069] sunxi:sunxi_mmc_host-4020000.sdmmc:[ERR]: Could not get store clock [ 0.474428] sunxi:sunxi_mmc_host-4020000.sdmmc:[ERR]: Could not get msi_lite clock [ 0.475236] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.492239] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.501531] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.510880] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.520159] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.529448] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.538076] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: Could not get mbus clock [ 0.538726] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.546202] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: Could not get store clock [ 0.562758] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: Could not get msi_lite clock [ 0.572128] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.581414] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.590691] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.600035] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.609310] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.617707] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !! [ 0.627037] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !! [ 0.635533] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.644823] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.654111] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.663385] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.672711] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.682003] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.691285] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.700598] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.709898] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.719191] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: smc 1 p2 err, cmd 1, RTO !! [ 0.727648] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: retry:set phase failed or over retry times [ 0.737523] sunxi:sunxi_mmc_host-4022000.sdmmc:[ERR]: retry:give up [ 0.744833] sunxi:sunxi_mmc_host-4020000.sdmmc:[ERR]: sdc0 :the host don't support tuning in kernel [ 1.235336] sunxi:sunxi_sidefuse init success! [ 1.241281] inno-combphy 4f00000.phy: get select3v3-supply fail [ 1.740355] sunxi-rc-recv 2005000.irrx: sunxi_irrx_resource_get: get ir protocol failed [ 1.771768] sunxi:axp2202_battery:[ERR]: axp2202-battery device is not configed [ 1.794813] sunxi-rfkill soc@3000000:rfkill: get gpio chip_en failed [ 1.804693] [NAND][NE] Not found valid nand node on dts [ 3.128108] cma: cma_alloc: reserved: alloc failed, req-size: 512 pages, ret: -12 [ 4.777883] sunxi:VE:[ERR]: 409 map_max_ve_freq_by_vf_sun55iw3(): can not match dvfs[0x1] and vol[900 mv], use default ve_freq [ 4.815646] cma: cma_alloc: reserved: alloc failed, req-size: 512 pages, ret: -12 [ 4.827791] sunxipart: failed to parse sunxi_gpt! [ 5.002596] sunxi:sound-mach:[ERR]: 535 simple_parse_of(): simple_dai_link_of failed [ 5.046546] sunxi:sound-codec-hdmi:[ERR]: 442 sunxi_codec_dev_probe(): register codec-hdmi success [ 5.064198] sunxi:sound-mach:[ERR]: 535 simple_parse_of(): simple_dai_link_of failed [ 5.084859] debugfs: Directory '7114000.i2s2_plat' with parent 'sndhdmi' already present! [ 5.094216] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !! [ 5.105028] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !! [ 5.175761] axp2202-bldo1: Restricting voltage, 3300000-1800000uV [ 5.182730] sunxi-rfkill soc@3000000:rfkill: wlan power[0] (axp2202-bldo1) set voltage failed [ 5.192433] sunxi-rfkill soc@3000000:rfkill: set power failed [ 5.250133] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 7, RTO !! [ 5.258714] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 7, RTO !! [ 5.267263] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 7, RTO !! [ 5.275819] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 7, RTO !! [ 5.310636] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !! [ 5.320383] sunxi:sunxi_mmc_host-4021000.sdmmc:[ERR]: smc 2 p1 err, cmd 52, RTO !! [ 5.625825] aicbsp: sdio_err:<aicwf_sdio_bus_pwrctl,1404>: bus down [ 6.762994] ieee80211 phy0: [ 6.762994] ******************************************************* [ 6.762994] ** CAUTION: USING PERMISSIVE CUSTOM REGULATORY RULES ** [ 6.762994] ******************************************************* Debian GNU/Linux 11 radxa-cubie-a5e ttyAS0 radxa-cubie-a5e login:

http://blog.armbian.com/content/images/2026/02/githubhighlights-2-1.webpThis week in Armbian development saw significant advancements across kernel, firmware, and build targets. The release of 6.18.y kernel UEFI images marks a major update, alongside expanded desktop build options including Cinnamon and KDE Neon for UEFI systems. Notable board support enhancements include the addition of custom build targets for Amlogic TV Boxes, the Raspberry Pi Zero 2W as a virtual board, and improved support for Orange Pi 3 LTS and Odroid M2 devices. Automation improvements streamline inventory rebuilds and board data management, while new features such as Armbian board auto-detection and browser enablement for Riscv64 boards enhance usability. Several bug fixes and configuration updates address issues across Hyper-V images, kernel configs, and u-boot versions. The changelog also highlights upgrades to wireless firmware, dependency management, and support for BTRFS on NanoPi R3S-LTS, reflecting ongoing efforts to broaden compatibility and stability. 6.18.y kernel UEFI images are out. by @igorpecovnik in armbian/armbian.github.io#221abl: feat: add extraargs from armbianEnv for mkbootimg. by @CodeChenL in armbian/build#9341Add -hyperv suffix to REDI_VARIANT for Hyper-V images. by @igorpecovnik in armbian/armbian.github.io#216Add Cinnamon and KDE Neon desktop builds for UEFI. by @igorpecovnik in armbian/armbian.github.io#209Add cloud image extensions to UEFI minimal targets. by @igorpecovnik in armbian/armbian.github.io#211Add custom build targets for Amlogic TV Boxes. by @SteeManMI in armbian/armbian.github.io#224Add ENABLE_EXTENSIONS to UEFI desktop targets. by @igorpecovnik in armbian/armbian.github.io#210Add KDE Neon and RISC-V XFCE desktop targets. by @igorpecovnik in armbian/armbian.github.io#214Add Raspberry Pi Zero 2W board as virtual board. by @igorpecovnik in armbian/armbian.github.io#223Add remote execution method for inventory rebuild. by @igorpecovnik in armbian/armbian.github.io#222Add REMOVE_EXTENSIONS blacklist support to generate_targets.py. by @igorpecovnik in armbian/armbian.github.io#217ath12k: Upgrade to WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICON…. by @kasimling in armbian/firmware#118Automation: when board data changes on push, execute inventory rebuild at armbian.github.io. by @igorpecovnik in armbian/build#9354BPI-M4-Zero / KickPi K2B: Update u-boot to v2026.01, ATF to lts-v2.12.9 and fixup the KickPi K2B linux DTS. by @pyavitz in armbian/build#9340Enable Browsers on two Riscv64 boards. by @igorpecovnik in armbian/armbian.github.io#219Extension: Bump Nvidia propriatery driver. by @igorpecovnik in armbian/build#9338feat: add Armbian board auto-detection and toast notification system. by @SuperKali in armbian/imager#91feat: add Dependabot configuration for dependency management. by @SuperKali in armbian/imager#70File was removed while it remained in series control file. . by @igorpecovnik in armbian/build#9339Fix errors in .editorconfig. by @iav in armbian/build#9363Fix file_extension extraction for Hyper-V cloud images. by @igorpecovnik in armbian/armbian.github.io#215Fix K3 issues - APT Caching, PB2, Missing KConfig. by @Grippy98 in armbian/build#9349KDE Neon: drop conflicting packages in order to assemble KDE desktop. by @igorpecovnik in armbian/build#9337kernel configs: disable unprivileged BPF. by @neheb in armbian/build#9082khadas-edge2: remove legacy uboot. by @efectn in armbian/build#9367Limit exposed.map to maximum 2 entries per board. by @igorpecovnik in armbian/armbian.github.io#220meson64: ressurect 6.12 as BRANCH=oldlts. by @rpardini in armbian/build#9350Odroid M2: Move main build target to CURRENT kernel branch. by @igorpecovnik in armbian/build#9357Odroid-M2: update uboot to v2025.10. by @mlegenovic in armbian/build#9359Orange Pi 3B: Update config. by @dust-7 in armbian/build#9370OrangePi 3 LTS: Add DTS and DEFCONFIG to u-boot v2026.01. by @pyavitz in armbian/build#9352OrangePi 3 LTS: Add ethernet support to u-boot defconfig. by @pyavitz in armbian/build#9365OrangePi 3 LTS: Fixup u-boot LED nodes. by @pyavitz in armbian/build#9358OrangePi 3 LTS: Update crust and u-boot defconfig. by @pyavitz in armbian/build#9372OrangePi 3 LTS: Use extlinux, remove aw859a-wifi.service, update current defconfig, etc.... by @pyavitz in armbian/build#9362Promoting Opi 3LTS and Odroid M2, demoting cubox-i and Jetson Nano. by @igorpecovnik in armbian/build#9353Radxa E52C: add mainline U-Boot support and kernel target configuration. by @okrc in armbian/build#9366radxa-e54c: board config: remove wayland-sessions-mask extension. by @schwar3kat in armbian/build#9351Refactor mesa-vpu extension: add architecture-specific browser selection. by @igorpecovnik in armbian/build#9347Remove Rockchip gpio patch, already applied upstream. by @tparys in armbian/build#9368Restore qemu performance fix for Ubuntu Noble. by @tparys in armbian/build#9371Restructured qcom/sm8550/ayn directory. by @Squishy123 in armbian/firmware#117Rock 5B Plus: Add GPIO names to edge dts. by @JohnTheCoolingFan in armbian/build#9348Support BTRFS on NanoPi R3S-LTS. by @clarkmcc in armbian/build#9343View the full article

TV Box Status Information Template Version 1.0 TV Box Name (example: TX3 mini): T9 CPU (example: amlogic s905w): RK3328 Armbian build file name: Armbian_community_25.11.0-trunk.367_Rk3318-box_trixie_current_6.12.54_minimal.img DTB file used: rockchip/rk3318-box.dtb Kernel Version: 6.12.56-current-rockchip64 Distribution Installed (focal, buster, etc): trixie Working Ethernet (Yes/No):Yes Max Ethernet Speed that works (100/1000): 100 Max Does wifi work (Yes/No): Yes 2/5 Does bluetooth work (Yes/No): Yes Does HDMI audio work (Yes/No): Yes - after last update , (also analog and spdif ports are available - not tested). Additional Comments (provide any additional information you feel is important): IR Receiver yes 5 Digit display working: yes MASKROM PINS for recovery flashing available on the back side. SOC RK3328 RAM 4Gx4 D9PQL VFD DRIVER FD6551 WLAN CHIP SP6330 32 GB EMMc KLMBG2JENB VT RT9045 vfd.conf rk3318-t9.dtso Log android gpio T9.txt

@Brow Mosh AI is wrong. Mainline supports - Your PMIC - Your DRAM timing - Your HDMI (Patches have been around for years but not accepted in mainline yet. I included it in my builds.) - Your regulators Supported in mainline but might need some dts changes. - Your weird SD wiring - Your eMMC layout ( Could be a gpio# issue) If you are booting into the kernel then I believe your SD is somewhat working. Maybe you need few tweaks to your dts or your DRAM settings are off. A failing or cheap SD card could also be your issue. Kernel boots Reaches userspace Shows login banner Without a DTS I can’t help you much. Also, can you post some boot logs. FEL over USB is your last option. It is possible. But I don't think your AI model will help much. I noticed with some AI models they will encourage you to quit when they can't find the correct information. The owner of the AI model wants you to pay for their deep learning version.

Update on NanoPi M4v2 ... I pulled the most recent Armbian build, and manually ran the build for the M4v2, and it fails on kernel patch "general-gpio-driver-no-sleep". See pastebin at https://paste.armbian.com/puvorasuco for failed build. Checking upstream at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git, it looks like branch 6.18.y already has the subject patch, and was pushed today. Since both the rockchip and rockchip64 families use mainline kernel, I just submitted a PR that kills that patch for both. See https://github.com/armbian/build/pull/9368.

Yesterday, I tried to use the digital IO in my opi zero3, with the Python GPIO package from https://opi-gpio.readthedocs.io/en/latest/ by Richard Hull It depends on having sysfs files in /sys/class/gpio/ My original opi zero has these files and it works, but my opi zero3 doesn’t have these files I learned that /sys/class/gpio is created if the linux kernel is configured with a specific option ON, as suggested in the documentation: https://github.com/rm-hull/OPi.GPIO https://linux-sunxi.org/GPIO Also, a developer has made a change on the opi.GPIO project to support opi zero3 https://github.com/rm-hull/OPi.GPIO/issues/79 I will have time to try this tomorrow... but I want to ask: is anyone using GPIO in its most basic way? As reference: I saw this older thread about zero3's GPIO... https://forum.armbian.com/topic/31493-how-to-enable-i2c3-on-orange-pi-zero-3/ It is using leebobby's "armbian" image, with raspi-config, and wiringpi Using my original opi-zero, I never needed to use armbian-config to enable basic gpio and the python opi.gpio just worked as documented Note: the opi.gpio only claims to support basic gpio, not i2c. Update: these are interesting potential solutions and discussions (but they are all from before there was armbian for opiz3) https://www.reddit.com/r/OrangePI/comments/16vfa4g/orange_pi_zero_3_gpio_python_library/ https://github.com/eutim/OPI.GPIO https://www.reddit.com/r/OrangePI/comments/16ioyri/gpio_python_library_for_orange_pi_zero_3/ https://www.reddit.com/r/OrangePI/comments/18iveo3/how_to_control_gpio_pins_in_android_orange_pi/

@Brow Mosh Have you tried extracting your arndroid dts to find the gpio settings for emmc? The only other thing I can suggest at this point is trying mainline U-Boot booted over USB (FEL). Booting mainline U-Boot via FEL completely bypasses SD.

http://blog.armbian.com/content/images/2026/02/githubhighlights-2.webpThis week’s Armbian development saw significant progress across multiple areas, including desktop environment enhancements, kernel updates, and expanded hardware support. Notable changes include the addition of GNOME desktop options, improvements to XFCE organization, and updates to U-Boot for several boards. The team introduced new board images and logos, refined Docker automation and documentation, and standardized numerous software modules for better maintainability. Kernel advancements featured bumps to 6.19-rc8, integration of ZFS v2.4.0, and targeted fixes for Rockchip and Odroid platforms. Community governance and build processes were also strengthened, alongside the deprecation of Matrix and OFTC chat utilities. These updates collectively improve user experience, system stability, and future development agility. Add community governance and improve documentation. by @igorpecovnik in armbian/armbian.github.io#197Add DESKTOP_APPGROUPS_SELECTED to stable XFCE desktop target. by @igorpecovnik in armbian/armbian.github.io#198Add documentation for ARMBIAN_DOCKER_AUTO_PULL build switch. by @igorpecovnik in armbian/documentation#865Add GNOME desktop and reorganize XFCE in stable targets. by @igorpecovnik in armbian/armbian.github.io#199Add Khadas Mind, Minisiforum logo and Orangepi 6 Plus. by @igorpecovnik in armbian/armbian.github.io#203Add manual append for standard UEFI images. by @igorpecovnik in armbian/armbian.github.io#204Add zfs-zed to GLOB pattern in ZFS configs. by @igorpecovnik in armbian/os#426armbian-kernel: add AMD DC support for UEFI boards. by @igorpecovnik in armbian/build#9324armbianmonitor: fix error message at the end of every report. by @EvilOlaf in armbian/build#9325bcm2711 Family: Remove post_family_tweaks_bsp__rpi_firmware func. by @pyavitz in armbian/build#9331Board images for Orange Pi RV2 and Orange Pi R2S. by @sven-ola in armbian/armbian.github.io#201Bump BesTV R3300-L U-Boot. by @retro98boy in armbian/build#9303Bump CAINIAO CNIoT-CORE U-Boot. by @retro98boy in armbian/build#9304Chat utilities: remove missing package. by @igorpecovnik in armbian/build#9334ci: run all unit tests on schedule and main branch workflow_dispatch. by @igorpecovnik in armbian/configng#727clang: enable colored diagnostic output for kernel compilation. by @iav in armbian/build#9310Deprecate Matrix. by @EvilOlaf in armbian/build#9318Deprecate OFTC and matrix. by @EvilOlaf in armbian/documentation#872docker: add automatic image pull cronjob and cleanup system. by @igorpecovnik in armbian/build#9265feat: add reusable board definitions to image JSON generator. by @igorpecovnik in armbian/armbian.github.io#202Fix missing Cinnamon menu by removing outdated Cinnamon menu applet blob.. by @schwar3kat in armbian/build#9300fix(software): correct stderr redirection placement in docker commands. by @igorpecovnik in armbian/configng#746fix(software): fix netdata module issues and add test cleanup. by @igorpecovnik in armbian/configng#747fix: motd: handle empty temperature values in printf. by @igorpecovnik in armbian/build#9296followup #9164 2ba0766 - add ubuntu resolute,questing to optional-cli. by @iav in armbian/build#9320forge1: switch to RK3506J variant and add OPTEE support. by @igorpecovnik in armbian/build#9326json: add kernel_version field to images output. by @igorpecovnik in armbian/armbian.github.io#206Kernels 6.18 needs ZFS v2.4.0. by @igorpecovnik in armbian/os#425mainline-kernel: bump 6.19 to 6.19-rc8. by @rpardini in armbian/build#9332mainline: bump to 6.19-rc7. by @EvilOlaf in armbian/build#9294networking: relax networkd-wait-online to avoid multi-NIC timeouts. by @igorpecovnik in armbian/build#9311Odroid XU4: remove upstreamed patches. by @igorpecovnik in armbian/build#9306odroidm1: u-boot v2026.01 + kernel fix for ethernet. by @rpardini in armbian/build#9333OrangePi 3 LTS: Update U-Boot to v2026.01 and Linux DTS "and other fixups". by @pyavitz in armbian/build#9323Re-enable build targets after fixing their assembly. by @igorpecovnik in armbian/armbian.github.io#200refactor(docker): use upstream docker-ce for bookworm, distro for others. by @igorpecovnik in armbian/configng#726refactor(immich): standardize module and update postgres interface. by @igorpecovnik in armbian/configng#733refactor(network): standardize modules and add hidden WiFi support. by @igorpecovnik in armbian/configng#739refactor(pihole): standardize module with docker.io and improve detection. by @igorpecovnik in armbian/configng#734refactor(software): move docker check to install command. by @igorpecovnik in armbian/configng#738refactor(software): standardize 33 docker modules with modern patterns. by @igorpecovnik in armbian/configng#736refactor(system): harden armbian_firmware module with standard conventions. by @igorpecovnik in armbian/configng#744refactor(system): standardize headers and ZFS modules with improved hardening. by @igorpecovnik in armbian/configng#742refactor(wireguard): consolidate status checks and simplify module interface. by @igorpecovnik in armbian/configng#731refactor: standardize ghost and mysql docker modules. by @igorpecovnik in armbian/configng#728Resolving boot issues. by @rvdr in armbian/build#9329Rockchip 6.19: drop upstreamed patches. by @igorpecovnik in armbian/build#9309rockchip/64: import mainlined patch to fix gpio . by @paolosabatino in armbian/build#9328rockchip64-6.18: fix helios64 pcie patch. by @igorpecovnik in armbian/build#9315rockchip64-current: rewrite patches. by @EvilOlaf in armbian/build#9313rockchip64-current: rewrite patches due to upstream changes in 6.18.8. by @EvilOlaf in armbian/build#9319rockchip64: fix clang build error. by @paolosabatino in armbian/build#9307rockchip: fix gpio-ir-recv stack dumps, other minor fixes. by @paolosabatino in armbian/build#9317SMART AM40: Bump U-Boot. by @retro98boy in armbian/build#9302sun55i aftercare. by @EvilOlaf in armbian/build#9321sunxi a523: Adding support for PCIe, SPI Flash and Iommu. by @rvdr in armbian/build#9280sunxi: drop unneeded patches. by @EvilOlaf in armbian/build#9312targets: change community builds from forky to trixie. by @igorpecovnik in armbian/armbian.github.io#207Update header level for Pi-hole Explained section. by @igorpecovnik in armbian/configng#748Update odroidxu4-current to 6.6.122. by @belegdol in armbian/build#9322Update sm8250 current kernel config. by @retro98boy in armbian/build#9292Use EDGE branches for Orangepi 6 and Minisforum R1S. by @igorpecovnik in armbian/armbian.github.io#205uwe5622: fix compilation with clang on Linux 6.19. by @iav in armbian/build#9314[RFC] qcs6490: fix patched dtb not compiled. by @amazingfate in [#9301](https://github....View the full article

Hi I've made a new kernel Auxiliary Display Driver for TM16XX and compatible LED controllers. This driver supports various LED controller chips, including TM16XX family, FD6XX family, PT6964, and HBS658. It provides support for both I2C and SPI interfaces. I wanted it to manage the hardware on the kernel space while having an easy sysfs user space interface. It also aims to reduce the code to maintain by relaying on existing kernel features instead of recoding them. Plus, you can switch to hardware i2c/spi (instead of software gpio) depending on the pins used. You can use "vfdconf-convert" to convert your existing vfd.conf to its device-tree version. Or you can use the already converted vfd.conf of https://github.com/arthur-liberman/vfd-configurations that are listed in the device table. You don't need to manually edit your device tree, the "make" command will apply the device tree source overlay to your dtb. It comes with a service written as a simple bash script. So it's easily customizable without having to write custom C code. Instructions and source code at https://github.com/jefflessard/tm16xx-display/ Could you please give it a try and report your feedback?

Version 3 Has been released! Complete UI Overhaul The entire user interface has been rebuilt from the ground up using Qt QML, delivering a modern automotive HMI experience optimized for touchscreen displays. New Home Screen - Large centered clock with configurable 12-hour/24-hour format - Gradient background (#00021A → #001D3F) - Swipe navigation to media player - Clean, minimal design with Readex Pro typography New Bottom Navigation Dock - 5-button dock: Home | Music | Android Auto | Volume | Settings - Always visible for quick access (except when running AA) - Icon-based navigation with visual feedback New Music Player - Album art display with track metadata - Playback controls (Previous, Play/Pause, Next) - Integrated with system media Redesigned Settings - Modern two-column layout with left sidebar navigation - 8 categories: General, Video, Audio, Input, Bluetooth, WiFi, System, About - Toggle switches, sliders, and radio buttons - Real-time system info (CPU temp, memory, frequency) - Live date/time display in header New Features - 12/24-Hour Time Toggle: Switch between time formats in Settings → General - Readex Pro Font: Variable weight font for consistent automotive typography - Modernized UI: The Original Crankshaft-NG was just not suitable for car use so i had to refresh it Technical Changes - Qt Widgets → QML Migration — Complete rewrite of UI layer - UIBackend Bridge — New C++ backend class exposing 50+ properties to QML - EGLFS Optimized — Designed for direct framebuffer rendering - No Animations — Instant transitions for 1GB RAM constraint - Centralized Theming — Theme.qml singleton for consistent styling Removed - GPIO settings (not applicable to TV Boxes) - DAC settings (using ALSA directly) - RTC settings (no CMOS battery, NTP only) - TSL2561 light sensor support (Pi-specific) - Camera module settings (Pi-specific) Bug Fixes - Fixed Cursor issue by utilizing Cursor plane (41, z-pos 2) - Fixed std::mutex missing include in RtAudioOutput - Fixed ColorOverlay import for Qt GraphicalEffects - Fixed time display showing 24hr with AM/PM suffix - Fixed buffer overflow warning in FFmpegDrmVideoOutput - Fixed QCursor conversion error in autoapp.cpp Known Issues: - Music player metadata not populated (requires media service integration, will be done in the next patch) - Volume popup not implemented (this require modifying the asound.conf before implementing) Issues? Open a ticket in https://github.com/Harleythetech/openauto-rk3229-armbian/issues Download https://github.com/Harleythetech/openauto-rk3229-armbian/releases/tag/oark322x-V3.0.0-alpha

If this is AW869A chip then it uses the AIC 8800 Linux Driver. My X98H TV box has a AIC8800 chip in it. https://linux-sunxi.org/Wifi#AW869A AW869A The AW869A is a highly integrated module with Dual band WiFi6 combination solution to support 1 × 1 IEEE 802.11b/g/n/ac/ax WLAN standards It uses the aic8800 firmware. A driver can be found at AIC 8800 Linux Driver. You'll need to compare the GPIO settings. Your Android dts uses HEX the mainline kernel is using DEC. https://www.rapidtables.com/convert/number/hex-to-decimal.html?x=12 rfkill { compatible = "allwinner,sunxi-rfkill"; status = "okay"; chip_en; power_en; pinctrl-0 = <0x63>; pinctrl-names = "default"; phandle = <0xcc>; wlan { compatible = "allwinner,sunxi-wlan"; clocks = <0x0e 0x04>; clock-names = "osc32k-out"; wlan_busnum = <0x01>; wlan_power; wlan_regon = <0x23 0x06 0x12 0x00>; wlan_hostwake = <0x23 0x06 0x0f 0x00>; wakeup-source; phandle = <0xcd>; }; bt { compatible = "allwinner,sunxi-bt"; clocks = <0x0e 0x04>; clock-names = "osc32k-out"; bt_power; bt_rst_n = <0x23 0x06 0x13 0x01>; phandle = <0xce>; }; }; btlpm { compatible = "allwinner,sunxi-btlpm"; status = "okay"; uart_index = <0x01>; bt_wake = <0x23 0x06 0x11 0x00>; bt_hostwake = <0x23 0x06 0x10 0x01>; wakeup-source; phandle = <0xd0>; }; Mainline dts: https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L87-L95 https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L182-L200 https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L278-L297 The specific values <0x23 0x06 0x12 0x00> generally map to: 0x23: The controller or bank ID: pinctrl@300b000 { phandle = <0x23>; 0x06: The specific GPIO pin number: In Allwinner's pinctrl driver, banks are 32 pins wide. The formula is: (Bank_Letter_Index * 32) + Pin_Number 1. The Bank Index Map Bank Index PA 0 PB 1 PC 2 PD 3 PE 4 PF 5 PG 6 PH 7 PI 8 0x12: The active-high/low flags or drive strength. In the 3-cell GPIO format used by Allwinner (sunxi), the third cell (e.g., 0x12) is a bitmask that defines the electrical properties of the pin. To decode 0x12 (which is binary 0001 0010), you break it down into bits: 1. Bitmask Breakdown for 0x12 Bit 0 (0x01): Active Polarity. 0 = Active High. 1 = Active Low (Our bit 0 is 0, so this is Active High). Bit 1 (0x02): Open Drain / Open Source. 0 = Push-Pull. 1 = Single-ended/Open-Drain (Our bit 1 is 1, so this is Open-Drain). Bit 4 (0x10): Internal Pull-up. 0 = No pull-up. 1 = Pull-up Enabled (Our bit 4 is 1, so this is Pull-up Enabled). Summary of 0x12: This pin is configured as Active High, with an Open-Drain output and an internal Pull-up resistor enabled. 0x00: Reserved or additional configuration. In Allwinner-based systems (like the H6 or H616), this value is defined in the GPIO controller's device tree binding documentation within the Linux kernel source code. The structure is documented in the kernel under Documentation/devicetree/bindings/pinctrl/allwinner,sun4i-a10-pinctrl.yaml

I think it depends on what you want. If you want to have some fun, then building this one is interesting actually, and there is more extensibility, and since radxa zero GPIO pin is compatible with Raspberry pi's, you can also get a DAC Mini Hat raspberry pi module, so there is more you can play or customize. But, if you just want to solve the problem and don't want to have these hassle, buying an existing product is a better option, so you have the warranty, customer support, and everything should work out of the box. I don't have Fosi Audio DS1 or Fiio Ka13, so every information I get is from the google search and cannot guarantee the correctness. From what I saw, Fiio Ka13 seems to be unable to work with PS5, and Fosi Audio DS1 can. This project only handles digital audio data, so I do not need to pay attention to the audio electronic properties when outputting (because that's the job of that USB speaker), and I do not know the sound quality of Fosi Audio DS1. One last word, if your original plan is to use this converter to connect to Hiby R3II, then to your headphone, that should work, but that is kind of redundant; there is more latency introduced, and the robustness could be wore because you have a longer output chain (from the engineering perspective). It would be easier to just get a high quality UAC 1.0 Amp.

Update 3: almost there! root@rk322x-box:~# dmesg | grep -i drm [ 6.738341] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [ 6.912602] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 6.914174] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. [ 11.565138] [drm] Initialized lima 1.1.0 for 20000000.gpu on minor 0 root@rk322x-box:~# dmesg | grep -i rockchip [ 0.068016] rockchip-gpio 11110000.gpio: probed /pinctrl/gpio@11110000 [ 0.069475] rockchip-gpio 11120000.gpio: probed /pinctrl/gpio@11120000 [ 0.070736] rockchip-gpio 11130000.gpio: probed /pinctrl/gpio@11130000 [ 0.071810] rockchip-gpio 11140000.gpio: probed /pinctrl/gpio@11140000 [ 1.330865] rockchip-rga 20060000.rga: HW Version: 0x04.01 [ 1.339866] rockchip-rga 20060000.rga: Registered rockchip-rga as /dev/video0 [ 1.360435] dwmmc_rockchip 30000000.mmc: IDMAC supports 32-bit address mode. [ 1.360814] dwmmc_rockchip 30010000.mmc: IDMAC supports 32-bit address mode. [ 1.361387] dwmmc_rockchip 30020000.mmc: IDMAC supports 32-bit address mode. [ 1.371466] dwmmc_rockchip 30000000.mmc: Using internal DMA controller. [ 1.371502] dwmmc_rockchip 30000000.mmc: Version ID is 270a [ 1.371594] dwmmc_rockchip 30000000.mmc: DW MMC controller at irq 49,32 bit host data width,256 deep fifo [ 1.372013] dwmmc_rockchip 30000000.mmc: Got CD GPIO [ 1.395186] dwmmc_rockchip 30010000.mmc: Using internal DMA controller. [ 1.395237] dwmmc_rockchip 30010000.mmc: Version ID is 270a [ 1.395356] dwmmc_rockchip 30010000.mmc: DW MMC controller at irq 50,32 bit host data width,256 deep fifo [ 1.395646] dwmmc_rockchip 30010000.mmc: allocated mmc-pwrseq [ 1.402395] dwmmc_rockchip 30020000.mmc: Using internal DMA controller. [ 1.402458] dwmmc_rockchip 30020000.mmc: Version ID is 270a [ 1.402603] dwmmc_rockchip 30020000.mmc: DW MMC controller at irq 51,32 bit host data width,256 deep fifo [ 11.719472] hantro-vpu 20020000.video-codec: registered rockchip,rk3399-vpu-enc as /dev/video2 [ 11.723548] hantro-vpu 20020000.video-codec: registered rockchip,rk3399-vpu-dec as /dev/video3 [ 25.632131] rk_gmac-dwmac 30200000.ethernet end0: PHY [stmmac-0:00] driver [Rockchip integrated EPHY] (irq=POLL) root@rk322x-box:~# dmesg | grep -i hdmi [ 0.055584] /vop@20050000: Fixed dependency cycle(s) with /hdmi@200a0000 [ 0.055722] /hdmi@200a0000: Fixed dependency cycle(s) with /vop@20050000 [ 22.293730] platform 200a0000.hdmi: deferred probe pending: (reason unknown) [ 22.293761] platform hdmi-sound: deferred probe pending: asoc-simple-card: parse error root@rk322x-box:~# ls -l /dev/dri total 0 drwxr-xr-x 2 root root 80 Jan 28 11:49 by-path crw-rw---- 1 root video 226, 0 Jan 28 11:49 card0 crw-rw---- 1 root render 226, 128 Jan 28 11:49 renderD128

Hello. BTT says what BTT Pi and CB1 is same, but realy not. Dunno why i brought what board. But now I owner of this "piece of ****" So. New board, clean install v25.11.2 for BigTreeTech CB1 running Armbian Linux 6.12.58-current-sunxi64 Packages: Debian stable (trixie) armbianEnv: overlays=gpu tft35_spi extraargs=fbcon=rotate:2 fbcon=rotate:2 for screen rotation, because armbian not from btt and didn`t have feature like param_tft35_spi_rotate Next, help me to determine how to enable UARTs and I2C From BIGTREETECH_Pi_V1.2.1 Hardware Pdf UART0: CPUX-UTX CPUX-RX UART2 (May work as i2c0; uart2-pi-pins; i2c0-pins ) Pi5 Pi6 UART3 (May work as i2c2; uart3-pi-pins; i2c2-pi-pins ) Pi9 Pi10 I2C (i2c4-ph-pins; spi1-pins): PH6 PH7 (must work, i`ll think i2c4-ph overlay present) All pins present in sun50i-h616-bigtreetech-cb1-sd, but didnt have overlays for it... I wish to stay uart0 for u-boot console first uart setup for klipper connections to mcu. any help? If I understand right PH6 is 7*32+6=230 gpioinfo output line 230: unnamed input consumer=kernel line 231: unnamed input consumer=kernel cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/300b000.pinctrl, 300b000.pinctrl: gpio-71 ( |spi0 CS1 ) out hi ACTIVE LOW gpio-74 ( |i2c-gpio ) out hi gpio-75 ( |spi0 CS0 ) out hi ACTIVE LOW gpio-76 ( |i2c-gpio ) out hi gpio-77 ( |spi0 CS2 ) out lo gpio-78 ( |dc ) out hi gpio-166 ( |:wifi_power ) out hi gpio-207 ( |:wifi_wake ) out hi gpio-210 ( |reset ) out hi ACTIVE LOW gpio-229 ( |led-0 ) out lo ACTIVE LOW

In the meantime, I fixed internal audio for "edge" (was: missing headphone GPIO). And also investigated around the esos.elf RTOS firmware. There's a license for that, which I added to my tree. The license basically says: use but do not infect with GPL: https://gitee.com/spacemit-buildroot/buildroot-ext/blob/k1-bl-v2.2.y/board/spacemit/k1/target_overlay/lib/firmware/LICENSE.spacemit_esos. Continuing on kthread issue. LG // Sven-Ola

I did establish a wifi connection and ssh sovol@IPaddress. Have the following: sovol@sovol:/$ ls -a -C . data lib opt run srv userdata .. dev lost+found packages sbin sys usr .resized etc media proc sdcard system var bin home mnt rockchip-test sha256sum.README tmp vendor boot info oem root sha256sum.txt udisk sovol@sovol:/$ uname -a Linux sovol 5.10.160 #54 SMP PREEMPT Mon Aug 5 22:22:56 CST 2024 aarch64 GNU/Linux Could not cd to root/ and tried to su using mks, makerbase, sovol and 1234 as root passwds. Edit: I can run root commands with sudo The boot/ directory only contained grub/, no hidden files and no *dtb. Edit: Regained wifi after changing channel ?congestion. I looked at the FCCid site and the photos submitted to the FCC show a Realtek rtk8189FTV chip. It looks like the Fn-Link chip was substituted perhaps due to Mainland/Taiwan tensions. Not sure the FCC knows about the chip substitution or if new wifi test data was generated. The wifi on this board is crippling in many ways, Crowsnest cam access saves me many trips up/down the stairs to check for print failures. Still, it does not look like Sovol will be providing any more firmware updates. The two that are available can only be installed by a wifi connection using OTA (Over The Air). Paranoia is high for wireless connections that you know nothing about. I'm wondering about replacing the mainboard with the mks-skipr and adding a wifi module with mainstream kernel support. May be a better path to MainStream klipper and reliable mainstream wifi. Edit: Was able to scp/pull the following files: config-5.10 gpio.txt ip_address.txt rockchip_config. Building my own image still may be an option but will need to deal with the wifi driver, a python script for crowsnest camera and the LED light. Edit: Armbian-mkspi has patches for rtl8189fs. Image building is doable - not sure if wifi will be improved but Mainline Klipper, a more recent kernel, packages with updates can be had on stock boards.

@Робертс My screen is constantly white. Here's my wiring diagram. Display-Orangepi zero 3 VCC-5v GND-GND CS-PH9(spi1) RST-PC14 D/C-PC7 SDI-PH7(mosi) SCK-PH4 BL-3.3v SDO-PH8(miso) Also, there might be a typo. The specified dc-gpio in your dts is described as PHC7. I don't quite understand, is it PC7 or PH7?

The Evolution of SBCs: From Hobby Boards to Edge ComputingOver the past two decades, single-board computers (SBCs) have transformed from experimental maker tools into the backbone of modern embedded and edge systems. What started as a handful of affordable hobby boards has grown into a diverse ecosystem powering automation, AI, and connected infrastructure around the world. From Prototypes to PossibilityEarly SBCs were humble experiments — small circuit boards combining processor, memory, and I/O on one platform. For years they lived quietly inside industrial machines and educational kits. The real turning point came in the early 2010s with boards like the Raspberry Pi, BeagleBone, and Cubieboard, which brought Linux to the maker community at a scale and price that anyone could access. These boards opened the floodgates for innovation. Suddenly, home labs, classrooms, and startups could prototype full Linux systems for the cost of a dinner. The appeal wasn’t just price — it was openness, GPIO access, and a thriving community that treated hardware as something to explore, not just consume. The Rise of a Global EcosystemAs demand grew, more vendors entered the field: Orange Pi, FriendlyElec, Radxa, and dozens of others expanded on the idea, each offering faster SoCs, more memory, and better I/O. Modern SBCs can now host NVMe storage, multiple displays, gigabit networking, and dedicated NPUs for AI workloads — features once reserved for full desktops or servers. They power digital signage, smart gateways, home servers, and even small AI clusters. Developers began caring not just about hardware specs, but also kernel stability, upstream drivers, and long-term support — exactly where Armbian excels. What’s NextLooking ahead, the direction is clear: AI acceleration everywhere – NPUs and neural engines are becoming standard on SBCs.Unified software stacks – Containers, orchestration tools, and reproducible builds are reaching the edge.Energy-aware computing – Solar and battery-powered deployments highlight the need for lean, resilient systems.Armbian’s role in this landscape is to provide the stable software foundation that ties it all together — open, optimized, and reliable across dozens of architectures. In SummarySBCs have grown up. They are no longer just learning tools or proof-of-concept boards — they are the quiet engines running modern infrastructure at the edge. Armbian sits at the heart of that transformation, helping these devices boot faster, run cleaner, and stay useful long after their first flash. The evolution of the SBC mirrors the story of open computing itself: innovation born from community effort, refined through shared knowledge, and extended by software that stays light enough to go anywhere. View the full article

Thank you Pearo, What does "S/N" mean? I just ended up using my orange pi zero 3 gpio without the additional DTS, which made connector numbering available in the gpioinfo command... There were comments that made it sound not really necessary, and it was more work than I wanted to take on. The solution for me was: https://forum.armbian.com/topic/33800-orange-pi-zero-3-gpio/#findComment-181191 This was 2 years ago, and I haven't even thought about it, all this time.

Bit late to the thread, but just a heads up. Been reading this thread and saw the DTS with the connector numbering. So I went to the manual to check the pinout and the pin number is listed as GPIO S/N. Just thought I would add to the thread.

http://blog.armbian.com/content/images/2026/01/T6-Plus-01.pngThe NanoPC T6 Plus, powered by the performance-optimized Armbian OS, is your ticket to a truly professional, high-speed edge computing experience. This industrial-grade device is built around the flagship Octa-core Rockchip RK3588 SoC and now features a massive upgrade to LPDDR5 RAM (up to 32GB), giving it the muscle to handle heavy virtualization, 8K media, and AI workloads effortlessly. Its core hardware is ideal for power users and enterprise integration. The dual 2.5GbE Ethernet ports ensure you can maximize the speed of high-bandwidth wired connections, while multiple M.2 slots (M-Key for NVMe and E-Key for Wi-Fi/BT) allow for blazing-fast storage arrays and wireless expansion. More importantly, the switch to LPDDR5 memory significantly boosts bandwidth, unleashing the full potential of the 8-core CPU and NPU. With Armbian, managing this SBC is simple and utilizes the device's full potential. To configure your system or install complex software stacks, just launch the terminal and run: sudo armbian-config. Navigate to Software and select from pre-packaged installers like Docker, Home Assistant or JellyFin. This single step leverages the RK3588’s processing power for seamless containerization and service hosting, combating supply chain bottlenecks with older LPDDR4X boards. Finally, the PCIe 3.0 x4 interface is perfect for attaching high-speed NVMe SSDs, instantly turning the T6 Plus into a high-performance NAS or media server capable of real-time transcoding. This is just one example of usage. It can serve as a compact 8K workstation, an advanced NVR surveillance hub, a powerful emulation gaming box, or a local LLM host utilizing the 6 TOPS NPU and RKLLM. Thanks to its rich interface options—including HDMI 2.1 output and 2.0 HDMI input—the T6 Plus excels in scenarios where multimedia performance and raw compute power are essential. From segmented home labs to industrial control systems. Combined with the efficiency of the new memory architecture and solid software support, it offers an unrivaled balance between performance, expandability, and reliability. Hardware specifications Feature Specification SoC Rockchip RK3588 CPU Octa-core ARM (4× Cortex-A76 @ 2.4GHz + 4× Cortex-A55 @ 1.8GHz) GPU ARM Mali-G610 MP4 Compatible with OpenGL ES 1.1/2.0/3.2, OpenCL 2.2, Vulkan 1.2 NPU 6 TOPS (INT8) Supports INT4, INT8, INT16, FP16 VPU 8K@60fps H.265 / VP9 / AVS2 decoder 8K@30fps H.264 decoder 8K@30fps encoder (H.265 / H.264) Memory 16 GB / 32 GB LPDDR5 (Upgraded from LPDDR4X) Storage 32GB / 64GB / 256GB eMMC 5.1 1 × M.2 M-Key (PCIe 3.0 x4) for NVMe SSD microSD (UHS-I) Ethernet 2 × 2.5 GbE ports (RTL8125BG) Wireless Optional via M.2 E-Key (PCIe 2.1 x1 + USB 2.0) Video Output 2 × HDMI 2.1 (Up to 8K@60fps) 1 × USB-C (DisplayPort 1.4) Video Input 1 × HDMI 2.0 Input (Up to 4K@60fps) USB 1 × USB 3.0 Type-A 1 × USB-C (Data/DP) Misc USB 2.0 headers Expansion 40-pin GPIO header Mini-PCIe connector Power Input DC 12V/2A (5.5 x 2.1mm jack) PCB 8-layer PCB, 110 × 80 mm Operating Temp 0 °C to 70 °C View the full article

Thank you guys for the work toward this RiscV SBC The website http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-RV2.html claims 130% faster than ARM A55 (which is 25% slower than my H618)... have you tested that? Are the USB, GPIO, SPI and MIPI DSI working? Are there any NPU examples provided by Orange Pi?

1) Language. Either I expressed myself incorrectly or I was misunderstood, but my communication on this forum will most likely proceed as follows: My message in Russian -> Translator -> My message in English And the same in reverse order. 2) A little information about me. I'm a school student, so I'm unlikely to understand any of the high-tech terms. 3) AI If it helps, here's the most productive thread of conversation with Deepseek: https://chat.deepseek.com/share/20dl6vpqy97gpu4et4 4) DTBO and DTS Thanks to AI, almost every new version of dts had a new name, but they all seemed to compile to dtbo with the same name. I'm thinking of finding one that can produce a gradient, but I haven't succeeded yet, and I haven't tried everything. I don't know what color it should be, but mine was a white-to-black gradient. I'll also attach a Python script for it. I didn't create it separately, but wrote it directly into the SSH console (as far as I understand). 5) Raspberry Pi I have a primary 32 GB SD card, which I've been using since installing Klipper on my 3D printer. I also have a spare 64 GB SD card, which I installed MainsailOS, KlipperScreen, and added printer.cfg to. Initially, when I tried using ready-made libraries, I used the primary card, and even used it for a few attempts with AI. But then I switched to a second (spare) card, so that if I messed up the firmware or made any irreparable changes, I could reinstall the OS, reset it to its original state (as mentioned at the beginning), and then repeat all the necessary operations from the beginning. It's probably best to record all your steps somewhere so that after successfully setting up the screen on the spare card, you can repeat the necessary steps on the main card. Just in case, I'll save the current config.txt and all created dts files on my PC. 6) Display I'm attaching a photo of my display and another from the product page on AliExpress. I already have it soldered into the Raspberry Pi. During my attempts, I soldered from spi1 to spi0 and back maybe five times. But I'm tired of this and want to stick with the current pinout with spi1, since I have two more accelerometers on spi0, which I desoldered while setting up the display. 7) Display nuance During the first connection, I slightly damaged the solder mask of the ground plane near the positive contact of the display with a soldering iron and shorted it out with solder. I thought something on the display was broken, so I desoldered and checked some components (the microcircuit, capacitors, and resistor), but they were intact. It was only later that I discovered the real problem. After solving the problem, I connected the 5-volt power supply, but after a couple of hours, I decided to switch it to 3.3 volts just in case. I can switch it back to 5 volts if necessary. I hope this short-circuit situation didn't affect the operation in any way. If this is helpful, I've attached all the DTS versions I currently have; they can be opened in Notepad++. When I find the one that produces the gradient, I'll edit this post or write a new one. test_display.txt ili9488-debug.dts ili9488-fixed.dtbo ili9488-fixed.dts ili9488-fixed-gpio.dts ili9488-full-init.dts ili9488-priority.dts ili9488-test.dts ili9488-test-18bit.dts ili9488-test-bgr.dts ili9488-test-reg36.dts ili9488-test-rotate.dts ili9488-working.dts ili9488-xpt2046.dts ili9488-64bit.dts ili9488-correct-horizontal.dts

Realy cool, but is gpio supposed? I can't get it to work do I need to download some drivers?

Hi, I have a board Orange Pi Zero with modified PAs for power of WiFi module from PA20 to PA02, by soldering a connection on board. This is done to allow connection of I2C DAC. I see that board definition in 'u-boot/configs/orangepi_zero_defconfig' It uses dts definition of: 'arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts' I need to modify one section of this dts file from: reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-wifi"; enable-active-high; gpio = <&pio 0 20 GPIO_ACTIVE_HIGH>; to: reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-wifi"; enable-active-high; gpio = <&pio 0 2 GPIO_ACTIVE_HIGH>; How can I do this and use armbian build script: compile.sh Thanks, Michal