Search the Community

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 did not find the build for Orange Pi Zero 3 Vice versa I found the build for Orange Pi Zero2 Both SBCs are equipped with Allwinner H6 CPU (H618 for the board Zero 3 and H616 for the board Zero2). Is the build for Orange Pi Zero2 compatible with Orange Pi Zero 3 as well?

I recently picked up an Orange Pi Zero 3 and have been trying to figure out how to get the i2c pins working on the GPIO. The pinout shows pins 2 and 3 (229 and 228 according to the orange pi version of wiringPi) being used to i2c-3. The downloadable images seem to be hodge-podge with the orange-pi-os version based on arch linux. But their instructions appears to be based on earlier orange pi models that had an Orange Pi OS based on armbian which included a 'orangepi-config' command similar to raspi-config. There is no orangepi-config in the arch-based Opi-OS. A third party image from leeboby includes a current buster version of Raspbian but while it contains raspi-config, it doesn't seem to enable i2c-3 and the i2c-0 does not seem to be showing any devices I connect to pins 2 and 3. After some armwrestling with their 'support' contact, he finally confirmed their new OS doesn't include the orangepi-config (big help - duh) but said I might want to check out their ubuntu and debian images (I'll try one of those later tonight). In the meantime, i've already done quite a bit of configuring of a RaspAp install and some other tools such as wireguard and the like for the application I hope to put the thing to, serving as a remote-gateway when I'm in my RV. I want to be able to use the i2c to monitor the 12v battery power and solar panels on the roof, hopefully so i can keep the remote connection powered when I leave the RV set up somewhere but head back downstate to work. dmesg shows that it detects an mv64xxx based i2c and a axp20x (AXP313a) i2c. I'm assuming the latter is used by the HDMI as running i2cdetect -l shows i2c-0 as the mv64xxx_i2c adapter and i2c-1 as DesignWare HDMI. But, as mentioned, connecting i2c devices to pins 2 and 3 as per the gpio pinout diagram (it's rotated 180 degrees on this board) doesn't wind up showing any of my connected devices in i2cdetect. So I think the raspbian image is trying to use whatever the OEM raspberry bcm chip config uses. the opi wiringpi gpio readall shows GPIO 229 - wPi 0 as SDA.3 on the second pin (physical 3) and GPIO 228, wPi 1 as SCL.3 on the third pin (physical 5) The /boot/config.txt was either non-existent or empty as after running raspi-config to try enabling i2c within it, the only line in the file was dtparam=i2c_arm=on and there is no cmdline.txt in that directory either. I tried this config.txt setup also with no changes after rebooting: dtparam=i2c_arm=off dtparam=i2c-gpio=on #dtoverlay=i2c-gpio,bus=3,i2c_gpio_sda=2,i2c_gpio_scl=3 dtoverlay=i2c-gpio,bus=3,i2c_gpio_sda=229,i2c_gpio_scl=228 (the commented out line being another variation I tried) This computer uses a H618 chip similar to the banana pis. I should note their wiringpi doesn't have an H618 configuration within it's source code, but detects it as H616. (I do not know if this effects how the command works or not) Any help getting i2c working is appreciated

[root@lalaki ~]# journalctl -p4 Sep 16 14:27:11 lalaki kernel: watchdog: watchdog0: watchdog did not stop! Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 0 Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 1 Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 2 Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 3 Sep 16 14:26:51 lalaki kernel: KASLR disabled due to lack of seed Sep 16 14:26:51 lalaki kernel: cacheinfo: Unable to detect cache hierarchy for CPU 0 Sep 16 14:26:51 lalaki kernel: axp20x-regulator axp20x-regulator: DCDC frequency on AXP313a is fixed to 3 MHz. Sep 16 14:26:51 lalaki kernel: axp20x-regulator axp20x-regulator: Error setting dcdc frequency: -22 Sep 16 14:26:51 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-ph not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: debugfs: Directory '1100000.mixer' with parent 'regmap' already present! Sep 16 14:26:51 lalaki kernel: debugfs: Directory '1100000.mixer' with parent 'regmap' already present! Sep 16 14:26:51 lalaki kernel: sun8i-dw-hdmi 6000000.hdmi: supply hvcc not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pc not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: sun50i-cpufreq-nvmem: will use speed0 CPU OPPs Sep 16 14:26:51 lalaki kernel: OF: /thermal-zones/gpu-thermal/cooling-maps/map0: could not get #cooling-cells for /soc/gpu@1800000 Sep 16 14:26:51 lalaki kernel: thermal_sys: Add a cooling_device property with at least one device Sep 16 14:26:51 lalaki kernel: thermal thermal_zone0: binding zone gpu-thermal with cdev cpufreq-cpu0 failed:-2 Sep 16 14:26:51 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pg not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pf not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: usb_phy_generic usb_phy_generic.4.auto: supply vcc not found, using dummy regulator Sep 16 14:26:51 lalaki kernel: usb_phy_generic usb_phy_generic.4.auto: dummy supplies not allowed for exclusive requests Sep 16 14:26:51 lalaki kernel: mmc0: host does not support reading read-only switch, assuming write-enable Sep 16 14:26:51 lalaki kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log. Sep 16 14:26:51 lalaki kernel: WCN_ERR: dts node for bt_wake not found Sep 16 14:26:53 lalaki kernel: sunxi_cedrus: module is from the staging directory, the quality is unknown, you have been warned. Sep 16 14:26:53 lalaki kernel: sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pi not found, using dummy regulator Sep 16 14:26:53 lalaki kernel: dwmac-sun8i 5020000.ethernet: Current syscon value is not the default 58000 (expect 0) Sep 16 14:26:53 lalaki kernel: wifi ini path = /lib/firmware/wifi_2355b001_1ant.ini Sep 16 14:26:53 lalaki kernel: sprdwl:sprdwl_get_fw_info length mismatch: len_count=83, r_len=89 Sep 16 14:26:53 lalaki kernel: sprdwl:sprdwl_get_fw_info, drv_version=1, fw_version=2, compat_ver=0 Sep 16 14:26:53 lalaki kernel: sprdwl:chip_model:0x2355, chip_ver:0x0 Sep 16 14:26:53 lalaki kernel: sprdwl:fw_ver:0, fw_std:0x7f, fw_capa:0x120f7f Sep 16 14:26:53 lalaki kernel: sprdwl:mac_addr:a0:67:20:f1:db:fb Sep 16 14:26:53 lalaki kernel: sprdwl:credit_capa:TX_WITH_CREDIT Sep 16 14:26:53 lalaki kernel: sprdwl:ott support:0 Sep 16 14:26:53 lalaki kernel: unisoc_wifi unisoc_wifi wlan0: mixed HW and IP checksum settings. Sep 16 17:10:16 lalaki kernel: unisoc_wifi unisoc_wifi wlan0: sprdwl_start_xmit drop msg due to TX Err Sep 16 17:10:17 lalaki kernel: unisoc_wifi unisoc_wifi wlan0: sprdwl_start_xmit drop msg due to TX Err Sep 16 17:10:17 lalaki kernel: unisoc_wifi unisoc_wifi wlan0: sprdwl_start_xmit drop msg due to TX Err ... Is part of the content merely informative? Should some of the parameters be corrected? for example: default_syscon_value = 58000, should it be changed to 0?