https://github.com/NickAlilovic/build/tree/Radxa-A7A

https://github.com/NickAlilovic/build/releases

To build your own image:

git clone https://github.com/NickAlilovic/build.git --branch Radxa-A7A

./compile.sh

"do not change the kernel configuration"

"show csc/wip/eos/tvb"

"I understand and agree"

"radxa-cubie-a7a" or "radxa-cubie-a7z"

rest is up to you...

Should you choose to run Armbian, ensure the CPU has adequate cooling by installing the Radxa Heatsink.
https://radxa.com/products/accessories/heatsink-6530b
https://radxa.com/products/accessories/heatsink-6540b

This is an MLIR-based lowering path from the TOSA v1 dialect to TIM-VX, VeriSilicon's OpenVX-based GPU/NPU ML Framework.

It includes the lowering from TOSA v1 to a custom timvx dialect (mirrors the TIM-VX C++ semantics) and a full lowering to C++ source.

It is currently on par in inference speed with the vendor ACUITY compiler pipeline while still giving you full control on the graph level.

In my own testing, on a Radxa Cubie A7Z \w Allwinner A733, ResNet-50 takes 8.0ms to inference, while the ACUITY-compiled baseline takes 7.3ms according to Radxa.

It all starts with Radxa/VeriSilicon's false advertisement of the NPU supporting MLIR, but turns out we just don't have it yet, so I made my own.

I have only tested the pipeline on the A733, but it should be able to be extended to any other VIP9000 variants as well.

Hello everyone. I'm kind of new in this SBC bussiness. I'm looking for a way to enable the ethernet port of the expansion board on this device. Hardware wise the port works on Dietpi, but the GPU works better on this version of armbian (Armbian Linux 6.19.9-edge-sunxi64). Anyone who could tell me o point me to the right direction? Thanks.

I have a OpiZ2w with Armbian. I flashed a SD-card, and then I copy the system and boot to a usb- hdd (sda) and the system boot to sda   Want hdd because It write much data and USB 2 don't take mush more speed.

But I get a warning about a file-error or something so I run fsck on sda(hdd) was a systemdisk, but run read-only, but anyway it does not boot any more  

I think I can take the usb-hdd and run fsck from another computer? I have one system with Ubuntu on a Intel 6 gen, and Raspberry pi 500 and 5. The Pi-machine have raspberry-pi OS and the other Ubuntu 24.04.Does the machin or system have any singificans?

Or is there another fix to fix so the /boot can find sda?

But I get a warning about a file-error or something so I run fsck on sda(hdd) that was a systemdisk, but when I run I choose to do it read-only, but anyway it does not boot any more.  

I think I can take the usb-hdd and run fsck from another computer? I have one system with Ubuntu on a Intel 6 gen, and Raspberry pi 500 and 5. The Pi-machine have raspberry-pi OS and the other Ubuntu 24.04.Does the machine or system have any significans?

Or is there another fix to fix so the /boot on SD-card can find sda on USB?

/Cheers

/Edit. I posted under Orange Pi Zero2, but that was wrong place, and get moved, but at the same time get my thread classed as solved, but the solving was just to get the question on right place. I have also cleared my question a little bit and  I can not take away the other. 

https://www.cnx-software.com/2025/07/07/allwinner-a527-t527-and-a733-datasheets-user-manuals-and-linux-sdk-released/

http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-4-Pro.html

Another Allwinner board dropped

figuring out the wifi chip is always hard, seem to be

https://www.taobao.com/list/item/931793873067.htm

https://pine64.sfo3.cdn.digitaloceanspaces.com/doc/datasheet/oz64/AIC8800DC Datasheet v1.0.pdf

as usual, it is uncertain if drivers and firmware is after all available.

Ethernet according to CNX seemed to be YT8531CA 
Ethernet seemed to be same as that in OrangePi Zero 3

https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/

WiFi is 'more critical' these days, if it is closed sourced and no firmware, then it is good as just a door stop.

Then that thare are other stuff the figure out especially the :

- DRAM controller,

- and various DRAM timing and configuration aspects

- many other low level specific stuff to even have u-boot to boot it up to the linux prompt.

- then the other devices e.g. uart etc. 

- then HDMI

- then gpu acceleration (or at least display video, not playing media yet)

- then media 

- and finally NPU, don't seemed documented yet

- many more known or unknown unknowns, audio etc

cat /proc/asound/cards
 0 [Codec          ]: sun4i-codec - H616 Audio Codec
                      h616-audio-codec
 1 [HDMI           ]: HDMI - HDMI
                      HDMI
 2 [Device         ]: USB-Audio - USB PnP Sound Device
                      C-Media Electronics Inc. USB PnP Sound Device at usb-5200400.usb-1, full speed
 

I need an always USB sound card with the number of 0

stable configuration for Orange Pi Zero 3 as a 24/7 SDR server.

The critical discovery: legacy kernel 6.6.75-sunxi64 is the only

stable option. The current kernel crashes within hours under SDR load.

Additional fixes:

- Blacklist aw859a WiFi driver (causes kernel instability)

- Blacklist DVB modules for RTL-SDR

- Lock libairspyhfSupport.so with chattr +i (SpyServer/SoapySDR conflict)

- Mask systemd-networkd-wait-online

- CPU governor: schedutil

- usbcore.autosuspend=-1 for USB SDR dongles

Running 3 SDRs simultaneously: RTL-SDR Blog V4, Airspy HF+, 

dedicated ADS-B. 4 antennas via HMC241 GPIO RF switch.

30+ decoders. Full Android control.

Complete guide: https://ozcet.github.io/sdr-server-guide

https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/

https://liliputing.com/orange-pi-zero-3-is-a-cheap-tiny-single-board-pc-with-up-to-4gb-ram-gigabit-ethernet-and-allwinner-h618/

http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-3.html

even the linux images is very 'fresh' as in that they are just released *yesterday* 😄

I have a couple of H3 based boards (Orange Pi Zero and FriendlyArm NanoPi Duo 2). With all of them I have the same issue:
command like "reboot" turn the board off instead of rebooting.

The workaround is to add following line in /boot/armbianEnv.txt
 

extraargs=reboot=warm

Running latest image on all of the boards.

Hey

Installed Armbian (Ubuntu-noble) with XFCE desktop on an HDD(sda) from SD-card, so I need to have an SD-card in my orange pi zero 2w. I wonder if I can move /boot to an another smaller SD-card? Or do I also need an "mbr" or someting also there u-boot are?

/Cheers

If it is, how do I install U-Boot into the SPI? Is there one specifically for the a5e?

Are you able to power on the board using the GPIO pins? If so please could someone advise which pins to connect to?

I also aim to put a 5.5 x 2.1mm barrel connection on the box (with a latching press button switch for isolation) for the +5v supply and connect a short micro USB connector from the barrel socket to the board and also attach the SATA power leads directly rather than powering from the board 2 pin connector to take the load off the micro USB input.

Boot seems to start fine with all kernel files load confirmed by u-boot output (vmlinuz, ramdisk dtb, etc) but then it goes mute while starting the kernel

@TheSnowfield, you are listed as the pocketchip board maintainer (thanks a lot for your contribution! 🙏), any ideas of what am I missing? Do you have a suggestion for a working build? Thanks!

Serial UART output:

U-Boot SPL 2016.01-00115-g5f814bb (Dec 09 2016 - 23:00:24)
Fuel Gauge: 77%
Battery Voltage: 3776mV
DRAM: 512 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from NAND


U-Boot 2021.10-rc5+ (Oct 21 2021 - 14:43:51 -0500) Allwinner Technology

CPU:   Allwinner A13 (SUN5I)
Model: NextThing C.H.I.P.
I2C:   ready
DRAM:  sunxi SPL version mismatch: expected 3, got 1
512 MiB
NAND:  4096 MiB
Loading Environment from nowhere... OK
Setting up a 480x272 lcd console (overscan 0x0)
In:    serial
Out:   vidconsole
Err:   vidconsole
sunxi SPL version mismatch: expected 2, got 1
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 5 USB Device(s) found
scanning bus usb@1c14400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot:  0
DIP: PocketCHIP (0x1) from Next Thing Co. (0x9d011a)
Found 1 extension board(s).

Device 0: Vendor: Mass     Rev: 1.00 Prod: Storage Device
            Type: Removable Hard Disk
            Capacity: 14832.0 MB = 14.4 GB (30375936 x 512)
