Search the Community

I know I need to find out which drivers to use... I just don't know where to start, I know I've seen some people having success with these displays - ili9488, and a couple others - I just don't know if this fits one of those overlays or not. (nothing I've tried so far has worked). Any help identifying and pointing in the right direction, I would greatly appreciate. Trying to get this to work on my Orange Pi Zero 3 4gb. (uploading images has failed.... so I guess I'll link them?) https://imgur.com/a/NORYCj7

Hello, I have a new LCD which I believe is an ili4988 (although the vendor says ili9486 and st7796) 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: 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: 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)

has anyone ordered and/or played with this 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 suddenly have a need to test Linux 6.11 or greater, because there's a needed improvement in the panel-mipi-dbi-spi driver (thread keyword ili9488) User "The Going" has kindly advised me to try his Armbian branch with Linux 6.12, so I am here sharing results as I test it with my Orange Pi Zero 3. Initial instructions: https://forum.armbian.com/topic/35635-armbian-242-is-broken-on-orange-pi-pc2/#findComment-207980 At first try, I decided to NOT follow this step: armbian/build> egrep '^-' patch/kernel/archive/sunxi-6.12/series.conf (finds all the excluded patches) Well, I continued. Choosing Linux Edge, shallow option, Bookworm minimal, there were zero problems: no patching errors and no compilation errors. At the end of the 4 hour compilation, I tested the resulting image in my Orange Pi Zero 3... and it booted fine. Not working at this moment: wifi (#iw dev returns nothing) spi1 (failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND when I use a dts overlay that works in Linux 6.7) usb (lsusb only shows the 2 root hubs, but not my usb devices) when I decompile sun50i-h618-orangepi-zero3.dtb there is no references to spi1 or hdmi (maybe more) Working: serial console ethernet other things not tested Next, I am going execute armbian/build> egrep '^-' patch/kernel/archive/sunxi-6.12/series.conf and find specific patches that maybe will improve my hardware situation. Result of that egrep search command, with patches I will try first, one by one, in bold

I have this screen here ili9486 : https://pt.aliexpress.com/item/32805704334.html?src=google&pdp_npi=4%40dis!BRL!43.31!38.51!!!!!%40!12000019014148570!ppc!!!&src=google&albch=shopping&acnt=768-202-3196&isdl=y&slnk=&plac=&mtctp=&albbt=Google_7_shopping&aff_platform=google&aff_short_key=UneMJZVf&gclsrc=aw.ds&&albagn=888888&&ds_e_adid=&ds_e_matchtype=&ds_e_device=c&ds_e_network=x&ds_e_product_group_id=&ds_e_product_id=pt32805704334&ds_e_product_merchant_id=107713925&ds_e_product_country=BR&ds_e_product_language=pt&ds_e_product_channel=online&ds_e_product_store_id=&ds_url_v=2&albcp=21106536414&albag=&isSmbAutoCall=false&needSmbHouyi=false&gad_source=1&gclid=EAIaIQobChMI14GV5um3iQMVK2BIAB0KwQPmEAYYASABEgJc4fD_BwE 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.

I'm looking to build an ntp server using the OrangePi Zero 3 and I noticed there is no pps-gpio device tree overlay for the h616 chipset only the h5 chipset. Has anyone created a custom dt overlay? Thanks in advance.

