Search the Community

https://forum.armbian.com/index.php?/search/&q=AP6212a There were some discussions and AFAIK I made some dirty hack to fix this firmware mess. It looks like it's not working ok.

On Black Hat 2017 security researcher Nitay Artenstein showed a vulnerability affecting millions of smartphones he called BroadPwn. The bug/vulnerability sits inside the firmware blobs but I didn't pay that much attention since I thought it would be related to recent smartphones and at least the one I use still receives full security fix support now in the 5th year. But when I heard that latest Raspbian release contains a fix for BroadPwn (RPi 3 and Zero W use BCM43438 to provide wireless capabilities) I asked myself immediately a question: http://www.cnx-software.com/2017/08/17/raspbian-for-raspberry-pi-boards-gets-upgraded-to-debian-stretch/#comment-545270 I booted my RPi 3, added the stretch repo, did an apt-update and checked (after updating the kernel): root@raspberrypi:~# apt list --upgradable Listing... Done device-tree-compiler/testing 1.4.4-1 armhf [upgradable from: 1.4.1-1+rpi1] dnsmasq/testing 2.76-5+rpi2 all [upgradable from: 2.76-5+rpi1] dnsmasq-base/testing 2.76-5+rpi2 armhf [upgradable from: 2.76-5+rpi1] libcairo2/testing 1.14.8-1+rpi1 armhf [upgradable from: 1.14.0-2.1+deb8u2+rpi1] libpam-modules/testing 1.1.8-3.6+rpi1 armhf [upgradable from: 1.1.8-3.1+deb8u2+rpi3] libpam-modules-bin/testing 1.1.8-3.6+rpi1 armhf [upgradable from: 1.1.8-3.1+deb8u2+rpi3] libpam-runtime/testing 1.1.8-3.6+rpi1 all [upgradable from: 1.1.8-3.1+deb8u2+rpi3] libpam0g/testing 1.1.8-3.6+rpi1 armhf [upgradable from: 1.1.8-3.1+deb8u2+rpi3] libraspberrypi-bin/testing 1.20170811-1 armhf [upgradable from: 1.20170703-1] libraspberrypi0/testing 1.20170811-1 armhf [upgradable from: 1.20170703-1] openmediavault/erasmus 3.0.87 all [upgradable from: 3.0.85] raspberrypi-bootloader/testing 1.20170811-1 armhf [upgradable from: 1.20170703-1] If I understand correctly a BroadPwn fix has to be applied to firmware blobs. Since the above is an Armbian userland combined with RPi kernel I checked Raspbian's firmware package: https://pastebin.com/bMWqwxcy So if the most common Wi-Fi chips on supported boards are affected (since AP6212 is just a BCM43438 A0 while AP6212A is an A1 BCM43438) we might want to provide an updated armbian-firmware package asapissimo, true?

Well, again talking to myself I put the exchanged firmware files online: http://kaiser-edv.de/tmp/NumpU4/brcmfmac43430-sdio-broadpwn-fix.tar Is anyone here with the following combination able to test whether exchanging this firmware file works or not? Board with AP6212 (not AP6212A as far as I understood) Mainline kernel and everything configured correctly to activate Wi-Fi) test with /lib/firmware/brcm/brcmfmac43430-sdio.bin as it's part of armbian-firmware package and from the link above later (collecting 'dmesg | grep brcm' of course) No idea whether /lib/firmware/brcm/brcmfmac43430-sdio.txt must also be replaced...

Obviously, I've missed the clearly visible 8198FTV, I was searching for the AP6212A

Thanks Zaror. The obvious question: Do you know of any plans to implement BT on the AP6212A in the near future? I'll carry on trying to work it out. It seems that some have BT running on the Nano Pi with AP6212/A chip?

