Permalink
Browse files

Correct firmware for Friendly ARM DEV kernel

Thanks @Fourdee
1 parent 3bfa63b commit 6df11c8889cac3c105bb6dea6e20310cd1a850df @igorpecovnik committed Dec 27, 2016
Binary file not shown.
Binary file not shown.
@@ -0,0 +1,54 @@
+#AP6212_NVRAM_V1.0_20140603
+# 2.4 GHz, 20 MHz BW mode
+
+# The following parameter values are just placeholders, need to be updated.
+manfid=0x2d0
+prodid=0x0726
+vendid=0x14e4
+devid=0x43e2
+boardtype=0x0726
+boardrev=0x1101
+boardnum=22
+macaddr=00:90:4c:c5:12:38
+sromrev=11
+boardflags=0x00404201
+xtalfreq=26000
+nocrc=1
+ag0=255
+aa2g=1
+ccode=ALL
+
+pa0itssit=0x20
+extpagain2g=0
+
+#PA parameters for 2.4GHz, measured at CHIP OUTPUT
+pa2ga0=-168,7161,-820
+AvVmid_c0=0x0,0xc8
+cckpwroffset0=5
+
+# PPR params
+maxp2ga0=90
+txpwrbckof=6
+cckbw202gpo=0x5555
+legofdmbw202gpo=0x77777777
+mcsbw202gpo=0xaaaaaaaa
+
+# OFDM IIR :
+ofdmdigfilttype=7
+# PAPD mode:
+papdmode=2
+
+il0macaddr=00:90:4c:c5:12:38
+wl0id=0x431b
+
+#OOB parameters
+hostwake=0x40
+hostrdy=0x41
+usbrdy=0x03
+usbrdydelay=100
+deadman_to=0xffffffff
+# muxenab: 0x1 for UART enable, 0x10 for Host awake
+muxenab=0x10
+# CLDO PWM voltage settings - 0x4 - 1.1 volt
+#cldo_pwm=0x4
+
@@ -1,3 +1,4 @@
+PM=0
nv_by_chip=1 \
43362 1 nvram_ap6210.txt
43430 0 nvram_ap6212.txt

3 comments on commit 6df11c8

@ThomasKaiser
Collaborator

Why always this firmware mess? bin/firmware-overlay/ap6212/ contains this stuff already.

@Fourdee
Contributor
Fourdee commented on 6df11c8 Dec 27, 2016 edited

@ThomasKaiser

Why always this firmware mess? bin/firmware-overlay/ap6212/ contains this stuff already.

  • The firmware location used by 4.9 kernel and brcm module is /lib/firmware/brcm/brcmfmac43430-sdio.xxx

Without this firmware added:

[ 7.182265] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.txt failed with error -2. 
@ThomasKaiser
Collaborator

We now have:

  • AP6212 on NanoPi Air and BPi M2+ (to be used with dhd and brcmfmac)
  • AP6210 on Cubietruck (to be used with ap6210 and brcmfmac for whatever reasons)
  • AP6211 on some Beelink X2
  • AP6181 on Banana Pro, M2, M1+ (to be used with ap6211 or brcmfmac driver) and some other Beelink X2 (there dhd and brcmfmac should be used)

Due to situation with Beelink X2 alone (3 different Wi-Fi chips on different production batches) we need a solution that checks SDIO bus and chip ID and then does what's necessary. If I understood correctly we already have such a working solution for legacy kernel (based on @jernejsk's findings/work): https://forum.armbian.com/index.php/topic/872-beelink-x2-with-armbian-possible/?p=16607

So now 'all' that's missing would be to consolidate firmware and nvram files in one location and to get firmware loading based on chip id correctly? And what does happen: Quite the opposite and files that are already there added to another location with different names.

Please sign in to comment.