Dear All, I get frequent and random disconnection from orangepizero3 onboard wifi with armibian community (self-built) both trunk and 24.02 current kernel, 6.6.26 and 6.6.28 message is always [21738.338021] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [21848.116072] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [21915.426734] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection sm_state (5), status: (2)! [21915.426817] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection Vodafone-CSC failed status code:1! [21919.477424] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [[21738.338021] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [21848.116072] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it [21915.426734] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection sm_state (5), status: (2)! [21915.426817] unisoc_wifi unisoc_wifi sta0: sprdwl_report_connection Vodafone-CSC failed status code:1! [21919.477424] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it Full logs available at armbianmonitor -u Any help/hint/solution deeply appreciated

I am experimenting with a cheap ILI9341 screen and mi OrangePi Zero LTS 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?

Hi there, recently I bought an Orange Pi Zero3 with 1GB RAM. I want to connect a 20*4 character LCD display(https://www.tinytronics.nl/en/displays/lcd/lcd-display-20*4-characters-with-white-text-and-blue-backlight-with-i2c-backpack) to it. I have previously used this display with Arduino UNO, which worked great. Now I want to use it with the Orange Pi Zero3 (Ubuntu 24.04). I have no experience with the Orange Pi or single-board computers in general. I followed some tutorials, but I couldn't make it work. I did this: Wiring: I2C Backpack Orange Pi Zero3 VCC Pin 2 GND Pin 6 SCL Pin 5 SDA Pin 3 Terminal: sudo apt-get install -y python-smbus i2c-tools user@orangepizero3:~$ sudo i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- user@orangepizero3:~$ sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 50: 50 -- -- -- 54 -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- It seems like the display cannot be found. How can I fix this?

I had an OrangePi Zero LTS and set up an access point using the following commands: % sudo apt install dnsmasq-base -y % sudo sed -i "s/#MulticastDNS=no/MulticastDNS=yes/g" /etc/systemd/resolved.conf % sudo nmcli connection add type wifi ifname wlan0 con-name access_point autoconnect yes ssid <ssid> % sudo nmcli connection modify access_point 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared % sudo nmcli connection modify access_point connection.mdns 2 % sudo nmcli connection modify access_point wifi-sec.key-mgmt wpa-psk % sudo nmcli connection modify access_point wifi-sec.psk "<password>" % sudo nmcli connection up access_point % sudo hostnamectl set-hostname <hostname> This worked fine, I can connect and ssh using `hostname.local` etc etc I recently just got a OrangePi Zero 3 and tried the minimal OS, I did the commands above along with: sudo apt install network-manager -y The access point does seem to appear and I can see it from phones and laptops etc but I can't connect to it. What is the best way to debug the issue? This is what it shows from the following commands: $ nmcli device DEVICE TYPE STATE CONNECTION wlan0 wifi connected access_point lo loopback connected (externally) lo p2p-dev-wlan0 wifi-p2p disconnected -- end0 ethernet unmanaged -- $ nmcli connection NAME UUID TYPE DEVICE access_point d7a42b9e-63bd-4e76-9457-018cbd43d712 wifi wlan0 lo a0764323-619d-4bd9-b029-fa8da5ed24c4 loopback lo Any help is appreciated! I should mention that the OrangePI Zero LTS OS wasn't the minimal one it was the server one so I'm not sure if I'm just missing something in the minimal OS for OrangePi Zero 3. I get these debug logs if I try and connect to the access point: Sep 29 13:41:35 <hostname> NetworkManager[846]: <debug> [1727613695.7400] ndisc-lndp[0xaaaae75732f0,"wlan0"]: processing libndp events Sep 29 13:41:35 <hostname> NetworkManager[846]: <debug> [1727613695.7409] platform: (end0) signal: address 6 changed: fd00::97ff:fe9b:cbc0/64 lft 7200sec pref 3600sec lifetime 1394-1394[3600,7200] dev 2 flags mngtmpaddr,noprefixroute src kernel Sep 29 13:41:35 <hostname> NetworkManager[846]: <debug> [1727613695.7412] platform: (end0) signal: address 6 changed: fd00::5bc2:4133:f0ea:931d/64 lft 7200sec pref 3600sec lifetime 1394-1394[3600,7200] dev 2 flags secondary src kernel Sep 29 13:41:35 <hostname> NetworkManager[846]: <debug> [1727613695.7441] manager: (end0): assume: don't assume because device is not managed Sep 29 13:41:40 <hostname> NetworkManager[846]: <debug> [1727613700.3462] ndisc-lndp[0xaaaae75732f0,"wlan0"]: processing libndp events Sep 29 13:41:40 <hostname> NetworkManager[846]: <debug> [1727613700.3471] platform: (end0) signal: address 6 changed: fd00::97ff:fe9b:cbc0/64 lft 7200sec pref 3600sec lifetime 1398-1398[3600,7200] dev 2 flags mngtmpaddr,noprefixroute src kernel Sep 29 13:41:40 <hostname> NetworkManager[846]: <debug> [1727613700.3474] platform: (end0) signal: address 6 changed: fd00::5bc2:4133:f0ea:931d/64 lft 7200sec pref 3600sec lifetime 1398-1398[3600,7200] dev 2 flags secondary src kernel Sep 29 13:41:40 <hostname> NetworkManager[846]: <debug> [1727613700.3499] manager: (end0): assume: don't assume because device is not managed Sep 29 13:41:44 <hostname> NetworkManager[846]: <debug> [1727613704.8566] ndisc-lndp[0xaaaae75732f0,"wlan0"]: processing libndp events Sep 29 13:41:44 <hostname> NetworkManager[846]: <debug> [1727613704.8575] platform: (end0) signal: address 6 changed: fd00::97ff:fe9b:cbc0/64 lft 7200sec pref 3600sec lifetime 1403-1403[3600,7200] dev 2 flags mngtmpaddr,noprefixroute src kernel Sep 29 13:41:44 <hostname> NetworkManager[846]: <debug> [1727613704.8578] platform: (end0) signal: address 6 changed: fd00::5bc2:4133:f0ea:931d/64 lft 7200sec pref 3600sec lifetime 1403-1403[3600,7200] dev 2 flags secondary src kernel Sep 29 13:41:44 <hostname> NetworkManager[846]: <debug> [1727613704.8603] manager: (end0): assume: don't assume because device is not managed

hi can somebody fix repostiory install list error for chromium as chrome-commen and chromedriver wont install problem: chromium/noble 9:126.0.6478.182-1~deb12u1+narmbian1 arm64 web browser installs with version therefore chromium-common and chromium-driver,will not install because its looking for dependency chromium 126.0.6478.182-1~deb12u1+n1 Without the ":9" i presume he following packages have unmet dependencies: chromium-driver : Depends: chromium (= 126.0.6478.182-1~deb12u1+n) E: Unable to correct problems, you have held broken packages. please can somebody fix

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.

I’m running Armbian debian minimal image on my Orange Pi Zero 3, using the onboard WiFi (wlan0) with the unisoc_wifi driver. The WiFi consistently drops with logs like these: [ 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 🙃

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

@ag123, @c0rnelius, and anyone else that has interest in sound on these devices. I have been able to put together a patch that enables audio for H161/H618 devices. So far only audio on HDMI works. Analog audio is still generating an error on startup. The patches were taken from a git repository by warpme: https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.6/files , and probably came from the Zunlong SDK. A lot of the code was written by Allwinner. @pixdrift generated a version of the patches for Armbian and I continued to work on them. I have a git repository if anyone would like to test, particularly on boards other than orangpizero3, on which I have tested. repository: https://github.com/stephengraf/armbian_build_sg.git There is another repository mentioned in the Armbian Forum: https://github.com/NickAlilovic/build If anyone has interest and skills to debug the analog audio, the dmesg errors are: [ 7.125509] ahub_dam-snd-soc-dummy-dai: substream ahub_dam-snd-soc-dummy-dai has no playback, no capture [ 7.125539] sunxi-snd-mach soc:ahub_dam_mach: ASoC: can't create pcm ahub_dam-snd-soc-dummy-dai :-22 [ 7.125780] sunxi-snd-mach: probe of soc:ahub_dam_mach failed with error -22

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