Search the Community

hello armbian developers recently i have tried to built my own kernel from linus' kernel tree(5.18.1). the build config i use cames from armbian 22.05 bullseye(5.15.43-sunxi) /boot/config-5.15.43-sunxi ,without any changes. the kernel was ok to boot,so i plan to add xr819 support for it，but after days of work，it seems not as easy as i thought. the driver ive tried is from here(https://github.com/karabek/xradio)，but it cant detect chip's hardware revision: [ 13.036884] xradio: XR819 device discovered [ 13.038054] xradio_wlan mmc1:0001:1: no mac address provided, using random [ 13.064445] xradio ERR: FWIO: Unknown hardware: -1. [ 13.064547] xradio ERR: BH: bh thread exiting [ 13.064893] xradio PM-DEV: xradio_pm_release but the stock armbian image works well(5.15.43-sunxi). so i have added a printk to make config reg value visible: ret = xradio_reg_read_32(hw_priv, HIF_CONFIG_REG_ID, &val32); printk(KERN_WARNING "xradio_wlan: read config reg value: 0x%x\n",val32); if (ret < 0) { xr_printk(XRADIO_DBG_WARN, "FWIO: can't read config register, err=%d.\n", ret); return ret; } on 5.15.43: [ 11.737046] xradio: XR819 device discovered [ 11.737725] xradio_wlan mmc1:0001:1: no mac address provided, using random [ 11.739304] xradio_wlan: read config reg value: 0x4005600 [ 11.920160] xradio: hardware vers. 7.9 [ 11.920199] xradio: firmware vers. 8 (WSM), build 5258, api 1060, cap 0x0003 [ 11.920217] xradio: Config USE_EXTENSIONS on 5.18.1: [ 13.036884] xradio: XR819 device discovered [ 13.038054] xradio_wlan mmc1:0001:1: no mac address provided, using random [ 13.039290] xradio_wlan: read config reg value: 0x4 [ 13.064445] xradio ERR: FWIO: Unknown hardware: -1. [ 13.064547] xradio ERR: BH: bh thread exiting [ 13.064893] xradio PM-DEV: xradio_pm_release it seems xradio_reg_read_32 will call xradio_reg_read , and it calls __xradio_read ... last call sdio_memcpy_fromio , so maybe upstream have changed some implementation of sdio?

How install linux-tools for USBIP >usbip WARNING: usbip not found for kernel 5.15.43 You may need to install the following packages for this specific kernel: linux-tools-5.15.43-sunxi linux-cloud-tools-5.15.43-sunxi You may also want to install one of the following packages to keep up to date: linux-tools-sunxi linux-cloud-tools-sunxi >apt install linux-tools-sunxi Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package linux-tools-sunxi I tried linux-cloud-tools-sunxi, linux-tools-5.15.43-sunxi, linux-cloud-tools-5.15.43-sunxi BUT package not found. Try switch on other kernel, from 5.15.43 to 5.10 - package not found. How install or compile linux-tools for USBIP?

Hi all. I am new in both OrangePi hardware and Armbian OS. I bought Orange Pi Zero 512 MB. I aim to develop a stand-alone device using this board. I am too confused with my readings. Do you have any idea for the following run rules together on the same board? (1) When I connect via serial (USB), it runs bash. It will ask user name and password. I can write a program, compile it, update the OS, and change settings. <This part is okay.> I want to use a GUI for this part. (2) When I supply 5-Volt power via extension pins, it runs stand-alone. It will not ask for a username and a password. It starts with an application developed in either Python or C programming languages. *** How can I combine these two in a single board? Is it necassary to change my board? Which OS should I use (I preferred Armbian)? Is it necessary to build a new image, or may I continue using the ready-built image? I will be appreciate if you share an answer with me. Thanks a lot.

Dear all, I occasionally have a full /var/log at startup on various boards, probably because the logs are not rotated /vaccuumd at boot (we had a thread about this in the old opi1 forum). The rotating /vaccuum is currently done every 15 minutes, so I figured why not do it directly at boot as well? For this purpose I updated /etc/cron.d/armbian-truncate-logs with an extra @reboot line: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */15 * * * * root /usr/lib/armbian/armbian-truncate-logs @reboot root /usr/lib/armbian/armbian-truncate-logs I rebooted several times, and didn't get a full /var/log anymore. All subsequent problems like failing networking when filesystem full also vanished;-) Kind regards, Dennis

