Search the Community

I want to use GPIO Pi16 on the 13 pin expansion header of the board. This pin is claimed by the kernel for the ethernet MAC. According to the SOC Datasheet this pin has the option to provide a 25 MHz clock signal for the ethernet MAC, which is not relevant for this board. Thanks to this Topic https://forum.armbian.com/topic/30274-armbian-build-how-to-modify-dts-file-to-change-gpio-mapping/ and the device tree source files https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner/sun50i-h618-orangepi-zero3.dts, https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero.dtsi and https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner/sun50i-h616.dtsi i managed to create an overlay named sun50i-h616-fix-emac-pin.dts to release the GPIO pin from the ethernet MAC/kernel. /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target=<&pio>; __overlay__{ ext_rgmii_pins: rgmii-pins { pins = "PI0", "PI1", "PI2", "PI3", "PI4", "PI5", "PI7", "PI8", "PI9", "PI10", "PI11", "PI12", "PI13", "PI14", "PI15"; function = "emac0"; drive-strength = <40>; }; }; }; fragment@1 { target = <&emac0>; __overlay__ { pinctrl-0 = <&ext_rgmii_pins>; }; }; }; sudo armbian-add-overlay /boot/sun50i-h616-fix-emac-pin.dts Even though I don't really understand how to write device tree overlays, surprisingly I could compile and apply the overlay to the kernel with the command above and it did its job. The GPIO is available now and the ethernet connection still works. Can someone who actually understands this subject review my code and include this change in the right form at the right spot?

Which is the correct overlay to specify for libcamera support for the Arducam IMX219? I am assuming this would go into /boot/armbianEnv.txt ? The packages libcamera0.3 libcamera-tools libcamera-v4l2 installed properly, however, all examples on the net apply to PIs and not the OrangePiZero... Thanks in advance.

Hello I am using Orange Pi Zero 3 and I installed the latest armbian version on it I have the picture through HDMI, but there is no sound!!! Isn't one of the main uses of these boards multimedia?! Why shouldn't this board have sound?!!! I have checked all the settings. Thank you. If there is a way, please help me My armbian version: Armbian_community_24.5.0-trunk.667_Orangepizero3_jammy_current_6.6.31_gnome_desktop

I believe that ethernet adaptor is not working properly because there's only one led blinking and its unable to receive ip address. I have tried to configure it with yaml files and manually with networkd and with static ip. I also tried to run dhcp on that interface and it received random ip outside of my network. Had no luck with network-manager either, it threw an error "ip configuration could not be reserved" With desktop image ethernet worked with no problem. So maybe there's a driver issue?

Hi Managed to get x11 to boot in latest armbian desktop Ubuntu gnome build x11vnc runs when manually running it fine but how many tutorials I have followed online it refuses to start as a service (auto) always gets bad access error when trying to get xauthority I guess ,even when I point it to the .xauthority files with -auth and used -auth guess tried all theses Tutorial 1 Tutorial 2 Tutorial 3 plus videos on YouTube has anyone got vnc to run on orange pi zero 3 Ubuntu noble gnome desktop From here at start up on x11? thanks

Hi, Running on Armbian_community 24.8.0-trunk.529 Bookworm with Linux 6.6.43-current-sunxi64 onthe orangepi zero3 And need to use the GPIO pins with python, not an expert here but have tried a few recommandations with no luck. Can anyone suggest method that works with the above OS/build please? Thanks! Rob.

Hi - is there anywhere a working guide to create a Wifi Access Point with this board ? I have tried the official debian ISO from orange pi and doing so with create_ap is very easy. I'd like to use armbian instead but using the "Minimal / IOT image with Armbian Linux v6.6" (bookworm) all I get is hell: I installed network-manager and armbian-config then used the later to try the hotspot configuration but then (several freezes and reboots after) it complains that "Unit hostapd.service is masked" and when I solve that, then dnsmasq fails and I see no helpful error message. I even tried connecting to a wifi network first before trying hotspot as I saw somewhere for an older board version that this could help but it does not help and also the system becomes way unstable while connected to wifi. I also tried using armbian-config to go back to a stable version but then the system freezes and and I can not ssh in. HELP!? P.S. All my connections to the box are being done through ssh & ethernet.