... is now current device
Scanning usb 0:1...
Found U-Boot script /boot/boot.scr
5475 bytes read in 4 ms (1.3 MiB/s)
## Executing script at 43100000
U-boot loaded from NAND
154 bytes read in 4 ms (37.1 KiB/s)
sun5i-r8-chip.dtb: No match
Load fdt: /boot/dtb/sun5i-r8-chip.dtb
14474151 bytes read in 780 ms (17.7 MiB/s)
10539688 bytes read in 557 ms (18 MiB/s)
Found mainline kernel configuration
25215 bytes read in 9 ms (2.7 MiB/s)
2146 bytes read in 7 ms (298.8 KiB/s)
Applying kernel provided DT fixup script (sun5i-a13-fixup.scr)
## Executing script at 45000000
Kernel image @ 0x42000000 [ 0x000000 - 0xa0d2a8 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    14474087 Bytes = 13.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Ramdisk to 49232000, end 49fffb67 ... OK
   Loading Device Tree to 491c3000, end 49231fff ... OK

Starting kernel ...

I found cubie-a5e-enable-usb3.dts  from radxa's git but could apply it.

Currently I am running 26.2.0-trunk.22.

Regards

Yesterday I upgraded my NanoPi Neo Plus2, during that the kernel version went from 6.12.74 (package version 26.2.0-trunk.478) to 6.18.19 (package version 26.2.0-trunk.626). This morning I noticed, that this kernel is missing the dm-snapshot.ko module. I searched the forum if anyone else is having this problem, but it appears I am the only one using this feature. I use snapshots to create consistent backups of the system.

Is there a reason why it was removed and more importantly is there a way to get it back without having to compile the kernel myself?

Greetings

PS: I should note, that I want the module back in newer kernel versions in the future. For now I downgraded to some older version that I was able to find a package for and got it working through that.

It worked on the older kernel, but now it doesn't 😞....

Supposedly this is the cause, but is it really?

Quote

DTB (device tree) does not configure GPIO reset/power for the UWE5622.

hci_uart cannot initialize the controller → hci0 is not created.

The overlay for BT in mainline 6.x does not yet exist in Trixie.

❌ Result: hciconfig -a and bluetoothctl list show nothing.

armbianmonitor -u

https://paste.armbian.com/uzudezufit

https://www.aliexpress.us/item/3256803856059047.html

I have read somewhere, that I can use an ili9341 spi driver, only by changing the resolution and changing the initialization script.

I looked in the waveshare website and github, they don't have anything for the ili9488

Then, I found some arduino code in http://www.lcdwiki.com/3.5inch_SPI_Module_ILI9488_SKU%3AMSP3520

(look for the "3.5 inch SPI Module Package(ILI9488)" link, then find the LCDWIKI_SPI.cpp

The initialization sequence is in line 1697:

				0xF7, 4, 0xA9, 0x51, 0x2C, 0x82,
				0xC0, 2, 0x11, 0x09,
				0xC1, 1, 0x41,
				0xC5, 3, 0x00, 0x0A, 0x80,
				0xB1, 2, 0xB0, 0x11,
				0xB4, 1, 0x02,
				0xB6, 2, 0x02, 0x22,
				0xB7, 1, 0xC6,
				0xBE, 2, 0x00, 0x04,
				0xE9, 1, 0x00,
				0x36, 1, 0x08,
				0xE0, 15, 0x00, 0x07, 0x10, 0x09, 0x17, 0x0B, 0x41, 0x89, 0x4B, 0x0A, 0x0C, 0x0E, 0x18, 0x1B, 0x0F,
				0xE1, 15, 0x00, 0x17, 0x1A, 0x04, 0x0E, 0x06, 0x2F, 0x45, 0x43, 0x02, 0x0A, 0x09, 0x32, 0x36, 0x0F,
				0x11, 0,
				TFTLCD_DELAY8, 120,
				0x29, 0

I am currently trying to convert it to a DTS-format init string, so that it fits my ili9341-fb.dts, which I made earlier this year:

/*
OrangePi Zero 3 -> ILI9341 LCD connections
SPI CLOCK = PH6
SPI DO (LCD MISO) = PH8 (OPIZ MISO)
SPI DI (LCD MOSI) = PH7 (OPIZ MOSI)
LCD DATA/CONTROL = PC7 *
LCD RESET = PC14 * could be any GPIO pin I want
CHIP SELECT = PH9
VCC = 3.3V PIN 17
GND = GND PIN 20
*/

/dts-v1/;
/plugin/;
/{
    compatible = "allwinner,sun50i-h616"; /*what is the H618*/
	fragment@0 {
	    target = <&pio>;
	    __overlay__{
	        display_pins: display_pins {
                    pins = "PC7", "PC14"; /* reset, DC pins, order does not matter*/
                    function = "gpio_out", "gpio_out";
                };
            };
	};
	fragment@1 {
        target = <&spi1>;
        __overlay__ {
            /* needed to avoid dtc warning */
            #address-cells = <1>;
            #size-cells = <0>;
            status="okay";
            pinctrl-names = "default";
            pinctrl-0 = <&spi1_pins>; /* Mux the PI to make sure they are set in spi Mode */
            cs-gpios = <&pio 7 9 0>;  /* PH9 chip select, H=7 */
            num-chipselects = <1>;
            display: display@0 {
                /*compatible = "adafruit,yx240qv29","ilitek,ili9341";*/
                compatible = "ilitek,ili9341";
                reg = <0>;
                pinctrl-names = "default";
                pinctrl-1 = <&display_pins>;
                spi-max-frequency = <40000000>;
                rotate = <270>; /* rotate for ili9341, rotation for yx240qv29 */
                bgr=<0>;
                fps = <15>;
                buswidth = <8>;
                height = <640>;
                width = <320>;
                reset-gpios = <&pio 2 14 1>; /* PC14 reset pin*/
                dc-gpios = <&pio 2 7 0>; /* PC7 Data control pin */
                debug = <3>;
                init = <0x10000b0 0x00
                        0x1000011
			0x20000ff
			0x100003a 0x55
			0x1000036 0x28
			0x10000c2 0x44
			0x10000c5 0x00 0x00 0x00 0x00
			0x10000e0 0x0f 0x1f 0x1c 0x0c 0x0f 0x08 0x48 0x98 0x37 0x0a 0x13 0x04 0x11 0x0d 0x00
			0x10000e1 0x0f 0x32 0x2e 0x0b 0x0d 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00
			0x10000e2 0x0f 0x32 0x2e 0x0b 0x0d 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00
			0x1000036 0x28
			0x1000011
			0x1000029>;
            };
        };
    };


    __overrides__ {
        rotate =  <&display>,"rotate:0";
        fps =     <&display>,"fps:0";
        debug =   <&display>,"debug:0";
    };
};

I am unsure how to start the init line, can someone help me?

Then, when I have that init string confirmed, I can use:

https://github.com/notro/panel-mipi-dbi/wiki

https://blog.csdn.net/CNflysky/article/details/125171176

To switch to the mipi-dbi driver, which would get me DRM (instead of FB)

i tried "Armbian_community_26.2.0-trunk.606_Radxa-cubie-a5e_trixie_edge_6.19.8_minimal.img"  and wlan didn't work, i think the device tree is broken Radxa-cubie-a5e kernel 6.19.x

as a quick fix, I copy the kernel 6.18.x "sun55i-a527-cubie-a5e.dtb" file to the /boot/dtb/allwinner directory to get wlan working.

[FAILED] Failed to start Apply Kernel Variables.
[FAILED] Failed to start Dispatcher daemon for systemd-networkd.
[FAILED] Failed to start Helper to synchronize boot up for ifupdown.
[DEPEND] Dependency failed for Raise network interfaces.

The system continues booting, but these errors appear every time.
Hardware:
Board: Orange Pi 3 LTS
Image: Armbian 26.2.1 Minimal / IoT
Storage: TF card
Questions:
Are these errors expected on this board?
Is there a configuration issue with network initialization?
Is this image fully supported for Orange Pi 3 LTS?
Thank you.

is there currently support for NVMe storage in Armbian trunk?

I tried to flash the latest build, added nvme ssd storage - but it is not seen in the system.

What to check?

i could control the OTG micro USB port power on my NanoPi Neo (H3) by exporting and writing to GPIO 354 (line 2 of GPIO chip with base 352)

I'm using Kernel V6.6.62 and I created a tiny device tree overlay defining. Excerpt below:

usb@1c19000 { dr_mode = "host" }
usb0-vbus { status = "okay" }

This works fine!

For test purposes, I switched to a NanoPi Neo2 (H5) with Kernel 6.6.62 (64 bit). Here, the OTG port is powered on and is usable by default without any overlay.

But the on/off control does not work anymore. All attempts to export GPIO 354 give "write error: Device or resource busy".

Schematics show no circuit difference in controlling the OTG power. In both cases its the same pin name on H3 and H5.

The new GPIO handling of newer kernels cannot be the reason, as I use the same kernel versions on H3 and H5 (beside bit width).

Any idea whats wrong and how I can again switch on/off OTG power?

I would like to know if i can connect to my orange pi zero 3

I have already tried to connect but without success, as I am new to this I would like you to help me if possible. 

Thanks!

Sorry for my English I'm on google.

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: 

I am looking for a forum where pcduino users can help each other.

Thank you,

Gaetano.

[   11.048517] unisoc_wifi wlan0: mixed HW and IP checksum settings.
[259241.515808] unisoc_wifi wlan0: sprdwl_report_connection Asus failed status code:30!
[345665.483530] unisoc_wifi wlan0: sprdwl_report_connection sm_state (5), status: (2)!
[345665.483567] unisoc_wifi wlan0: sprdwl_report_connection Asus failed status code:1!

NetworkManager also reports:

link timed out.
Activation failed for connection 'Asus'

After the crash, restarting NetworkManager doesn’t resolve the issue. Trying modprobe -r unisoc_wifi fails, saying the module is not found. The only way to fix it is to reboot the system.

My USB WiFi dongle works fine without these issues, so it seems specific to the onboard WiFi.

Has anyone else experienced this or found a solution for this driver?

I'm getting to the point I'm going to write a cron job when the network drops to reboot the machine 🙃

my dts file:

35Lcd.dts

U-Boot SPL 2024.07 (Feb 25 2026 - 15:51:42 +0300)
DRAM: 512 MiB
Trying to boot from MMC1
CMD_SEND:0
               ARG                      0x00000000
               MMC_RSP_NONE
CMD_SEND:8
               ARG                      0x000001aa
               RET                      -110
CMD_SEND:55
               ARG                      0x00000000
               RET                      -110
CMD_SEND:0
               ARG                      0x00000000
               MMC_RSP_NONE
CMD_SEND:1
               ARG                      0x00000000
               RET                      -110
Card did not respond to voltage select! : -110
spl: mmc init failed with error: -95
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

 

U-Boot SPL 2024.01_armbian-202ns16550_serial serial@1c28000: p024.01-S866c-P7738-Hadc5-Vefe9-B2eb2-R448a (Feb 06 2026 - 03:49:45 +0000) Allwinner Technology
0)
Model: FriendlyARM NanoPi NEent from FAT... Unable to use mmc 1:1...
ial
Err:   serial
Net:   No ethernet found.
starting USB...
No working controllers found
1(part 0) is current device
Scacr
5475 bytes read in 2 ms (2.6 MiB/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
MMC: no card present
* **
Failed to load '/boot/armbianEnv.txt'
Load fdt: /boot/dtb/sun8i-h3-nan13293004 bytes read in 419 ms (30.3 MiB/s)
10014752 bytes read in 317 ms (30.1 MiB/s)
ion
43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    13292940 Bytes = 12.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree bloing Ramdisk to 49352000, end 49fOK
   Loading Device Tree to 49
Starting kernel ...


U-Boot SPL 2024.01_armbian-2024.01-S866c-P7738-Hadc5-Vefe9-B2eDRAM: 512 MiB
Trying to boot frns16550_serial serial@1c28000: p
CPU:   Allwinner H3 (SUN8I 168Core:  64 devices, 16 uclasses, mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... In:    serial,usbkbd
Out:   serial
Err:   serial
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Sca/s)
## Executing script at 4310dary SD
MMC: no card present
** Bad device specification mmc 0Failed to load '/boot/armbianEnv.txt'
Load fdt: /boot/dtb/sun8i-h3-nanopi-neo-air.dtb
13293004 bytes read in 433 ms (29.3 MiB/s)
it Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uux RAMDisk Image (gzip compressed)
   Data Size:    13292940 Bytes = 12.7 MiB
   Load Address: 00000000
   Entry Point:  0000b at 43000000
   Booting using the fdt blob at 0x43000000
Working Ramdisk to 49352000, end 49fff58c ... 2e0000, end 49351fff ... OK
Worns16550_serial serial@1c28000: p19


U-Boot 2024.01_armbian-22eb2-R448a (Feb 06 2026 - 03:49:45 +0000) Allwinner Technology
O Air
DRAM:  512 MiB
ent from FAT... switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
MMC: no card present
** Bad device specification mmc 0 **
Failed to load '/boot/armbianEnv.txt'
13293004 bytes read in 447 ms (2ing Ramdisk to 49352000, end 49f ing USB...
No working controlleAutoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Sca0000
* Bad device specification mmc 0 **
Failed to load '/boot/armbianEnv.txt'
Load fdt: /boot/dtb/sun8i-h3-nanopi-neo-air.dtb
13293004 bytes read in 433 ms (29.3 MiB/s)
OK
## Flattened Device Tree blob at 43000000
   Booting using ing FDT set to 43000000
   Loading Ramdisk to 49352000, end 49fff58c ... OK
   Loading Device Tree to 492e0000, end 49351fff ... OK
Working FDT set to 492e0000

Starting kernel ...

I builded armbian image with compile.sh BOARD=nanopiair BRANCH=legacy RELEASE=bookworm BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no CLEAN_LEVEL="make,debs,cache" OVERLAYS="analog-codec i2c0 i2c1 i2c2 usbhost2 usbhost3" COMPRESS_OUTPUTIMAGE=sha,gz WIREGUARD=yes NAMESERVER=8.8.8.8 DOCKER_ARMBIAN_BASE_IMAGE="ubuntu:jammy" for Nanopi Neo Air. Image is flashed to eMMC. Is any way to solve it?

Fix that might work for Zero2w is here https://forum.armbian.com/topic/31654-orange-pi-zero-2w/ (planning to test it soon)

Can somebody confirm Opi Zero2W 1.5GB has still this issue with some Armbian images ?  Armbian minimal boots without aby issues. Not sure why it works and desktop doesnt.

apt update produces "Hash Sum mismatch"

Anyways, doing my part testing legacy boards, hahahaha

A device of mine, running Armbian, cannot communicate with an Android device in my LAN. Otherwise everything else works.

My Orange Pi Zero 2w running Armbian can ping all of my LAN IPs (and access theyre net services also) , but fails at pinging an Android device (which is connected through WiFi): "Destination Host Unreachable".

Same goes the other way around where Termux runs on the above mentioned Android 15 device but cannot ping ("Destination Host Unreachable") the host running Armbian or access it via ssh (it simply stalls).

Everything else works just fine, all of my devices connect with each other without a glitch; they can all access every other running ssh instance inside the lan (which is a mix of Windows, Linux and Android devices). 

The very same Orange Pi Zero 2w running Armbian is perfectly accessible via ssh from all other hosts and vice versa.

The Android device running Termux is capable of pinging and accessing all other ssh hosts.

And there's more; I'm running Wireguard on the Orange Pi and it works fine. it works so good that once I access the lan with the Android Device through Wireguard, I can suddenly ping the Armbian host and ssh login into it.

Always using the very same IP address (no dns involved).

I wonder where I should look. I cannot imagine what's causing it.

Any suggestions? Is this a known scenario?

ArmBian Community running on Orange Pi Zero 2w

v26.2 rolling for Orange Pi Zero2W running Armbian Linux 6.12.71-current-sunxi64

Packages:     Debian stable (trixie)

Android 15 running Termux

Android REL 15 aarch64

Linux 5.10.236-android12-9-00020

Termux googleplay.2026.02.11

There's no WiFi separation on the router side.

my Cubitruck with  Armbian 23.8.1 Bullseye  has the false Time and i can't change this.

i don't know who is the problem.

"date" says me "Mo 9. Feb 19:24:06 CET 2026" but now we have 05:26, when i set date with "sudo date -s "2026-02-09 05:26:00", it looks like it will be override in the next moment, then "date" says 

 sudo date -s "2026-02-09 05:26:00"
Mo 9. Feb 05:26:00 CET 2026
root@cubietruck ~ > date
Mo 9. Feb 19:26:27 CET 2026

 dmesg | grep -i rtc
[    0.000000] Kernel command line: root=UUID=19cf2f1d-1a31-4890-bc04-a2f1c4e4e021 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=ba110a34-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u rtc-hctosys=0  sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1
[    0.000000] Unknown kernel command line parameters "ubootpart=ba110a34-01 ubootsource=mmc rtc-hctosys=0 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory", will be passed to user space.
[    1.553534] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes
[    1.555880] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes
[    1.573650] sunxi-rtc 1c20d00.rtc: registered as rtc0
[    1.573701] sunxi-rtc 1c20d00.rtc: setting system clock to 2026-02-09T18:15:12 UTC (1770660912)
[    1.755046] axp20x-i2c 1-0034: Backup (RTC) battery charging is enabled
[    2.161281]     rtc-hctosys=0

 sudo systemctl restart chrony
chronyc tracking
chronyc sources -v
Reference ID    : 00000000 ()
Stratum         : 0
Ref time (UTC)  : Thu Jan 01 00:00:00 1970
System time     : 0.000000000 seconds slow of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 6.181 ppm slow
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Not synchronised

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current best, '+' = combined, '-' = not combined,
| /             'x' = may be in error, '~' = too variable, '?' = unusable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^? listserver.trexler.at         0   6     0     -     +0ns[   +0ns] +/-    0ns
^? time.netzwerge.de             0   6     0     -     +0ns[   +0ns] +/-    0ns
^? 2a02:8108:4d82:e400:9677>     0   6     0     -     +0ns[   +0ns] +/-    0ns
^? static.179.181.75.5.clie>     0   6     0     -     +0ns[   +0ns] +/-    0ns
^? 2a09:e1c1:efc4:1337::123      0   6     0     -     +0ns[   +0ns] +/-    0ns
^? 2a01:7e01::f03c:94ff:fee>     2   6     1     0  +50282s[+50282s] +/-   27ms
^? nobody.yourvserver.net        0   6     0     -     +0ns[   +0ns] +/-    0ns
^? ctb01.martinmoerch.dk         0   6     0     -     +0ns[   +0ns] +/-    0ns
^? fritz.box                     0   6     0     -     +0ns[   +0ns] +/-    0ns

What can be the problem and how can i fix it.

Thank you

But DietPies support for the ZeroPi is based on armbian, so I tried this directly:

oldest image not working: Armbian_community_25.8.0-trunk.338_Zeropi_bookworm_current_6.12.35_minimal.img.xz

bootlog12.txt

newest image working: Armbian_community_25.5.0-trunk.256_Zeropi_bookworm_legacy_6.1.104_minimal.img.xz

bootlog13.txt

Does anybody have an idea what it could be?

**2. Environment:**
*   **Hardware:** Orange Pi PC (Allwinner H3)
*   **Image/Distribution:** "Forky" (appears to be an Armbian-based rolling Debian fork)
*   **Kernel:** `6.12.68-current-sunxi` (build@armbian) #1 SMP Fri Jan 30 09:28:49 UTC 2026
*   **Graphics Stack:** Modern DRM/KMS (`sun4i-drm`). The legacy `fb` driver is not active.
*   **Monitor:** Connected via HDMI. EDID is correctly read (tested with `modetest`).

**3. Steps to Reproduce:**
1.  Boot the system with the affected image on an Orange Pi PC.
2.  Log in to the text console (`tty1`).
3.  Run `stty size`. It will always return `30 90`.
4.  Observe that the terminal only uses the top-left quarter of a 1920x1080 display.

**4. Diagnostic Evidence:**
```bash
# Console size is fixed and wrong:
$ stty size < /dev/tty1
30 90

# Framebuffer is provided by DRM and reports correct resolution:
$ cat /sys/class/graphics/fb0/name
sun4i-drmdrmfb
$ cat /sys/class/drm/card0/card0-HDMI-A-1/modes | head -1
1920x1080

# Kernel boot parameters (from /proc/cmdline) include video settings, but are ignored:
root=UUID=... video=HDMI-A-1:1920x1080@60 console=tty1 ...

# All attempted fixes that FAILED:
# - Boot parameters: `fbcon=font:VGA8x16`, `vt.global_cursor_default=0`, `drm_kms_helper.edid_firmware=...`
# - Runtime commands: `resizecons`, `setupcon`, `stty rows cols`, writing to `/sys/class/graphics/fbcon/`
# - Service restarts: `getty@tty1`, `gpm`
```

**5. Expected Behavior:**
The text console should automatically scale to use the full resolution of the framebuffer. For a 1920x1080 framebuffer with an 8x16 font, the expected `stty size` should be approximately `67 240` (or `67 120` for a 16x16 font). The console should fill the entire display.

**6. Additional Notes:**
*   The same hardware works correctly with a **Debian Bookworm** image and an older kernel, where console auto-scaling functions perfectly.
*   This indicates a **regression** in the `6.12.68-current-sunxi` kernel build or its DRM/KMS configuration for the Allwinner H3.
*   The bug makes the distribution unsuitable for any headless or console-focused use case on this hardware.

**7. Questions for Maintainers:**
*   Is there a specific kernel configuration option (`CONFIG_*`) for Allwinner H3 DRM that controls TTY auto-scaling?
*   Has the `vt` or `drm` subsystem changed in a way that requires new boot parameters for this hardware?
*   Can this be worked around without a kernel recompile?

Orange Pi 3 LTS rarely recognize ethernet connection.

How to reproduce?

Flash Orange Pi 3 LTS with an image of the latest version of Armbian.

Extra Info

The latest images tested which worked flawlessly was: 

Armbian_community_25.11.0-trunk.437_Orangepi3-lts_trixie_current_6.12.47_minimal.img

Armbian_23.8.3_Orangepi3-lts_jammy_current_6.1.53_minimal.img

Images tested which didn't worked:

Armbian_community_26.2.0-trunk.151_Orangepi3-lts_trixie_current_6.12.63_minimal.img

Armbian_community_26.2.0-trunk.100_Orangepi3-lts_trixie_current_6.12.63_minimal.img

In the boot log is this line:

Quote

ERROR: FDT image overlaps OS image (OS=0x41000000..0x418750d0)

So I tried to modify `fdt_addr_r` env variable and were able to succesfully boot with theese commands executed in u-boot console:

Quote

env set fdt_addr_r 0x41900000
boot

So adding following line to /boot/armbianEnv.txt on sdcard can fix booting permanently:

Quote

fdt_addr_r=0x41900000

Complete boot log:

Quote

U-Boot SPL 2022.07-armbian (May 01 2023 - 22:12:06 +0000)
DRAM: 128 MiB
Trying to boot from MMC1


U-Boot 2022.07-armbian (May 01 2023 - 22:12:06 +0000) Allwinner Technology

CPU:   Allwinner V3s (SUN8I 1681)
Model: PineCube IP Camera
DRAM:  128 MiB
Core:  46 devices, 19 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20ca0
MMC:   mmc@1c0f000: 0, mmc@1c10000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial@1c28800
Out:   serial@1c28800
Err:   serial@1c28800
Net:   No ethernet found.
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
4121 bytes read in 2 ms (2 MiB/s)
## Executing script at 41900000
U-boot loaded from SD
Boot script loaded from mmc
154 bytes read in 2 ms (75.2 KiB/s)
12336677 bytes read in 512 ms (23 MiB/s)
8868048 bytes read in 369 ms (22.9 MiB/s)
Found mainline kernel configuration
18803 bytes read in 7 ms (2.6 MiB/s)
Failed to load '/boot/dtb/overlay/sun8i-v3s-fixup.scr'
Kernel image @ 0x41000000 [ 0x000000 - 0x8750d0 ]
## Loading init Ramdisk from Legacy Image at 41c00000 ...
  Image Name:   uInitrd
  Image Type:   ARM Linux RAMDisk Image (gzip compressed)
  Data Size:    12336613 Bytes = 11.8 MiB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 41800000
  Booting using the fdt blob at 0x41800000
ERROR: FDT image overlaps OS image (OS=0x41000000..0x418750d0)
SCRIPT FAILED: continuing...
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
No ethernet found.
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
Retrieving file: pxelinux.cfg/000000
No ethernet found.
Retrieving file: pxelinux.cfg/00000
No ethernet found.
Retrieving file: pxelinux.cfg/0000
No ethernet found.
Retrieving file: pxelinux.cfg/000
No ethernet found.
Retrieving file: pxelinux.cfg/00
No ethernet found.
Retrieving file: pxelinux.cfg/0
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.

 

U-Boot SPL 2022.10-armbian (Jun 15 2023 - 13:35:35 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1
ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19


U-Boot 2022.10-armbian (Jun 15 2023 - 13:35:35 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: LinkSprite pcDuino3
DRAM:  1 GiB
Core:  52 devices, 23 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20c90
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1...
Unknown monitor
Unknown monitor
In:    serial
Out:   serial
Err:   serial
Net:   eth_designware ethernet@1c50000: Can't get reset: -2
eth0: ethernet@1c50000
230454 bytes read in 12 ms (18.3 MiB/s)
Unknown monitor
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 2 USB Device(s) found
scanning bus usb@1c14400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
4121 bytes read in 2 ms (2 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
154 bytes read in 2 ms (75.2 KiB/s)
16660327 bytes read in 690 ms (23 MiB/s)
8480576 bytes read in 355 ms (22.8 MiB/s)
Found mainline kernel configuration
42775 bytes read in 9 ms (4.5 MiB/s)
5532 bytes read in 5 ms (1.1 MiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
Kernel image @ 0x42000000 [ 0x000000 - 0x816740 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    16660263 Bytes = 15.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 4901c000, end 49fff727 ... OK
   Loading Device Tree to 48fa9000, end 4901bfff ... OK
DE is present but not probed

Starting kernel ...

I will gratefully for any possible insight

Cheers

Ryzer

I have successfully built the image using the armbian configuration script (bookworm current), the board boots and runs teslausb, however, I am unable to install the driver for my wifi dongle. The error when starting the install-driver.sh script is "your kernel headers are not properly installed". I tried apt install linux-headers-current-sunxi and kernel-headers-armmp, they install successfully but I still get the same error about the kernet headers not being properly installed.

The drivers are for rtl88x2bu cloned from morrownr on github

Any help would be appreciated

Gaetano.

https://www.aliexpress.us/item/2251832431328471.html

I found these recent instructions to be able to display graphics here:

https://ryjelsum.me/homelab/xpt2046-ili9341-opi-zero/

with a reference to a previous experience (without mentioning success)

https://hackaday.io/project/190371-g-edm/log/217902-first-success-with-armbian-nanopi-and-ili9341-touch

and independently, I found these instructions and experiences here:

https://docs.armbian.com/User-Guide_Allwinner_overlays/

https://forum.armbian.com/topic/27457-connecting-banana-pi-m2-zero-with-ili9341-display-over-spi-on-latest-armbian-image/ <-just found it and it has some success with BananaPi M2 Zero

https://tech-de.netlify.app/articles/de547180/index.html

https://4pda.to/forum/index.php?showtopic=782242&st=5060#entry112401076

I connected with wires as shown in instructions: https://forum.armbian.com/topic/28674-text-version-of-orange-pi-zero-pinout/

And the LCD's LED input pin to 3.3V

I activated the spi-add-cs1 overlay in arbian-config

I copied the dts for opiZ into ~/ili9341/ili9341-touch-double-spi-cs.dts

Then, I executed:
 

cd ili9341
armbian-add-overlay ili9341-touch-double-spi-cs.dts

Then, I rebooted, and my LCD just looks gray.

My armbianEnv looks like this:

verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun8i-h3
overlays=spi-add-cs1 tve usbhost2 usbhost3
rootdev=UUID=7d9a7016-73db-4f9c-a5bd-e3e5ab53ffc4
rootfstype=ext4
user_overlays=ili9341-touch-double-spi-cs
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

my armbianmonitor -u: https://paste.armbian.com/arogurekiv

I am still not done checking against the experiences with Bpi M2-0, but I ask here: anyone has experience with ILI9341+XPT2046, in either OrangePi Zero or Zero 3?

Should I downgrade to Linux 6.1.53?

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/

With latest edge 6.15.4 the board boots fine, shutdown also clean and complete but on reboot it does not again start up. Need to powercycle😒

I gets stuck et end of shutdown. Same for latest bookworm image (I think it's 6.12x).

Earlier ones did work.

=> Any other board also affected?

=> Is for reboot the watchdog involved?

   T.

Failed to retrieve unit state: Transport endpoint is not connected

    _             _    _                                         _ _        
   /_\  _ _ _ __ | |__(_)__ _ _ _    __ ___ _ __  _ __ _  _ _ _ (_) |_ _  _ 
  / _ \| '_| '  \| '_ \ / _` | ' \  / _/ _ \ '  \| '  \ || | ' \| |  _| || |
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, |
                                 |___|                                 |__/ 
 v26.2 rolling for Orange Pi Zero running Armbian Linux 6.12.63-current-sunxi

 Packages:     Debian stable (trixie)
 Support:      for advanced users (rolling release)
Failed to retrieve unit state: Transport endpoint is not connected

trying reboot:

root@orangepizero:~# reboot 
Call to Reboot failed: Connection timed out
 

OK, unpacked one of my old breadboard projects on focal Linux nanopiduo 5.10.60-sunxi #21.08.2 SMP Tue Sep 14 16:28:44 UTC 2021 armv7l armv7l armv7l GNU/Linux. CPU idles cool, so I do a:

sudo cat /sys/class/regulator/regulator.5/microvolts
1100000

It looks like 6.x kernel/nobel is using 1.3v. There it is. 1.1V. That confirms the mismatch perfectly. Your old Focal breadboard is running at 1.1V, while the modern Noble board is forcing 1.3V.

On these chips, that 0.2V difference is massive because power (and heat) scales with the square of the voltage. Moving from 1.1V to 1.3V increases heat output by about 40%, which is why one board is a stable 50°C and the other is a 96°C furnace.

So more hacking to do. I'll see if I can do a build hack.

trunk 100 works fine.

Hi all. 

I have a board nanopi neo air with armbian linux on it.   We with my colleague try to setting up ffmpeg with cedrus264 for hardware accelerated  capturing video from ov5640-like camera device. 

There is my  armbianmonitor.  

There are my v4l2-ctl -d /dev/videox -D out:

After some reconfiguration of dts, we can successfully capture video in low fps with 

ffmpeg -f v4l2 -framerate 25 -video_size 960x720 -i /dev/video1 output.mkv

but with 

ffmpeg -f v4l2 -channel 0 -video_size 960x720 -i /dev/video1 -pix_fmt nv12 -r 30 -b:v 64k -c:v cedrus264 test.mp4

ffmpeg failed: 

Ffmpeg was buided from FFmpeg-Cedrus, also we  try follow this and use this binaries - result haven't changed. 

After some inspecting sources of ffmpeg-cedrus we found that ffmpeg try to open /dev/cedar_dev device, which don't exists in our system.  Ffmpeg fails on opening device. If we replace /dev/cedar_dev by /dev/video0, where is our cedrus driver, ffmpeg fails on ioctl IOCTL_GET_ENV_INFO.  In source, it is 99 or 101 line.

We check kernel config for configuration, provided by Sunxi-Cedrus and determine that cedrus was configured right. 

Also we  have tried all described actions on official armbian buster image for nanopi neo air and we have got the same result. 

What we does wrong? 

In orange pi zero 3, we need to stay in bookworm to get video acceleration, so this guide helps build labwc in bookworm

As a greeter, I chose pi-greeter, because it is the lightest login manager I could setup, without any X11

https://github.com/robertojguerra/opiz3-labwc-setup

I am open to read any improvements, or show me how I could make deb packages.

In the near future, I will make a step-by-step video tutorial in Youtube.

*sorry for my bad English.

I found the page https://www.armbian.com/longanpi-3h/ Sipeed LonganPi 3H but no OS images to download. Can anyone help me and give me links to ISOs or there are none yet?

I've already successfully compiled an image by adding a new config to u-boot and armbian-build, and a device tree to the linux kernel. Now I'm looking to get the WiFi working, but I can't seem to find where I can change its pin definitions.

I'm using the AP6212: the SDIO pins are connected to SDC1 (aka mmc1) like every other board, but the WL_REG_ON (aka WL-PMU-EN) and WL_HOST_WAKE (aka WL-WAKE-AP) pins are connected to GPIO pins different from all other boards, so I'll need to change their pin assignments in the kernel manually. But I can't find where are these pins defined! Do I need to change it via u-boot, the kernel, a module or some config file?

Any pointers would be appreciated! Thanks in advance

Using a clean install of Armbian 22.02.1  with Linux 5.15.25-sunxi on a NanoPi NEO the green & blue LEDs no longer work. Previously they have worked with both Armbian and DietPi.

# uname -a
Linux nanopineo 5.15.25-sunxi #22.02.1 SMP Sun Feb 27 09:23:25 UTC 2022 armv7l GNU/Linux

# cat /sys/devices/platform/leds/leds/nanopi:green:status/trigger
cat: '/sys/devices/platform/leds/leds/nanopi:green:status/trigger': No such file or directory

# cat /sys/class/leds/led{0,1}/trigger
cat: /sys/class/leds/led0/trigger: No such file or directory
cat: /sys/class/leds/led1/trigger: No such file or directory

# ls -lha /sys/class/leds/
total 0
drwxr-xr-x  2 root root 0 Dec 31  1969 .
drwxr-xr-x 62 root root 0 Dec 31  1969 ..

# grep led /var/log/syslog
Feb 27 22:38:48 nanopineo kernel: [    2.532268] leds-gpio: probe of leds failed with error -16
Feb 27 22:38:48 nanopineo kernel: [    2.534730] ledtrig-cpu: registered to indicate activity on CPUs

# locate leds
/usr/bin/setleds
/usr/include/linux/uleds.h
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/input/input-leds.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/led-class-flash.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-an30259a.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-axp20x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bcm6328.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bcm6358.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-bd2802.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-cpcap.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-cr0014114.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-dac124s085.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-el15203000.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-is31fl319x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-is31fl32xx.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3530.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3532.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm355x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3642.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3692x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lm3697.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp3944.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp3952.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5521.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5523.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp5562.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp55xx-common.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp8501.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lp8860.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-lt3593.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-max77650.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-mlxreg.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca9532.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca955x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pca963x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-pwm.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-regulator.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-spi-byte.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-tca6507.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-ti-lmu-common.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/leds-tlc591xx.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-as3645a.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-ktd2692.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-lm3601x.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-rt4505.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/flash/leds-rt8515.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-audio.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-backlight.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-camera.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-gpio.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-netdev.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-oneshot.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-pattern.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-timer.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-transient.ko.xz
/usr/lib/modules/5.15.25-sunxi/kernel/drivers/leds/trigger/ledtrig-tty.ko.xz
/usr/share/X11/xkb/compat/ledscroll
/usr/share/man/man1/setleds.1.gz

# ls -l /proc/device-tree/leds
total 0
-r--r--r-- 1 root root 10 Apr 10 10:35 compatible
drwxr-xr-x 2 root root  0 Apr 10 10:30 led-0
drwxr-xr-x 2 root root  0 Apr 10 10:30 led-1
-r--r--r-- 1 root root  5 Apr 10 10:35 name
-r--r--r-- 1 root root  8 Apr 10 10:35 pinctrl-0
-r--r--r-- 1 root root  8 Apr 10 10:35 pinctrl-names
drwxr-xr-x 2 root root  0 Apr 10 10:30 pwr
drwxr-xr-x 2 root root  0 Apr 10 10:30 status

# ls -l /proc/device-tree/leds/led-0
total 0
-r--r--r-- 1 root root 16 Apr 10 10:36 gpios
-r--r--r-- 1 root root 19 Apr 10 10:36 label
-r--r--r-- 1 root root 10 Apr 10 10:36 linux,default-trigger
-r--r--r-- 1 root root  6 Apr 10 10:36 name

# ls -l /proc/device-tree/leds/led-1
total 0
-r--r--r-- 1 root root  3 Apr 10 10:36 default-state
-r--r--r-- 1 root root 16 Apr 10 10:36 gpios
-r--r--r-- 1 root root 17 Apr 10 10:36 label
-r--r--r-- 1 root root  6 Apr 10 10:36 name

# ls -l /proc/device-tree/leds/pwr
total 0
-r--r--r-- 1 root root 16 Apr 10 10:37 gpios
-r--r--r-- 1 root root 15 Apr 10 10:37 label
-r--r--r-- 1 root root 11 Apr 10 10:37 linux,default-trigger
-r--r--r-- 1 root root  4 Apr 10 10:37 name

# ls -l /proc/device-tree/leds/status
total 0
-r--r--r-- 1 root root 16 Apr 10 10:37 gpios
-r--r--r-- 1 root root 20 Apr 10 10:37 label
-r--r--r-- 1 root root 10 Apr 10 10:37 linux,default-trigger
-r--r--r-- 1 root root  7 Apr 10 10:37 name

# cat /proc/device-tree/leds/led-0/gpios

<nothing>

# cat /proc/device-tree/leds/led-0/label
nanopi:blue:status

# cat /proc/device-tree/leds/led-0/linux,default-trigger
heartbeat

# cat /proc/device-tree/leds/led-0/name
led-0

# cat /proc/device-tree/leds/led-1/default-state
on

# cat /proc/device-tree/leds/led-1/gpios
9

# cat /proc/device-tree/leds/led-1/label
nanopi:green:pwr

# cat /proc/device-tree/leds/led-1/name
led-1

# cat /proc/device-tree/leds/pwr/gpios
9

# cat /proc/device-tree/leds/pwr/label
nanopi:red:pwr

# cat /proc/device-tree/leds/pwr/linux,default-trigger
default-on

# cat /proc/device-tree/leds/pwr/name
pwr

# cat /proc/device-tree/leds/status/gpios

<nothing>

# cat /proc/device-tree/leds/status/label
nanopi:green:status

# cat /proc/device-tree/leds/status/linux,default-trigger
heartbeat

# cat /proc/device-tree/leds/status/name
status

In the armbian-config .dts editor I found that led-0 and led-1 are reversed from what I found above. led-0 is blue and led-1 is green. I don't know if that's a show stopper or not.

--- current.dts > edit not saved, kept original ---

1463         leds {
1464                 compatible = "gpio-leds";
1465
1466                 led-0 {
1467                         label = "nanopi:green:pwr";
1468                         gpios = <0x3f 0x00 0x0a 0x00>;
1469                         default-state = "on";
1470                 };
1471
1472                 led-1 {
1473                         label = "nanopi:blue:status";
1474                         gpios = <0x0e 0x00 0x0a 0x00>;
1475                         linux,default-trigger = "heartbeat";
1476                 };
1477         };

The config-5.15.25-sunxi file shows;

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_ONESHOT=m
CONFIG_LEDS_TRIGGER_DISK=y
CONFIG_LEDS_TRIGGER_MTD=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
CONFIG_LEDS_TRIGGER_BACKLIGHT=m
CONFIG_LEDS_TRIGGER_CPU=y
CONFIG_LEDS_TRIGGER_ACTIVITY=y
CONFIG_LEDS_TRIGGER_GPIO=m
CONFIG_LEDS_TRIGGER_DEFAULT_ON=y

I booted with a previous version of DietPi and the LEDs were working as before. It looks like everything needed is there and the correct default trigger is shown etc,

I'm not sure where to look next.

on a Sunvell R69 (H2) and a NanoPi Neo (H3) I got these "old known" eth0 Link Up/Down syndrom, but couldnt find a solution in the forum while using the search-engine

armbianmonitor -u
System diagnosis information will now be uploaded to

Sunvell R69 - Linux sunvell-r69 5.4.0-rc8-sunxi #19.11.3 SMP Wed Nov 27 17:01:29 CET 2019 armv7l armv7l armv7l GNU/Linux : 

http://ix.io/232T

NanoPi Neo - Linux npi-neo 5.3.3-sunxi #5.98 SMP Sat Oct 5 18:34:15 +03 2019 armv7l GNU/Linux :

http://ix.io/232U

in dmesg it looks like
 

[10536.264427] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10568.008879] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10571.081067] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10575.177000] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10580.297247] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10604.873552] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10607.945753] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10608.969632] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10612.041827] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10631.498029] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[10633.546213] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[10636.618141] dwmac-sun8i 1c30000.ethernet eth0: Link is Down