I'm trying to add a USB device using configfs to the zero but I don't want to break the pre existing serial connection on USB0 so I want to put it on USB3, the overlay has this as usbhost3 so before I spend hours designing a daughter board and trying to fix something that's never going to work the question is can I use this interface for a device.

Hi everyone, Since i update to kernel 5.15.25-sunxi , every reboot the mac of wlan0 changed the mac address and router giv him another ip. i will be very happy to solve this issue , Thanks! Note: I tried to re-download the ARMBIAN from the official website, and burned a new SD. This experience did not help. First boot: Second boot:

I have an orange pi zero that I'm going to use as a pi hole. When installing pi hole, I received a "Error: Unable to update package cache. Please try "sudo apt update"." I did just that and received another error stating Err:1 https://ports.ubuntu.com focal InRelease Could not connect to ports.ubuntu.com:443 (2620:2d:4000:1::19). - connect (111: Connection refused) Could not connect to ports.ubuntu.com:443 (185.125.190.39). - connect (111: Connection refused) Could not connect to ports.ubuntu.com:443 (2620:2d:4000:1::16). - connect (111: Connection refused) Could not connect to ports.ubuntu.com:443 (185.125.190.36). - connect (111: Connection refused) Err:2 https://ports.ubuntu.com focal-security InRelease Unable to connect to ports.ubuntu.com:https: Err:3 https://ports.ubuntu.com focal-updates InRelease Unable to connect to ports.ubuntu.com:https: Err:4 https://ports.ubuntu.com focal-backports InRelease Unable to connect to ports.ubuntu.com:https: Ign:5 https://apt.armbian.com focal InRelease Err:6 https://apt.armbian.com focal Release Redirection from https to 'http://armbian.chi.auroradev.org/apt/dists/focal/Release' is forbidden [IP: 2605:7900:20::5 443] Reading package lists... Done E: The repository 'https://apt.armbian.com focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. I tried changing the mirror url in /etc/apt/sources.list.d/armbian.list as @Werner suggested, but I still get the same error even when using the mirror. This is basically what's in the armbian.list deb http://armbian.tnahosting.net/dl/ focal main focal-utils focal-desktop Any clues as to what's going on??

I have installed Armbian_22.02.1_Orangepizero_bullseye_current_5.15.25.img.xz. I started my OrangePi 0. I chose ZSH (not BASH) I did Update and Upgrade. When trying to execute the command (as a normal user) build-essential I get: orangepizero:~:% build-essential zsh: command not found: build-essential orangepizero:~:% sudo apt-get install build-essential Reading package lists... Done Building dependency tree... Done Reading state information... Done build-essential is already the newest version (12.9). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. orangepizero:~:% build-essential zsh: command not found: build-essential How can I successfully run build-essential?

I have Armbian 22.02 Bullseye installed on my Orange Pi zero. The wifi connection worked fine at first, but after a few reboots the device 'wlan0' seems to no longer exist. In the Armbian-config settings the entry wifi is no longer present and also in ifconfig wlan0 is no longer displayed. I have now reflushed the system 3 times and always have the same problem.

Using Orange Pi zero Revision 1.5 loaded with Armbian Buster 21.08 ArmbianMonitor Logs: http://ix.io/3UXu The board is reporting very low temperatures, with htop and when I ssh on the login banner. Temperatures range from 3 or 4 C but also seen -3404C screenshot https://imgur.com/a/SCLVMYl Previously with Armbian 19.11 and kernel 5.4 temperatures were reported normal 33 or 37C I dont overclock and run my SoC from 480 to 960MHz (keeps current and power down). Screenshot of Armbian 19.11 kernel 5.4 and kernel 5.10.4.sunxi temperatures were normal (30 - 37C) Screenshot below: https://imgur.com/a/cFoXG8H Not sure what has changed in kernel 5.10.60, will it be safe to download to kernel 5.4.88 or will it break my installation? Everything else is working fine. Thanks in advance

Hello... after last update, I'm got this issue .. MAC address for wifi changed after reboot ... (and dhcp reservation does not work .. of course) It happen on all 5.15.x 5.16.x kernels .. Armbian 22.02.1 with Linux 5.16.11-sunxi - has problem Armbian 22.02.1 with Linux 5.15.25-sunxi - has problem downgrade to 5.10 works Armbian 22.02.1 with Linux 5.10.60-sunxi - Is OK .. Have anybody same problem ..?? is any way, how can I solve this issue ..? thanks ... for answer(s)...