Hi, I am having problems connecting my orange pi zero 3 to my TV via hdmi: No matter what I try the TV reports "no signal". Before I came to armbian I have tried the vendor-supplied debian and arch images and could not get hdmi output on any of them, so it might be that my micro-hdmi adapter is faulty or that the hdmi-port on the device itself is faulty, but over the weekend I cannot replace any hardware so I thought I try here to see if anyone has an idea on what to try. The image I am currently running is Armbian_community_24.5.0-trunk.58_Orangepizero3_jammy_current_6.6.17_gnome_desktop.img. When I log into the device I can see that an Xorg process is running. xrandr produces this output: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 HDMI-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.32 56.25 848x480 60.00 640x480 59.94 When I disconnect the hdmi-cable xrandr reports "HDMI-1 disconnected", so at least a little bit of hdmi-functionality is there... The device is connected via an micro-hdmi adapter and a hdmi-cable, I have checked the hdmi-cable but I do not have another adapter nor do I have another micro-hdmi device, so unfortunately I cannot test the adapter. What I have noticed is that (at least sometimes) the device seems to lose network-connectivity (ethernet) when the hdmi-cable is connected - and regains connectivity as soon as the hdmi-cable is disconnected, so there seems to be some conflict between hdmi and ethernet. I do not know where the display modes come from that xrandr displays as the TV is a 4k model that supports a lot more modes. So my question is: Is there anything I could try to get hdmi working or at least to narrow down the problem?

I'm trying to setup a GPS-based time server on an Orange PI Zero 3, running Armbian 24.8.0-trunk.495, kernel 6.6.43-current-sunxi64. I have the exact same hardware setup working fine on a RaspberryPI 4b, running RPI OS / Debian 11 (bullseye) , kernel 6.1.21-v8+ #1642. On the RPI4, gpsd recognises the (cheap chinese "M8N") GPS module as u-blox and keeps working in a stable way root@rpi4:~# gpsctl /dev/ttyS0 /dev/ttyS0 identified as a u-blox SW ROM CORE 3.01 (107888),HW 00080000 at 9600 baud. the /boot/config.txt has these two lines for the UART config enable_uart=1 init_uart_baud=9600 On the OPIZ3 I configured /boot/armbianEnv.txt for UART5; I didn't find any setting for the initial UART speed overlays=uart5-ph The resulting /dev/ttyS1 is mostly working but not really well. "gpsd --nowait --debug 1 --speed 9600 /dev/ttyS1" works, but it (usually) does not recognise the module as u-blox, and remains on the NMEA text protocol, meaning I can't use ubxtool. And it logs a constant stream of "bad checksum" and other errors, and disconnect/reconnect cycles, which aren't nice for the clock stability. root@orangepizero3-01:~# gpsctl /dev/ttyS1 /dev/ttyS1 identified as a NMEA0183 at 9600 baud. root@orangepizero3-01:~# journalctl -u gpsd ... Aug 12 18:57:49 orangepizero3-01.home gpsd[5223]: gpsd:WARN: bad checksum in NMEA packet; expected 23. Aug 12 18:57:49 orangepizero3-01.home gpsd[5223]: gpsd:WARN: NMEA0183: malformed GPGSV - fieldcount 19 % 4 != 0 ... Aug 12 18:57:53 orangepizero3-01.home gpsd[5223]: gpsd:WARN: bad checksum in NMEA packet; expected 2C. Aug 12 18:57:53 orangepizero3-01.home gpsd[5223]: gpsd:WARN: device read of /dev/ttyS1 returned error or packet sniffer failed sync (flags {ERROR}) Aug 12 18:57:53 orangepizero3-01.home gpsd_hook[10889]: start args: /dev/ttyS1 DEACTIVATE Aug 12 18:57:53 orangepizero3-01.home gpsd_hook[10893]: start args: /dev/ttyS1 ACTIVATE Aug 12 18:57:54 orangepizero3-01.home gpsd[5223]: gpsd:WARN: bad checksum in NMEA packet; expected 3C. ... Once in a while, seemingly randomly, restarting gpsd seems "lucky" and it does recognise the module as u-blox and for a while it's a bit more stable, using the binary UBX protocol, to fail again after some hours. So, I'm wondering if it's an issue with the OPIZ3 GPIO/UART, or with the Armbian kernel, or what. Has anybody seen the same or similar issue? Or if you have some suggestion on how to debug this (if possible without an oscilloscope), it would be much welcome. Cheers, Sergio