I have the feeling its could have to do with using 1GBit/1000MBit devices on the same 100MBit-Ethernet-Hub, because I do get much mor of these messages when my armbian-build-system-PC is on (which uses a onboard GBit-Ethernet-Card).
On the 100MBit-Hub there are also some othe 1GBit-Devices like the NanoPi Neo2.

On the PC I did try to force the 1GBit-Card to 100MBit with ethtool -s eth0 speed 100 autoneg off 

But that doesnt seem to help.

On other SBC-devices I could find these messages in the dmesg (and in the froum search it was a problem 4 to 2 years ago)

On the other hand there was a disscussion about a new driver version for kernel 4.1.4 at
https://forum.armbian.com/topic/4364-dwmac-sun8i- driver-v6/

With debian stretch armabian 5.41 and kernel 4.1.4.34 I did see that problem (and doenst feel it at a SSH-session) on the Sunvell R69. 

The kernel works, but installing the .deb failed because my extlinux script could not copy:

/usr/lib/linux-image-6.18.1-edge-sunxi/overlay/sun8i-h3-analog-codec.dtbo

The whole overlay folder does not exist. It does exist for  6.12.58-current-sunxi  and last time I compiled kernel for the nanopineo was 6.16.8, the overlays were created.

I remember it was also once the case with edge kernel for other SBC ( .deb package from the Armbian beta repo). That time own local build did create overlays.

