ag123 Posted July 11, 2023 Posted July 11, 2023 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* 😄 0 Quote
dziekon Posted July 13, 2023 Posted July 13, 2023 (edited) I ordered the 2GB version some time ago, should arrive in about week or two, judging by the previous orders from Xunlong's shop. I have quite high hopes for it, since it should be slightly faster and much cheaper than the OPi Zero 2. Will see how the bring up goes, hopefully I'll be able to at least boot it up with minor tinkering. Edited July 13, 2023 by dziekon 0 Quote
ag123 Posted July 13, 2023 Author Posted July 13, 2023 (edited) I took a look at the kernel and noted that the latest snapshot is based on 6.1.31 kernel https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-6.1-sun50iw9 this matches that of the just recently released binaries for Ubuntu and Debian http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.html the drill down links: https://drive.google.com/drive/folders/1ek_VaZiNpCTq_H3T_e1AgKKWyXAxL9q1 https://drive.google.com/drive/folders/1VPf5HCs5jva_J4Y8SfKOnGygWfuxVPiT a note in the commit history suggest that this recent kernel also works for the Orange Pi Zero 2 H616 https://github.com/orangepi-xunlong/linux-orangepi/commits/orange-pi-6.1-sun50iw9 This is pretty encouraging, as it would be more of a cumulative update rather than redo, which often break many things. It helps as well as those who have invested in the earlier OPi Zero 2 would see continuity and all these efforts to test and mainline the recent changes for H616 Orange Pi Zero 2 likely works well on Orange Pi Zero 3 (just fresh out of the oven) as well. Hopefully, as more people help to test changes and the mainlining efforts that we'd soon have H616 and H618 supported in the mainline Armbian releases. Edited July 13, 2023 by ag123 0 Quote
Donely Gunn Posted August 3, 2023 Posted August 3, 2023 I am new to the armbian field, but in my research, I came across this github repo that claims to have armbian builds for orange pi zero 3 : https://github.com/leeboby/armbian-images I have not tested these, since I don't have my board yet. I hope they are useful though. I will test them as soon as I get my board. 0 Quote
Werner Posted August 4, 2023 Posted August 4, 2023 10 hours ago, Donely Gunn said: t claims to have armbian builds Claims. But that's it. Those are made and provided by 3rd party. Armbian cannot and will not provide support for such. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity 0 Quote
movie9409 Posted August 5, 2023 Posted August 5, 2023 I can confirm 4GB model works with https://github.com/leeboby/armbian-images `ubuntu22.04 server` for the first time when I logged in as root. After I reboot or shutdown it disappears from the `ipscan`. Unfortunately I'd had no hdmi-micro hdmi cable to connect the SBC directly to the monitor couldn't go further debugging. Anyway the non-official Armbian image provided by the official Orangepi team works..weirdly. 0 Quote
ag123 Posted August 7, 2023 Author Posted August 7, 2023 (edited) I just tried the Orange Pi released images for http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.html Orangepizero3_1.0.0_ubuntu_jammy_server_linux6.1.31.7z https://drive.google.com/drive/folders/1902uBSV0tQCqlx8d0rv153GZbuWz1cM6 on a Orange Pi Zero 3 2GB board. In the same way, I don't have HDMI and hence simply test accessing it over the network. for Orange Pi Zero 3 released Ubuntu Jammy 6.1.31 server image, currently: - ethernet works, I'm able to login over ethernet - wifi apparently works, I managed to do a scan for visible APs. However, while messing with hostapd to setup an AP. I got stuck with the authentication part. As i remembered, the wifi interface has to be placed on the bridge for hostapd to work. So next, I messed with using nmcli to setup a bridge. Unfortunately, on rebooting due to the different network config, I can't connect over the network. I tried connecting on the serial terminal at the uart pins as documented in the manual. 'unfortunately' I found that it is more of a log spooled out on serial tty, and worse I got screenfuls of gibberish this is most likely due to a baud rate mismatch It is kind of a waste of a tty to simply spool logs. Edited August 7, 2023 by ag123 0 Quote
ag123 Posted August 7, 2023 Author Posted August 7, 2023 (edited) next up try the 'unofficial' armbian images https://github.com/leeboby/armbian-images ok in armbian I got a boot console on the uart Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.37.2 [/usr/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -a -C0 /dev/mmcblk1p1 armbi_root: recovering journal armbi_root: clean, 43126/916864 files, 567125/3800064 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Armbian 23.08.0-trunk jammy! -.mount [ OK ] Created slice Slice /system/modprobe. [ OK ] Created slice Slice /system/serial-getty. [ OK ] Created slice User and Session Slice. [ OK ] Started Forward Password R…uests to Wall Directory Watch. [ OK ] Set up automount Arbitrary…s File System Automount Point. [ OK ] Reached target Slice Units. [ OK ] Reached target Swaps. [ OK ] Reached target System Time Set. [ OK ] Reached target Local Verity Protected Volumes. [ OK ] Listening on RPCbind Server Activation Socket. [ OK ] Listening on Syslog Socket. [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on udev Kernel Socket. [ OK ] Reached target Socket Units. Mounting Huge Pages File System... Mounting POSIX Message Queue File System... Mounting Kernel Debug File System... Starting Restore / save the current clock... Starting Set the console keyboard layout... Starting Create List of Static Device Nodes... Starting Load Kernel Module chromeos_pstore... Starting Load Kernel Module configfs... Starting Load Kernel Module drm... Starting Load Kernel Module efi_pstore... Starting Load Kernel Module fuse... Starting Load Kernel Module pstore_blk... Starting Load Kernel Module pstore_zone... Starting Load Kernel Module ramoops... Starting Load Kernel Modules... Starting Remount Root and Kernel File Systems... Starting Coldplug All udev Devices... dev-hugepages.mount dev-mqueue.mount [ OK ] Mounted Huge Pages File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Kernel Debug File System. sys-kernel-debug.mount [ OK ] Finished Restore / save the current clock. fake-hwclock.service [ OK ] Finished Create List of Static Device Nodes. kmod-static-nodes.service [ OK ] Finished Load Kernel Module chromeos_pstore. [ OK ] Finished Load Kernel Module configfs. [ OK ] Finished Load Kernel Module drm. [ OK ] Finished Load Kernel Module efi_pstore. [ OK ] Finished Load Kernel Module fuse. [ OK ] Finished Load Kernel Module pstore_blk. [ OK ] Finished Load Kernel Module pstore_zone. [ OK ] Finished Load Kernel Module ramoops. Mounting FUSE Control File System... Mounting Kernel Configuration File System... [ OK ] Finished Remount Root and Kernel File Systems. systemd-remount-fs.service [ OK ] Mounted FUSE Control File System. sys-fs-fuse-connections.mount [ OK ] Mounted Kernel Configuration File System. sys-kernel-config.mount Starting Load/Save Random Seed... Starting Create System Users... run-credentials-systemd\x2dsysusers.service.mount [ OK ] Finished Set the console keyboard layout. keyboard-setup.service [ OK ] Finished Load/Save Random Seed. systemd-random-seed.service [ OK ] Finished Create System Users. systemd-sysusers.service Starting Create Static Device Nodes in /dev... [ OK ] Finished Create Static Device Nodes in /dev. systemd-tmpfiles-setup-dev.service [ OK ] Reached target Preparation for Local File Systems. Mounting /tmp... Starting Rule-based Manage…for Device Events and Files... [ OK ] Mounted /tmp. tmp.mount [ OK ] Reached target Local File Systems. Starting Armbian leds state... Starting Armbian ZRAM config... Starting Set console font and keymap... Starting Tell Plymouth To Write Out Runtime Data... [ OK ] Finished Coldplug All udev Devices. systemd-udev-trigger.service Starting Helper to synchronize boot up for ifupdown... [ OK ] Finished Set console font and keymap. console-setup.service [ OK ] Finished Tell Plymouth To Write Out Runtime Data. plymouth-read-write.service [ OK ] Finished Helper to synchronize boot up for ifupdown. ifupdown-pre.service [ OK ] Finished Armbian leds state. armbian-led-state.service [ OK ] Started Rule-based Manager for Device Events and Files. systemd-udevd.service Starting Show Plymouth Boot Screen... [ OK ] Listening on Load/Save RF …itch Status /dev/rfkill Watch. Starting Load/Save RF Kill Switch Status... [ OK ] Started Show Plymouth Boot Screen. plymouth-start.service [ OK ] Started Forward Password R…s to Plymouth Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Reached target Path Units. [ OK ] Found device /dev/ttyS0. [ OK ] Reached target Hardware activated USB gadget. dev-zram0.swap Starting Load Kernel Module chromeos_pstore... Starting Load Kernel Module efi_pstore... Starting Load Kernel Module pstore_blk... Starting Load Kernel Module pstore_zone... Starting Load Kernel Module ramoops... [ OK ] Finished Load Kernel Module chromeos_pstore. [ OK ] Finished Load Kernel Module efi_pstore. [ OK ] Finished Load Kernel Module pstore_blk. [ OK ] Finished Load Kernel Module pstore_zone. [ OK ] Finished Load Kernel Module ramoops. [ OK ] Finished Armbian ZRAM config. armbian-zram-config.service Starting Armbian memory supported logging... var-log.hdd.mount var-log.mount systemd-rfkill.service [ OK ] Started Load/Save RF Kill Switch Status. [ OK ] Finished Load Kernel Modules. systemd-modules-load.service Starting Apply Kernel Variables... [ OK ] Finished Apply Kernel Variables. systemd-sysctl.service Starting Raise network interfaces... Starting Load Kernel Module chromeos_pstore... Starting Load Kernel Module efi_pstore... Starting Load Kernel Module pstore_blk... Starting Load Kernel Module pstore_zone... Starting Load Kernel Module ramoops... [ OK ] Finished Load Kernel Module chromeos_pstore. [ OK ] Finished Load Kernel Module efi_pstore. [ OK ] Finished Load Kernel Module pstore_zone. [ OK ] Finished Load Kernel Module pstore_blk. [ OK ] Finished Load Kernel Module ramoops. [ OK ] Finished Raise network interfaces. networking.service Starting Load Kernel Module chromeos_pstore... Starting Load Kernel Module efi_pstore... Starting Load Kernel Module pstore_blk... Starting Load Kernel Module pstore_zone... Starting Load Kernel Module ramoops... [ OK ] Finished Load Kernel Module chromeos_pstore. [ OK ] Finished Load Kernel Module efi_pstore. [ OK ] Finished Load Kernel Module pstore_blk. [ OK ] Finished Load Kernel Module ramoops. [ OK ] Finished Load Kernel Module pstore_zone. [ OK ] Finished Armbian memory supported logging. armbian-ramlog.service Starting Journal Service... [ OK ] Started Journal Service. systemd-journald.service Starting Flush Journal to Persistent Storage... [ OK ] Finished Flush Journal to Persistent Storage. systemd-journal-flush.service Starting Create Volatile Files and Directories... [ OK ] Finished Create Volatile Files and Directories. systemd-tmpfiles-setup.service Mounting RPC Pipe File System... [ OK ] Started Entropy Daemon based on the HAVEGE algorithm. haveged.service Starting RPC bind portmap service... Starting Network Name Resolution... Starting Record System Boot/Shutdown in UTMP... [ OK ] Mounted RPC Pipe File System. run-rpc_pipefs.mount [ OK ] Reached target rpc_pipefs.target. [ OK ] Reached target NFS client services. [ OK ] Finished Record System Boot/Shutdown in UTMP. systemd-update-utmp.service [ OK ] Reached target System Initialization. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Listening on D-Bus System Message Bus Socket. Starting Armbian hardware monitoring... Starting Armbian hardware optimization... [ OK ] Finished Armbian hardware monitoring. armbian-hardware-monitor.service [ OK ] Started RPC bind portmap service. [ OK ] Reached target Preparation for Remote File Systems. [ OK ] Reached target Remote File Systems. [ OK ] Reached target RPC Port Mapper. rpcbind.service [ OK ] Finished Armbian hardware optimization. armbian-hardware-optimize.service [ OK ] Reached target Basic System. Starting Save/Restore Sound Card State... [ OK ] Started Regular background program processing daemon. cron.service [ OK ] Started D-Bus System Message Bus. dbus.service Starting Network Manager... [ OK ] Started Save initial kernel messages after boot. dmesg.service Starting Remove Stale Onli…t4 Metadata Check Snapshots... Starting LSB: Load kernel …d to enable cpufreq scaling... Starting LSB: rng-tools (Debian variant)... Starting System Logging Service... Starting Resets System Activity Logs... Starting User Login Management... Starting WPA supplicant... [ OK ] Finished Save/Restore Sound Card State. [ OK ] Reached target Sound Card. alsa-restore.service [ OK ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots. rsyslog.service [ OK ] Started System Logging Service. [ OK ] Started LSB: rng-tools (Debian variant). rng-tools-debian.service [ OK ] Finished Resets System Activity Logs. sysstat.service [ OK ] Started LSB: Load kernel m…ded to enable cpufreq scaling. loadcpufreq.service Starting LSB: set CPUFreq kernel parameters... cpufrequtils.service [ OK ] Started LSB: set CPUFreq kernel parameters. [ OK ] Started Network Name Resolution. systemd-resolved.service [ OK ] Reached target Host and Network Name Lookups. Starting LSB: Set sysfs variables from /etc/sysfs.conf... Starting Bluetooth service... [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. sysfsutils.service [ OK ] Started User Login Management. systemd-logind.service [ OK ] Started WPA supplicant. wpa_supplicant.service [ OK ] Started Network Manager. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. NetworkManager.service Starting chrony, an NTP client/server... Starting OpenVPN service... Starting /etc/rc.local Compatibility... Starting Notify NFS peers of a restart... Starting OpenBSD Secure Shell server... Starting Permit User Sessions... [ OK ] Started Unattended Upgrades Shutdown. unattended-upgrades.service [ OK ] Started vnStat network traffic monitor. vnstat.service [ OK ] Finished OpenVPN service. openvpn.service [ OK ] Started /etc/rc.local Compatibility. rc-local.service [ OK ] Started Notify NFS peers of a restart. rpc-statd-notify.service [ OK ] Finished Permit User Sessions. systemd-user-sessions.service [ OK ] Started Bluetooth service. bluetooth.service [ OK ] Reached target Bluetooth Support. Starting Hold until boot process finishes up... Starting Terminate Plymouth Boot Screen... Starting Hostname Service... [FAILED] Failed to start OpenBSD Secure Shell server. [FAILED] Failed to start OpenBSD Secure Shell server. Armbian 23.08.0-trunk Jammy ttyS0 orangepizero3 login: for some reason, the board didn't register the keystrokes typed in the console, maybe it is some issues with my usb serial - uart dongle. but well that looks cool bummer can't login to SSH, but ping works, so ethernet works Edited August 7, 2023 by ag123 0 Quote
ag123 Posted August 7, 2023 Author Posted August 7, 2023 (edited) next try the Debian bookworm image instead https://github.com/leeboby/armbian-images Welcome to ARMBIAN! Documentation: https://docs.armbian.com | Community: https://forum.armbian.com IP address: 192.168.1.173 Create root password: ****** Repeat root password: ****** Warning: Weak password, it does not contain enough DIFFERENT characters! Choose default system command shell: 1) bash 2) zsh 1 Shell: BASH Creating a new user account. Press <Ctrl-C> to abort yay, I'm in SSH, confirmed ethernet works ssh 192.168.1.173 -l root root@192.168.1.173's password: ___ ____ _ _____ _____ / _ \| _ \(_) |__ /___ _ __ ___|___ / | | | | |_) | | / // _ \ '__/ _ \ |_ \ | |_| | __/| | / /| __/ | | (_) |__) | \___/|_| |_| /____\___|_| \___/____/ Welcome to Armbian 23.08.0-trunk Bookworm with Linux 6.1.31-sunxi64 No end-user support: built from trunk System load: 28% Up time: 16 min Memory usage: 6% of 1.94G IP: 192.168.1.173 CPU temp: 44°C Usage of /: 11% of 15G RX today: 56.3 KiB [ 0 security updates available, 1 updates total: apt upgrade ] Last check: 2023-08-07 20:51 Last login: Mon Aug 7 20:41:40 2023 from 192.168.1.2 er erm, it is actually nice and colorful, text copy couldn't get the colors strangely, the serial terminal is blank in the bootup, but that sshd over ethernet 'just works' ok I 'accidentally' saw this in the serial terminal in after a reboot Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.38.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 armbi_root: clean, 48668/944704 files, 488641/3800064 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Armbian 23.08.0-trunk bookworm! [ OK ] Created slice system-getty.slice - Slice /system/getty. [ OK ] Created slice system-modpr…lice - Slice /system/modprobe. [ OK ] Created slice system-seria… - Slice /system/serial-getty. [ OK ] Created slice user.slice - User and Session Slice. [ OK ] Started systemd-ask-passwo… Requests to Wall Directory Watch. [ OK ] Set up automount proc-sys-…rmats File System Automount Point. [ OK ] Reached target integrityse…Local Integrity Protected Volumes. [ OK ] Reached target slices.target - Slice Units. ... long [ OK ] Started unattended-upgrade…0m - Unattended Upgrades Shutdown. [ OK ] Started vnstat.service - vnStat network traffic monitor. [ OK ] Finished openvpn.service - OpenVPN service. [ OK ] Started rc-local.service - /etc/rc.local Compatibility. [ OK ] Started systemd-hostnamed.service - Hostname Service. [ OK ] Finished systemd-user-sess…ervice - Permit User Sessions. Starting plymouth-quit-wai… until boot process finishes up... Starting plymouth-quit.ser… Terminate Plymouth Boot Screen... Armbian 23.08.0-trunk Bookworm ttyS0 orangepizero3 login: well, I still have problems typing things into the console, it seemed the characters typed 'didn't get across' to the H618 uart, even though this time the text is properly received and displayed at 115200 baud from a different PC Edited August 7, 2023 by ag123 0 Quote
ag123 Posted August 7, 2023 Author Posted August 7, 2023 (edited) well avahi-daemon and avahi-utils should be bundled in the 'core' Armbian base distribution, well that's my pet peeve, prejudice . apt-get install avahi-daemon avahi-utils darn, missing vi(m) apt-get install vim edit vi /etc/avahi/avahi-daemon.conf ... [publish] publish-workstation=yes then from another station > avahi-browse -a + eth0 IPv6 orangepizero3 [02:00:6c:53:f7:f9] Workstation local > ping -4 orangepizero3.local PING orangepizero3.local (192.168.1.173) 56(84) bytes of data. 64 bytes from 192.168.1.173 (192.168.1.173): icmp_seq=1 ttl=64 time=0.514 ms > ssh orangepizero3.local user@orangepizero3.local's password: ___ ____ _ _____ _____ / _ \| _ \(_) |__ /___ _ __ ___|___ / | | | | |_) | | / // _ \ '__/ _ \ |_ \ | |_| | __/| | / /| __/ | | (_) |__) | \___/|_| |_| /____\___|_| \___/____/ Welcome to Armbian 23.08.0-trunk Bookworm with Linux 6.1.31-sunxi64 No end-user support: built from trunk System load: 27% Up time: 28 min Memory usage: 6% of 1.94G IP: 192.168.1.173 CPU temp: 43°C Usage of /: 12% of 15G RX today: 9.4 MiB [ 0 security updates available, 1 updates total: apt upgrade ] Last check: 2023-08-07 20:59 Last login: Mon Aug 7 21:06:17 2023 user@orangepizero3:~$ looks pretty decent, system load is a little high though for what is a 'verbatim' setup lol user@orangepizero3:~$ nmcli d DEVICE TYPE STATE CONNECTION end0 ethernet connected Wired connection 1 lo loopback connected (externally) lo wlan0 wifi disconnected -- p2p-dev-wlan0 wifi-p2p disconnected -- user@orangepizero3:~$ nmcli d wifi IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY A0:36:BC:4A:3B:49 CopperTiger Infra 9 270 Mbit/s 90 ▂▄▆█ WPA2 WPA3 F0:2F:74:74:70:F1 CopperTiger Infra 9 270 Mbit/s 70 ▂▄▆_ WPA2 WPA3 24:F5:A2:42:E3:81 Linksys07844 Infra 12 540 Mbit/s 70 ▂▄▆_ WPA2 ok so it seemed wifi works as well Edited August 7, 2023 by ag123 0 Quote
hmartin Posted August 7, 2023 Posted August 7, 2023 (edited) @ag123 can you post the full bootlog for the armbian release from GitHub (23.08)? I tried both bookworm and jammy with several micro SD cards (including name brands like Samsung) and my board (4GB model) never gets further than the following: U-Boot SPL 2021.07-armbian (Jul 12 2023 - 10:04:49 +0000) DRAM: 4096 MiB Trying to boot from MMC1 * Armbian_23.08.0-trunk_Orangepizero3_bookworm_current_6.1.31-1GB-2GB.img.xz (sha256: 6c58ad6122fd62769e1063164df3cdf004af9d498f69db3f1c86094cc749a375) * Armbian_23.08.0-trunk_Orangepizero3_jammy_current_6.1.31-1GB-2GB.img.xz (sha256: 7a794393ef8a5fedc73c4cc977cc5f29660ba106f17d0a6c2322a926f88e91fe) And yes, I did copy the 4GB dtb and u-boot as instructed. I know this forum is not the place to ask for support for unofficial Armbian forks, but I'm just curious if you encountered any such issues. If I remove the micro SD card entirely, the board boots some kind of Android from the SPI: U-Boot SPL 2021.07-orangepi (Jul 15 2023 - 15:02:23 +0800) DRAM: 4096 MiB Trying to boot from MMC1 [53]HELLO! BOOT0 is starting! [56]BOOT0 commit : 3ae35eb [59]set pll start [61]periph0 has been enabled [64]set pll end [67]unknow PMU [69]unknow PMU [73]PMU: AXP1530 [77]dram return write ok [80]board init ok [81]DRAM BOOT DRIVE INFO: V0.651 [85]the chip id is 0x2000 [87]chip id check OK [98]DRAM_VCC set to 1100 mv [101]DRAM CLK =792 MHZ [103]DRAM Type =8 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [114]Actual DRAM SIZE =4096 M [117]DRAM SIZE =4096 MBytes, para1 = 310a, para2 = 10001000, dram_tpr13 = 2006c61 [130]DRAM simple test OK. [133]rtc standby flag is 0x0, super standby flag is 0x0 [138]dram size =4096 [141]Use rtc to store dram tuning para [146]spinor id is: 5e 40 18, read cmd: 0b [150]Succeed in reading toc file head. [154]The size of toc is 9c000. [317]Entry_name = u-boot [322]Entry_name = monitor [326]Entry_name = dtb [330]Jump to second Boot. NOTICE: BL3-1: v1.0(debug):05d6c57 NOTICE: BL3-1: Built : 13:35:35, 2021-10-28 NOTICE: BL3-1 commit: 8 NOTICE: cpuidle init version V2.0 ERROR: Error initializing runtime service tspd_fast NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3<FF> U-Boot 2018.05 (Jul 10 2023 - 10:32:18 +0800) Allwinner Technology [00.408]CPU: Allwinner Family [00.411]Model: sun50iw9 I2C: ready [00.415]DRAM: 2 GiB [00.419]Relocation Offset is: 75f5d000 [00.439]secure enable bit: 0 [00.441]pmu_axp152_probe pmic_bus_read fail [00.445]PMU: AXP1530 [00.451]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=400Mhz [00.457]gic: sec monitor mode [00.462]flash init start [00.464]workmode = 0,storage type = 3 SF: Detected zb25vq128as with page size 256 Bytes, erase size 64 KiB, total 16 MiB [00.481]sunxi flash init ok [00.485]Loading Environment from SUNXI_FLASH... OK [00.514]get secure storage map err [00.517]sunxi secure storage is not supported [00.521]usb burn from boot delay time 0 weak:otg_phy_config [00.535]usb prepare ok [53]HELLO! BOOT0 is starting! [56]BOOT0 commit : 3ae35eb [59]set pll start [61]periph0 has been enabled [64]set pll end [67]unknow PMU [69]unknow PMU [73]PMU: AXP1530 [77]dram return write ok [80]board init ok [81]DRAM BOOT DRIVE INFO: V0.651 [85]the chip id is 0x2000 [87]chip id check OK [98]DRAM_VCC set to 1100 mv [100]DRAM CLK =792 MHZ [103]DRAM Type =8 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [114]Actual DRAM SIZE =4096 M [117]DRAM SIZE =4096 MBytes, para1 = 310a, para2 = 10001000, dram_tpr13 = 2006c61 [130]DRAM simple test OK. [133]rtc standby flag is 0x0, super standby flag is 0x0 [138]dram size =4096 [141]Use rtc to store dram tuning para [146]spinor id is: 5e 40 18, read cmd: 0b [150]Succeed in reading toc file head. [154]The size of toc is 9c000. [312]Entry_name = u-boot [317]Entry_name = monitor [321]Entry_name = dtb [325]Jump to second Boot. NOTICE: BL3-1: v1.0(debug):05d6c57 NOTICE: BL3-1: Built : 13:35:35, 2021-10-28 NOTICE: BL3-1 commit: 8 NOTICE: cpuidle init version V2.0 ERROR: Error initializing runtime service tspd_fast NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3<FF> U-Boot 2018.05 (Jul 10 2023 - 10:32:18 +0800) Allwinner Technology [00.403]CPU: Allwinner Family [00.406]Model: sun50iw9 I2C: ready [00.410]DRAM: 2 GiB [00.413]Relocation Offset is: 75f5d000 [00.434]secure enable bit: 0 [00.436]pmu_axp152_probe pmic_bus_read fail [00.440]PMU: AXP1530 [00.445]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=400Mhz [00.452]gic: sec monitor mode [00.457]flash init start [00.459]workmode = 0,storage type = 3 SF: Detected zb25vq128as with page size 256 Bytes, erase size 64 KiB, total 16 MiB [00.476]sunxi flash init ok [00.480]Loading Environment from SUNXI_FLASH... OK [00.509]get secure storage map err [00.512]sunxi secure storage is not supported [00.516]usb burn from boot delay time 0 weak:otg_phy_config [00.530]usb prepare ok [01.333]overtime [01.337]do_burn_from_boot usb : no usb exist [01.341]get secure storage map err [01.344]secure storage init fail [01.349]update dts [01.353]update part info [01.357]update bootcmd [01.359]No ethernet found. Hit any key to stop autoboot: 0 Android's image name: sun50i_arm64 [04.895]Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.170 (orangepi@ubuntu) (gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05) ) #15 SMP PREEMPT Thu Jun 29 17:36:03 CST 2023 [ 0.000000] Boot CPU: AArch64 Processor [410fd034] [ 0.000000] bootconsole [earlycon0] enabled On the HDMI output I have an error that it can't find initramfs, which is probably expected since there's no SD card present. Edited August 7, 2023 by hmartin 0 Quote
ag123 Posted August 7, 2023 Author Posted August 7, 2023 hi, no worries, it'd be good if OPi Z 3 becomes a 'supported' board, it is a pretty good board really, as a little Wifi router. for the Debian bookworm image booting up on my 2 GB OPi Z 3 the front parts is like such U-Boot SPL 2021.07-armbian (Jul 12 2023 - 10:04:49 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.9(debug):armbian NOTICE: BL31: Built : 02:24:54, Jul 11 2023 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0827f8, model: OrangePi Zero3 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: cortex_a53: CPU workaround for 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. U-Boot 2021.07-armbian (Jul 12 2023 - 10:04:49 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: OrangePi Zero3 I2C: ready DRAM: 2 GiB MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. starting USB... No working controllers found Autoboot in 1 seconds, press <Space> to stop ÿÿþÿÿïÿswitch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3259 bytes read in 4 ms (794.9 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 207 bytes read in 3 ms (67.4 KiB/s) 39163 bytes read in 9 ms (4.1 MiB/s) 4203 bytes read in 7 ms (585.9 KiB/s) Applying kernel provided DT fixup script (sun50i-h616-fixup.scr) ## Executing script at 45000000 18189653 bytes read in 1509 ms (11.5 MiB/s) 22464520 bytes read in 1864 ms (11.5 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=417f0000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 18189589 Bytes = 17.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 48ea7000, end 49fffd15 ... OK Loading Device Tree to 0000000048e35000, end 0000000048ea6fff ... OK Starting kernel ... Loading, please wait... Starting systemd-udevd version 252.6-1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... ^[[2J^[[3J^[[-1;-1fdone.^M Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.^M Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems^M done.^M Begin: Will now check root file system ... fsck from util-linux 2.38.1^M [/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -a -C0 /dev/mmcblk1p1 ^M armbi_root: recovering journal^M armbi_root: clean, 48679/944704 files, 489197/3800064 blocks^M done.^M done.^M Begin: Running /scripts/local-bottom ... done.^M Begin: Running /scripts/init-bottom ... done.^M ^M Welcome to ^[[1mArmbian 23.08.0-trunk bookworm^[[0m!^M armbi_root: recovering journal^M armbi_root: clean, 48679/944704 files, 489197/3800064 blocks^M done.^M done.^M Begin: Running /scripts/local-bottom ... done.^M Begin: Running /scripts/init-bottom ... done.^M ^M Welcome to ^[[1mArmbian 23.08.0-trunk bookworm^[[0m!^M The rest are the kernel boot proper, as it is verbose, I've attached it here. Note that I'm booting the 'server' image rather than the bigger 'desktop' image. I've not done Armbian 23.08.0-trunk Jammy as I ran into the OpenSSH daemon 'killed' issue which I didn't have a solution at hand to 'fix' it. I'm not sure what else I'd be able to help thus far. Apparently, the uboot or rather the boot loader setup is the tricky part as 1GB & 2 GB, 1.5 GB and 4 GB has different boot loader setups. armbianbookworkbootlog.zip 0 Quote
ag123 Posted August 7, 2023 Author Posted August 7, 2023 (edited) for the 1.5 GB and 4GB boards there are some instructions and binaries here https://github.com/leeboby/opizero3-uboot-dtb for the 4 GB version the google translation is like such: 1 First download the bin file of 4g memory u-boot: 4gb memory u-boot bin file 2 Then download the dtb file corresponding to 4gb memory: 4gb memory dtb file 3 Then insert the TF card that has been burnt into the opizero3 linux6.x system into other linux machines 4 Then use the sudo fdisk -l command to view the device name of the tf card: For example: /dev/sdax 5 Then mount the file system in the tf card to the /mnt directory of the linux machine: sudo mount /dev/sdax /mnt 6 Then copy the dtb file to the /boot/dtb/allwinner/ directory in the TF card (please modify this directory according to the actual situation, do not copy): example code, need to adapt based on actual sitiation: sudo cp sun50i-h616-orangepi-zero3-4gb.dtb /mnt/boot/dtb/allwinner/sun50i-h616-orangepi-zero3.dtb 7 Then use the following command to update the bin file of u-boot to the TF card sudo dd bs=1k seek=8 if=u-boot-sunxi-with-spl-opizero3-4gb.bin of=/dev/sdax Note that steps 3 - 7 are done on a different Linux machine (which probably can even be a small board e.g. Raspberry Pi or an existing Armbian board that runs. And assuming that you are workng it say on a usb SD card reader. If you are working that on your PC, do be careful with the commands, as it is intended to edit binaries on the image written to a TF card. Be careful about working on your PC to idenfity the correct device disk or risk trashing data on your hard drives. Edited August 7, 2023 by ag123 0 Quote
hmartin Posted August 7, 2023 Posted August 7, 2023 5 hours ago, ag123 said: for the 1.5 GB and 4GB boards there are some instructions and binaries here https://github.com/leeboby/opizero3-uboot-dtb Yes, I've followed the instructions: $ sudo mount /dev/sda1 /mnt/ $ sudo cp sun50i-h616-orangepi-zero3-4gb.dtb /mnt/boot/dtb/allwinner/sun50i-h616-orangepi-zero3.dtb $ sudo dd bs=1k seek=8 if=u-boot-sunxi-with-spl-opizero3-4gb.bin of=/dev/sda 631+1 records in 631+1 records out 646523 bytes (647 kB, 631 KiB) copied, 0.156442 s, 4.1 MB/s Unfortunately, it does not boot beyond "Trying to boot from MMC1" which makes me believe that there is probably an issue with the u-boot/SPL for the 4GB board. 0 Quote
ag123 Posted August 8, 2023 Author Posted August 8, 2023 (edited) I did a little google search and stumbled into this https://linux-sunxi.org/Bootable_SD_card my guess is, when you get U-Boot SPL 2021.07-armbian (Jul 12 2023 - 10:04:49 +0000) DRAM: 4096 MiB Trying to boot from MMC1 At least a part of uboot started up on the SD / MMC card, as the 'SPL' part of uboot resides at 8 k address, in that seek=8, dd instruction. for the rest I'm not sure what happened. Edited August 8, 2023 by ag123 0 Quote
hmartin Posted August 8, 2023 Posted August 8, 2023 (edited) I carved u-boot out of the Jammy image from Google Drive (Orangepizero3_1.0.0_ubuntu_jammy_server_linux6.1.31.7z) and applied it to the bookworm image (along with copying the dtb, as instructed) and now it's booting. I updated the GitHub issue with my test results. I'll attach it here so that people don't have to download a 575MB image from Google Drive just to carve it (gunzip it first). u-boot-jammy.bin.gz Edited August 8, 2023 by hmartin 0 Quote
ag123 Posted August 8, 2023 Author Posted August 8, 2023 cool, congrats the uwe5622 wifi apparently have issues, while wifi scan using nmcli d wifi list initially works, attempts to connect to a station results in a dump recorded in dmesg, some abstracts: [ 6.931488] wifi ini path = /lib/firmware/wifi_2355b001_1ant.ini [ 6.957269] sprdwl:sprdwl_get_fw_info length mismatch: len_count=83, r_len=89 [ 6.957278] sprdwl:sprdwl_get_fw_info, drv_version=1, fw_version=2, compat_ver=0 [ 6.957282] sprdwl:chip_model:0x2355, chip_ver:0x0 [ 6.957286] sprdwl:fw_ver:35940, fw_std:0x7f, fw_capa:0x120fff [ 6.957290] sprdwl:mac_addr:24:b7:2a:46:13:f7 [ 6.957296] sprdwl:credit_capa:TX_WITH_CREDIT [ 6.957298] sprdwl:ott support:0 ... lots of verbose stuff like [ 146.832213] sdiohal:chn8 tx push old, cmdid=25, mstime=146361, record_time=146361 [ 146.832222] chn8 tx push old: 00 00 00 00 .........;...... [ 146.832273] WCN_ERR: mdbg_dump_data dump memory error:-110 [ 146.832280] WCN: mdbg dump bt modem 0 ok! [ 146.832284] WCN_ERR: read HCI_ARM_WR_RD_MODE reg error:-1 [ 146.832291] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 146.832295] WCN: mdbg dump bt_cmd buf 0 ok! [ 146.832298] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 146.832302] WCN: mdbg dump btevent buf 0 ok! [ 146.832306] WCN_ERR: mdbg_dump_data dump memory error:-1 ... [ 165.825379] NETDEV WATCHDOG: wlan0 (unisoc_wifi): transmit queue 0 timed out [ 165.825509] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x230/0x240 [ 165.825554] Modules linked in: algif_hash algif_skcipher af_alg bnep hci_uart btqca btrtl btbcm btintel bluetooth ecdh_generic ecc sunrpc lz4hc lz4 zram binfmt_misc polyval_ce polyval_generic sunxi_cir rc_core sunxi_cedrus(C) videobuf2_dma_contig v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc sprdwl_ng sunxi_addr cfg80211 sprdbt_tty rfkill uwe5622_bsp_sdio fuse dm_mod motorcomm dw_hdmi_cec dwmac_sun8i mdio_mux display_connector [ 165.825855] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 6.1.31-sunxi64 #1 [ 165.825874] Hardware name: OrangePi Zero3 (DT) [ 165.825885] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) so connect failed thereafter nmcli d wifi list returns an empty list I'm not sure how to recover from that, disable and enable the IF did not help sudo ip link set wlan0 down sudo ip link set wlan0 up nmcli d wifi list still returns an empty list lsmod ... uwe5622_bsp_sdio 204800 2 sprdbt_tty,sprdwl_ng uwe5622_bsp_sdio is linked to sprdbt_tty,sprdwl_ng, which in turns is linked to other stuff, hence it can't be simply 'rmmod'ed, reboot works, recovers the wifi scanning, but not connecting. (witnessed another dmesg dump after reboot, but initially "nmcli d wifi list" still works, it stops after a while and return an empty list 0 Quote
ag123 Posted August 8, 2023 Author Posted August 8, 2023 USB works, managed to mount a sd card in a usb card reader and examine some files. [ 890.861713] usb 1-1: new high-speed USB device number 4 using ehci-platform [ 891.021896] usb 1-1: New USB device found, idVendor=8564, idProduct=4000, bcdDevice= 0.04 [ 891.021926] usb 1-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2 [ 891.021944] usb 1-1: Product: Transcend [ 891.021957] usb 1-1: Manufacturer: TS-RDF5A [ 891.021971] usb 1-1: SerialNumber: 000000000004 [ 891.023086] usb-storage 1-1:1.0: USB Mass Storage device detected [ 891.023810] scsi host0: usb-storage 1-1:1.0 [ 891.066751] usbcore: registered new interface driver uas [ 892.041439] scsi 0:0:0:0: Direct-Access TS-RDF5A Transcend 0004 PQ: 0 ANSI: 6 [ 892.042515] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 892.413021] sd 0:0:0:0: [sda] 62552064 512-byte logical blocks: (32.0 GB/29.8 GiB) [ 892.414640] sd 0:0:0:0: [sda] Write Protect is off [ 892.414655] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00 [ 892.416125] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 892.424143] sda: sda1 0 Quote
ag123 Posted August 8, 2023 Author Posted August 8, 2023 I tried messing with hostapd, running the uwe5622 wifi in AP mode, trying to setup as a WiFi hotspot. used the 'generic' WPA passphrase based configs as like the 'simple' entries https://wiki.gentoo.org/wiki/Hostapd not much success, in dmesg [ 229.654023] (NULL net_device): sprdwl_uninit_fw failed! [ 229.654158] ieee80211 phy0: sprdwl_cfg80211_del_iface driver removing! [ 229.713879] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 229.717841] ieee80211 phy0: sprdwl_cfg80211_del_iface driver removing! [ 240.180745] ieee80211 phy0: sprdwl_cfg80211_del_iface driver removing! [ 240.217512] (NULL net_device): sprdwl_init_fw failed! [ 240.217801] ieee80211 phy0: sprdwl_cfg80211_del_iface driver removing! [ 339.310954] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! [ 339.311346] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! [ 341.419621] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! [ 341.420389] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! [ 343.663494] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! then in /var/log/syslog 2023-08-08T21:56:25.386610+08:00 orangepizero3 wpa_supplicant[910]: wlan0: CTRL-EVENT-SCAN-FAILED ret =-5 retry=1 2023-08-08T21:56:26.389340+08:00 orangepizero3 wpa_supplicant[910]: wlan0: CTRL-EVENT-SCAN-FAILED ret =-5 retry=1 2023-08-08T21:56:27.391984+08:00 orangepizero3 wpa_supplicant[910]: wlan0: CTRL-EVENT-SCAN-FAILED ret =-5 retry=1 2023-08-08T21:56:27.958806+08:00 orangepizero3 wpa_supplicant[910]: p2p-dev-wlan0: CTRL-EVENT-DSCP-PO LICY clear_all 2023-08-08T21:56:27.960039+08:00 orangepizero3 systemd[1]: Stopping wpa_supplicant.service - WPA supp licant... ^ those are consistent with nmcli d wifi list returning an empty list further down on hostapd 2023-08-08T21:58:17.537085+08:00 orangepizero3 systemd[1]: Starting hostapd.service - Access point and authentication server for Wi-Fi and Ethernet... 2023-08-08T21:58:17.637276+08:00 orangepizero3 hostapd[1775]: nl80211: Could not configure driver mode 2023-08-08T21:58:17.637497+08:00 orangepizero3 hostapd[1775]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 2023-08-08T21:58:17.637649+08:00 orangepizero3 hostapd[1775]: nl80211 driver initialization failed. 2023-08-08T21:58:17.637735+08:00 orangepizero3 hostapd[1775]: wlan0: interface state UNINITIALIZED->DISABLED 2023-08-08T21:58:17.637818+08:00 orangepizero3 hostapd[1775]: wlan0: AP-DISABLED 2023-08-08T21:58:17.637925+08:00 orangepizero3 hostapd[1775]: wlan0: CTRL-EVENT-TERMINATING 2023-08-08T21:58:17.638017+08:00 orangepizero3 hostapd[1775]: hostapd_free_hapd_data: Interface wlan0 wasn't started 2023-08-08T21:58:17.639465+08:00 orangepizero3 kernel: [ 339.310954] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! 2023-08-08T21:58:17.639480+08:00 orangepizero3 kernel: [ 339.311346] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! 2023-08-08T21:58:17.641144+08:00 orangepizero3 systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE 2023-08-08T21:58:17.641602+08:00 orangepizero3 systemd[1]: hostapd.service: Failed with result 'exit-code'. 0 Quote
ag123 Posted August 8, 2023 Author Posted August 8, 2023 (edited) much ado about serial terminal /dev/ttyS0 I've got a weird problem on the OPi Z3, thus far I've seen all the boot messages on the serial console, it turns out it is /dev/ttyS0. However, it doesn't 'accept/receive any inputs'. Hence, I can't login over serial tty. tried > systemctl stop serial-getty@ttyS0.service > echo hello > /dev/ttyS0 -- ok I saw that in the serial terminal :) > cat /dev/ttyS0 -- type something from the other end, nothing > systemctl start serial-getty@ttyS0.service -- ok login prompt appears in the serial terminal, but can't login I got so confused, I tried a 'loop back' test on my serial dongle, i.e. I took out the wire connected to RX pin on the Opi board, and connect it to TX on my usb-uart dongle. type something, ok i saw what i typed 'perfect' take out the wire, nothing, as expected next I plug that wire back to the RX pin on Opi board, oops something jerked on the connection, all gibberish, ok reboot, unplug power replug. Oops, now even ethernet goes out dark oh but suddenly I see the login prompt on my serial console again, type something, username, password voila logged in then to fix ethernet power down from serial console 'systemctl poweroff', unplug, replug again, retried a few times. finally, ... now I've got ethernet and serial tty console back it seemed to be a 'hardware' problem, a pin stuck 'low' or 'high'? well, I'd never know the mystery, but in case a usb-uart dongle is 'not working' try disconnect and reconnect the TX, RX, GND wires oh and about gibberish, like these 1st check your *baud rates*, it'd need to be 115200 bps and 8N1, thereafter it seemed to work 'quite perfect' my USB-uart dongle is actually an stm32f103 'blue pill' board https://stm32-base.org/boards/STM32F103C8T6-Blue-Pill.html running a stm32duino sketch https://github.com/rogerclarkmelbourne/Arduino_STM32/tree/master/STM32F1/libraries/A_STM32_Examples/examples/Communication/USB-uart-w-signals this sketch has got some bugs, hence I'd not recommend it. But in case anyone decides to use that post the questions in https://www.stm32duino.com/ and if i chanced upon it, i'd try to answer it there. but that there are 'cheap and good' usb-uart dongles, e.g. the (original, as in the chip) FT232 dongles and a search for "usb uart" in the usual online marketplaces Amazon, Ebay, Aliexpress etc would turn them up. https://www.amazon.com/s/ref=nb_sb_noss?field-keywords=usb+uart get 3.3v ones Edited August 8, 2023 by ag123 0 Quote
ag123 Posted August 9, 2023 Author Posted August 9, 2023 (edited) tried the Debian bookworm image from OrangePi dmesg [ 2282.163357] device wlan0 entered promiscuous mode [ 2282.229125] unisoc_wifi unisoc_wifi wlan0: sprdwl_change_beacon failed [ 2282.229151] unisoc_wifi unisoc_wifi wlan0: sprdwl_cfg80211_start_ap failed to start AP! [ 2282.242846] device wlan0 left promiscuous mode didn't work as well, so it has more to do with the wifi driver code, however, the errors are different. it'd seem there is also some conflicts with wpa_supplicant etc edit: I managed to get hostapd up on OrangePi Z3 using OrangePi's Debian bookworm image after all. apparently, 'limited' options are supported, 802.11g apparently seemed possible. # hostapd.conf # the interface used by the AP interface=wlan0 # bridge, this probably isn't necessary if you are not bridging bridge=br0 # "g" simply means 2.4GHz band hw_mode=g # the channel to use channel=5 # limit the frequencies used to those allowed in the country #ieee80211d=1 # the country code #country_code=US # 802.11n support #ieee80211n=1 # QoS support, also required for full speed on 802.11n/ac/ax #wmm_enabled=1 # the name of the AP ssid=orangepi # 1=wpa, 2=wep, 3=both auth_algs=1 # WPA2 only wpa=2 wpa_key_mgmt=WPA-PSK rsn_pairwise=CCMP wpa_passphrase=somepassword - NetworkManager has to be set as unmanaged for wlan0, nmcli dev set wlan0 managed no this is temporary there is a way to make the confit permanent as well https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-configuring_ip_networking_with_nmcli#configuring-networkmanager-to-ignore-certain-devices disable bluetooth and wpa_supplicant service to avoid conflicts systemctl stop bluetooth.service systemctl disable bluetooth.service systemctl stop wpa_supplicant.service systemctl disable wpa_supplicant.service it would normally be necessary to configure a dhcp server if there is no other on the network or configure a bridge and place wlan0 and the ethernet interface on it. Note that when you are playing with bridging etc, it is advisable to use the uart interface. it is super easy to hose the connected ethernet interface e.g. using nmcli network manager commands and after that there is 'no way' to access the board other than using uart (and perhaps usb gadget) interface. on the OrangePi images, connecting to AP seemed possible wlan0: connected to wifi "wlan0" wifi (unisoc_wifi), 80:A0:53:73:A3:89, hw, mtu 1500 inet4 192.168.2.158/24 route4 192.168.2.0/24 metric 600 route4 default via 192.168.2.1 metric 600 Edited August 9, 2023 by ag123 0 Quote
lk404 Posted August 12, 2023 Posted August 12, 2023 (edited) Maybe Linux 6.5 Kernal will contain support for orange pi zero 3. Looks promising. https://lore.kernel.org/lkml/20230804170856.1237202-1-andre.przywara@arm.com/ Edited August 12, 2023 by lk404 0 Quote
ag123 Posted August 15, 2023 Author Posted August 15, 2023 (edited) those look quite interesting, I'm thinking if it may be good to backport those changes back into 6.1.x used with Armbian currently. However, I'd think similarly, it is going to take a lot of work to do the same, including testing etc. another idea which may be quite interesting could be to try the new v6.5 kernel, compile from source, but thinking it through, the steps would likely to be quite similar with tests etc. e.g. that it is less likely to be a 'just works' setup and requires quite a bit of work to have all the peripherals working. Edited August 15, 2023 by ag123 0 Quote
LibertyGiraffe Posted August 24, 2023 Posted August 24, 2023 I have one of these, any updates on progress so far? 0 Quote
ag123 Posted August 24, 2023 Author Posted August 24, 2023 (edited) I'd guess you can try some of the unsupported , user build images a couple of posts back https://github.com/leeboby/armbian-images I've tried the Debian 'server' images on a 2GB board, and the findings are in the comments above. I've also tried the Orange Pi released images, those work better. But that among the surprises, it seemed there are some hardware problems even with those images released by Orange Pi. Ethernet is not working after a while and after a few reboots, things are totally jammed even on the serial console. But that to work with these boards, use a serial console with a usb-uart dongle, as you may not be able to access it over ethernet and/or wifi. quite some details is covered with the comments above. Edited August 24, 2023 by ag123 0 Quote
ag123 Posted September 18, 2023 Author Posted September 18, 2023 there is a new thread open on orange pi zero 3 0 Quote
ag123 Posted September 18, 2023 Author Posted September 18, 2023 (edited) i think orange pi zero 3 is after all gaining popularity as it is an 'upgraded' orange pi zero 2, 2+ with more dram, e.g. like up to 4 GB, that will make a lot of difference for some apps http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-3.html Edited September 18, 2023 by ag123 0 Quote
ag123 Posted September 18, 2023 Author Posted September 18, 2023 (edited) I've been trying the vendor images (non-armbian, but likely an armbian derivative) https://drive.google.com/drive/folders/1CJYrhHyyje9dEY4-t7JhcZBJfdAFBJro https://drive.google.com/drive/folders/10zlO-0mMz-fqRQOKAOWX-mQA_UbN_C1n and the wifi malfunctioned after running for some 1+ days, things got worse as initially i've been able to manually restart the wifi. then some other corruption creep in on the microsd card and I'm not sure the cause of it. note, non-armbian. for armbian, i think wifi etc is still 'work in progress', wifi isn't quite working yet as of last try, as noted in some earlier comments above. Edited September 18, 2023 by ag123 0 Quote
sortinousn Posted September 22, 2023 Posted September 22, 2023 I have the same issue on the OPi Zero 3. I used the Armbian image in the leeboy/armbian repository and followed the instructions on updating the dtb and bin file for the 4gig variant and it works. however WIFI does not and I can't connect at all. I see that there was an issue that was fixed earlier this week regarding the Orange Pi Wifi drivers and xradio not working. I think if someone was to pull the latest armbian and build the kernel it might work (I'm very new to all this, otherwise I would!). 0 Quote
SteeMan Posted September 22, 2023 Posted September 22, 2023 18 minutes ago, sortinousn said: I used the Armbian image in the leeboy/armbian repository That would not be an armbian image then if it didn't come from official Armbian sources. So this isn't really the place to discuss non-armbian builds. 2 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.