Hi, I am trying to get a led matrix to work via the SPI interface but cannot get it to work. I have enabled the interface and have an spi-device under /dev and there is a spi-module loaded. I have tried to connect MOSI and MISO to run spidev-test and everything seems to be fine but when I connect the led-matrix simply nothing happens. I can run the example-scripts from the luma-matrix library without getting an error - but there is simply nothing appearing on the matrix - however it does light up when I touch it on the backside... i have tried to use different values for param_spidev_spi_bus and param_spidev_spi_cs in armbianenv.txt but to no avail... Does anybody have an idea what I could try? many thanks!

Hi there, I'm trying to set up AP + STA on wlan0 using Orange Pi Zero 2W and Orange Pi Zero 3 with the Armbian image. I managed to do this on a Raspberry Pi Zero W. I encountered a problem: when creating a virtual access point, the process hangs and cannot be killed. Any attempt to view the logs after starting the process also leads to a hang, and only a reboot helps. This problem does not occur on the Raspberry Pi. I use the command: sudo iw phy phy0 interface add ap0 type __ap. For testing, I added an external USB Wi-Fi module to the Orange Pi Zero 3 and managed to create a virtual access point on it without any problems or hangs, so this problem only occurs on wlan0. The issue occurs on both Orange Pi Zero 2W and Orange Pi Zero 3, and they behave the same. Also, attempting to delete wlan0 via 'sudo iw dev wlan0 del' causes the device to hang. Has anyone encountered this situation? Is there a solution to this problem, and is it possible to make AP and STA on one interface on OPi Zero 2W/3 ? Here is the output of 'iw list': Wiphy phy1 //wlan0 Orange Pi [...] Supported interface modes: * IBSS * managed * AP * P2P-client * P2P-GO * P2P-device software interface modes (can always be added): valid interface combinations: * #{ managed, AP } <= 1, #{ P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1, total <= 3, #channels <= 2 [...] Wiphy phy0 //USB Wi-Fi adapter [...] Supported interface modes: * managed * AP * AP/VLAN * monitor software interface modes (can always be added): * AP/VLAN * monitor software interface modes (can always be added): * AP/VLAN * monitor interface combinations are not supported [...] Here is the output of 'iw list' on the Raspberry Pi: Wiphy phy0 [...] Supported interface modes: * IBSS * managed * AP * P2P-client * P2P-GO * P2P-device software interface modes (can always be added): valid interface combinations: * #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1, total <= 3, #channels <= 2 * #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1, total <= 4, #channels <= 1 [...] As far as I understand, based on the "valid interface combinations", wlan0 on the Orange Pi cannot support both managed and AP simultaneously. Could this be the reason? For the Wi-Fi adapter, "interface combinations are not supported". Thanks in advance!

My friend, when he next inserted the microSD card into the Orange Pi Zero 2 slot, the microSD slot fell off the board 😞 It is not possible to solder it because some of the tracks on the board have become detached so Is it possible to run the ArmBian system on OZPi v2 with a copy of the microSD system on a USB Pendrive? I am looking for a method to run OZIPI v2 without microSD on the system via USB disk

I posted this in the Orange Pi Zero 3 topic earlier but got not response. **How would one go about to get the default u-boot config that is flashed to spi to have netretry turned on?** > If anyone is interested, here is a guide to netboot (pxe) the orange pi zero 3: https://raymii.org/s/tutorials/Netboot_PXE_Armbian_on_an_Orange_Pi_Zero_3_from_SPI_with_NFS_root_filesystem.html