Hi Igor, I've been trying to get BT running on the OPI Z+2 H5. Think I'm rather confused. I'm trying to connect the AP6212A BT to uart3 (ttyS3) with no luck. The new firmware seems to be correctly located in /lib/firmware/ap6212 and /etc/firmware/ap6212 and /lib/firmware/brcm. I tried using overlay to enable uart3, see below: /boot/armbianEnv.txt verbosity=1 console=both overlay_prefix=sun50i-h5 rootdev=UUID=578b81e7-8242-47b1-ade8-b92dd7aa9e94 rootfstype=ext4 overlays=uart3 param_uart3_rtscts=1 However, I'm not sure how to enable uart3? I also noticed the "default ttyS1 port" in /etc/init.d/ap6212-bluetooth: # Select tty port if [ -z "$PORT" ]; then log_warning_msg "No PORT set in /etc/default/ap6212, will use ttyS1" PORT="ttyS1" Also, in /etc/default/ap6212: # # Default it is called to be uncertain wich MAC address the chipset has. # Therefore it is recommendable to set the MAC address manually. # This can be done by setting the variable MAC_ADDR with a chosen value. # If this variable is empty or not set the default 11:22:33:44:55:66 will be chosen. MAC_ADDR=43:29:B1:55:01:01 # PORT=ttyS1 I read the following (I don't know if this is the same for the H5 version): Overlay pinmux conflicts Some controllers may share the SoC pins in some configurations. For example on Allwinner H3 UART 3 and SPI 1 use the same pins - PA13, PA14, PA15, PA16. The result from : root@orangepizeroplus2:/boot# setserial -g /dev/ttyS* /dev/ttyS0, UART: undefined, Port: 0x0000, IRQ: 27 /dev/ttyS1, UART: unknown, Port: 0x0000, IRQ: 0 /dev/ttyS2, UART: unknown, Port: 0x0000, IRQ: 0 /dev/ttyS3, UART: unknown, Port: 0x0000, IRQ: 0 During boot there are two failures: [ OK ] Reached target Slices. Mounting POSIX Message Queue File System... Starting Nameserver information manager... Mounting Huge Pages File System... Starting Restore / save the current clock... Starting Load Kernel Modules... Starting Create list of required st... nodes for the current kernel... Mounting Debug File System... [ OK ] Created slice system-serial\x2dgetty.slice. Starting Set console keymap... Starting Remount Root and Kernel File Systems... [ OK ] Mounted Debug File System. [ OK ] Mounted Huge Pages File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Started Restore / save the current clock. [FAILED] Failed to start Load Kernel Modules. See 'systemctl status systemd-modules-load.service' for details. [ OK ] Started Create list of required sta...ce nodes for the current kernel. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Nameserver information manager. [ OK ] Started Set console keymap. and... [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Started Raise network interfaces. [FAILED] Failed to start LSB: Patch firmware for ap6212 adapter. See 'systemctl status ap6212-bluetooth.service' for details. [ OK ] Started Login Service. Stopping LSB: Starts LIRC daemon.... Starting LSB: set CPUFreq kernel parameters... However, if I edit /etc/default/ap6212 and change ttyS1 to ttyS3, the boot error ([FAILED] Failed to start LSB: Patch firmware for ap6212 adapter.) disappears : /etc/default/ap6212: # # Default it is called to be uncertain wich MAC address the chipset has. # Therefore it is recommendable to set the MAC address manually. # This can be done by setting the variable MAC_ADDR with a chosen value. # If this variable is empty or not set the default 11:22:33:44:55:66 will be ch$ MAC_ADDR=43:29:B1:55:01:01 # #PORT=ttyS1 PORT=ttyS3 Boot: [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Started Raise network interfaces. [ OK ] Started LSB: Starts LIRC daemon.. [ OK ] Started Login Service. Stopping LSB: Starts LIRC daemon.... Starting LSB: set CPUFreq kernel parameters... Starting Set console scheme... [ OK ] Started Set console scheme. [ OK ] Started LSB: set CPUFreq kernel parameters. And now ttyS3 at least has an IRQ assigned: root@orangepizeroplus2:~# setserial -g /dev/ttyS* /dev/ttyS0, UART: undefined, Port: 0x0000, IRQ: 27 /dev/ttyS1, UART: unknown, Port: 0x0000, IRQ: 0 /dev/ttyS2, UART: unknown, Port: 0x0000, IRQ: 0 /dev/ttyS3, UART: undefined, Port: 0x0000, IRQ: 28 But if I run: root@orangepizeroplus2:/etc/init.d# ./ap6212-bluetooth start [....] Starting ap6212-bluetooth (via systemctl): ap6212-bluetooth.service[ 902.857904] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) Job for ap6212-bluetooth.service failed because the control process exited with error code. See "systemctl status ap6212-bluetooth.service" and "journalctl -xe" for details. failed! and: root@orangepizeroplus2:/etc/init.d# systemctl status ap6212-bluetooth.service ● ap6212-bluetooth.service - LSB: Patch firmware for ap6212 adapter Loaded: loaded (/etc/init.d/ap6212-bluetooth; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2017-07-30 17:40:38 UTC; 1min 28s ago Docs: man:systemd-sysv-generator(8) Process: 1467 ExecStart=/etc/init.d/ap6212-bluetooth start (code=exited, status=1/FAILURE) Jul 30 17:40:17 orangepizeroplus2 systemd[1]: Starting LSB: Patch firmware for ap6212 adapter... Jul 30 17:40:28 orangepizeroplus2 ap6212-bluetooth[1467]: Initialization timed out. Jul 30 17:40:28 orangepizeroplus2 ap6212-bluetooth[1467]: bcm43xx_init Jul 30 17:40:38 orangepizeroplus2 ap6212-bluetooth[1467]: Initialization timed out. Jul 30 17:40:38 orangepizeroplus2 ap6212-bluetooth[1467]: bcm43xx_init Jul 30 17:40:38 orangepizeroplus2 ap6212-bluetooth[1467]: Can't get device info: No such device Jul 30 17:40:38 orangepizeroplus2 systemd[1]: ap6212-bluetooth.service: Control process exited, code=exited status=1 Jul 30 17:40:38 orangepizeroplus2 systemd[1]: Failed to start LSB: Patch firmware for ap6212 adapter. Jul 30 17:40:38 orangepizeroplus2 systemd[1]: ap6212-bluetooth.service: Unit entered failed state. Jul 30 17:40:38 orangepizeroplus2 systemd[1]: ap6212-bluetooth.service: Failed with result 'exit-code'. and: root@orangepizeroplus2:/etc/init.d# journalctl -xe -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-rfkill.service has finished starting up. -- -- The start-up result is done. Jul 30 17:40:18 orangepizeroplus2 wpa_supplicant[730]: p2p-dev-wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Jul 30 17:40:18 orangepizeroplus2 kernel: brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) Jul 30 17:40:18 orangepizeroplus2 NetworkManager[591]: <info> [1501436418.4796] device (wlan0): supplicant interface state: disabled -> scannin Jul 30 17:40:18 orangepizeroplus2 wpa_supplicant[730]: wlan0: Trying to associate with SSID 'mondevices' Jul 30 17:40:19 orangepizeroplus2 NetworkManager[591]: <info> [1501436419.0117] device (wlan0): supplicant interface state: scanning -> associa Jul 30 17:40:19 orangepizeroplus2 wpa_supplicant[730]: wlan0: Associated with 14:cc:20:93:36:c8 Jul 30 17:40:19 orangepizeroplus2 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jul 30 17:40:19 orangepizeroplus2 NetworkManager[591]: <info> [1501436419.5373] device (wlan0): supplicant interface state: associating -> 4-wa Jul 30 17:40:19 orangepizeroplus2 wpa_supplicant[730]: wlan0: WPA: Key negotiation completed with 14:cc:20:93:36:c8 [PTK=CCMP GTK=CCMP] Jul 30 17:40:19 orangepizeroplus2 wpa_supplicant[730]: wlan0: CTRL-EVENT-CONNECTED - Connection to 14:cc:20:93:36:c8 completed [id=0 id_str=] Jul 30 17:40:19 orangepizeroplus2 NetworkManager[591]: <info> [1501436419.5467] device (wlan0): supplicant interface state: 4-way handshake -> Jul 30 17:40:21 orangepizeroplus2 ntpd[762]: Deleting interface #5 wlan0, fe80::8623:d245:4363:1493%2#123, interface stats: received=0, sent=0, Jul 30 17:40:28 orangepizeroplus2 ap6212-bluetooth[1467]: Initialization timed out. Jul 30 17:40:28 orangepizeroplus2 ap6212-bluetooth[1467]: bcm43xx_init Jul 30 17:40:38 orangepizeroplus2 ap6212-bluetooth[1467]: Initialization timed out. Jul 30 17:40:38 orangepizeroplus2 ap6212-bluetooth[1467]: bcm43xx_init Jul 30 17:40:38 orangepizeroplus2 ap6212-bluetooth[1467]: Can't get device info: No such device Jul 30 17:40:38 orangepizeroplus2 systemd[1]: ap6212-bluetooth.service: Control process exited, code=exited status=1 Jul 30 17:40:38 orangepizeroplus2 systemd[1]: Failed to start LSB: Patch firmware for ap6212 adapter. -- Subject: Unit ap6212-bluetooth.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ap6212-bluetooth.service has failed. -- -- The result is failed. Jul 30 17:40:38 orangepizeroplus2 systemd[1]: ap6212-bluetooth.service: Unit entered failed state. Jul 30 17:40:38 orangepizeroplus2 systemd[1]: ap6212-bluetooth.service: Failed with result 'exit-code'. Jul 30 17:42:43 orangepizeroplus2 ntpd[762]: xxx.xx.xx.x local addr 192.168.0.105 -> <null> Jul 30 17:42:43 orangepizeroplus2 ntpd[762]: xxx.xx.xx.x local addr 192.168.0.105 -> <null> Jul 30 17:42:43 orangepizeroplus2 ntpd[762]: xxx.xx.xx.x local addr 192.168.0.105 -> <null> Jul 30 17:42:43 orangepizeroplus2 ntpd[762]: xxx.xx.xx.x local addr 192.168.0.105 -> <null> So it looks like this is failing due to the ttyS3 issue. If I run: root@orangepizeroplus2:/etc/init.d# hciattach /dev/ttyS3 bcm43xx 115200 flow bdaddr 11:22:33:44:55:66 bcm43xx_init Initialization timed out. Lastly I tried changing ttyS1 to ttyS3 in /etc/init.d/ap6212-bluetooth: # Select tty port if [ -z "$PORT" ]; then #log_warning_msg "No PORT set in /etc/default/ap6212, will use ttyS1" #PORT="ttyS1" log_warning_msg "No PORT set in /etc/default/ap6212, will use ttyS3" PORT="ttyS3" I looked at the /boot/dtb-4.11.10-sun50iw2/allwinner/overlay/sun50i-h5-fixup.scr file. Where do the phandle HEX numbers come from? I see that in /boot/dtb/allwinner/sun50i-h5-orangepi-zeroplus.dtb uart1 rts and cts are specified: uart1_rts_cts { pins = "PG8", "PG9"; function = "uart1"; linux,phandle = <0x33>; phandle = <0x33>; So, are these phandle assignments overridden by /boot/dtb-4.11.10-sun50iw2/allwinner/overlay/sun50i-h5-fixup.scr overlay file? if test "${param_uart1_rtscts}" = "1"; then fdt get value tmp_phandle1 /soc/pinctrl@01c20800/uart1 phandle fdt get value tmp_phandle2 /soc/pinctrl@01c20800/uart1_rts_cts phandle fdt set /soc/serial@01c28400 pinctrl-names "default" "default" fdt set /soc/serial@01c28400 pinctrl-0 "<${tmp_phandle1}>" fdt set /soc/serial@01c28400 pinctrl-1 "<${tmp_phandle2}>" env delete tmp_phandle1 tmp_phandle2 Thanks for any advice you can supply to get the BT running.....

