Search the Community

Hi everybody, I'm using the Armbian Buster mainline based kernel 5.10.y image on https://www.armbian.com/orange-pi-zero-plus-2-h3/ but I also tried the Focal one. I searched the forum deeply and I saw that someone in the past (forum post closed, otherwise I would have continued there) managed to have BT working by "faking" the /lib/firmware/brcm/brcmfmac43430-sdio.bin, that boot tries to load having error -2, copying the ap6212/fw_bcm43438a1.bin in its place. But it seems that it only works with legacy images, infact, with my mainline image I keep failing. Which legacy image should I look for? I was thinking that https://www.armbian.com/orange-pi-zero-plus-2-h3 already lists customized images, but I think I completely misunderstood. Thank you for any help

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?

Hi all! I make a board base on H3 CPU, I got a 8G EMMC under mmc2, and a ap6212a chip under mmc1. It boots successfully with the "armbian orange-pi-pc-plus", the emmc works fine while the wifi does not work, so, i changed the dts's mmc1 section based on the file 'sun8i-h3-orangepi-pc-plus.dts' in 'arch/arm/boot/dts/' directory, the mmc1 is changed to as follows: &mmc1 { vmmc-supply = <&reg_vcc3v3>; vqmmc-supply = <&reg_vcc3v3>; mmc-pwrseq = <&wifi_pwrseq>; bus-width = <4>; non-removable; status = "okay"; /* * Explicitly define the sdio device, so that we can add an ethernet * alias for it (which e.g. makes u-boot set a mac-address). */ sdio_wifi: sdio_wifi@1 { reg = <1>; compatible = "brcm,bcm4329-fmac"; interrupt-parent = <&pio>; interrupts = <6 10 IRQ_TYPE_LEVEL_HIGH>; /* PG10 / EINT10 */ interrupt-names = "host-wake"; }; wifi_pwrseq: wifi_pwrseq { compatible = "mmc-pwrseq-simple"; pinctrl-names = "default"; reset-gpios = <&r_pio 0 7 GPIO_ACTIVE_HIGH>; post-power-on-delay-ms = <200>; }; }; I refered to the dts file of orangepi-zero-plus2 whose mmc1 got a ap6212 chip too. After i changed it, I compile the new image and burned to the sd card and boot, but the wifi does not work at all. while i got the brcmfmac.ko loaded: # modprobe -a brcmfmac it succeed with no output, but i got nothing when i ran the command "dmesg | grep brcmfmac" Did I write the dts file wrong? or something else? Any advice is much appreciated, Thank you!

Hi, I'm trying to use bluetooth with the Mainline 4.11.9-sun8i armbian kernel (I also tried 4.11.7-sun8i). I activated ttyS3 (uart3) in armbianEnv.txt: verbosity=1 logo=disabled console=serial overlay_prefix=sun8i-h3 rootdev=UUID=59c35982-ddad-4bf0-8b72-a8974bfe88a6 rootfstype=ext4 overlays=uart3 spi-spidev param_uart3_rtscts=1 param_spidev_spi_bus=0 Unfortunately hciconfig -a does not find any device. I already tried to set the baudrate but no chance to get bluetooth alive: service bluetooth stop rfkill unblock all echo "0" > /sys/class/rfkill/rfkill0/state echo "1" > /sys/class/rfkill/rfkill0/state echo " " > /dev/ttyS3 hciattach /dev/ttyS3 bcm43xx 1500000 flow hciconfig hci0 up brings: bcm43xx_init Initialization timed out. Can't get device info: No such device root@nanopiair:~# Any idea whats going wrong here? Regards Bernhard

It seems that the latest Nano Pi Neo Air Boards and the relatively new Orange Pi Zero Plus 2 both use a modified version of the AP6212 WiFi+Bluetooth module, which is physically labelled as AP6212A. This new module apparently requires different drivers to operate. From my own experience, I was unable to get the internal WiFi module to work on a Nano Pi Neo Air (with AP6212A) using any of the Armbian distributions. However, I was able to get WiFi to work on that board with the Friendly Arm distribution at from https://www.mediafire.com/folder/sr5d0qpz774cs/NanoPi-NEO_Air#oc15bwqbuxgxe. I just received a second Nano Pi Neo Air from a different vendor, and this one was apparently one of the older boards because it came without a wifi antenna, and the WiFi module was labeled AP6212. The internal WiFi on this board worked perfectly with the legacy Armbian distribution for the Nano Pi Neo Air. I've seen elsewhere that there has been some trouble getting WiFi to work with the Orange Pi Zero Plus 2, and I suspect it is because of the change in the WiFi module. I personally know nothing of how to change or compile WiFi drivers, but would comparing the drivers in the Friendly Arm distribution help?

Good evening, I'm using a NanoPi Neo Air for streaming audio via bluetooth to a I2S sink. It's working in general but the audio data breaks away every second. It's always a on/off. I'm pretty sure it's connected to the speed between H3 - AP6212a but I'm not able to get it to work propably. I set the UART ttyS3 speed to 1500000 bit/s: My Fexedit looks like that: [bt_para] │ │bt_used = 1 │ │bt_uart_id = 3 │ │bt_uart_baud = 1500000 │ │bt_rst_n = port:PG13<1><default><default><0> │ │bt_wake = port:PA08<1><default><default><0> │ │bt_host_wake = port:PA07<0><default><default><0> │ │bt_host_wake_invert = 0 and I changed the AP6212a speed like this: systemctl stop bluetooth.service cp /lib/firmware/ap6212/bcm43438a1.hcd /etc/firmware/ap6212/4343A0.hcd echo "0" > /sys/class/rfkill/rfkill0/state echo "1" > /sys/class/rfkill/rfkill0/state echo " " > /dev/ttyS3 hciattach /dev/ttyS3 bcm43xx 1500000 bcm43xx_init Set Controller UART speed to 1500000 bit/s Flash firmware /etc/firmware/ap6212/4343A0.hcd Set Controller UART speed to 1500000 bit/s Device setup complete I already tried to go up 3000000 bit/s but the firmware flashing process stucks when I try it. Any idea why my I2S audio bus can't deliver the whole data? Regards Bernhard EDIT: output of hciconfig -a: root@nanopiair:~# hciconfig -a hci0: Type: BR/EDR Bus: UART BD Address: 43:29:B1:55:01:01 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:520 acl:0 sco:0 events:23 errors:0 TX bytes:1090 acl:0 sco:0 commands:23 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'nanopiair' Class: 0x00041c Service Classes: Unspecified Device Class: Audio/Video, Portable Audio HCI Version: 4.1 (0x7) Revision: 0xf2 LMP Version: 4.1 (0x7) Subversion: 0x2122 Manufacturer: Broadcom Corporation (15)