Hi! So the problem is when I configure wifi hotspot using hostapd, isc-dhcp-server, and ifupdown, I'm able to start the AP, connect to it, and ping. However, the moment any device connects to the AP the serial console gets spammed with this message around once a second: protocol 0000 is buggy, dev wlan0 This happens on the unofficial Armbian build (from the Armbian OrangePi Zero3 page), DietPi, and the official OrangePi Debian build. The wireless band doesn't matter. Kernel version: 6.1.31-sun50iw9. I tried to set up the AP with NetworkManager, but couldn't manage to connect to it. Probably DHCP issues that I couldn't resolve. I haven't run the AP for a prolonged period, only like 1hour. So I'm not sure if this has any effect on the performance and stability. Could somebody suggest if this is something to worry about or just a harmless warning?

I used python script with Orange pi zero 3 (Armbian_community_24.8.0-trunk.6_Orangepizero3_bookworm_current_6.6.31_minimal.img) Observation: 1) /dev/ttyS1 is actually Serial 2 as per pin diagram as per Orange Pi Zero 3 - Armbian web page 2) /dev/ttyS2 is actually Serial 5 as per pin diagram as per Orange Pi Zero 3 - Armbian web page 3) even if I set rtscts=True in crateing object ser in above script, there is no output on rts or cts pin. I am looking forward to have RTS pin remain high during transmission to easily integrate ic for RS485 communication. I was glad that Amrbian for Orange Pi Zero 3 has out of the box RTS CTS pin support which otherwise is a complicated matter for me. Please guide how to make the serial port work along with RTS pin to remain high during transmission of data. Regards

My environment is ManjaroLinux, x86 with docker installed on the system, I want to build the system for orangepizero3 via Arbian/build, I chose the CSC version, but there is an error during the build process, here is the log file:log How should I this problem? Thanks.

Hi, what are currently the options of controlling 433Mhz sender/receiver devices from an orange Pi zero 3? Currently the gpios are no longer exposed via sysfs but you could re-enable that feature by compiling a new kernel with the proper configuration. Then wiringpi would work again and you could use 433Utils. But what would be the options without compiling a new kernel? What 433Mhz library exists that uses the new way of controlling the gpios? I am a bit confused about the current state of affairs, please enlighten me...

Just installed armbian on an Orange Pi Zero 3. Right of the bat, had it apt updated and tried to install armbian-config. The package is unavailable, though. me@orangepizero3:~$ apt search armbian-config Sorting... Done Full Text Search... Done me@orangepizero3:~$ apt policy armbian-config armbian-config: Installed: (none) Candidate: (none) Version table: me@orangepizero3:~$ cat /etc/apt/sources.list.d/armbian.list deb [signed-by=/usr/share/keyrings/armbian.gpg] http://beta.armbian.com bookworm main bookworm-utils bookworm-desktop Having checked the beta.armbian.com, I don't see the `main` pool. Mirrors do have it, though. Very odd!

I have question. OZPI v3 has support for hardware DS18B20 thermal sensor via w1-gpio ? In armbian-config when we got to the “system” section and select “Hardware” is not existing w1-gpio or OZPI v3 has not support for w1-gpio hardware ? Does not work because there is no device tree file (in the /boot/dtb/allwinner/) and we need to create it ??? like for OZPI v2 ?: 1. Create text file "sun50i-h616-w1-gpio.dts" /dts-v1/; / { compatible = "xunlong,orangepi-zero2\0allwinner,sun50i-h616"; fragment@0 { target = <0xffffffff>; __overlay__ { w1_pins { pins = "PC9"; function = "gpio_in"; phandle = <0x01>; }; }; }; fragment@1 { target-path = [2f 00]; __overlay__ { onewire@0 { compatible = "w1-gpio"; pinctrl-names = "default"; pinctrl-0 = <0x01>; gpios = <0xffffffff 0x02 0x06 0x00>; status = "okay"; }; }; }; __symbols__ { w1_pins = "/fragment@0/__overlay__/w1_pins"; }; __fixups__ { pio = "/fragment@0:target:0\0/fragment@1/__overlay__/onewire@0:gpios:0"; }; __local_fixups__ { fragment@1 { __overlay__ { onewire@0 { pinctrl-0 = <0x00>; }; }; }; }; }; 2. After you need to compile it, with command "dtc -O dtb -o sun50i-h616-w1-gpio.dtbo sun50i-h616-w1-gpio.dts" 3. Copy it too /boot/dtb/allwinner/overlay/