I am not sure where to look or what could be wrong.
 

After upgrading to Armbian 26 (kernel version 6.12.58), the onboard network card (end0) experienced a severe degradation in transmission performance (reduced to approximately 1/10 of previous levels). Upon investigation, it was discovered that the kernel driver (dwmac-sun8i) has locked all hardware offload features (TSO/GSO/Checksum), forcing the CPU to handle all processing in software.

root@orangepi3:~# uname -r
6.12.58-current-sunxi64

root@orangepi3:~# dpkg --list | grep linux-image
ii  linux-image-current-sunxi64       26.2.0-trunk.48                         arm64        Armbian Linux current kernel image 6.12.58-current-sunxi64

root@orangepi3:~# readlink /sys/class/net/end0/device/driver
../../../../bus/platform/drivers/dwmac-sun8i

root@orangepi3:~# ethtool -k end0
Features for end0:
rx-checksumming: off
tx-checksumming: off
        tx-checksum-ipv4: off
        tx-checksum-ip-generic: off [fixed]
        tx-checksum-ipv6: off
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: off
        tx-scatter-gather: off
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
        tx-tcp-segmentation: off [fixed]
        tx-tcp-ecn-segmentation: off [fixed]
        tx-tcp-mangleid-segmentation: off [fixed]
        tx-tcp6-segmentation: off [fixed]
generic-segmentation-offload: off
generic-receive-offload: off
large-receive-offload: off [fixed]
rx-vlan-offload: on [fixed]
tx-vlan-offload: off [fixed]
ntuple-filters: off [fixed]
receive-hashing: off [fixed]
highdma: on [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: off [fixed]
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: off [fixed]
tx-gso-list: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: on [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: off
macsec-hw-offload: off [fixed]
rx-udp-gro-forwarding: off
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]
 

Could you please help look into this issue? We are looking forward to seeing it fixed in an upcoming release. Thank you very much.

Regards,

GBH

My board Nano pi neo2 

I have been trying to get sound working on my Orange Pi Zero 3, and I am facing persistent issues. I installed every operating system listed on Armbian’s Orange Pi Zero 3 page and followed all the standard setup procedures. Despite updating all packages and even performing kernel updates, I have never been able to get any sound output from the device.

I have checked multiple configurations, tried different OS images, and ensured that all drivers are up to date, but nothing works. The device otherwise functions normally, but audio simply does not come through under any circumstances.

Could you please provide guidance or a solution? Any help would be greatly appreciated.

Latest stable community release:

https://github.com/armbian/community/releases/download/24.5.0-trunk.123/Armbian_community_24.5.0-trunk.123_Orangepipc2_bookworm_current_6.6.20_minimal.img.xz

With update 23.11 -> 24.2 the orange pi pc2 no longer starts.

I tried a new sd installation and it too does not appear on the network. Right now I don't have a serial cable to check but it is possible that the network driver is missing or not working.

SD, SBC and PSU are 100% working: a revert to 23.11.2 makes it work perfectly.

apt update
Stary:1 http://deb.debian.org/debian bookworm InRelease
Stary:2 http://security.debian.org bookworm-security InRelease                                                          
Stary:3 https://download.docker.com/linux/debian bookworm InRelease                                                     
Stary:4 http://deb.debian.org/debian bookworm-updates InRelease                                                         
Stary:5 http://deb.debian.org/debian bookworm-backports InRelease                                                       
Stary:6 https://dtcooper.github.io/raspotify raspotify InRelease                                                        
Stary:7 https://github.armbian.com/configng stable InRelease                                                            
Stary:8 http://armbian.lv.auroradev.org/beta bookworm InRelease                                       
Czytanie list pakietów... Gotowe                         
Budowanie drzewa zależności... Gotowe
Odczyt informacji o stanie... Gotowe   
1 package can be upgraded. Run 'apt list --upgradable' to see it.
root@orangepi3-lts:~# apt list --upgradable
Listing... Gotowe
armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49]
N: There is 1 additional version. Please use the '-a' switch to see it
root@orangepi3-lts:~# apt list --upgradable -a
Listing... Gotowe
armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49]
armbian-bsp-cli-orangepi3-lts-current/now 25.8.0-trunk.49 arm64 [installed,upgradable to: 25.11.0-trunk.401]

maybe someone has already dealt with this message and error?

Does the image come with and install non free software on the computer? If so is there documentation showing how to do a fully free software installation of the Armbian_community_25.11.0-trunk.546_Lime2_trixie_current_6.12.58_minimal.img image?

Free software is software you can use, share, modify and redistribute. Thank you.

I wrote aind compile little module only for tests:

#include <linux/module.h>
#include <linux/sched.h>

static int errval = 0;

//module_param(errval,int,S_IRWXU);
module_param(errval,int,S_IWUSR|S_IRUSR|S_IWGRP|S_IRGRP);
MODULE_PARM_DESC(errval,"Value to return from init function");
int my_init_module(void)
{
	
	
    printk("errval=%d\n",errval);
	return errval;
}

void my_cleanup_module(void)
{
	printk("The module is now unloaded\n");
}
module_init(my_init_module);
module_exit(my_cleanup_module);
MODULE_LICENSE("GPL");

compile by:

make -C /lib/modules/6.6.75-current-sunxi64/build  M=$(PWD) modules

And it cause segmentation fault

onlyme@orangepizero3:~/modules/errors$ sudo insmod errs.ko
[sudo] password for onlyme: 

Message from syslogd@orangepizero3 at Mar 10 13:35:33 ...
 kernel:[  331.593726] Internal error: Oops: 0000000096000004 [#1] SMP

Message from syslogd@orangepizero3 at Mar 10 13:35:33 ...
 kernel:[  331.798432] Code: 540005a0 f9401680 aa1a03e2 aa1703e1 (f9406400) 
Segmentation fault

On Ubuntu x86 and raspbian (raspbery pi 3) it works, on orangepi zero 3 dosnet. Why?

Quote

[   22.495764] sun55i-gmac200 4510000.ethernet: deferred probe timeout, ignoring dependency
[   22.495788] sun55i-gmac200 4510000.ethernet: probe with driver sun55i-gmac200 failed with error -110
 

2025-06-05T11:29:33.367636+02:00 bananapipro2 kernel: [934985.549250] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) dump-ftrace-buffer(z) replay-kernel-logs(R)

