Jump to content

Search the Community

Showing results for tags 'orangepizeroplus2-h3'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. I just installed the image located here and am unable to get a bluetooth keyboard and mouse to connect. https://www.armbian.com/orange-pi-zero-plus-2-h3/ And used armbian-config -> Network -> Enable bluetooth. Here's the output of some common debugging commands I found in the forums. root@orangepizeroplus2-h3:~# lsusb Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@orangepizeroplus2-h3:~# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no root@orangepizeroplus2-h3:~# root@orangepizeroplus2-h3:~# sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2023-07-11 21:43:39 EDT; 21min ago Docs: man:bluetoothd(8) Main PID: 2945 (bluetoothd) Status: "Running" Tasks: 1 (limit: 828) Memory: 424.0K CPU: 283ms CGroup: /system.slice/bluetooth.service └─2945 /usr/lib/bluetooth/bluetoothd Jul 11 21:43:39 orangepizeroplus2-h3 systemd[1]: Starting Bluetooth service... Jul 11 21:43:39 orangepizeroplus2-h3 bluetoothd[2945]: Bluetooth daemon 5.64 Jul 11 21:43:39 orangepizeroplus2-h3 systemd[1]: Started Bluetooth service. Jul 11 21:43:39 orangepizeroplus2-h3 bluetoothd[2945]: Starting SDP server Jul 11 21:43:39 orangepizeroplus2-h3 bluetoothd[2945]: Bluetooth management interface 1.22 initialized root@orangepizeroplus2-h3:~# hcitool scan Device is not available: No such device root@orangepizeroplus2-h3:~# I also ran armbianmonitor -U > monitor.txt The results of which are attached to this message. It seems like the bluetooth service comes up, but it doesn't see any bluetooth devices. Can anyone point me in the right direction? monitor.txt
  2. Hi! I am trying to use Armbian 23.5 Jammy XFCE for new Orange Pi Zero Plus 2. I have TTL-USB connection through Serial port. In pyutty window i see log U-Boot SPL 2022.07-armbian (May 27 2023 - 19:28:04 +0000) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (May 27 2023 - 19:28:04 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero Plus 2 DRAM: 512 MiB Core: 65 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: No ethernet found. ** Reading file would overwrite reserved memory ** Failed to load '/boot/boot.bmp' There is no valid bmp file at the given address starting USB... Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1d000: USB EHCI 1.00 scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) 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 4121 bytes read in 4 ms (1005.9 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 180 bytes read in 3 ms (58.6 KiB/s) 16682525 bytes read in 693 ms (23 MiB/s) 8477464 bytes read in 355 ms (22.8 MiB/s) Found mainline kernel configuration 33498 bytes read in 10 ms (3.2 MiB/s) 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo 4185 bytes read in 6 ms (680.7 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 Kernel image @ 0x42000000 [ 0x000000 - 0x815b18 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 16682461 Bytes = 15.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49017000, end 49fffddd ... OK Loading Device Tree to 48fa6000, end 49016fff ... OK Starting kernel ... and this is all. My orange can not boot propertly. Is it possible to do something? Other image... Please help!
  3. Hello, Im trying to get 2 Uarts working on an Orange Pi Zero+2. Im using armbian Buster image for OPiZ+2 Linux orangepizeroplus2-h3 5.4.43-sunxi #20.05.2 SMP Mon Jun 1 18:26:22 CEST 2020 armv7l GNU/Linux I added UART1, UART2 and UART3 to armbianEnv.txt and was able to read / write on ttyS2 on pins 8 (PA00) and 10 (PA01). But couldnt find which pins ttyS1 or ttyS3 are on. I read at that UART 3 should be Tx PA13 Pin 24 Rx PA14 Pin 23 Is anyone able to suggest which pins I can use for a 2nd UART and is there a file I can look in to find the configuration for the UART Overlays ? Thanks Chris ______________________ Sorry, my mistake with wiring. ttyS3 does work on Tx PA13 Pin 24 Rx PA14 Pin 23 So armbian UART overlays working as required.
  4. Good afternoon, I run Armbian bullseye on my orangepi zeroplus2-h3. My wifi hotspot causes the OS to reboot sometimes, with the error "xradio WSM-ERR: bh error!>>> 0x0012 (16)" I use the NetworkManager conf files below for my wifi hotspot. echo """ [connection] id=mywifi uuid=58356325-7da4-4d1d-ad6b-54f33bfee335 type=wifi autoconnect=false interface-name=wlan0 permissions= [wifi] band=bg mac-address-blacklist= mode=ap ssid=IQLINK-1 [wifi-security] key-mgmt=wpa-psk psk=123456789 [ipv4] address1=192.168.43.1/24 dns-priority=2 dns-search= method=shared route-metric=2 [ipv6] addr-gen-mode=stable-privacy dns-priority=2 dns-search= method=auto route-metric=2 """ > /etc/NetworkManager/system-connections/mywifi.nmconnection echo """[main] dns=default rc-manager=file plugins=ifupdown,keyfile [ifupdown] managed=true [device] match-device=driver:wlan0 wifi.scan-rand-mac-address=no """ > /etc/NetworkManager/NetworkManager.conf I get the syslog error below and the OS reboot : Feb 2 13:17:37 myhostname kernel: [ 2583.698290] xradio WSM-ERR: bh error!>>> 0x0006 (12) Feb 2 13:17:37 myhostname kernel: [ 2583.698301] ------------[ cut here ]------------ Feb 2 13:17:37 myhostname kernel: [ 2583.698307] WARNING: CPU: 1 PID: 996 at drivers/net/wireless/xradio/ap.c:645 xradio_bss_info_changed+0x72f/0xb04 [xradio_wlan] Feb 2 13:17:37 myhostname kernel: [ 2583.698376] Modules linked in: binfmt_misc nft_chain_nat xt_MASQUERADE xt_state xt_conntrack ipt_REJECT nf_reject_ipv4 nft_counter xt_tcpudp nft_compat nf_tables nfnetlink nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 option usb_wwan qmi_wwan usbserial cdc_wdm lz4hc lz4 zram xradio_wlan mac80211 smsc cfg80211 nls_iso8859_1 sun4i_gpadc_iio industrialio smsc95xx cdc_acm usbnet sun8i_thermal rfkill libarc4 uio_pdrv_genirq uio cpufreq_dt usb_f_acm u_serial g_serial libcomposite ip_tables x_tables autofs4 pwrseq_simple sunxi phy_generic Feb 2 13:17:37 myhostname kernel: [ 2583.698679] CPU: 1 PID: 996 Comm: wpa_supplicant Tainted: G W 5.15.89-sunxi #trunk Feb 2 13:17:37 myhostname kernel: [ 2583.698694] Hardware name: Allwinner sun8i Family Feb 2 13:17:37 myhostname kernel: [ 2583.698708] [<c010cd21>] (unwind_backtrace) from [<c01095f5>] (show_stack+0x11/0x14) Feb 2 13:17:37 myhostname kernel: [ 2583.698737] [<c01095f5>] (show_stack) from [<c09e10b5>] (dump_stack_lvl+0x2b/0x34) Feb 2 13:17:37 myhostname kernel: [ 2583.698766] [<c09e10b5>] (dump_stack_lvl) from [<c011c439>] (__warn+0xad/0xc0) Feb 2 13:17:37 myhostname kernel: [ 2583.698792] [<c011c439>] (__warn) from [<c09dada7>] (warn_slowpath_fmt+0x43/0x7c) Feb 2 13:17:37 myhostname kernel: [ 2583.698813] [<c09dada7>] (warn_slowpath_fmt) from [<bf9d6f47>] (xradio_bss_info_changed+0x72f/0xb04 [xradio_wlan]) Feb 2 13:17:37 myhostname kernel: [ 2583.698873] [<bf9d6f47>] (xradio_bss_info_changed [xradio_wlan]) from [<bf940a79>] (ieee80211_bss_info_change_notify+0x79/0x174 [mac80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.699288] [<bf940a79>] (ieee80211_bss_info_change_notify [mac80211]) from [<bf952fd3>] (ieee80211_do_open+0x19f/0x5e8 [mac80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.699678] [<bf952fd3>] (ieee80211_do_open [mac80211]) from [<bf9535bf>] (ieee80211_if_change_type+0x147/0x254 [mac80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.700058] [<bf9535bf>] (ieee80211_if_change_type [mac80211]) from [<bf959373>] (ieee80211_change_iface+0x23/0x19c [mac80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.700441] [<bf959373>] (ieee80211_change_iface [mac80211]) from [<bf8c3ff7>] (cfg80211_change_iface+0x107/0x2e4 [cfg80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.701188] [<bf8c3ff7>] (cfg80211_change_iface [cfg80211]) from [<bf8e28cd>] (nl80211_set_interface+0xc9/0x164 [cfg80211]) Feb 2 13:17:37 myhostname kernel: [ 2583.701568] [<bf8e28cd>] (nl80211_set_interface [cfg80211]) from [<c08d9555>] (genl_rcv_msg+0x125/0x27c) Feb 2 13:17:37 myhostname kernel: [ 2583.701761] [<c08d9555>] (genl_rcv_msg) from [<c08d899d>] (netlink_rcv_skb+0x81/0xb4) Feb 2 13:17:37 myhostname kernel: [ 2583.701781] [<c08d899d>] (netlink_rcv_skb) from [<c08d8f9d>] (genl_rcv+0x21/0x30) Feb 2 13:17:37 myhostname kernel: [ 2583.701799] [<c08d8f9d>] (genl_rcv) from [<c08d8301>] (netlink_unicast+0x125/0x1a4) Feb 2 13:17:37 myhostname kernel: [ 2583.701816] [<c08d8301>] (netlink_unicast) from [<c08d851b>] (netlink_sendmsg+0x19b/0x36c) Feb 2 13:17:37 myhostname kernel: [ 2583.701834] [<c08d851b>] (netlink_sendmsg) from [<c08601ef>] (sock_sendmsg+0x23/0x2c) Feb 2 13:17:37 myhostname kernel: [ 2583.701858] [<c08601ef>] (sock_sendmsg) from [<c0860495>] (____sys_sendmsg+0x181/0x194) Feb 2 13:17:37 myhostname kernel: [ 2583.701877] [<c0860495>] (____sys_sendmsg) from [<c08615e5>] (___sys_sendmsg+0x49/0x64) Feb 2 13:17:37 myhostname kernel: [ 2583.701898] [<c08615e5>] (___sys_sendmsg) from [<c08618a7>] (__sys_sendmsg+0x37/0x58) Feb 2 13:17:37 myhostname kernel: [ 2583.701918] [<c08618a7>] (__sys_sendmsg) from [<c0100061>] (ret_fast_syscall+0x1/0x52) Feb 2 13:17:37 myhostname kernel: [ 2583.701939] Exception stack(0xcfdedfa8 to 0xcfdedff0) Feb 2 13:17:37 myhostname kernel: [ 2583.701954] dfa0: 01d9d868 01da4288 00000006 beb3f7c8 00000000 00000000 Feb 2 13:17:37 myhostname kernel: [ 2583.701968] dfc0: 01d9d868 01da4288 b6f651f0 00000128 b6f46000 00000001 00000004 01db6c68 Feb 2 13:17:37 myhostname kernel: [ 2583.701977] dfe0: 00000128 beb3f778 b6b5765f b6ad07e6 Feb 2 13:17:37 myhostname kernel: [ 2583.702054] ---[ end trace e554f90c3b6dcdf3 ]--- Feb 2 13:17:37 myhostname kernel: [ 2583.702077] xradio WSM-ERR: bh error!>>> 0x0012 (16) Feb 2 13:17:37 myhostname kernel: [ 2583.702087] xradio STA-ERR: wsm_set_tx_queue_params failed! Feb 2 13:17:37 myhostname kernel: [ 2583.702093] xradio WSM-ERR: bh error!>>> 0x0012 (16) Feb 2 13:17:37 myhostname kernel: [ 2583.702100] xradio STA-ERR: wsm_set_tx_queue_params failed! Feb 2 13:17:37 myhostname kernel: [ 2583.702106] xradio WSM-ERR: bh error!>>> 0x0012 (16) Feb 2 13:17:37 myhostname kernel: [ 2583.702112] xradio STA-ERR: wsm_set_tx_queue_params failed! Feb 2 13:17:37 myhostname kernel: [ 2583.702117] xradio WSM-ERR: bh error!>>> 0x0012 (16) Feb 2 13:17:37 myhostname kernel: [ 2583.702124] xradio STA-ERR: wsm_set_tx_queue_params failed! Feb 2 13:17:39 myhostname systemd[1]: systemd-rfkill.service: Succeeded. Thanks for your help. Clouvis
  5. Since volatile journald logging is done in-memory in /run/log/journal, and made persistent in /var/log.hdd/journal, the rsync of /var/log/journal in nand-sata-install no longer works because it is a symlink to /var/log.hdd/journal in the live system, and will create a circular symlink when booting from NAND. On the target image /var/log is the folder that is directory-mounted to /var/log.hdd during boot. I propose to exclude /var/log from the rsync, and rsync /var/log.hdd to /var/log on the target image. Another solution could be to exclude only /var/log/journal from the rsync, and create an empty /var/log/journal in the target image. Kind regards, Dennis
  6. I have been following a project on git hub and none of the commands work like the project as I have Armbian Focal installed. I need Armbian Bionic with Linux opiz2b 4.19.57-sunxi #5.90 SMP or 4.19.127-sunxi. I realise this is from 2019 and may be too old now to do anything with it. Is it possible to still get this? I can only find minimal versions in the archives that are much newer than this. I have to state here that I am a complete novice at this and so really have no idea what I am doing.
  7. Hello, I am not able to get the keyboard working. I have tried the downloads and compiling my own images. Bulleye is the only thing I can get to compile. There are error massages if I try to compile anything other than Bulleye.
  8. 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
  9. Orange Pi Zero 2 After installation Armbian 22.02 Focal stopped loading. help me please in UART outputs the following U-Boot SPL 2021.01-rc4-armbian (Jan 05 2021 - 03:01:27 +0100) DRAM: 1024 MiB
  10. Good day Armbian Forums! I'm having some trouble with builds of Armbian (up to and including 21.08.6 | kernel 5.10.60-sunxi) seeing wireless access points that are configured to channels 12 & 13 on my Orange Pi Zero Plus2 boards (H3 + 256mb RAM). Specifically, the default Android image (a generic Chinese-language Android multimedia system) that's loaded onto these boards can see and connect to access points that have been set to all channels (1-13) successfully, but any Armbian image I have tried fails to see anything (and subsequently cannot connect) to routers on channels 12 & 13. Due to the nature of this, I believe it may be a region setting or driver I'm missing here. Additionally, in my region (Australia) channels 12 & 13 are allowed, and routers routinely use them. With REGDOMAIN=AU set in /etc/default/crda (and system rebooted), running iw reg get reports country AU set correctly; then running iwlist wlan0 channel reports channels 1-13 are listed, which should be what we want. But then, if I run nmcli dev wifi, or iwlist wlan0 scan | grep SSID, or even use armbian-config's wifi utility, I do not see any routers set to channels 12 & 13. Manually connecting to the SSID via nmcli also fails - it just does not see any routers. Changing these routers to channel 11 and below, they appear with all three commands, and can be connected to successfully. What I have found: Wi-Fi chip is reported to be: "Broadcom BCM43438 combo and Bluetooth Low Energy" wifi (brcmfmac), 70:4A:0E:6C:0C:7C, hw, mtu 1500 If I cd to /usr/lib/firmware/brcm and run ls | grep 43438, a bcm43438-sdio.hcd file is there. Running dmesg | grep brcm command reports the following: root@orangepizeroplus2-h3:/home/julian# dmesg | grep brcm [ 8.368914] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 8.413375] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.xunlong,orangepi-zero-plus2-h3.txt failed with error -2 [ 8.413395] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43430-sdio.xunlong,orangepi-zero-plus2-h3.txt [ 9.060813] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 9.101374] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 9.107035] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2016 11:30:56 version 7.45.77.h8.4 FWID 01-ee8a6268 The above tells me that there's an issue with the driver and clm_blob [9.101374] and as such we may have limited channels available (and I'm hoping if that's the issue, it's fixable) - However, I have read elsewhere that perhaps the clm_blob is contained within the driver already and to ignore that message (telling us what we're experiencing). And, if that is case, is there a configuration file I'm missing to 'unlock' these channels? Research tells me it's either the driver or a misconfiguration. Unfortunately, due to the nature of their use (embedded applications in environments where higher channels may be required), requiring the end user to change their Wi-Fi channel is not a feasible option. Many thanks for your help!
  11. Before this I used to connect my APM 2.8.4 Flight controller to a Raspberry PI on Ground, Pin 8 and Pin 10. Today I tried to connect it to my orange pi zero plus2 H3. Pin 9, Pin 8 and Pin 10. On armbian-config toggle UART2. When i tried to connect to it using cat /dev/ttyS2 nothing came out. Once a while sent out some gibberish. I set the correct buadrate at 57600 and 91600 to no available. But I know the settings are correct because when I connect using USB through /dev/ttyACM0 it works. I tried ttyS1 and ttyS3 nothing came out of it. On Raspberry I had done this many times just by turning on the Serial Connection using raspi-config. Anyone have any solution for this?
  12. I am operating a headless data acquisition system with Orange Pi Zero Plus2. In the readings I collect among others data from a discrete separate 18B20 sensor and record the H3 CPU temperature. The 18B20 reading comes from the w1 kernel routine, the CPU temp is provided by armbian OS. With the new OS 5.8.16 I see a strange effect: reading .... the external sensor at /sys/bus/w1/devices/<sensID>/temperature and the CPU temperature at /etc/armbianmonitor/datasources/@soctemp it gives the same reading correct to a 1/100 degree. Even when the system runs low power - this cannot be true. I have no idea how these results can be mixed in the system. Reading the w1 result with checksum in 2 lines is identical to the result above. So I guess something is wrong with the armbian SocTemp reading even though it could be correct within a couple of degrees. Apart from the readings the Orange Pi Zero board operates fine without major problems. Any suggestions ?
  13. After recent upgrade of Debian Buster stable on Orange Pi Zero Plus 2 leds entries disappeared from class directory: Could anybody provide some guidance on how to get them back?
  14. I'm trying to set up an OPi Zero Plus 2 with Armbian Buster. As the board has no soldered USB connectors and mine is still in the mail, I was forced to do all this via the serial console via the three pins on the board. (So no nano or nmtui or anything that has an interface.) I run into a problem where a) I couldn't join my WiFi network and b) NetworkManager refused to believe I don't want to use IPv6. So I had to disable NetworkManager and go the wpa_supplicant route. So now I'm in the position that I got everything to work BUT I have to *manually* enable wpa_supplicant and then issue ifdown and ifup - all via the serial console - at every boot before it works. Basically I have to do this at *every* boot: > login as user # sudo su # wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf # ifdown wlan0 # ifup wlan0 After that I have a working IPv4 address and everything works, I can use ssh to connect to the OPi and it connects to the internet like it should (can 'apt update' etc.) The thing is, I REALLY don't want to keep it connected to another computer 24/7 and issue those commands every time it reboots. systemctl: https://pastebin.com/y8tk0DaN At this point, what should've been a 5min job (install armbian on the eMMC on the board) have turned into a 4h+ series of problems after problems after problems. I have followed some eight tutorials and advice that I've found on the subject and NONE of them have worked fully. Some at all. If I had the USB port, I'd most probably just re-flash the SD and start over and keep network manager and deal with whatever that comes with (I don't like NM, it gets in the way FAR too often if you want to manually do something), but I don't and it's impossible to use nmtui via the serial console. And it more or less works right now, only it doesn't start fine at reboot. There must be some easy way to get this to work from this point onward, right? ps. I can't paste armbianmonitor -U anywhere as it exceeds all limits on every paste site I have tried. EDIT: Managed to get armbianmonitor -u working, my bad for forgetting to "sudo" it. sorry.
  15. Hello, I have a OrangePi Zero+2 board and I am using i2c ports for connect several devices. Some i2c works OK. But I requiere r-i2c port. But the port does not work I have spend several days trying to make it works. Please, Can somebody help me?. This is turning into a headache. Thanks in advance.
  16. Hello everybody! I wanted to report that I was unable to boot with the "Bionic minimal 20.02.0-rc1" image "Bionic minimal 19.11.6 current" did not work either The red onboard is led flashing nothin else works. The Bionic download link on the top of the page is dead as well. With the same board, SD-card, power supply and USB cable I had no problem so far running the "Buster 20.02.0-rc1 current" image (beside some "armbian-configuration" flaws Did not try any further debugging so far any ideas? Andreas
  17. The Orange Pi Zero +2 H3 with USB hat will hard lock up on boot at "Starting Armbian Hardware Monitoring" when booting the latest (and at least one previous) available Buster (and Bullseye) images over HDMI console. Tested on multiple SD cards with the same result. (I will test with serial later, I do not have the time to remove it from the case at the moment; I figured I would post it now in case anyone had a chance to check before I could.)
  18. I installed Armbian_5.75_Orangepizeroplus2-h3_Debian_stretch_next_4.19.20. But it can't boot up. These image can boot up. Armbian_5.65_Orangepizeroplus2-h3_Debian_stretch_next_4.14.78 Armbian_5.69_Orangepizeroplus2-h3_Debian_stretch_next_4.19.13
  19. Hello, I have an OrangePi Zero H2 which until recently was running almost flawlessly with the Armbian_5.38_Debian_stretch_4_14_14 image. When I did a kernel upgrade using "apt-get dist-upgrade" (because I had earlier the error message ~"failed to Load Kernel Modules", and dist-upgrade was recommended), and this dist-upgrade failed inbetween (probably because of power consumption), the SD card was left in unbootable state. (error msg see below [1]) I concluded that the /boot directory was corrupted, so from a new installation of Armbian_5.38_Debian_stretch_4_14_14 made elsewhere I copied all the /boot directory over to my SD card. This made the (first) SD card again bootable in the first stages, but it now will not continue after "starting version 232". Is there a way to make the installation still working by copying parts of a fresh new installation of Armbian_5.38_Debian_stretch_4_14_14 over? I am asking because of the many changes made on the SD card in course of time. (Such rescue method could be of general interest.) Thanks (I have meanwhile a new power supply.) [1] ... Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 206 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 241 bytes read in 167 ms (1000 Bytes/s) 5400639 bytes read in 643 ms (8 MiB/s) 6972808 bytes read in 811 ms (8.2 MiB/s) Found mainline kernel configuration ** File not found /boot/dtb/sun8i-h2-plus-orangepi-zero.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ** File not found /boot/dtb/overlay/sun8i-h3-analog-codec.dtbo ** ** File not found /boot/dtb/overlay/sun8i-h3-usbhost2.dtbo ** ** File not found /boot/dtb/overlay/sun8i-h3-usbhost3.dtbo ** ** File not found /boot/dtb/overlay/sun8i-h3-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5400575 Bytes = 5.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... Device 0: Vendor: Generic Rev: 8.07 Prod: Flash Disk Type: Removable Hard Disk Capacity: 30200.0 MB = 29.4 GB (61849600 x 512) ... is now current device Scanning usb 0:1... _sun8i_emac_eth_init: Timeout missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-42-80-86-76-5c *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 *** ERROR: `serverip' not set
  20. Hi im using Orange Pi Zero +2 H3 with the current armbian image. 4.19 y i think... basically Im using HDMI out but i want to use the analog audio pins on my project. However the pins seem to be disabled and there doesnt appear any way to enable them. alsamixer only shows the allwinner,HDMI but no controls... Pulse audio panel seems less than helpfulp, lists Analogoutput but doesnt actually send any sound out through the pins. I warn you im not a linux power user. I can just about get around terminal but I dont know where files are off by heart or know exactly what and where to edit. So maybe a little hand holding :) Reading the forums a little people talk about editing a audio.conf file but having a look in the location they mention, no such file exists. if anyone knows this issue and a sure fire way to fix it please let me know :) Thanks Mangy_Dog
  21. Hello, I just use the Zero Plus 2 H3 with extension, using Armbian 5.83 but failed to get the combo to play the sound I use the command aplay -l but return no sound card found How to install driver for sound in this board?
  22. I'm trying to use PA18/PA19 for custom purposes. I need to put these pins to Input state without any pullups/pulldowns. What I can achieve is: to put these pins to input state via the command: gpio mode 30 in gpio mode 31 in ("tri" instead of "in" does not work, it accepts the command, but a multimeter shows the input is still high, as well as gpio readall) These pins are probably pulled high because they are I2C pins. I want to disable the I2C functionality but have not found any means to do so. I have tried this dts script: ##### /dts-v1/; / { compatible = "allwinner,sun8i-h3","allwinner,sun50i-h5","friendlyarm,nanopi-neo2"; fragment@0 { target-path = "/soc/pinctrl@1c20800"; __overlay__ { i2c1 { function = "gpio_in"; bias-high-impedance; }; }; }; }; ###### and had a look at the device tree after a reboot: dtc -I fs -O dts -o ./extracted.dts /proc/device-tree The values got inserted right, but pin behaviour did not change. What I also cannot do is to activate pulldown on those pins. It has no effect. Also tried a python library - https://github.com/duxingkei33/orangepi_PC_gpio_pyH3 - to no avail. Board is an Orange Pi Zero +2 with H3 processor. To sum it up: Input mode is working (with pullup still activated) Pulldown is not working Deactivating Pullup is not working Setting Pin to output mode and switching high/low is working Kernel: 4.19.38-sunxi
  23. Hello! Is there any way to config the frequency used by the DRAM driver when throttling takes place, or even better, disable the DRAM throttling at all? First of all, I have to say that that I'm pushing my Orange Pi Zero H3 board to run at very hot temperatures due to my CPU throttling settings so I can play some retro arcade games (I know I may burn it). But it seems the DRAM driver has its own throttling settings, and it takes place reducing DRAM frequency to 132Mhz. At such DRAM frequency there is flickering at HDMI output. May 13 18:30:31 inova-casa kernel: [15484.645810] [hotplug]: cpu(0) try to kill cpu(2) May 13 18:30:31 inova-casa kernel: [15484.645873] [hotplug]: cpu2 is killed! . May 13 18:30:31 inova-casa kernel: [15484.647486] [ddrfreq] DDR: 408000KHz->132000KHz start May 13 18:30:31 inova-casa kernel: [15484.647500] [ddrfreq] current cpu is cpu0 May 13 18:30:31 inova-casa kernel: [15484.648753] [ddrfreq] elapsed: 1087us May 13 18:30:31 inova-casa kernel: [15484.648773] [ddrfreq] DDR: 408000KHz->132000KHz ok! Unfortunately, manually setting the DRAM frequency don't work either. I mean, when I send the command, the frequency don't change. sudo echo 480000 >/sys/devices/platform/sunxi-ddrfreq/devfreq/sunxi-ddrfreq/cur_freq
  24. Hello... I've got an Orange Pi Zero Plus 2 H3 with Armbian Stretch. Kernel: 4.14.70-sunxi armbianEnv.txt: I did: cp -a /lib/firmware/ap6212/fw_bcm43438a1.bin /lib/firmware/brcm/brcmfmac43430-sdio.bin dmesg when searching for "brcm" gives me: [ 8.123186] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001 [ 8.256708] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 8 2016 15:31:47 version 7.46.57.4.ap.r4 (A1 Station/P2P) FWID 01-3621395e es6.c5.n4.a3 In /etc/default/ap6212 I have: PORT=ttyS1 But the script /etc/init.d/ap6212-bluetooth is failing... with the error "Initialization timed out." Is there any "how-to" for the Orange Pi Zero Plus 2 to get Bluetooth working?
  25. I am trying to get composite video fully working on an Orange Pi Zero Plus 2. I installed the legacy kernel image, and I've been able to turn on composite out, but I just get a blank screen on boot and there is no /dev/fb0. Is there anything else I have to do to enable the framebuffer. This is the (I believe) relevant portions of the script.fex file: [boot_disp] advert_disp = 0 auto_hpd = 1 output_type = 4 hdmi_channel = 0 hdmi_mode = 4 cvbs_channel = 1 cvbs_mode = 11 output_full = 1 hdmi_mode_check = 1 [disp_init] disp_init = 1 disp_mode = 1 screen0_output_type = 3 screen0_output_mode = 5 screen1_output_type = 2 screen1_output_mode = 14 fb0_framebuffer_num = 2 fb0_format = 10 fb0_pixel_sequence = 0 fb0_scaler_mode_enable = 1 fb1_framebuffer_num = 2 fb1_format = 10 fb1_pixel_sequence = 0 fb1_scaler_mode_enable = 1 [hdmi_para] hdmi_used = 0 hdpc_enable = 0 [tv_para] tv_used = 1 tv_dac_used = 1 tv_dac_src0 = 0 these are some possible relevant lines from boot. [ 0.000000] Kernel command line: root=UUID=ab03f9a3-0ba3-4236-8857-33f3229b7a85 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 monitor=composite-ntsc panic=10 consoleblank=0 loglevel=1 ubootpart=75ceecdb-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=96M cgroup_enable=memory swapaccount=1 [ 0.614087] [DISP]disp_module_init [ 0.614413] cmdline,init_disp= [ 0.614448] cmdline,disp= [ 0.615200] [DISP]disp_module_init finish [ 1.029299] cmdline,disp= [ 1.029629] [DISP] disp_init_tv,line:539:screen 0 do not support TV TYPE! [ 1.029647] [DISP] bsp_disp_tv_register,line:998:'ptv is null [ 1.029710] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr1<-->device1, type=2, mode=14
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines