TRay

I checked new sensor DS18B20 but still the same error in dmesg info, so I will try with my RPI or OZPI v1 z kernel 6.1 check use w1-gpio overlay

Thank you for your answer and suggestions. Hmm, the problem is that I have a DS18B20 sensor connected to OZPIv3, which I used in another project on another SBC. PIN DATA DS18B20 is connected to PC10 and through the 4k7 resistor to VCC 3.3V and the third pin DS18B20 to GND I will have to check this sensor again to see if RPI or OZPIv1 works on the 6.1.x kernel or I will take another unit for testing.

I read again info https://docs.armbian.com/User-Guide_Allwinner_overlays/ and compile overlay by command: armbian-add-overlay w1-gpio.dts I see that in /boot/overlay-user/ is file w1-gpio.dtbo in /boot/armbianEnv.txt user_overlays=w1-gpio param_w1_pin=PC10 param_w1_pin_int_pullup=1 after this I reboot OZPI v3 after restart OZPIv3 I check dmesg info where found [ 4.990724] Driver for 1-wire Dallas network protocol. [ 4.997793] sun50i-h616-pinctrl 300b000.pinctrl: pin PC10 already requested by onewire@0; cannot claim for 300b000.pinctrl:74 [ 4.997833] w1-gpio onewire@0: gpio_request (pin) failed [ 4.997841] w1-gpio: probe of onewire@0 failed with error -22 cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/300b000.pinctrl, 300b000.pinctrl: gpio-76 ( |red:status ) out lo gpio-77 ( |green:power ) out hi gpio-80 ( |regulator-usb1-vbus ) out hi gpio-166 ( |cd ) in lo ACTIVE LOW gpio-210 ( |reset ) out hi ACTIVE LOW Can anyone help?

Refer to https://docs.armbian.com/User-Guide_Allwinner_overlays/ The file sun50i-h616-w1-gpio.dtbo should be copied to /boot/overlay-user/ and /boot/armbinaEnv.txt should be to contain for DS18B20 connected to GPIO 74/PC10 user_overlays=w1-gpio param_w1_pin=PC10 param_w1_pin_int_pullup=1

I found information that this is a dtc issue. The error can be suppressed with -W no-unit_address_vs_reg, for example: dtc -W no-unit_address_vs_reg -O dtb -o sun50i-h616-w1-gpio.dtbo sun50i-h616-w1-gpio.dts or warning can be squashed by adding #address-cells and #size-cells

Much better, but still warning: sun50i-h616-w1-gpio.dts:20.35-26.27: Warning (unit_address_vs_reg): /fragment@1/__overlay__/onewire@0: node has a unit name, but no reg or ranges property

I found another example dtoverlay support for 1-wire subsystem on H616 devices https://github.com/orangepi-xunlong/linux-orangepi/pull/21 /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&pio>; __overlay__ { w1_pins: w1_pins { pins = "PC10"; function = "gpio_in"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { onewire@0 { compatible = "w1-gpio"; pinctrl-names = "default"; pinctrl-0 = <&w1_pins>; gpios = <&pio 2 10 0>; /* PC10 */ status = "okay"; }; }; }; }; I will try used

I tried to make of file with command: dtc -O dtb -o sun50i-h616-w1-gpio.dtbo sun50i-h616-w1-gpio.dts but result is with warring so we can not use example from Orange Pi Zero 2 to create dtbo file for OZPI v3 ? Warning (unit_address_vs_reg): /__local_fixups__/fragment@1/__overlay__/onewire@0: node has a unit name, but no reg or ranges property sun50i-h616-w1-gpio.dts:27.33-69: Warning (gpios_property): /fragment@1/__overlay__/onewire@0:gpios: cell 1 is not a phandle reference sun50i-h616-w1-gpio.dts:27.33-69: Warning (gpios_property): /fragment@1/__overlay__/onewire@0:gpios: Could not get phandle node for (cell 1)

Hi @ag123 Thank you for the replay but in case the DS18B20 uses a 1-wire bus, libgpiod is used to use the deprecated sysfs interface to GPIO, so it does not apply in this case, but I may be wrong

Looking to /boot/dtb-6.6.30-current-sunxi64/allwinner/overlay/ for h616 not exit dtbo sun50i-h616-w1-gpio.dtbo So for this reason not available in armbina-config in HARDWARE setup w1-gpio so we can not at current use 1-Wire sensor to define on which GPIO is connected 1-Wire sensor DS18B20 uses the 1-wire bus so it will be nice to have possibility use 1-Wire sensors with OZPI v3

Hi, I am not sure but in HARDWARE armbian-config when we set [*] w1-gpio (on for example OZPI v1 with ArmBian v23) is only set automatic loading modules during start up system? modprobe wire modprobe w1-gpio modprobe w1-therm I do this manually and I see exist path in system /sys/bus/w1/devices/ but we need know how to set number GPIO to use 1-Wire hardware, on Armbian v23 (Debian v11) it was added in /boot/armbianEnv.txt param_w1_pin=PA14 param_w1_pin_int_pullup=1 but how do this in Armbian v25 (based on Debian v12) so if I would like to connect my thermal sensor to GPIO 74 (PC10) I should be set in armbianEnv.txt ? param_w1_pin=PC10 param_w1_pin_int_pullup=1

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

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/

Yes, I confirm the OZPI v3 UART5 described in the original documentation and as /dev/ttyS5 in ArmBian it is marked as /dev/ttyS1 and works correctly

I try to find where is problem with UART5 dmesg |grep serial [ 1.306076] sun50i-h616-pinctrl 300b000.pinctrl: pin-224 (5000000.serial) status -517 [ 1.306095] dw-apb-uart 5000000.serial: Error applying setting, reverse things back [ 1.306231] sun50i-h616-pinctrl 300b000.pinctrl: pin-226 (5001400.serial) status -517 [ 1.306249] dw-apb-uart 5001400.serial: Error applying setting, reverse things back [ 1.333692] 5000000.serial: ttyS0 at MMIO 0x5000000 (irq = 296, base_baud = 1500000) is a 16550A [ 1.334902] 5001400.serial: ttyS1 at MMIO 0x5001400 (irq = 297, base_baud = 1500000) is a 16550A dmesg don't show ttyS5 only ttyS0 and ttyS1 so UART5 on PIN26 header is ttyS1 not ttyS5 ?

I'm using Armbian an OZPI v3 beta with the kernel: Linux localhost 6.6.23-current-sunxi64 #3 SMP Tue Mar 26 22:22:53 UTC 2024 aarch64 GNU/Linux In armbian-config UART5 is enabled and: ls -al /dev/ttyS5 crw-rw---- 1 root dialout 4, 69 Mar 31 09:49 /dev/ttyS5 I am trying to use communication via serial port UART5 /dev/ttyS5 but without success. When I try to set parameters for serial port stty -F /dev/ttyS5 9600 cs8 -cstopb -parenb stty: /dev/ttyS5: Input/output error When try to send command: echo "AT+VERSION" >/dev/ttyS5 -bash: echo: write error: Input/output error Has anyone successfully used communication via UART5 on OZPI v3?

Looking on news about kernel 6.8 : https://www.cnx-software.com/2024/03/11/linux-6-8-release-notable-changes-arm-risc-v-mips-architectures/#arm-updates-in-linux-6-8 it was added support for Orange Pi Zero 2W:

Hi I have installed the latest image for Orange Pi Zero v1 https://dl.armbian.com/orangepizero/archive/Armbian_24.2.1_Orangepizero_bookworm_current_6.6.20.img.xz link from https://www.armbian.com/orange-pi-zero/ After the first boot, I see that it is kernel 6.6.20 Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.20-current-sunxi Linux version 6.6.20-current-sunxi (armbian@next) (arm-linux-gnueabihf-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Sat Mar 2 17:23:09 UTC 2024 and when I run apt update& apt upgrade apt list --upgradable Listing... Done armbian-firmware/bookworm,bookworm 24.2.1 all [upgradable from: 24.2.1] linux-image-current-sunxi/bookworm 24.2.1 armhf [upgradable from: 24.2.1] and when running apt upgrade apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: armbian-firmware linux-image-current-sunxi 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 111 MB of archives. After this operation, 42.3 MB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://fi.mirror.armbian.de/apt bookworm/main armhf armbian-firmware all 24.2.1 [75.2 MB] Get:2 http://fi.mirror.armbian.de/apt bookworm/main armhf linux-image-current-sunxi armhf 24.2.1 [35.7 MB] Fetched 111 MB in 1min 6s (1,678 kB/s) (Reading database ... 41412 files and directories currently installed.) Preparing to unpack .../armbian-firmware_24.2.1_all.deb ... Unpacking armbian-firmware (24.2.1) over (24.2.1) ... Preparing to unpack .../linux-image-current-sunxi_24.2.1_armhf.deb ... Armbian 'linux-image-current-sunxi' for '6.6.20-current-sunxi': 'prerm' starting. Armbian 'linux-image-current-sunxi' for '6.6.20-current-sunxi': 'prerm' finishing. Armbian 'linux-image-current-sunxi' for '6.6.16-current-sunxi': 'preinst' starting. Armbian 'linux-image-current-sunxi' for '6.6.16-current-sunxi': 'preinst' finishing. Unpacking linux-image-current-sunxi (24.2.1) over (24.2.1) ... Armbian 'linux-image-current-sunxi' for '6.6.20-current-sunxi': 'postrm' starting. Armbian 'linux-image-current-sunxi' for '6.6.20-current-sunxi': 'postrm' finishing. Setting up linux-image-current-sunxi (24.2.1) ... Armbian 'linux-image-current-sunxi' for '6.6.16-current-sunxi': 'postinst' starting. dkms: autoinstall for kernel 6.6.16-current-sunxi was skipped since the kernel headers for this kernel do not seem to be installed. update-initramfs: Generating /boot/initrd.img-6.6.16-current-sunxi update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.16-current-sunxi Image Name: uInitrd Created: Tue Mar 12 07:11:59 2024 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 17410594 Bytes = 17002.53 KiB = 16.60 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.16-current-sunxi to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.16-current-sunxi' update-initramfs: Armbian: done. Remove unused generated file: /boot/uInitrd-6.6.20-current-sunxi Remove unused generated file: /boot/initrd.img-6.6.20-current-sunxi Armbian: update last-installed kernel symlink to 'zImage'... '/boot/zImage' -> 'vmlinuz-6.6.16-current-sunxi' Armbian: Debian compat: linux-update-symlinks install 6.6.16-current-sunxi boot/vmlinuz-6.6.16-current-sunxi I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.16-current-sunxi I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.16-current-sunxi I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.16-current-sunxi I: /initrd.img is now a symlink to boot/initrd.img-6.6.16-current-sunxi Armbian 'linux-image-current-sunxi' for '6.6.16-current-sunxi': 'postinst' finishing. Setting up armbian-firmware (24.2.1) ... After reboot it seems kernel 6.6.20 was replaced by 6.6.16 Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-sunxi Linux version 6.6.16-current-sunxi (armbian@next) (arm-linux-gnueabihf-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Fri Feb 23 08:25:28 UTC 2024 Is that correct?