The system continues to work (although I remember that it stooped at this point in older releases).

Is there any action required? I am afraid that this could stop my system which is running unattended for longer periods usually.

I am running v25.2.2 for Banana Pi Pro running Armbian Linux 6.12.20-current-sunxi.

I'm getting stuck trying to compile the cedar_ve kernel driver from https://github.com/uboborov/sunxi-cedar-mainline

I have downloaded the kernel source using armbian-config and then built the sunxi-cedar-mainline kernel driver. However, I fail to load the driver due to version magic:

Quote

root@nanopineo:~# modprobe cedar_ve
modprobe: ERROR: could not insert 'cedar_ve': Exec format error
root@nanopineo:~# dmesg | tail -n 1
[  653.998366] cedar_ve: version magic '5.15.80 SMP mod_unload ARMv7 thumb2 p2v8 ' should be '5.15.80-sunxi SMP mod_unload ARMv7 thumb2 p2v8 '

When trying to force the load:

Quote

root@nanopineo:~# modprobe -f cedar_ve
modprobe: ERROR: could not insert 'cedar_ve': Exec format error

But no dmesg message about magic check failure.
 

Here's some more details:

uname -r returns: 6.12.23-current-sunxi64

cat /boot/armbianEnv.txt returns:

verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun50i-h616
rootdev=UUID=adb61282-df86-4116-9688-e94c56913687
rootfstype=ext4
overlays=i2c0-pi i2c1-pi
param_i2c1_pin_sda=3
param_i2c1_pin_scl=5
user_overlays=
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

sudo i2cdetect -l returns:
i2c-0   i2c             DesignWare HDMI                         I2C adapter
i2c-1   i2c             mv64xxx_i2c adapter                     I2C adapter
i2c-2   i2c             mv64xxx_i2c adapter                     I2C adapter
i2c-3   i2c             mv64xxx_i2c adapter                     I2C adapter
i2c-4   i2c             mv64xxx_i2c adapter                     I2C adapter

sudo i2cdetect -y 1 returns:
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Here's a picture of the display:

Here's a picture of the pin layout:

VCC is going to 3.3v, GND to GND, SDA to pin 3, and SCK to pin 5

Thanks!

Feel free to ask for more details!

It should have A40I CPU, like the M2 Ultra (which is actually supported)

To enable i2c on PH4 and PH5 pins, one would have to have to following lines in /boot/armbianEnv.txt files:

Quote

overlay_prefix=sun50i-h616
overlays=i2c3-ph

Reboot and see the new devices with:

Quote

ls /dev/i2c*

Scan for all the connected i2c devices:

Quote

 

sudo apt install i2c-tools

i2cdetect -y 2

 

All relevant (and some extra) overlays can be seen with the following command:

Quote

ls /boot/dtb/allwinner/overlay/sun50i-h616*

To see the configuration one could disassemble the dtb binary file and search it's contents for i2c3-ph

Quote

 

cd /boot/dtb/allwinner

dtc -I dtb -O dts sun50i-h618-orangepi-zero3.dtb > opz3.dts

 

Whenever making changes it would be the best to connect a serial monitor to the physical serial pins (3 separate pins labeled with UART and GND, RX, TX) to see kernel output at boot (115200 baud rate). The kernel log would have a line for loading the dtbo (or maybe an error for missing file:

Quote

Applying kernel provided DT overlay sun50i-h616-i2c3-ph.dtbo

For easier reference there are included lsmod output, kernel config and dts files from an armbian and the opiz version for "original" debian image (distributed by a sketchy Google drive link, it runs an unnecessary service with weird software repositories enabled by default).

lsmod-armbian lsmod-opiz kernel-armbian.config kernel-opiz.config opz3-armbian.dts opiz3-opiz.dts

/dts-v1/;
/plugin/;
/ {
    compatible = "allwinner,sun50i-h616";
    fragment@0 {
        target = <&spi1>;
        __overlay__ {
            status = "okay";
        cs-gpios = <&pio 7 5 0>,<&pio 2 15 0>; /*PH5=CS0 for lcd, PC15=CS1 for touch*/
            display: display@0 {
                compatible = "ilitek,ili9341";
                reg = <0>;
                pinctrl-names = "default";
                spi-max-frequency = <20000000>;
                rotate = <270>;
                bgr = <0>;
                fps = <30>;
                buswidth = <8>;
                regwidth = <16>;
                height = <480>;
                width = <320>;
                reset-gpios = <&pio 2 14 1>; /* PC14 */
                dc-gpios = <&pio 2 6 0>; /* PC6 */
                debug = <3>;
                init = <0x10000b0 0x00 // Interface Mode Control
                        0x1000011  // Sleep Out
                        0x20000ff  // Delay (255ms)
                        0x10000C0 0x0D 0x0D  // Power Control 1
                        0x10000C1 0x43  // Power Control 2
                        0x10000C5 0x00 0x48 0x80  // VCOM Control 1
                        0x10000C7 0x00  // VCOM Control 2
                        0x1000036 0x28  // Memory Access Control (Rotacao)
                        0x100003A 0x55  // Pixel Format Set (16bit)
                        0x10000B1 0xB0 0x11  // Frame Rate Control
                        0x10000F0 0x01 // Enable Extended Comand Set
                        0x10000F6 0x00 0x01 0x32 // SPI ilInterface Control
                        0x1000026 0x01 // Gamma Set
                        0x10000E0 0x0F 0x31 0x2B 0x0C 0x0E 0x08 0x4E 0xF1 0x37 0x07 0x10 0x03 0x0E 0x09 0x00  // Positive Gamma Correction
                        0x10000E1 0x00 0x0E 0x14 0x03 0x11 0x07 0x31 0xC1 0x48 0x08 0x0F 0x0C 0x31 0x36 0x0F  // Negative Gamma Correction
                        0x10000B6 0x02 0x02 0x3B  // Display Function Control
                        0x1000011  // Sleep Out
                        0x20000ff  // Delay (255ms)
                        0x1000029>; // Display ON
            };

            ads7846: ads7846@1 {
                compatible = "ti,ads7846";
                reg = <1>;
                pinctrl-names = "default";
                spi-max-frequency = <1000000>;
                interrupt-parent = <&pio>;
                interrupts = <2 10 2>; /* PC10 - IRQ */
                pendown-gpio = <&pio 2 10 1>; /* PC10 */
                
                /* OPTIONS */
                ti,x-min = /bits/ 16 <0>;
                ti,y-min = /bits/ 16 <0>;
        ti,x-max = /bits/ 16 <0xFFF>;
        ti,y-max = /bits/ 16 <0xFFF>;
                ti,pressure-min = /bits/ 16 <0>;
                ti,pressure-max = /bits/ 16 <0xFFF>;
                ti,x-plate-ohms = /bits/ 16 <400>;
                ti,swap-xy = <1>;
        };
        };
    };
};

Here's what I got in the console:

root@orangepizero3:~# dmesg | grep -i "spi\|ili9486\|fb_"
[    1.496981] sun6i-spi 5010000.spi: Error applying setting, reverse things back
[    1.497500] sun6i-spi 5011000.spi: cannot register SPI host
[    1.504082] sun6i-spi 5010000.spi: Error applying setting, reverse things back
[    1.504504] sun6i-spi 5011000.spi: cannot register SPI host
[    1.512160] spi-nor spi0.0: supply vdd not found, using dummy regulator
[    6.677433] fb_ili9341: module is from the staging directory, the quality is unknown, you have been warned.
[    6.677997] fb_ili9341 spi1.0: fbtft_property_value: width = 320
[    6.678010] fb_ili9341 spi1.0: fbtft_property_value: height = 480
[    6.678018] fb_ili9341 spi1.0: fbtft_property_value: regwidth = 16
[    6.678025] fb_ili9341 spi1.0: fbtft_property_value: buswidth = 8
[    6.678033] fb_ili9341 spi1.0: fbtft_property_value: debug = 3
[    6.678041] fb_ili9341 spi1.0: fbtft_property_value: rotate = 270
[    6.678049] fb_ili9341 spi1.0: fbtft_property_value: fps = 30
[    6.678234] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'reset' GPIO
[    6.678260] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'dc' GPIO
[    6.678279] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'rd' GPIO
[    6.678294] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'wr' GPIO
[    6.678310] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'cs' GPIO
[    6.678325] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'latch' GPIO
[    6.678340] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678354] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678369] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678383] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678398] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678412] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678426] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678441] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678456] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678470] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678485] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678499] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678514] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678528] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678543] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678557] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678572] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678587] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678604] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678621] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678638] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678655] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678672] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678689] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678706] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678723] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678740] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678757] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678774] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678791] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678808] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678825] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678842] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678859] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678876] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678893] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678910] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678927] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678944] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.678961] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.678978] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.678995] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.679012] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.679029] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.679046] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.679063] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO
[    6.679080] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO
[    6.679098] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO
[    6.701957] ads7846 spi1.1: supply vcc not found, using dummy regulator
[    6.703555] ads7846 spi1.1: touchscreen, irq 77
[    6.704030] input: ADS7846 Touchscreen as /devices/platform/soc/5011000.spi/spi_master/spi1/spi1.1/input/input0
[    6.801201] fb_ili9341 spi1.0: init: write_register:
[    6.801229] fb_ili9341 spi1.0: buf[0] = B0
[    6.801238] fb_ili9341 spi1.0: buf[1] = 00
[    6.801397] fb_ili9341 spi1.0: init: write_register:
[    6.801406] fb_ili9341 spi1.0: buf[0] = 11
[    6.801441] fb_ili9341 spi1.0: init: msleep(255)
[    7.073196] fb_ili9341 spi1.0: init: write_register:
[    7.073241] fb_ili9341 spi1.0: buf[0] = C0
[    7.073265] fb_ili9341 spi1.0: buf[1] = 0D
[    7.073284] fb_ili9341 spi1.0: buf[2] = 0D
[    7.073489] fb_ili9341 spi1.0: init: write_register:
[    7.073510] fb_ili9341 spi1.0: buf[0] = C1
[    7.073530] fb_ili9341 spi1.0: buf[1] = 43
[    7.073701] fb_ili9341 spi1.0: init: write_register:
[    7.073721] fb_ili9341 spi1.0: buf[0] = C5
[    7.073743] fb_ili9341 spi1.0: buf[1] = 00
[    7.073762] fb_ili9341 spi1.0: buf[2] = 48
[    7.073781] fb_ili9341 spi1.0: buf[3] = 80
[    7.073952] fb_ili9341 spi1.0: init: write_register:
[    7.073973] fb_ili9341 spi1.0: buf[0] = C7
[    7.073994] fb_ili9341 spi1.0: buf[1] = 00
[    7.074163] fb_ili9341 spi1.0: init: write_register:
[    7.074183] fb_ili9341 spi1.0: buf[0] = 36
[    7.074203] fb_ili9341 spi1.0: buf[1] = 28
[    7.074372] fb_ili9341 spi1.0: init: write_register:
[    7.074392] fb_ili9341 spi1.0: buf[0] = 3A
[    7.074414] fb_ili9341 spi1.0: buf[1] = 55
[    7.074581] fb_ili9341 spi1.0: init: write_register:
[    7.074601] fb_ili9341 spi1.0: buf[0] = B1
[    7.074622] fb_ili9341 spi1.0: buf[1] = B0
[    7.074641] fb_ili9341 spi1.0: buf[2] = 11
[    7.074809] fb_ili9341 spi1.0: init: write_register:
[    7.074829] fb_ili9341 spi1.0: buf[0] = F0
[    7.074850] fb_ili9341 spi1.0: buf[1] = 01
[    7.075018] fb_ili9341 spi1.0: init: write_register:
[    7.075038] fb_ili9341 spi1.0: buf[0] = F6
[    7.075058] fb_ili9341 spi1.0: buf[1] = 00
[    7.075077] fb_ili9341 spi1.0: buf[2] = 01
[    7.075096] fb_ili9341 spi1.0: buf[3] = 32
[    7.075264] fb_ili9341 spi1.0: init: write_register:
[    7.075285] fb_ili9341 spi1.0: buf[0] = 26
[    7.075306] fb_ili9341 spi1.0: buf[1] = 01
[    7.075474] fb_ili9341 spi1.0: init: write_register:
[    7.075494] fb_ili9341 spi1.0: buf[0] = E0
[    7.075515] fb_ili9341 spi1.0: buf[1] = 0F
[    7.075534] fb_ili9341 spi1.0: buf[2] = 31
[    7.075553] fb_ili9341 spi1.0: buf[3] = 2B
[    7.075571] fb_ili9341 spi1.0: buf[4] = 0C
[    7.075590] fb_ili9341 spi1.0: buf[5] = 0E
[    7.075609] fb_ili9341 spi1.0: buf[6] = 08
[    7.075628] fb_ili9341 spi1.0: buf[7] = 4E
[    7.075647] fb_ili9341 spi1.0: buf[8] = F1
[    7.075665] fb_ili9341 spi1.0: buf[9] = 37
[    7.075684] fb_ili9341 spi1.0: buf[10] = 07
[    7.075703] fb_ili9341 spi1.0: buf[11] = 10
[    7.075722] fb_ili9341 spi1.0: buf[12] = 03
[    7.075742] fb_ili9341 spi1.0: buf[13] = 0E
[    7.075761] fb_ili9341 spi1.0: buf[14] = 09
[    7.075780] fb_ili9341 spi1.0: buf[15] = 00
[    7.075954] fb_ili9341 spi1.0: init: write_register:
[    7.075974] fb_ili9341 spi1.0: buf[0] = E1
[    7.075995] fb_ili9341 spi1.0: buf[1] = 00
[    7.076014] fb_ili9341 spi1.0: buf[2] = 0E
[    7.076034] fb_ili9341 spi1.0: buf[3] = 14
[    7.076053] fb_ili9341 spi1.0: buf[4] = 03
[    7.076071] fb_ili9341 spi1.0: buf[5] = 11
[    7.076090] fb_ili9341 spi1.0: buf[6] = 07
[    7.076109] fb_ili9341 spi1.0: buf[7] = 31
[    7.076128] fb_ili9341 spi1.0: buf[8] = C1
[    7.076147] fb_ili9341 spi1.0: buf[9] = 48
[    7.076165] fb_ili9341 spi1.0: buf[10] = 08
[    7.076184] fb_ili9341 spi1.0: buf[11] = 0F
[    7.076203] fb_ili9341 spi1.0: buf[12] = 0C
[    7.076222] fb_ili9341 spi1.0: buf[13] = 31
[    7.076241] fb_ili9341 spi1.0: buf[14] = 36
[    7.076260] fb_ili9341 spi1.0: buf[15] = 0F
[    7.076432] fb_ili9341 spi1.0: init: write_register:
[    7.076452] fb_ili9341 spi1.0: buf[0] = B6
[    7.076473] fb_ili9341 spi1.0: buf[1] = 02
[    7.076493] fb_ili9341 spi1.0: buf[2] = 02
[    7.076511] fb_ili9341 spi1.0: buf[3] = 3B
[    7.076679] fb_ili9341 spi1.0: init: write_register:
[    7.076699] fb_ili9341 spi1.0: buf[0] = 11
[    7.076797] fb_ili9341 spi1.0: init: msleep(255)
[    7.361180] fb_ili9341 spi1.0: init: write_register:
[    7.361202] fb_ili9341 spi1.0: buf[0] = 29
[    7.490659] fb_ili9341 spi1.0: Display update: 2321 kB/s, fps=0
[    7.491267] graphics fb0: fb_ili9341 frame buffer, 480x320, 300 KiB video memory, 16 KiB buffer memory, fps=31, spi1.0 at 20 MHz

