Wallys DR9074-6E(PN02.7) QCN9074 refuses to work on 6GHz band

[Mariusz]

I also got my hands on AXE75 which is a 6E router and I am able to get
QCN9074 work in STA mode.

With 160Mhz it did not work but it may be anything. However with 80Mhz
I am able to get a successful connection fully authenticated with
WPA3. So radio wise it operates in 6Ghz band after driver patch with
board_id=0xa2. Now I'm trying to understand why it still does not work
in AP mode.

root at s4:/home/angel# wpa_cli status
Selected interface 'wlp6s0'
bssid=1c:61:b4:c8:93:f4
freq=6115
ssid=test
id=0
mode=station
wifi_generation=6
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=SAE
pmf=2
mgmt_group_cipher=BIP
wpa_state=COMPLETED
ip_address=192.168.6.123
address=c4:4b:d1:d0:00:7e
uuid=07aaca38-a259-53ef-b12b-bb4cf5dad8d8

On Sat, 19 Nov 2022 at 16:16, Robert Marko <robert.marko at sartura.hr> wrote:
>
> On Sat, Nov 19, 2022 at 2:40 PM Mariusz <enebeo at gmail.com> wrote:
> >
> > I have contacted Wallys again but I am skeptical about resolution.
> > They don't consider board_id an issue and provided the same response,
> > on integrated systems it is due the bootloader to set it properly so
> > it is not fused and obviously not included in x86 scenario.
>
> Hi, this is not really the case, how would the bootloader set the board_id
> which is supposed to be fused on the device so FW would report the correct one?
> You can only workaround that by hardcoding it in the driver or on non-x86
> in DTS and force-loading the correct BDF that way.
>
> > Since this
> > is a private project I doubt QCA will support my efforts and free
> > access to their portals gives nothing. Found online some SDK for
> > version ath10k/IPQ8074 and athtestcmd to deal with OTP/fusing but
> > that's far beyond home project effort.
> >
> > Tried also to compile it in OpenWRT with moderate success. ath11ko /
> > qrtr.ko modules are built but the module never goes past power on
> > success.
> > mhi mhi0: Requested to power ON
> > mhi mhi0: Power on setup success
> > mhi mhi0: Wait for device to enter SBL or Mission mode
> >
> > Even the newest kernel in OpenWRT master development branch 5.16 is
> > quite behind and backporting anything is another non-trivial task.
>
> ath11k won't work in OpenWrt master currently, I have been supporting IPQ807x
> and recently PCI version as well out-of-tree with hopes of getting it soon into
> OpenWrt once 6.1 backports become available as that gets rid of like 300-ish
> backported patches.
>
> Regards,
> Robert
> >
> > On Fri, 18 Nov 2022 at 15:06, Sven Eckelmann <sven at narfation.org> wrote:
> > >
> > > On Friday, 18 November 2022 13:48:43 CET Mariusz wrote:
> > > > Mine is from a different supplier - Wallys - and I bought it 2 weeks
> > > > ago but not sure how old their stock is. PCB looks slightly different
> > > > than Pinapple's. Is it likely to have the same issue?
> > >
> > > It definitely has the same issue (because you reported that board_id is
> > > 255/0xff) but I have no idea whether Wallytech ever fixed it. At least I was
> > > never in contact about this problem with them. But sending around precompiled
> > > kernel module binaries (for an unknown kernel build), with some hacks to fix
> > > their hardware production errors (missing module id fusing in the OTP for
> > > their separately sold modules), doesn't make me confident that they are able
> > > to solve this problem correctly.
> > >
> > > In their defense, QCA doesn't make it really easy. It seems like their
> > > reference designs with Pine on 6Ghz are (mostly?) for (embedded Linux) APs
> > > which use the normal flash (NOR or NAND) to store the calibration data. And
> > > for these devices, they use the devicetree (or various other hacks) to load
> > > the correct board data.
> > >
> > > Wallystech has to find the correct document on createpoint which describes the
> > > process. It was something like "module" "board id" "fusing". But it is not the
> > > "Board ID Fusing for 802.11ax WLAN AP Chipsets" which only describes the way
> > > how you would to it for thei internal wifi of the IPQ807x/IPQ60xx/... SoC.
> > > You/they are searching for the corresponding document for Pine IPQ9074. Most
> > > likely hidden in some QDART documents.
> > >
> > >
> > > Regarding the problem that some countries are not allowing 6GHz: You have to
> > > either get a firmware from QCA which has it enabled or you modify the BDFs
> > > ("board-" files in the board-2.bin) to enable 6GHz in the (enabled) embedded
> > > REGDB of the BDFs for the specific country. Unfortunately, the data structures
> > > of the BDF are not officially documented and you would need an official QSDK/
> > > ATH.11.X release from QCA to fetch the bdf2txt.py, txt2bdf.py and the
> > > corresponding template for your BDF to extract and modify it.
> > >
> > > Kind regards,
> > >         Sven
> >
> > --
> > ath11k mailing list
> > ath11k at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/ath11k
>
>
>
> --
> Robert Marko
> Staff Embedded Linux Engineer
> Sartura Ltd.
> Lendavska ulica 16a
> 10000 Zagreb, Croatia
> Email: robert.marko at sartura.hr
> Web: www.sartura.hr