Hello. First, I have an LTS board that provides only 3.05 on the 3.3 pins. Is it normal ? Anyway, in case this was the issue, I have built a new voltage regulator, and now supply the DHT22 and pullup resistor with 3.60V My issue is simple: when plugged on normal 1W bus, the DHT22 kills the bus, and makes other devices non working. I have moved all other devices on a new bus, leaving the DHT on a bus I know works fine. Some people mentionned the DHT is not compliant with official 1W libraries, and can not be recognised with normal timings, so, special libs are required. I have removed param_w1_pin=PA06 for the hysical pin 7, and installed new software. I have a very bad experience with python, and I have never been able to make any python lib/project, on any board of any brand; I always get some error at some point. The only non python lib/app for DHT22 I have found is https://github.com/pilkch/climbatize but after heavily patching it (to fix various bugs), the app still seems unable to communicate with the probe. I have checked more than 12 times the sensor is connected to the so called pin 7 (PA06), pin 2 in WiringPi, and changed the physical sensor (paid for a new item). Who can help reading this probe ? I am just running out of ideas. The only issue that bothers me is that I am not physically 100% certain that Climbatize manipulates pin7. I have entered the loop that manipulates some pin, but at some point it's calling wiringPi, and my multimeter always shows 3.6V on the pin; I don't have a scope to check the pin goes down, and applying a LED on a pulledup pin will not produce a perceptible OFF time. I would need to solder an inverted gate to transform the logic, but even then, the light pulses may be too short for my eyes. I really dont think 3.60V could burn the oPi board; and 3.05 could be a huge reason for the DHT22 to refuse to work. I could plug a lab regulated supply, but I think it would be overkill. I do have spare/new/unused boards; but all my LTS boards deliver 3.05. (yes I have some boards left in 2022; I had bought *MANY* spare ones years ago).

We had a custom script that would perform kernel updates. As part of the update, we would look for this package and would make sure it was install. We are erroring out as this package is no longer installed. I am currently using 5.10.34-sunxi and was trying to update to 5.10.60-sunxi. The error is : E: Can't find a source to download version '21.02.3' of 'linux-buster-root-current-orangepizero:armhf' This was working as of a couple of months ago. (Looking at the armbian-config scripts, we are essentially following the same logic. We imagine this script would have the same issues. We tried running armbian-config, but did not have the switch option).

Hi, I'm trying to set a different GPIO state at boot (output 0) on a Orange pi Zero and I couldn't find any solution to this. Can someone tell me if this is possible and if yes how to do it ? Thanks !

My third Orange Pi Zero came last week, yesterday I plugged it and had heating issues... So I started reading, learning and testing.... Setup: OPiZ-1: 256 MB, no SPI flash - Has extension board plugged - for comparison OPiZ-2: 512 MB, with SPI flash OPiZ-3: 256 MB, with SPI flash (new one with problem) Test conditions: All with (newish) Sandisk Ultra 16 GB Class 10 All new formatted (SD Formatter) and burned/validated (Etcher v1.0.0) with Armbian_5.25_Orangepizero_Debian_jessie_default_3.4.113.img All on my desk - side by side, ambient temperature 25.0-25.1 C (20 cm from boards, no air flow) No case, no passive/active cooling Power supply 7 port 5V 36W total, 2.4A per port (wait, wait, I tried others, separated etc - I'm testing them with USB V/A/W tester - 5.2-5.3V / 0.260-0.350 A) First install done, rebooted, apt-get update && apt-get upgrade'd, rebooted, tested

Hello, i update my OrangePiZero OS from Linux 5.10.43-sunxi to Linux 5.10.60-sunxi my screen fbtft spi lcd stop working , the screen is black. If there is a solution to this issue I would love to get help, thanks! here my configuration (work on 5.10.43). (Armbianmonitor link of 5.10.43 on top) (Armbianmonitor link of 5.10.60 Attached as a file ) fbtft.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; }; }; fragment@1 { target = <&pio>; __overlay__ { spi1_cs_pins: spi1_cs_pins { pins = "PA13"; function = "gpio_out"; }; opiz_display_pins: opiz_display_pins { pins = "PA7", "PA2", "PA6"; function = "gpio_out"; }; }; }; fragment@2 { target = <&spi1>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; pinctrl-0=<&spi1_pins &spi1_cs_pins>; cs-gpios=<&pio 0 13 1>; opizdisplay: opiz-display@0{ compatible = "ilitek,ili9341"; reg = <0>; pinctrl-names = "default"; pinctrl-0 = <&opiz_display_pins>; spi-max-frequency = <32000000>; rotate = <270>; bgr; fps = <30>; buswidth = <8>; reset-gpios = <&pio 0 7 1>; dc-gpios = <&pio 0 2 0>; led-gpios= <&pio 0 6 0>; debug = <5>; status="okay"; }; }; }; __overrides__ { speed = <&opizdisplay>,"spi-max-frequency:0"; rotate = <&opizdisplay>,"rotate:0"; fps = <&opizdisplay>,"fps:0"; debug = <&opizdisplay>,"debug:0"; }; }; /boot/armbianEnv.txt is: verbosity=1 bootlogo=true console=serial overlay_prefix=sun8i-h3 overlays=analog-codec i2c0 uart1 uart2 user_overlays=fbtft mcp7940 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u 1.txt