I'm connecting exactly according to this picture:

My English is not native so i`ll try to write in simlpe way.

image

Armbian_23.8.1_Orangepipc_jammy_current_6.1.47_minimal.img.xz

my dts:

/dts-v1/;
/plugin/;
/ {
    compatible = "allwinner,sun8i-h3";
    fragment@0 {
        target = <&spi0>;
        __overlay__ {
            status = "okay";
            // cs-gpios = <&pio 0 9 0>,<&pio 0 8 0>; /* PA9=CS0 for LCD, PA8=CS1 for touch */
            display: display@0 {
                compatible = "ilitek,ili9341";
                reg = <0>;
                pinctrl-names = "default";
                spi-max-frequency = <20000000>;
                txbuflen = <65536>;
                rotate = <270>;
                bgr = <0>;
                fps = <30>;
                buswidth = <8>;
                regwidth = <16>;
                height = <480>;
                width = <320>;
                reset-gpios = <&pio 0 2 1>; /* PA20 */
                dc-gpios = <&pio 0 71 0>; /* PA10 */
                debug = <0>;
                init = <0x10000b0 0x00 // Interface Mode Control
                        0x1000011  // Sleep Out
                        0x20000ff  // Delay (255ms)
                        0x10000C0 0x0D 0x0D  // Power Control 1
                        0x10000C1 0x43  // Power Control 2
                        0x10000C5 0x00 0x48 0x80  // VCOM Control 1
                        0x10000C7 0x00  // VCOM Control 2
                        0x1000036 0x28  // Memory Access Control (Rotacao)
                        0x100003A 0x55  // Pixel Format Set (16bit)
                        0x10000B1 0xB0 0x11  // Frame Rate Control
                        0x10000F0 0x01 // Enable Extended Comand Set
                        0x10000F6 0x00 0x01 0x32 // SPI ilInterface Control
                        0x1000026 0x01 // Gamma Set
                        0x10000E0 0x0F 0x31 0x2B 0x0C 0x0E 0x08 0x4E 0xF1 0x37 0x07 0x10 0x03 0x0E 0x09 0x00  // Positive Gamma Correction
                        0x10000E1 0x00 0x0E 0x14 0x03 0x11 0x07 0x31 0xC1 0x48 0x08 0x0F 0x0C 0x31 0x36 0x0F  // Negative Gamma Correction
                        0x10000B6 0x02 0x02 0x3B  // Display Function Control
                        0x1000011  // Sleep Out
                        0x20000ff  // Delay (255ms)
                        0x1000029>; // Display ON
                };
//                xpt2046: xpt2046@1 {
//                                compatible = "ti,ads7846";
//                                reg = <1>;
//                                spi-max-frequency = <2000000>;
//                                interrupts = <0 7 2>; /* high-to-low edge triggered */
//                                interrupt-parent = <&pio>;
//                                pendown-gpio = <&pio 0 7 0>;
//                                ti,keep-vref-on = <1>;
//                                ti,x-min = /bits/ 16 <200>;
//                                ti,x-max = /bits/ 16 <3900>;
//                                ti,y-min = /bits/ 16 <200>;
//                                ti,y-max = /bits/ 16 <3900>;
//                                ti,x-plate-ohms = /bits/ 16 <60>;
//                                ti,pressure-max = /bits/ 16 <255>;
//                                ti,swap-xy = <1>;
//            };
        };
    };
};

when board boots, display switch from white to black. Without console output.

gpio readall - looks good. all pins present.

when I try Armbian_25.8.1_Orangepione_noble_current_6.12.43.img.xz

board boots. add overlay to it, by armbian-add-overlays

remove HDMI cable. (Really good first-config over ssh, why not to add this to other boards, like mine?)

reboot

Display works(Ony if HDMI is unpluged), with output of boot Armbian.

I`ll think this something wrong with output on spi LCD over OrangePi PC Armbian build, or sometning like that way....

Any advise?

UPD:

Ok. I get it to work.(Armbian_23.8.1_Orangepipc_jammy_current_6.1.47_minimal.img.xz)