Hello everyone ! I'm facing a hard issue that I still cannot solve. On my Raspberry, on Raspberry Os, to be able to use Rustdesk (https://github.com/rustdesk/rustdesk, an open source Teamviewer ) I needed to add some tweaks to the /boot/config.txt file: hdmi_force_hotplug=1 (See doc) hdmi_group=2 (See doc) Now, I'm trying to replicate these behaviours on Armbian for Opi zero 3 (but it could probably work for all Allwinner cpus if a solution is found) When looking on the Armbian documentation for Sunxi, I've found this (See doc) : For example to always use the hdmi connector, even if no cable is inserted, using edid info when available and otherwise initalizing it at 1024x768@60Hz, use: setenv video-mode sunxi:1024x768-24@60,monitor=dvi,hpd=0,edid=0 That really looks like what I want to achieve, but when adding this line to the /boot/boot.cmd file, re-building it using: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr and after rebooting, I still can't connect to my distant Opi. Am I missing something? Did someone has faced something similar? Thanks for any help !

Hi. I would like to know if someone can help me. I was successfully able to compile armbian 6.6.30 with all of @Stephen Graf patches for my orangepi zero 3 having Full Audio working even on HDMI. see below for reference. Now I have a 2nd project. It runs the h616 with 2GB DDR3 RAM with AXP313. Can someone help me with a patch for the AXP313 on h616. Or alternatively, could my h618 orangepi zero 3 setup work if I patch it to run with DDR3? If so where can I find such a patch. Thanks in advance.

For information purposes, that the 1.3-inch SH1106 OLED connected to I2C on OZPI v3 works very well OLED connected to PIN 3 of SDA and PIN 5 of SCK and in armbian-config in HARDWARE set to [*] i2c3-ph Using tools i2cdetect -y shows that the OLED is at address 0x3c All Python code with the adafruit library works fine

Hello! I have Orange Pi Zero 3 I got Armbian image from this link - https://github.com/armbian/community/releases/download/24.5.0-trunk.474/Armbian_community_24.5.0-trunk.474_Orangepizero3_bookworm_current_6.6.28_minimal.img.xz Of course I've made apt update and apt upgrade And now I'm tying to install zigbee2mqtt using this guide - https://www.zigbee2mqtt.io/guide/installation/01_linux.html So, I can't list USB devices root@orangepizero3:~# ls -l /dev/ttyACM0 ls: cannot access '/dev/ttyACM0': No such file or directory root@orangepizero3:~# ls -l /dev/serial/by-id ls: cannot access '/dev/serial/by-id': No such file or directory I have tryed some tips I've found but no result, only I can see my device in this- root@orangepizero3:~# dmesg -w . . . [ 1958.349181] usb 4-1: new full-speed USB device number 2 using ohci-platform [ 1958.585233] usb 4-1: New USB device found, idVendor=1a86, idProduct=55d4, bcdDevice= 4.42 [ 1958.585266] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1958.585286] usb 4-1: Product: SONOFF Zigbee 3.0 USB Dongle Plus V2 . . . So, do someone have idea how to fix it and get /dev/serial/by-id**** usb addres for config need? Thanks)

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

Is this the right place to post this type of content? I have a board for Orange Pi. Since I'm usually using windows, it's very inconvenient to burn u-boot. I'll post it to github later if you guys are interested! （Machine translated, English not so good, don't know if the description is apt or not.）