(Finally this forum lets me enter a new topic. It's failing most of the time, making it really hard to solve my actual problem if the infrastructure also fails.) I'm using an Orange Pi Zero board and try to make it talk to a radio module via SPI. The whole thing already works on a Raspberry Pi so the module and cabling is correct. But the module doesn't respond to requests on the Orange Pi. Since this doesn't do anything, I searched for issues like this and along the way found an SPI loopback tool. I tried it and it returned all zeros. The tool readme suggests that the MOSI and MISO pins are not connected, but they are. I checked and resoldered those pins and connected both with a jumper. The hardware is 100% correct. It must be the software that doesn't understand the SPI interface here. The same tool shows a correct echo on the RasPi. I also found another topic here about the Allwinnder H6 chip where a patch in Armbian was necessary to resolve the same issue. I couldn't respond there due to a permanent forum outage and then lost the link. So I believe that the same error is in the Orange Pi Zero image. I didn't understand what was changed there, something deep within the system. The armbianmonitor -u command failed with an internal server error response, so I uploaded the logs elsewhere. The Google form in front of this bug report recommended paste.debian.net but that service is unsuitable because its length limit of 150 kB is not sufficient.

Hi, I'm using an Orange PI ZERO HC2 + and usb (mt7601u) wifi dongle to create a hotspot. The configuration is as follow <HOTSPOT>WLAN0 [ Orange PI ZERO HC2+] WLAN1 <connected to my box> At startup when hostapd is launched to create the hotspot i get the following output . See below <HOSTAPD ERROR>. My hostapd.conf is below. Wlan0 use for xradio_wlan as physical driver Wlan1 use for mt7601 as physical drive I did some testing. I have the exact same config with a pi3. And have no problem. I tested the hostapd provided with the orange pi on the pi3, it works no problem. On the orange PI, If i do it the other way round : wlan1 to deal with hotspot, wlan0 to connect to my box. <HOTSPOT>WLAN1 [ Orange PIZERO ] WLAN0 <connected to my box> I get the same error. So its does not depend on the underneath driver ( wradio_wlan, or mt7601u). So it looks like something fishy with the driver nl80211 declared in the hostapd.conf. Any help would be appreciated. Note: i guess its easy to reproduce, use my hostapd.conf below: hostapd myhostapd.conf # HOSTAPD ERROR -------------------------------------------------------------------------------------- hostapd -Kd myhostapd.conf random: getrandom() support available Configuration file: nfx-hostapd.conf nl80211: Supported cipher 00-0f-ac:1 nl80211: Supported cipher 00-0f-ac:5 nl80211: Supported cipher 00-0f-ac:2 nl80211: Supported cipher 00-0f-ac:4 nl80211: Supported cipher 00-0f-ac:10 nl80211: Supported cipher 00-0f-ac:8 nl80211: Supported cipher 00-0f-ac:9 nl80211: Supported cipher 00-0f-ac:6 nl80211: Supported cipher 00-0f-ac:13 nl80211: Supported cipher 00-0f-ac:11 nl80211: Supported cipher 00-0f-ac:12 nl80211: Using driver-based off-channel TX nl80211: Driver-advertised extended capabilities (default) - hexdump(len=8): 00 00 00 00 00 00 00 40 nl80211: Driver-advertised extended capabilities mask (default) - hexdump(len=8): 00 00 00 00 00 00 00 40 nl80211: interface wlan0 in phy phy1 nl80211: Set mode ifindex 4 iftype 3 (AP) nl80211: Failed to set interface 4 to mode 3: -95 (Operation not supported) nl80211: Try mode change after setting interface down nl80211: Set mode ifindex 4 iftype 3 (AP) nl80211: Failed to set interface 4 to mode 3: -95 (Operation not supported) nl80211: Interface mode change to 3 from 0 failed nl80211: Could not configure driver mode nl80211: deinit ifname=wlan0 disabled_11b_rates=0 nl80211: Remove monitor interface: refcount=0 netlink: Operstate: ifindex=4 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP) nl80211: Set mode ifindex 4 iftype 2 (STATION) nl80211 driver initialization failed. hostapd_interface_deinit_free(0x1eb0020) hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1 hostapd_interface_deinit(0x1eb0020) wlan0: interface state UNINITIALIZED->DISABLED hostapd_bss_deinit: deinit bss wlan0 wlan0: AP-DISABLED hostapd_cleanup(hapd=0x1eb0d80 (wlan0)) wlan0: CTRL-EVENT-TERMINATING hostapd_free_hapd_data: Interface wlan0 wasn't started hostapd_interface_deinit_free: driver=(nil) drv_priv=(nil) -> hapd_deinit hostapd_interface_free(0x1eb0020) hostapd_interface_free: free hapd 0x1eb0d80 hostapd_cleanup_iface(0x1eb0020) hostapd_cleanup_iface_partial(0x1eb0020) hostapd_cleanup_iface: free iface=0x1eb0020 # --------myhostapd.conf interface=wlan0 driver=nl80211 #ht_capab= #driver=mt7601u #driver=mac80211 #driver=xradio_wlan ssid=CHEZLAUTRE hw_mode=g channel=6 ieee80211n=1 wmm_enabled=1 ht_capab=[HT40][SHORT-GI-20][DSSS_CCK-40] macaddr_acl=0 auth_algs=1 ignore_broadcast_ssid=0 wpa=2 wpa_key_mgmt=WPA-PSK wpa_passphrase=delautrecote rsn_pairwise=CCMP

I installed the pyA20 library for controlling GPIO, but I can't get the internal pullup resistor to work anymore. I managed to get it working before, but after playing around with other things, it stopped working. I have a very simple circuit going on, with just a light switch and I'm trying to read the light switch using the internal pull-up resistor. I managed to get it working for a few days, but that's it. I gave up and decided to solder on my own 10K pull-up resistor from the input pin to 3.3V. To my surprise, the results were the same, the input pin floated. Everything works fine with an Arduino. This is all very strange and I hope someone can help me. I'm running all the latest software and kernel.

I have found other treads that address "tv out not working" but none have been applicable. They point to files that are not on my system. It is an older orange pi zero. I have installed the latest armbian image. Here is the "lsb_release -a" return: Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal I am currently operating headless and the login splash screen says "Welcome to Arbian 21.02.3 Focal with Linux 5.10.21-sunxi" I am trying to use the 13 pin connector. Pin 2 = ground (shield) and Pin 9 = video signal (center conductor) I have found forum threads about enabling the tv out but ... My current installation does not have a /boot/script.bin file ... Other forum threads also refer to files that I do not have. One thread says: ("the OPZ will not use the tvout port, unless you add "tv" on the /etc/modules file") I DO have the /etc/modules file and I tried adding the letters "tv" on the second line of my /etc/modules file but still no output. Other threads talk about editing the fex file but I can't get the fex editor compliled and installed using their instructions. Can anyone offer some suggestions? Thanks in advance!

Hello there. I have problems with connecting device with 1-wire protocol. Device: DHT11 Temperature-Humidity Sensor - It is Arduino version with pullup on the board. Board: Orange Pi Zero LTS (H2+) System: Linux orangepizero 5.10.21-sunxi #21.02.3 SMP Mon Mar 8 00:28:04 UTC 2021 armv7l armv7l armv7l GNU/Linux Based on instructions im preformed some steps: 1) Through armbian-config im enabled w1-gpio 2) Installed gpio app to get info about ports: +-----+-----+----------+------+--Orange Pi Zero--+------+----------+-----+-----+ | H2+ | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | H2+ | +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+ | | | 3.3v | | | 1 || 2 | | | 5v | | | | 12 | 8 | SDA.0 | ALT3 | 0 | 3 || 4 | | | 5V | | | | 11 | 9 | SCL.0 | ALT3 | 0 | 5 || 6 | | | 0v | | | | 6 | 7 | GPIO.7 | ALT3 | 0 | 7 || 8 | 0 | ALT3 | TxD3 | 15 | 198 | | | | 0v | | | 9 || 10 | 0 | ALT3 | RxD3 | 16 | 199 | | 1 | 0 | RxD2 | ALT3 | 0 | 11 || 12 | 0 | ALT3 | GPIO.1 | 1 | 7 | | 0 | 2 | TxD2 | ALT3 | 0 | 13 || 14 | | | 0v | | | | 3 | 3 | CTS2 | ALT3 | 0 | 15 || 16 | 0 | ALT3 | GPIO.4 | 4 | 19 | | | | 3.3v | | | 17 || 18 | 0 | ALT3 | GPIO.5 | 5 | 18 | | 15 | 12 | MOSI | ALT3 | 0 | 19 || 20 | | | 0v | | | | 16 | 13 | MISO | ALT3 | 0 | 21 || 22 | 0 | ALT3 | RTS2 | 6 | 2 | | 14 | 14 | SCLK | ALT3 | 0 | 23 || 24 | 0 | ALT3 | CE0 | 10 | 13 | | | | 0v | | | 25 || 26 | 1 | IN | GPIO.11 | 11 | 10 | +-----+-----+----------+------+---+---LEDs---+---+------+----------+-----+-----+ | 17 | 30 | STAT-LED | OUT | 0 | 27 || 28 | | | PWR-LED | | | +-----+-----+----------+------+---+-----+----+---+------+----------+-----+-----+ | H2+ | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | H2+ | +-----+-----+----------+------+--Orange Pi Zero--+---+------+---------+-----+--+ 3) I have changed /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 w1-gpio rootdev=UUID=d522be3f-9ac0-489b-9d79-500c38e89c86 rootfstype=ext4 param_w1_pin=PA10 param_w1_pin_int_pullup=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u 4) Also changed CPU /etc/default/cpufrequtils ENABLE=true MIN_SPEED=1400000 MAX_SPEED=1400000 GOVERNOR=interactive As you can see, im using PA 10 port and i can see at "gpio readall" value of "V" sign, when im disconnecting wire from board - it is going to be zero, after reconnection it is again going to be 1. Thats showing thats im using correct port. Now im trying to analyze logs at dmesg, and i see this related information, in case loading WITH CONNECTED WIRE [ 12.182141] Driver for 1-wire Dallas network protocol. [ 12.199201] gpio-10 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file In case of DISCONNECTED WIRE LOG WILL BE: [ 12.182141] Driver for 1-wire Dallas network protocol. [ 12.199201] gpio-10 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 614.571146] w1_master_driver w1_bus_master1: w1_search: max_slave_count 64 reached, will continue next search. [ 661.463966] w1_master_driver w1_bus_master1: Attaching one wire slave 00.800000000000 crc 8c [ 661.474854] w1_master_driver w1_bus_master1: Family 0 for 00.800000000000.8c is not registered. [ 720.081030] w1_master_driver w1_bus_master1: Attaching one wire slave 00.400000000000 crc 46 [ 720.091987] w1_master_driver w1_bus_master1: Family 0 for 00.400000000000.46 is not registered. [ 766.913878] w1_master_driver w1_bus_master1: Attaching one wire slave 00.c00000000000 crc ca [ 766.924868] w1_master_driver w1_bus_master1: Family 0 for 00.c00000000000.ca is not registered. [ 837.355159] w1_master_driver w1_bus_master1: Attaching one wire slave 00.200000000000 crc 23 [ 837.366059] w1_master_driver w1_bus_master1: Family 0 for 00.200000000000.23 is not registered. [ 895.996491] w1_master_driver w1_bus_master1: Attaching one wire slave 00.a00000000000 crc af If will connect WIRE again in this case, messages stopping appear. There are no any success with experimenting on changing GPIO port or Device (i have multiple boards and devices) or pullup Core debugging: After getting all experiments unsuccessful im going and check linux core on driver level. There are function thats making search of connected devices: https://github.com/analogdevicesinc/linux/blob/master/drivers/w1/w1.c /** * w1_search() - Performs a ROM Search & registers any devices found. * @dev: The master device to search * @search_type: W1_SEARCH to search all devices, or W1_ALARM_SEARCH * to return only devices in the alarmed state * @cb: Function to call when a device is found * * The 1-wire search is a simple binary tree search. * For each bit of the address, we read two bits and write one bit. * The bit written will put to sleep all devies that don't match that bit. * When the two reads differ, the direction choice is obvious. * When both bits are 0, we must choose a path to take. * When we can scan all 64 bits without having to choose a path, we are done. * * See "Application note 187 1-wire search algorithm" at www.maxim-ic.com * */ void w1_search(struct w1_master *dev, u8 search_type, w1_slave_found_callback cb) On this function im seeing thats search going until dev->max_slave_count will be reached and if no devices found we will see: dev_info(&dev->dev, "%s: max_slave_count %d reached, ""will continue next search.\n", __func__,dev->max_slave_count); Everything looks like correct, so we getting error in case of no devices found, but i see the problem thats on next iteration im getting this errors: [ 766.913878] w1_master_driver w1_bus_master1: Attaching one wire slave 00.c00000000000 crc ca [ 766.924868] w1_master_driver w1_bus_master1: Family 0 for 00.c00000000000.ca is not registered. Because this errors appear in case of this condition: if ( (triplet_ret & 0x03) != 0x03 ) { if ((desc_bit == last_zero) || (last_zero < 0)) { last_device = 1; dev->search_id = 0; } else { dev->search_id = rn; } desc_bit = last_zero; cb(dev, rn); } on callback function. Based on code research i see thats some "break" on data reading cycle fired or something, thats why im not getting error messages on dmesg in case or WIRE CONNECTED. But w1_master_attempts is increasing, so search cycles going fine Questions: 1) So core is found some device on empty port and trying to connect, how this possible? And why? 2) Why there are no logs in case of connected wire to port but problem with connection? I see debug logs there but i think i need to recompile core to check it. 3) How to make my 1-wire works?

Hi, As you can see in the armbianmonitor output, an error prevents from using the Spi with the Orange pi Zero board using a newly downloaded Armbian image. The output refers to the Armbian-Hirsute image (the last one tested) but the same error also occurs with the Buster and Focal images. Unfortunately I don't have the knowledge to correct the following error myself: [3.349869] sun6i-spi 1c68000.spi: chipselect 0 already in use [3.349901] spi_master spi0: spi_device register error / soc / spi @ 1c68000 / flash @ 0 [3.349953] spi_master spi0: Failed to create SPI device for / soc / spi @ 1c68000 / flash @ 0 The only commands executed in a fresh image are: 1) armbian-config to activate spidev and 2) added two Spi parameters in the armbianEnv.txt file . I hope that someone more experienced than me (and there are many in the forum!) Will suggest the way to avoid this issue or that with the next Armbian release it won't show up anymore. Thank you all.

Hi there. I use Orange Pi zero as home print server. It works for few months for now and I am very pleased with that. Although, my printer falls into deep sleep after printing (it's Brother HL-1110EW) and cannot be woken up by the server. I have to start printer manually to print next printouts. Thus I wanted to install tea4cups to drive a relay turning the printer on and off when needed. I installed the WiringOP-zero (from here: https://github.com/xpertsavenue/WiringOP-Zero) but then strange things become to happen. I connected temporarily a LED diode to indicate the changes of the GPIO. (GPIO-7 and GND). The LED is on all the time, no matter what command I send. Even if "gpio readall" shows "0" state on GPIO-7 the led still is on. I tried to push the values through "echo": But also without success. That means gpio readall still shows changes in the table but there are no physical changes on the pin (the voltage still is on). Then I thought that maybe there is no kernel module loaded, but I can see that w1-gpio is loaded: lsmod Module Size Used by aes_arm_bs 20480 2 crypto_simd 16384 1 aes_arm_bs ccm 20480 6 xradio_wlan 110592 1 mac80211 532480 1 xradio_wlan sun4i_gpadc_iio 16384 0 cfg80211 491520 2 mac80211,xradio_wlan industrialio 53248 1 sun4i_gpadc_iio zram 24576 2 sun8i_thermal 16384 0 sunxi_cedrus 32768 0 rfkill 20480 3 cfg80211 libarc4 16384 1 mac80211 v4l2_mem2mem 20480 1 sunxi_cedrus videobuf2_dma_contig 20480 1 sunxi_cedrus videobuf2_memops 20480 1 videobuf2_dma_contig videobuf2_v4l2 20480 2 sunxi_cedrus,v4l2_mem2mem videobuf2_common 40960 3 sunxi_cedrus,v4l2_mem2mem,videobuf2_v4l2 w1_gpio 16384 0 wire 32768 1 w1_gpio cn 16384 1 wire uio_pdrv_genirq 20480 0 uio 16384 1 uio_pdrv_genirq cpufreq_dt 20480 0 usb_f_acm 20480 1 u_serial 24576 3 usb_f_acm g_serial 16384 0 libcomposite 45056 2 g_serial,usb_f_acm ip_tables 24576 0 x_tables 24576 1 ip_tables autofs4 36864 2 pwrseq_simple 16384 1 sunxi 16384 0 phy_generic 20480 2 sunxi Then I started to read forums, including this one. Still no clue what is happening, I did not find any similar case. I run out of ideas -maybe anyone would have some? Oh, I forgot one thing that may be interesting - driving onboard red led actually works. (gpio 30) EDIT: I changed the driving pin for pin9 and it works fine. Pin 7 is damaged or anything? Dunno.

Hi I am using an OrangePi Zero 2+ with AllWinner H3 and i need both uart. I enable them with armbian-config and on pins Uart2 on pins 8 and 10 work fine bat uart1 on pins 11, 13 don't. The pin on this board is not the same as orangepi zero? I mast make some setup to make uart1 to work? auto@orangepizeroplus2-h3:~$ uname -a Linux orangepizeroplus2-h3 5.9.14-sunxi #20.11.3 SMP Fri Dec 11 20:31:12 CET 2020 armv7l armv7l armv7l GNU/Linux auto@orangepizeroplus2-h3:~$ cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=i2c1 uart1 uart2 uart3 usbhost2 usbhost3 rootdev=UUID=f2961b16-88cc-46d0-8297-931c6211f21c rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u auto@orangepizeroplus2-h3:~$ ls -al /dev/ttyS* crw--w---- 1 root tty 4, 64 Feb 26 07:57 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 Feb 26 07:58 /dev/ttyS1 crw-rw---- 1 root dialout 4, 66 Feb 26 07:58 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 Feb 26 07:56 /dev/ttyS3 crw-rw---- 1 root dialout 4, 68 Feb 26 07:56 /dev/ttyS4 crw-rw---- 1 root dialout 4, 69 Feb 26 07:56 /dev/ttyS5 crw-rw---- 1 root dialout 4, 70 Feb 26 07:56 /dev/ttyS6 crw-rw---- 1 root dialout 4, 71 Feb 26 07:56 /dev/ttyS7 auto@orangepizeroplus2-h3:~$ dmesg | grep tty [ 0.000000] Kernel command line: root=UUID=f2961b16-88cc-46d0-8297-931c6211f21c rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart= ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 0.000272] printk: console [tty1] enabled [ 2.333990] printk: console [ttyS0] disabled [ 2.334080] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 40, base_baud = 1500000) is a 16550A [ 2.334160] printk: console [ttyS0] enabled [ 2.335312] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 41, base_baud = 1500000) is a 16550A [ 2.336286] 1c28800.serial: ttyS2 at MMIO 0x1c28800 (irq = 42, base_baud = 1500000) is a 16550A [ 2.337239] 1c28c00.serial: ttyS3 at MMIO 0x1c28c00 (irq = 43, base_baud = 1500000) is a 16550A [ 4.955994] systemd[1]: Created slice system-serial\x2dgetty.slice. [ 5.613942] systemd[1]: Found device /dev/ttyGS0. [ 6.438922] systemd[1]: Found device /dev/ttyS0. auto@orangepizeroplus2-h3:~$ pyserial-miniterm /dev/ttyS2 --- Miniterm on /dev/ttyS2 9600,8,N,1 --- --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H --- sdfsdf --- exit ---

I used armbianmonitor -r on my OPi Zero just like I did previously on OPi One. On OPi One everything is working fine. On my zero it doesn't display all the information for CPU. It shows: CPU total: undefined% (Sys: undefined%, User: undefined%, I/O wait: undefined%, Nice: undefined%) CPU frequency: 1.008GHz DRAM frequency: Not available Governor: ondemand Active CPU cores: 4 Vcore: undefined If I run armbianmonitor -m it shows these data I checked Allwinner_H3_Extended.conf and I noticed that it reads files from /tmp (/tmp/cpustat, /tmp/disktemp, e.t.c) On my OPi One I see these files On OPi Zero there is no rpimonitor folder. I only see these armbian-hardware-optimization.OkJBzI systemd-private-0b4c896481294542b7b1cd8e7a270133-chrony.service-SHnE1R systemd-private-0b4c896481294542b7b1cd8e7a270133-haveged.service-qSLdic What could be the issue?