ili9341 may be changed to ili9486. Didn`t matter...why?

dmesg | grep graphics
[    9.406143] graphics fb1: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 64 KiB buffer memory, fps=31, spi0.0 at 16 MHz

con2fbmap 1 1
 

and it works....

UPD 2: ili9486.dtbo With touch working, tested trought evtest

I have an Orange Pi Zero 3 with Allwinner H618 (1GB RAM version). The CPU specs say up to 1.5 GHz (1512000 kHz), and it hits that fine on other distros (like official Orange Pi Ubuntu images or Debian builds). But on Armbian, max freq is stuck at 1416000 kHz, even on latest kernels.

Board: Orange Pi Zero 3 (H618, 1GB RAM) Armbian Version: Armbian Bookworm (fresh SD flash, ran armbian-upgrade after boot) Kernel Versions Tested:

6.12.43-current-sunxi64

6.12.47-current-sunxi64

6.15.4-edge-sunxi64

6.16.8-edge-sunxi64 (current edge, i think)

What happens:

scaling_available_frequencies only goes up to 1416000.

With governor=performance and MAX_SPEED=1512000 in cpufrequtils, under load (stress --cpu 4) it never goes above 1416000.

No throttling (temps <65°C with heatsink, armbianmonitor clean).

dmesg says "sun50i_cpufreq_nvmem: Using CPU speed bin speed0" and seems to fallback to H616 limits, cutting OPP table.

Tried:

armbian-config to switch kernels.

Edit /etc/default/cpufrequtils (GOVERNOR=performance, MAX_SPEED=1512000).

extraargs=cpufreq.default_governor=performance in /boot/armbianEnv.txt. No DTB changes (don't want to break stuff).

On non-Armbian (e.g., Orange Pi's Ubuntu 24.04), 1512000 shows in available freqs and runs full speed. Armbian works for basics (WiFi, Ethernet, local server), but this caps perf by ~7%.

Attached outputs from 6.16.8-edge. How to unlock full OPP for H618 speed bin 0?

Thanks.
By the way, this is my first time using Armbian and posting on the forum, so sorry if anything's off.

Zaplemon

freq_info.txt dmesg_cpufreq.txt armbianmonitor_load.txt uname.txt

Armbian-unofficial_25.11.0-trunk_Nanopiduo_noble_current_6.12.51.img

I am trying to get the micro-USB port to work as a USB serial gadget (g_serial / libcomposite).

What I have done / observed:

g_serial and libcomposite modules are loaded:

lsmod | grep g_serial g_serial 12288 0 libcomposite 49152 2 g_serial,usb_f_acm

ConfigFS is mounted:

mount | grep configfs configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)

UDC exists:

ls /sys/class/udc/ musb-hdrc.2.auto

Gadget folder does not exist:

ls /sys/kernel/config/usb_gadget/ # output: empty

Trying to manually bind a gadget fails:

echo musb-hdrc.2.auto | sudo tee /sys/kernel/config/usb_gadget/g1/UDC # Output: tee: UDC: Device or resource busy

Current UDC mode:

cat /sys/class/udc/musb-hdrc.2.auto/device/mode b_idle

There is no /sys/class/usb_role/usb0/role available to force device mode.

This setup works fine on Jammy kernel, same cable, same SD card rootfs.

Problem:

The OTG controller comes up in b_idle mode, preventing the USB gadget from binding. /dev/ttyACM0 never appears on the host PC. It seems like the device tree / overlay for Noble 6.12.51 is not configuring the OTG port for peripheral mode.

What I want:

USB serial gadget (g_serial) working over the micro-USB port on Noble 6.12.51 build.

Any advice on the correct overlay or device tree modification needed to bring the OTG port into device mode at boot.

Extra info:

CONFIG_USB_CONFIGFS_SERIAL=y in kernel

CONFIG_USB_LIBCOMPOSITE compiled as module

Micro-USB cable confirmed working with Jammy kernel

Modules: libcomposite, g_serial, usb_f_acm present

Thanks in advance for guidance!

Here are the versions I’m using:

Kernel:
5.15.48-sunxi

OS:
Linux nanopineo 5.15.48-sunxi #22.05.3 SMP Wed Feb 19 15:56:03 UTC 2025 armv7l GNU/Linux

I’m having a problem.
Sometimes, during boot, I see the following log:

Quote

U-Boot SPL 2021.10-armbian (Feb 19 2025 - 15:25:27 +0000)
DRAM: 512 MiB
Trying to boot from MMC2

U-Boot 2021.10-armbian (Feb 19 2025 - 15:25:27 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyARM NanoPi NEO
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:1... 
In:    serial
Out:   serial
Err:   serial
Net:   phy interface0

Error: ethernet@1c30000 address not set.
No ethernet found.

starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... 1 USB Device(s) found
scanning bus usb@1c1d400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3965 bytes read in 2 ms (1.9 MiB/s)
## Executing script at 43100000
Unknown command '#' - try 'help'
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
553 bytes read in 1 ms (540 KiB/s)
11910689 bytes read in 377 ms (30.1 MiB/s)
8378424 bytes read in 266 ms (30 MiB/s)
Found mainline kernel configuration
30287 bytes read in 4 ms (7.2 MiB/s)
Failed to load '/boot/dtb/overlay/-fixup.scr'
Kernel image @ 0x42000000 [ 0x000000 - 0x7fd838 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11910625 Bytes = 11.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 494a4000, end 49fffde1 ... OK
   Loading Device Tree to 49434000, end 494a3fff ... OK

Starting kernel ...

After this message, the system halts.

The only way to fix it is to flash the image again or to boot from an SD card and mount the EMMC which fixes the file system. 

I noticed that the device doesn’t use the overlay_prefix variable from /boot/armbianEnv.txt.
It shows this message:

Quote

Failed to load '/boot/dtb/overlay/-fixup.scr'

I tried adding the overlay_prefix variable manually in the boot.cmd file, but it didn’t help.

Previously, I changed:

Quote

setenv devnum "0"

to

Quote

setenv devnum "1"

Could that be the cause?

I changed it back to default

Quote

setenv devnum "0"

but the problem still happens.

Do you have any ideas what could be wrong?

drv-sun8i-a83t-cedrus-add-variant.patch

It now appears to load but complains about being unable to allocated an SRAM:

[   10.046406] cedrus 1c0e000.video-codec: Failed to claim SRAM
[   10.046490] cedrus 1c0e000.video-codec: Failed to probe hardware
[   10.091215] cedrus 1c0e000.video-codec: Failed to claim SRAM
[   10.091339] cedrus 1c0e000.video-codec: Failed to probe hardware
[   10.419296] cedrus 1c0e000.video-codec: Failed to claim SRAM
[   10.419597] cedrus 1c0e000.video-codec: Failed to probe hardware
[   20.193058] cedrus 1c0e000.video-codec: Failed to claim SRAM
[   20.193114] cedrus 1c0e000.video-codec: Failed to probe hardware
[   20.193322] platform 1c0e000.video-codec: deferred probe pending: (reason unknown)

Using both sun8i-a23-a33.dtsi and sun8i-h3.dtsi as points of reference, I attempted to make an SRAM allocation under the system controller but this still appears to fail with the same failure messages. I have double checked in the user manual and VE memory should definitely exist at 0x01D0 0000.

arm-dts-sun8i-a83t-add-ve-node.patch

I would be grateful for any pointers.

Thanks 

Ryzer

I'm using the Orange Pi Zero 3 and would really appreciate a lightweight desktop image with just the XFCE desktop, a web browser, and basic tools (like file manager, terminal, etc.) with video acceleration.

The current Armbian desktop image works, but it includes a lot of software I don’t need. I’m looking for something more minimal — just enough for light use and a faster experience.

Does anyone have (or know how to build) a stripped-down XFCE image for this board?

Thanks in advance!

Hi!

Is the Orange Pi3 image suitable for the Orange Pi3 LTs? Or where to find it?

Hardware:

• Board: Orange Pi Zero 2W (Allwinner H618)
• Audio Module: MAX98357A (I2S)

Connections:

• BCLK → PI13 (Pin 7)
• LRC/WS → PI14 (Pin 16)
• DIN → PI15 (Pin 31)
• 5V/GND → Properly connected

Software:

• Armbian Version: 25.5.0-trunk.147 (nightly)
• Kernel: 6.6.75-current-sunxi64

Configuration:

/boot/armbianEnv.txt:

overlay_prefix=sun50i-h618 overlays=i2s param_i2s=on

Problem:

• No sound output via MAX98357A.
• aplay -l returns "no soundcards found".
• dmesg | grep i2s shows no output, indicating the I2S driver is not loaded.
• Missing I2S overlay: Checked /boot/dtb/allwinner/overlay/ — no sun50i-h618-i2s.dtbo (only I2C overlays are present).
• Loaded sound modules: Only snd_soc_hdmi_codec (HDMI audio).

Steps Taken:

1. Verified physical wiring (BCLK/LRC/DIN, 5V/GND).
2. Updated to the latest nightly build (25.5.0-trunk.147).
3. Added overlays=i2s, param_i2s=on to /boot/armbianEnv.txt.
4. Tried manual driver load: modprobe sun8i-i2s (no effect).

Questions:

1. Is I2S support for Allwinner H618 available in kernel 6.6.75?
2. Are there plans to add sun50i-h618-i2s.dtbo in future releases?
3. Is there a workaround to enable I2S on H618 (e.g., custom DTB)?
4. Would upgrading to kernel 6.7+ resolve this?

Diagnostics:

uname -a:

Linux orangepizero2w 6.6.75-current-sunxi64 #1 SMP Sat Feb 1 17:37:57 UTC 2025 aarch64 GNU/Linux

cat /etc/armbian-release:

VERSION=25.5.0-trunk.147 BRANCH=current BOARD=orangepizero2w

dmesg | grep -i i2s: No output.

Request:
Any guidance or patches to enable I2S on H618 would be greatly appreciated. Thank you!

I have an orange pi zero 3 and am trying to ssh into this board. Ive written all three minimal files to different 32gb sd cards. After I write the drive I add a blank ssh file and a wpa_supplicante.conf file with my wifi info on it. I install the os with balanaetecher or Rufus(I've tried so many things. I find my IP when I try to ssh doesn't work) but I can ping the zero. I've tried windows 8.1, and 11 plus Linux mint same thing. 

Could someone please help me? This probably should take 20 minutes but I've been at it for 2.5 days

docker: Error response from daemon: error gathering device information while adding custom device "/dev/video0": no such file or directory

I have no webcam attached and I am not planning to use it for now, Can I disable this check?
 

Hi All

First post here.

Have been using Rpi Zero 2W for a couple of years in various installations and other then speed been happy with it.

So got an Orange Pi Zero 2 W in an attempt to use it as a plug in replacement for the Rpi.

Installed Armbian and other than a booting issue, it all works.

The first obstacle is the i2c, it is obvious that is nowhere near as easy as a Rpi to set up.

I have read many posts and get more confused as the days go on.

So, the question:

Is there a step by step instruction on how to enable I2C.

I am connecting 2 x ADS1115 A2D converters, one at &H48 and the 2nd at &H49.

When I use i2cdetect -l 

i2c-0     i2c     DesignWare HDMI

i2c-1     i2c     mv64xxx_i2c   Adapter

i2c-2     i2c              ditto

When I use i2cdetect -y 0

&h30 and &h50  show up

When I use i2cdetect -y 1

I get UU on &h36

In software, I can do a

fd = i2c_open("/dev/i2c-0")    or use i2c-1

rc = i2cselect (fd,&h48,0)

BUT, I cannot write or read to the device.(obviously because it does not exist according to i2cdetect )

My  armbianEnv.txt has

overlays=i2c3          changed from i2c0 after reading some posts.

dtparam i2c_arm=on

In armbian-config /system/kernel/booto001/ I have ticked i2c0-pi   and for 2 and 3 as well.

So after all that I have no idea how to proceed.

Regards

EDIT: kern.log has repeated entries as follows:

mv64xxx_i2c 5002000 Error applying settings reverse things back

Although H3 soc supports lpae (Large Physical Address Extension), but kernel has CONFIG_ARM_LPAE flag not set and so we can't use more than 3GB of memory (1GB is reserved for kernel).

(Processors that implement the ARMv7-A Large Physical Address Extension (LPAE), expand the range of accessible physical addresses from 4GB (232 bytes) to 1024GB (240 bytes) a terabyte, by translating 32-bit virtual memory addresses into 40-bit physical memory addresses.)

After looking around I found that there isn't any armbian release where this flag is enabled, but other distros have this correctly enabled by default,

debian https://wiki.debian.org/DebianKernel/ARMMP

openwrt

I also wonder if used build options are generic or did they make use of CPU extensions. H3 also supports VFPv4 or VFPv4-D32
for H3 example:  -march=armv7ve -mtune=cortex-a7 -mfloat-abi=hard -mfpu=neon-vfpv4

my output from
cat /proc/cpuinfo
 

orangepi-PC
    processor       : 3
    model name      : ARMv7 Processor rev 5 (v7l)
    BogoMIPS        : 65.14
    Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
    CPU implementer : 0x41
    CPU architecture: 7
    CPU variant     : 0x0
    CPU part        : 0xc07
    CPU revision    : 5

Anyway I thought I would have ago at creating an image, I suppose given the age of the board issues are to be expected. I have had some success in fixes some of the issues encountered despite being relatively new to Armbian and Linux in general. After learning how to create patches, firstly I managed to get UART2 which was originally conflicting with the PMU as they shared the same assigned interrupt number of 3. From what I can tell this different to the normal PMU which I find that the power chip is normally referred to as there also appears to be some internal component within the A10 also called the 'PMU' . This seems to be something to do with core monitor as the A20 chip features 2 of these 'PMU's, one for each core. Looking at the user manual suggest that this should be 49. Now this has been patched I can use UART2 without getting an error although it is exposed as ttyS1 for some reason that I have yet to figure out.

The second patch I made was to get HDMI output working which I was able to do by using the Cubieboard as a point of reference as they share similar hardware. I found this out by initially using images targeted at the Cubieboard as they appear to be a lot more recent and provide HDMI out so I knew that copying the sections other would. Additionally I found  a way to get it working on my main 4K monitor after coming across a post which suggested lowering the size of the CMA buffer from the default size of 128mb to 64mb.

Now again the main problem I face is when I try to shutdown, this time it relates to a kernel panic:

[ 2508.547646] WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.h:41 i2c_transfer+                                                                             0x93/0xbc
[ 2508.561239] No atomic I2C transfer handler for 'i2c-1'
[ 2508.571971] Modules linked in: cfg80211 btusb btintel btrtl btbcm bluetooth a                                                                             xp20x_adc sun4i_gpadc_iio industrialio lima gpu_sched r8188eu(C) sun4i_ts ecdh_g                                                                             eneric rfkill ecc joydev input_leds sunxi_cedrus(C) v4l2_mem2mem videobuf2_dma_c                                                                             ontig videobuf2_memops videobuf2_v4l2 videobuf2_common zram evdev uio_pdrv_genir                                                                             q display_connector uio cpufreq_dt nfsd auth_rpcgss sch_fq_codel nfs_acl lockd g                                                                             race sunrpc ip_tables x_tables autofs4 pinctrl_axp209 sun4i_gpadc sunxi phy_gene                                                                             ric gpio_keys icplus(E)
[ 2508.635429] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G         C  E     5                                                                             .15.32-sunxi #trunk
[ 2508.651044] Hardware name: Allwinner sun4i/sun5i Families
[ 2508.663328] [<c010cea9>] (unwind_backtrace) from [<c01095b9>] (show_stack+0x1                                                                             1/0x14)
[ 2508.678114] [<c01095b9>] (show_stack) from [<c09cc035>] (dump_stack_lvl+0x2b/                                                                             0x34)
[ 2508.692774] [<c09cc035>] (dump_stack_lvl) from [<c011b5a9>] (__warn+0xad/0xc0                                                                             )
[ 2508.707135] [<c011b5a9>] (__warn) from [<c09c5c23>] (warn_slowpath_fmt+0x5f/0                                                                             x7c)
[ 2508.721785] [<c09c5c23>] (warn_slowpath_fmt) from [<c0795a5f>] (i2c_transfer+                                                                             0x93/0xbc)
[ 2508.736949] [<c0795a5f>] (i2c_transfer) from [<c0795ac3>] (i2c_transfer_buffe                                                                             r_flags+0x3b/0x50)
[ 2508.752981] [<c0795ac3>] (i2c_transfer_buffer_flags) from [<c0697577>] (regma                                                                             p_i2c_write+0x13/0x24)
[ 2508.769489] [<c0697577>] (regmap_i2c_write) from [<c0694023>] (_regmap_raw_wr                                                                             ite_impl+0x48b/0x560)
[ 2508.786008] [<c0694023>] (_regmap_raw_write_impl) from [<c0694139>] (_regmap_                                                                             bus_raw_write+0x41/0x5c)
[ 2508.802806] [<c0694139>] (_regmap_bus_raw_write) from [<c06939b1>] (_regmap_w                                                                             rite+0x35/0xc8)
[ 2508.818874] [<c06939b1>] (_regmap_write) from [<c06948b5>] (regmap_write+0x29                                                                             /0x3c)
[ 2508.834263] [<c06948b5>] (regmap_write) from [<c069e723>] (axp20x_power_off+0                                                                             x23/0x30)
[ 2508.850053] [<c069e723>] (axp20x_power_off) from [<c0137ded>] (__do_sys_reboo                                                                             t+0xf5/0x16c)
[ 2508.866244] [<c0137ded>] (__do_sys_reboot) from [<c0100061>] (ret_fast_syscal                                                                             l+0x1/0x52)
[ 2508.882357] Exception stack(0xc154dfa8 to 0xc154dff0)
[ 2508.895490] dfa0:                   4321fedc bef4aaa8 fee1dead 28121969 4321f                                                                             edc 00000000
[ 2508.911883] dfc0: 4321fedc bef4aaa8 bef4aaa4 00000058 bef4aaa8 bef4aaa4 fffff                                                                             000 bef4aaac
[ 2508.928357] dfe0: 00000058 bef4aa1c b6eb81b5 b6e367e6
[ 2508.941715] ---[ end trace 8381275b8efb7dea ]---
[ 2510.584023] i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 2511.128016] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00                                                                             000000
[ 2511.175494] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G        WC  E     5                                                                             .15.32-sunxi #trunk
[ 2511.192848] Hardware name: Allwinner sun4i/sun5i Families
[ 2511.206836] [<c010cea9>] (unwind_backtrace) from [<c01095b9>] (show_stack+0x1                                                                             1/0x14)
[ 2511.223311] [<c01095b9>] (show_stack) from [<c09cc035>] (dump_stack_lvl+0x2b/                                                                             0x34)
[ 2511.239614] [<c09cc035>] (dump_stack_lvl) from [<c09c5a4d>] (panic+0xc1/0x238                                                                             )
[ 2511.255555] [<c09c5a4d>] (panic) from [<c011fd5d>] (complete_and_exit+0x1/0x1                                                                             8)
[ 2511.271612] [<c011fd5d>] (complete_and_exit) from [<fee1dead>] (0xfee1dead)
[ 2511.287376] ---[ end Kernel panic - not syncing: Attempted to kill init! exit                                                                             code=0x00000000 ]---

I have seen 1 or 2 other post which appear to be a similar issue.

Aside from that SPI does not work, but I gather this is currently a more general issue due to changes in the way the SPIDEV works. it's strange, I can enable the overlay and specify the bus and it shows up under /dev as expected but it does not appear to be sending any date when try to interface with LCD screen. I did a loopback test and it return all zero as if the pins where disconnected. The last version I found it correctly worked on was a Cubieboard image with kernel 5.10. I did come across one post which suggested a possible fix although I'm not sure if this has been implemented yet.

I know this probably a bit of a length first post but thanks for taking the time to read and I look forward to hear suggestions of where to start looking next as I know I still have a lot to learn.

Here are the logs:

http://ix.io/46XA

cheers

Ryzer

Moreover, the blocking for certain selected devices doesn't work either. In my case, the blocking is: HDMI Audio... in the file: /etc/modprobe.d/blacklist.conf

blacklist sun9i_hdmi_audio
blacklist snd_soc_simple_card

Are these changes related to the detection/blocking, etc., of block devices in Linux?

./compile.sh BOARD=nanopineo BRANCH=current RELEASE=noble BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=xz

However, if I add the CPU governance variables, such as this:

./compile.sh BOARD=nanopineo BRANCH=current RELEASE=noble BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=xz CPUMIN=81600 CPUMAX=96000

...the build fails with the following error text:

./compile.sh mike
[🚸] This script requires root privileges; Docker is unavailable [ trying to use sudo ]
[🌿] Applying cmdline param [ 'PREFER_DOCKER': '(unset)' --> 'no' early ]
[🌱] Skip     cmdline param [ 'ARMBIAN_RELAUNCHED': already set to 'yes' early ]
[🌿] Applying cmdline param [ 'SET_OWNER_TO_UID': '(unset)' --> '1000' early ]
[🌱] Skip     cmdline param [ 'PREFER_DOCKER': already set to 'no' after config 'config-mike.conf' ]
[🌱] Skip     cmdline param [ 'ARMBIAN_RELAUNCHED': already set to 'yes' after config 'config-mike.conf' ]
[🌱] Skip     cmdline param [ 'SET_OWNER_TO_UID': already set to '1000' after config 'config-mike.conf' ]
[🌱] Starting single build process [ nanopineo ]
[🌱] Checking [ basic host setup ]
[🌱] Build host OS release [ noble ]
[🌱] Build host architecture [ arm64 ]
[🌱] Sourcing board configuration [ /home/mike/build/config/boards/nanopineo.csc ]
[✅] change-tracking: after sourcing board file config/boards/nanopineo.csc [ BOARDFAMILY='sun8i' ]
[✅] change-tracking: after sourcing board file config/boards/nanopineo.csc [ BOOTCONFIG='nanopi_neo_defconfig' ]
[✅] change-tracking: after defaulting LINUXFAMILY to BOARDFAMILY [ LINUXFAMILY='sun8i' ]
[🌱] Starting main configuration
[🌱] Using REVISION from [ main VERSION file: '25.11.0-trunk' ]
[🌿] Enabling extension [ armbian-config ]
[🌱] Sourcing family configuration [ /home/mike/build/config/sources/families/sun8i.conf ]
[🌿] Enabling extension [ sunxi-tools ]
[💥] Error 1 occurred in main shell [ at /home/mike/build/lib/functions/configuration/main-config.sh:552
   source_family_config_and_arch() --> lib/functions/configuration/main-config.sh:552
          do_main_configuration() --> lib/functions/configuration/main-config.sh:291
                do_with_logging() --> lib/functions/logging/section-logging.sh:81
    do_with_conditional_logging() --> lib/functions/logging/section-logging.sh:111
    prep_conf_main_build_single() --> lib/functions/main/config-prepare.sh:29
         cli_standard_build_run() --> lib/functions/cli/cli-build.sh:22
        armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136
                 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:208
                           main() --> compile.sh:50
 ]

I looked at the source_family_config_and_arch() function source, and the file that gets passed into it (/home/mike/build/config/sources/families/sun8i.conf) exists on my box, but something is causing the failure at line 552 anyway.  What's strange is that the exact same LINUXFAMILY / BOARDFAMILY is configured in my working command (with all the params passed on the cmdline), like this:

🌱] Sourcing board configuration [ /home/mike/build/config/boards/nanopineo.csc ]
[✅] change-tracking: after sourcing board file config/boards/nanopineo.csc [ BOARDFAMILY='sun8i' ]
[✅] change-tracking: after sourcing board file config/boards/nanopineo.csc [ BOOTCONFIG='nanopi_neo_defconfig' ]
[✅] change-tracking: after defaulting LINUXFAMILY to BOARDFAMILY [ LINUXFAMILY='sun8i' ]
[🌱] Starting main configuration
[🌱] Using REVISION from [ main VERSION file: '25.11.0-trunk' ]
[🌿] Enabling extension [ armbian-config ]
[🌱] Sourcing family configuration [ /home/mike/build/config/sources/families/sun8i.conf ]
[🌿] Enabling extension [ sunxi-tools ]
[✅] change-tracking: after sourcing family config [ KERNEL_MAJOR_MINOR='6.12' ]
[✅] change-tracking: after sourcing family config [ LINUXFAMILY='sunxi'  # (was: 'sun8i') ]
[✅] change-tracking: after sourcing family config [ KERNELPATCHDIR='archive/sunxi-6.12' ]
[✅] change-tracking: after sourcing family config [ BOOTBRANCH='tag:v2024.01' ]
[✅] change-tracking: after sourcing family config [ BOOTPATCHDIR='u-boot-sunxi' ]
[✅] change-tracking: after sourcing family config [ NETWORKING_STACK='network-manager' ]

The build/config/sources/families/sun8i.conf file, referenced in the log output, contains a proper CPUMIN and CPUMAX, so I'm not sure why specifying them on the command line blows up the build.

# SPDX-License-Identifier: GPL-2.0
#
# Copyright (c) 2013-2023 Igor Pecovnik, igor@armbian.com
#
# This file is a part of the Armbian Build Framework
# https://github.com/armbian/build/
#
# shellcheck source=config/sources/families/include/sunxi_common.inc
source "${BASH_SOURCE%/*}/include/sunxi_common.inc"

if [[ -z ${OVERLAY_PREFIX} ]]; then
        OVERLAY_PREFIX='sun8i-h3'
fi

[[ -z $CPUMIN ]] && CPUMIN=480000
[[ -z $CPUMAX ]] && CPUMAX=1400000

Any thoughts on what I'm doing wrong?

On NanoPi Duo2 I'm trying to use the builtin video hw processor.

ffmpeg already works with -hwaccel v4l2request but throws errors:

Press [q] to stop, [?] for help
[h264 @ 0x11645f0] Using V4L2 media driver cedrus (6.12.35) for S264
[V4L2RequestContext @ 0xae5f0db0] Failed to create buffer of type 1: Cannot allocate memory (12)
[h264 @ 0x11645f0] Failed setup for format drm_prime: hwaccel initialisation returned error.

dmesg

[ 8906.864389] cma: __cma_alloc: reserved: alloc failed, req-size: 3038 pages, ret: -12
[ 8906.872255] cma: number of available pages: 42@86+128@384+34@3550+34@6622+34@9694+34@12766+34@15838+34@18910+34@21982+1570@25054=> 1978 free of 26624 total pages
[ 8906.886783] cedrus 1c0e000.video-codec: dma alloc of size 12443648 failed
root@nanopiduo2:~#

I already did play around with armbianEnv tweaking extraargs cma  but no success.

I found a link talking about VPU device tree dma limitations https://git.sec.in.tum.de/croemheld/linux/-/blob/v5.1-rc5/Documentation/devicetree/bindings/media/cedrus.txt

Zitat

Device-tree bindings for the VPU found in Allwinner SoCs, referred to as the Video Engine (VE) in Allwinner literature. The VPU can only access the first 256 MiB of DRAM, that are DMA-mapped starting from the DRAM base. This requires specific memory allocation and handling.

I already decompiled the DT and verified there are is no such "reserved-memory"  section.   Is this the root cause?

Maybe someone can provide some hints or ideas confirming that I'm on the right track? If yes I'd give it a try adjusting the DT.

     T.

For long (long) time I did not update my nano pi duo image, recently I changed microSD card and wanted start fresh with latest image.

I have tried latest debian image and also tried building image for the BOARD target as `nanopiduo`, but in in both cases my board is stuck at ...
 

U-Boot SPL 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Va723-Bb703-R448a (Mar 09 2025 - 03:54:39 +0000)
DRAM: 128 MiB                           
Trying to boot from MMC1                
ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19
                                        
                                        
U-Boot 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Va723-Bb703-R448a (Mar 09 2025 - 03:54:39 +0000) Allwinner Technology
                                        
CPU:   Allwinner H3 (SUN8I 1680)        
Model: FriendlyARM NanoPi DUO           
DRAM:  128 MiB
Core:  57 devices, 16 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20ca0
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial,usbkbd
Out:   serial
Err:   serial
Net:   No ethernet found.
starting USB...
No working controllers found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
5475 bytes read in 6 ms (890.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
182 bytes read in 6 ms (29.3 KiB/s)
Load fdt: /boot/dtb/sun8i-h2-plus-nanopi-duo.dtb
8431400 bytes read in 357 ms (22.5 MiB/s)
11476944 bytes read in 484 ms (22.6 MiB/s)
Found mainline kernel configuration
36294 bytes read in 20 ms (1.7 MiB/s)
Working FDT set to 43000000
504 bytes read in 17 ms (28.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo
504 bytes read in 17 ms (28.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo
4185 bytes read in 17 ms (240.2 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
Kernel image @ 0x42000000 [ 0x000000 - 0xaf1fd0 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8431336 Bytes = 8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
Working FDT set to 43000000
   Loading Ramdisk to 497f5000, end 49fff6e8 ... OK
   Loading Device Tree to 42ee4000, end 42f55fff ... OK
Working FDT set to 42ee4000

Starting kernel ...

[    2.314576] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    2.322869] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.43-current-sunxi #1
[    2.330722] Hardware name: Allwinner sun8i Family
[    2.335438] Call trace: 
[    2.335467]  unwind_backtrace from show_stack+0x11/0x14
[    2.343286]  show_stack from dump_stack_lvl+0x37/0x42
[    2.348377]  dump_stack_lvl from panic+0xc9/0x278
[    2.353116]  panic from mount_root_generic+0x171/0x1f4
[    2.358299]  mount_root_generic from prepare_namespace+0x161/0x1ae
[    2.364527]  prepare_namespace from kernel_init_freeable+0x1f9/0x20a
[    2.370928]  kernel_init_freeable from kernel_init+0x21/0x100
[    2.376720]  kernel_init from ret_from_fork+0x11/0x1c
[    2.381808] Exception stack(0xc8821fb0 to 0xc8821ff8)
[    2.386881] 1fa0:                                     00000000 00000000 00000000 00000000
[    2.395074] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.403265] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[    2.410060] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

In older images, CPU was detected as `Allwinner H2+`, however now it's detecting as H3.

I have tried couple other SD cards, with same error.

What config I can try to get my `nanopi duo` working?

offtopic: I tried images available from  friendlyelec drive, which are getting stuck at "Starting kernel".

I currently want to reduce the transmission power of the NanoPi Neo Air.

This means that I simply want to be able to set the Wifi transmission power in 10% steps, for example.

What I have already tried:

1. Instructions according to Wiki: OpenWrt image is not flashed. No access via browser.
   But it doesn't matter: max. transmission power is used in AP mode. 
   Setting as in the Wiki image "TransmitPower:auto" probably does not apply here anyway.
2. Network Manager TUI via "sudo nmtui" has no such settings.
3. Adjust the NVRAM files in "/lib/firmware/brcm" or "/lib/firmware/ap6212" step by step. 
   All changes are saved in the txt file but not written to the host driver.
   The tests do not recognise any changes. No matter how I adjust the values. (Many different attempts)
4. Firmware patch ("brcmfmac43430a1-sdio.bin") with HxD: The place where "Maxp2ga0" is set is found & edited in binary file. --> 07 60 3F 60 6D 61 78 70 32 67 61 30 = `?`maxp2ga0
   Bytes for maxp2ga0: 07 60Bytes for maxp2ga1: 3F 60
   3F 60 → 0x603F or 0x3F60 → similar, typically 0x60 = 96 → 20 dBm (Both antenna values have been set)
   Unfortunately, this change is not loaded into the host driver on the chip either...
   Continue working on existing "locked" firmware with Seemoo Lab? (unlikely)
5. Throttling Tx-Power via command "sudo iw dev wlan0 set txpower fixed 1500"
   Change is displayed under "iwconfig wlan0", but it is either overwritten directly or not taken into account at all.
   No change is noticeable in the tests, no matter how low the value is set.
6. Other firmware & NVRAM tested: Wifi does not start at all (IP rebount reconnect try xx) or the W-Lan is not visible.
   Maybe you can start here again and find a working firmware that is not "locked"? Which software to use?
    

I test with Putty via the wifi connection. I use the following command:

for i in $(seq 1 30); do iw dev wlan0 station dump | awk '/signal/ {print $2}'; sleep 1; done \
| awk '{x[NR]=$1; s+=$1} END{ if (NR>0) {mean=s/NR; for(i=1;i<=NR;i++) v+=(x[i]-mean)^2; sd=sqrt(v/NR); print 'N="NR, "mean="mean, "sd="sd} }'

This measures the connection strength in dBm every second, 30 times, and only outputs the mean value.

I always have the same 3 measurement positions with the exact same antenna alignment. 

(In a corridor: 3m, 12m, 25m)

Interesting stuff:

• sudo iw phy phy0 info
• dmesg | tail -n 50 | grep -i brcmfmac
• File paths: /lib/firmware/brcm & /lib/firmware/AP6212
• CC code (country) is not set by default: "sudo iw reg get" & "sudo iw reg set DE"

Are there any other approaches or have I overlooked something?
Thank you very much for your help!

Board Orangepi 3LTS with bookworm minimal
 

Also as a matter of wondering - why there are two zram devices: one of 1/2 of RAM (as usual) and another of quite small 50MB only, what is it for?

root@heaven:~# fdisk -l
<redacted>

Disk /dev/mmcblk2boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk2boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

<redacted>

Disk /dev/zram0: 987,53 MiB, 1035497472 bytes, 252807 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

I am trying to get the cedar_ve device working for OPIZ2W. 

I am currently running this image: Orangepizero2w_1.0.4_ubuntu_noble_server_linux6.1.31

My uname -a:

Linux orangepizero2w 6.1.31-sun50iw9 #1.0.4 SMP Wed Oct 9 13:39:53 CST 2024 aarch64 aarch64 aarch64 GNU/Linux

To do this I am trying to follow these steps:

1. Modify a dts for OPIZ2W to include cedar_ve.

2. Donwloan cedrus driver and build it.

3. Compile modified ffmpeg with x264cedrus support

Have anyone tried this? I have only found builds for recent kernel for the H3 CPU, none for the H618.

I am looking for a DTS that supports cedar_ve for Orange Pi Zero 2W or any other things that can point me in the right direction.

I am using Nanopi Neo board and I need RS485 driver to control DE pin automatically.

I have prepared DTS Overlay file:

/dts-v1/;
/plugin/;

/ {
    compatible = "allwinner,sun8i-h3";

    fragment@0 {
        target = <&uart1>;
        __overlay__ {
            status = "okay";
            pinctrl-names = "default";
            pinctrl-0 = <&uart1_pins &uart1_de_pin>;
            rs485-rts-gpios = <&gpio6 8 0>;  /* PG8 active-low */
            linux,rs485-enabled-at-boot-time;
            rs485-rts-delay = <0 300>;
        };
    };

    fragment@1 {
        target = <&uart2>;
        __overlay__ {
            status = "okay";
            pinctrl-names = "default";
            pinctrl-0 = <&uart2_pins &uart2_de_pin>;
            rs485-rts-gpios = <&gpio0 2 0>;  /* PA2 active-low */
            linux,rs485-enabled-at-boot-time;
            rs485-rts-delay = <0 300>;
        };
    };
};
 

I produced dtbo file from dts one with the command: dtc -@ -I dts -O dtb -o rs485.dtbo rs485.dts

I copied this rs485.dtbo file to /boot/dtb/overlay. Also I added rs485 string to ArmbianEnv.txt and rebooted. 

But only TX works, RX doesn't. 

What should  I do else to make it work?

I see the device tree file here:

```