I didn't realise that the heat issue was related to the original OPI Zero but having re-read the posting I see that it was. I did see the thread regarding the change from AP6212 to AP6212A however and the comments in this thread have put my mind at rest. High speed connectivity isn't required for my unit but stability is. The links to the tests indicate that wifi perfomance is more than adequate. I shall go with the OPI-Zero Plus 2 for the moment and change the design to suit. Thanks again for the comments.

Huh? Is OPi Zero Plus 2 also affected by 'heat issues' (which according to Xunlong are just different thermal calibration issues -- no idea since not having an OPi Zero 1.4 around. Also 'Wi-Fi' issues should be fixed by the hardware change on PCB rev 1.4 -- no idea since... no one is testing this for reasons unknown to me). NanoPi Air as well as OPi Zero Plus 2 both feature AP6212A Wi-Fi which works pretty nice also with mainline kernel (maybe a 'firmware fix' -- renaming a file -- needed). And I found Wi-Fi on OPi Lite relatively performant (given it's 1T1R 2.4GHz Wi-Fi).

Thanks Igor. Pointing me to search for AP6212 led to other posts and post topics and I ended up at this post: https://forum.armbian.com/index.php?/topic/4578-example-support-proposal-for-rock64/& Although this is kind of off topic, I started this post explaining having tried the ESP32, CHIP, CHIP PRO and now the Orange Pi Zero+2 H5. I now have 5 x ESP32, 3 x CHIP, 7 x CHIP PRO (+ development kit) and 3 x OPI Z+2 H5. I found @TKaiser Board Support Proposal particularly interesting. Obviously I'm a newbie here and knew nothing about Armbian until purchasing the OPI boards just a few days ago, I wish I had known about Armbian sooner then perhaps I would not have such a large graveyard of latest tech SBC's. To the point of @TKaiser's post, as a "user" and "newbie" the information Armbian can provide PRIOR to a user purchasing a new, latest and greatest board based on Google searches and technical specs, is invaluable IMO. On each of the above boards I hit a brick wall and cannot continue development due to support issues. I read that it would have been a smarter choice to purchase the OPI Z+2 H3 version rather than the H5 version. My project specifically requires Linux OS, WIFI, BLE, GPIO and Camera. It also needs to be very inexpensive. You guys are so knowledgeable about the intricacies of each board you support (whether good or bad) that as a user I could make a far more informed decision based on your board recommendations which in turn are based on my board functionality requirements. At this point, referring to the specific board requirements above, should I add the OPI Z+2 H5 to the graveyard and go for the OPI Z+2 H3 board? If so, do you know if the H3 board definitely supports Bluetooth Low Energy? I presume the H3 board uses the older and inferior performing AP6212 chip rather than the AP6212A chip? FYI: The CHIP was the only board that provided all required functions albeit camera operation via USB which is just too slow FPS. Later to find out the CHIP uses low quality components, is not recommended for commercial use and is not warranted (after all, it's only $9)!! They recommended the CHIP PRO. Unfortunately, on the CHIP PRO the CSI camera interface seems completely unsupported and the CSI hardware connection looks a little weird when compared to other CSI boards and cameras. Thanks yet again for all your help.

Got anybody here a idea where the 1500000 bit/s come from? It's not a regular baud rate and AP6212a datasheet tells me that this chip can handle up to 3 Mbps. So why can't I use 3000000 bit/s? Regards

Wow!! Thanks yet again re: Smelly and buggy 3.10.x Kernel. I'll re-install the Armbian OS and attempt some debugging re: AP6212A firmware. Do you recommend the latest nightly version and to keep an eye on the progress for relevant fixes (USB OTG (host), Bluetooth LE and CSI) followed by a re-install each time? You mentioned in another post that the "Failure" to load the AP6212 files related only to bluetooth which makes sense as WIFI is working fine.

The problem with OS from OrangePi is that it's v0.2 and its smelly and buggy 3.10.x kernel will stay there forever. There is one crazy issue with AP6212A and AP6212. They both seek for the firmware in the same place while they need a different one. Type AP6212A in a search to get insights. I have no idea if low energy Bluetooth functions are working - we usually end our testings when some HID device is able to connect. In any case you have way more chances of success with modern kernel 4.12.x, which is at least supported and is getting fixes on daily base. Not much is usable from that kernel since its too big difference. Most of core functions were written from scratch - you can monitor progress here.

Thanks for your replies. A litte more progress by installing the debian OS from orangepi.org (debian_jessie_zeroplus2_H5_V0_2.rar). This version enables the micro USB OTG (host mode) for use with USB hub, mouse and keyboard, WIFI worked immediately from the desktop setup. Unfortunately, bluetooth seems non-existent on this version. Having read the Armbian details on the AP6212A WIFI and bluetooth combo chip, I'm assuming the AP6212A firmware files are pretty much standard regardless of which OS is running? I don't see the firmware files even exist in the /lib/firmware/ folder for the above OS. To get bluetooth and bluetooth Low Energy working, is it a matter of configuration settings to enable the AP6212A's bluetooth function? I realize of course, the above OS is not Armbian, thought it may help with the micro USB OTG (host) setup in the Armbian OS. Any ideas on how bluetooth can be enabled, followed by bluetooth Low Energy function/setup? Thanks again....

I'm using Nano Pi Neo Air. AP6212a is located on ttyS3. It's working under 3.4 kernel. BT-WAKE-AP and AP-WAKE-BT is a good hint. Thank you for this! Can you tell me how I activate these pins in DT? I guess you are talking about Pins PA7 and PA8? Thanks for your help.

Voltage regulation is also different (none on the engineering samples, after I explained to FriendlyELEC's Weidong that voltage regulation just don't work with Allwinner's shitty legacy kernel but there's no problem with mainline he said they want to redesign NEO Plus2 to switch between 1.1V and 1.3V again and NanoPi M1 Plus 2 should even get I2C accessible voltage regulation like on larger Orange Pis. Don't fool yourself. Ampak just recently started to mark AP6212A correctly, the AP6212A chips we find on many boards within the last half year all show 'AP6212' instead. It's only a matter of firmware (and maybe still a tweak is needed with mainline kernel, didn't had a look since 1T1R/2.4GHz Wi-Fi is low performing crap anyway)

Thank you for your fast reply. I kinda got it working. I thought it's enough to set the uart speed once but you need to make it on every boot. So I wrote startscript what sets the uart speed to 1500000 bit/s and it's working without timeouts. It's not my goal yet because the AP6212a datasheet says that it's possible to work with 3000000 bit/s. Unfortunately I'm not able to set this speed. Furthermore Bluteooth audio streaming is not running very stable. I know it from Raspberry Pi with 4.x kernel and it was really easy and smooth. It seems that it's a problem connected to 3.4 kernel. Can you give me any info about how to activate blutooth on 4.x kernel? I already tried to make it work but with 4.x mainline release you don't have this fex file to activate the hardware modules. I got stucked with building a new device tree. Maybe you can give me some more info about it? Do you know when a 4.x kernel will be officially available for Nano Pi Neo Air? Thanks a lot Regards Bernhard

I have exactly the same problem on Orange Pi Zero Plus 2 H3 (the same Broadcom AP6212a) phone is connected via bluetooth, in pulse I can see it as A2DP source but the audio is cut off each and every second in my case I'm not using I2S - so it is not related with I2S but with bluetooth or pulse Any idea how to fix this is appreciated. thanks

And mine has got an AP6212 without the A The pictures on FriendlyARM site show an AP6212A on the PCB, but the features listing and the pdf schematics clearly indicate AP6212

Somebody needs to create proper u-boot configuration and kernel device tree BTW. Engineering samples, which we received, are different - they don't have AP6212A but "beloved" XR819 known from Opi Zero. I assume the rest is the same, but it has to be checked.

Thanks! Just getting my bearings - compiled u-boot and 3.14.29 kernel using the khadas github's Ubuntu branches a few days ago - so luckily I had created a bootable SD already using dd. I have been running Armbian_5.27_S9xxx_Ubuntu_xenial_3.14.29_mate_20170619 from SD so I already enabled multiboot as well. WOW this things runs great... Will play with this image today. Oh also to get the firmware for Khadas VIM Wifi working I edited a couple files per these patches I found: https://github.com/khadas/LibreELEC.tv/blob/Vim-devel/packages/linux-firmware/wlan-firmware/patches/wlan-firmware-03-AP6212A-AP6255-firmware-auto-select.patch https://github.com/khadas/LibreELEC.tv/blob/Vim-devel/packages/linux-firmware/wlan-firmware/patches/wlan-firmware-04-AP6212-firmware-auto-select.patch I have the Pro (2GB/16GB EMMC) which uses AP6255 - but brought in support for AP6212 too. After this running sudo modprobe dhd Got the wifi up and running

I was not talking about votes/polls. I was talking about why we behave like idiots and start to support boards solely based on the fact that a hardware vendor sent us dev samples worth few bucks. Again (!!!) two examples: https://forum.armbian.com/index.php?/topic/4378-nightly-images/&do=findComment&comment=33601 (why do we start with something like Orange Pi Zero Plus 2 H5, it makes absolutely no sense at all --> Armbian no, Android yes/don't care) Again (!!!) my proposal is not to start as soon as someone sends us hardware but to open a new thread in not yet existing 'Board Bring Up Discussion' subforum. There the person who's interested in a specific device has to elaborate on why it would be a good idea to support the specific hardware or whether it's not (vendor behaviour being one of the potential reasons. If a vendor doesn't provide correct specs/schematics, advertises with wrong numbers, doesn't fix documentation mistakes even if told multiple times, sends out partially defective dev samples, doesn't document timely if he exchanged relevant hardware parts -- I'm talking about AP6212 vs. AP6212A here -- that's a good reason to avoid that hardware and document this at the same time so surprised users get the idea why developers consider dealing with a specific hardware not worth their time. That way we might even see some vendors improving over time if their irresponsible behaviour is documented again and again). I'm still only talking about a group decision based on a real discussion when/whether to start working on a device or not. No polls/votes, especially no user polls! If tomorrow a hypothetical 'PicoPi Bullcrap' for $5 is announced immediately 1000 new users sign up here and vote for Armbian support. We already experienced in the past that the cheaper the device the cheaper some people behave. If Armbian might start such a transparent discussion process and users feel they need to ignore developer reasoning then they can start a poll thread on their own asking for a specific new donate button. And then later they're able to vote for board support by donating the amount of cash they were talking about in the first place. That way it's also ensured that we won't start on 'PicoPi Bullcrap' ever since those people only buying as cheap as possible are also too cheap to donate a single Cent. And again: Board bring up is fun, board support the more boring part consuming time, energy and resources. We should triple check whether devices are worth getting 'supported' status or not. That's why I already talked about .playground vs. .wip. Allows developers to focus on fun stuff without risking to waste later time on the boring part. But as we could see with OPi 2G-IoT that does not even work with .wip boards

No, you need a different firmware. The famous manufacturer of this M2+ fail exchanged Wi-Fi chip (AP6212 in the beginning, now AP6212A).

That is excellent news on the OPiWin ... do you think that it should/will work on the OPi Win+ (AP6212A) ? I had hoped that they'd kept the same spec but just updated the ram chips ..... I have one of these for a project. I have installed the latest updates and even recompiled my own kernel debs from build system with no luck. I did see some information about the dhd module in other posts but i can't find it. Otherwise, what can i do to help get this working ? Do i need to do a full image install rather than upgrades ? In terms of my skill level, i'm a unix admin of some years so happy to supply debug output etc etc Many, many thanks for all the awesome work

So I have a NanoPi Neo Air and I wanted to make an Access Point out of it using Hostapd and Dnsmasq. I tried using armbian but I have the AP6212A Wifi Chip so I can't use armbian as it just doesn't detect that wlan0 even exists. And based on googling I'm not even sure if that issue is resolved. If anyone can tell me how to resolve this issue with Armbian I will gladly switch over). So I switched over to the FriendlyArm distribution and it detects the wlan0 module successfully and I am able to connect to the internet. I even got Hostapd and Dnsmasq running but the Hostapd isn't broadcasting the AP (or at least it isn't being picked up by anything) even though the service seems to have run successfully except: "hostap Failed to set TX queue parameters for queue 0". Does anyone know if I have to do something special to get the AP6212A into accesspoint mode using FriendlyArm? TL;DR: Does anyone know if I have to do something special to get the AP6212A into accesspoint mode using FriendlyArm distribution? Or does anyone know how to get AP6212A wifi chip working on the mainline Armbian distribution?

Just FYI, OPi Win use AP6212A. WiFi & BT works fine on legacy kernel, just do as @igor say, enable uart and load the firmware for the A series. Small tip: if you are using TTL debug BT does not work.