/boot/dtb/allwinner/overlay/sun50i-h616-uart5-ph.dtbo

```

But after adding `overlays=uart5-ph` to `armbianEnv.txt` and rebooting, I'm not getting any new serial device created.  Any idea what I need to do?

First of all, thank You for your work.
On a project we are using Nanopi Neo Air boards with an Allwinner h3 processor and a 8GB eMMC flashed with an Armbian OS:

$ uname -a
Linux <DEVICE_HOSTNAME> 6.6.75-legacy-sunxi #1 SMP Sat Feb  1 17:37:57 UTC 2025 armv7l GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

Recently we have been getting increasing reports of the boards being stuck on boot, on message 'Starting Kernel ...' (checked from logs available on COM port).

Although this behavior is highly undesirable, since the eMMC is visible in device tree when booting from an SD-Card, it can be recovered by running command

$ fsck /dev/mmcblk2p1

In order to reproduce this behavior we have set up a continuous power cycle test where, booting from eMMC:

• Device is powered on
• After 70 seconds (enough time for the system to boot), power supply is interrupted
• Device remains powered off for 10 seconds

This would account for around 1000 power cycles per day and we were able to get the device bricked in the range of 68 to 5500 power cycles.

We then repeated the test but by booting from an SD-Card and were not able to reproduce the issue, having reached power cycle counts of 34381.

Does anyone have a clue on why the eMMC displays this behavior, or is someone able to provide some guidance on what we could do/check to try to prevent this from happening (or making the eMMC more resilient to power cycles)?

How can I get the image of Opi plus 2 ?? Plz let me know:(