IPQ5018: GLiNET B3000 info

Hostle · 2024-10-03T16:37:57.493Z

Here is the original bins I started with

ipq5018 -->https://github.com/Telecominfraproject/wlan-ap/blob/7d336070d7b689cf2cffaa1c0eb269d8f310487e/feeds/ipq807x_v5.4/ath11k-wifi/board-gl-b3000.bin.IPQ5018

ipq6122 -->https://github.com/Telecominfraproject/wlan-ap/blob/7d336070d7b689cf2cffaa1c0eb269d8f310487e/feeds/ipq807x_v5.4/ath11k-wifi/board-gl-b3000.bin.QCN6122

I've been trying to make sense of the process, from what you said here

IPQ5018: Support for Linksys MX2000 Atlas 6 & MX5500 Atlas 6 Pro For Developers

updated QCN9074 board file works, thanks! for my own learning, what did you do to 'fix' it? Something in addition to? extract stock bdwlan.bin (.ba0 in my case) remove regdomain using ath11k_bdf_tool -r download latest QCN9074 board-2.bin from qca repo and extract regdb.bin using ath11k_bdf_tool -e update regdb in board file using ath11k_bdf_tool -u patch board file, set value at offset 0x45c to 0x0 package board file using ath11k-bdencoder And any changes to the other board files for ipq501…

but i am still failing to grasp the entire procedure.

IPQ5018: Support for Linksys MX2000 Atlas 6 & MX5500 Atlas 6 Pro

extract stock bdwlan.bin (.ba0 in my case)

where did you extratct it from ?

IPQ5018: Support for Linksys MX2000 Atlas 6 & MX5500 Atlas 6 Pro

remove regdomain using ath11k_bdf_tool -r

seems pretty straight forward, same goes for steps 2 3 4 and 6

IPQ5018: Support for Linksys MX2000 Atlas 6 & MX5500 Atlas 6 Pro

patch board file, set value at offset 0x45c to 0x0

I am assume your using this tool to achieve this ?

IPQ5018: Support for Linksys MX2000 Atlas 6 & MX5500 Atlas 6 Pro

ath11k_bdf_tool.py -p bdwlan.bin 0x45c 00

I guess the biggest piece I am missing is where to extract the stock bdwlan.bin ?

georgem83 · 2024-10-03T17:09:40.154Z

Boot into the stock firmware and do a find on bdwlan.* to find the directory.
Tar it and scp to your PC.
Run dmesg | grep cnss to find out which board file is used for each radio.
After you know which one, run the steps above. You will need the qca-swiss-army-knife tool to extract/package the board file for use in ath11k.

Hostle · 2024-10-03T17:25:59.916Z

Ok, do I need to reload stock firmware, or can I just search the partitions that i dumped from the stock firmware. Going back to stock makes me nervous at this point, as all I have is the img file, but i'll do it if necessary.

georgem83 · 2024-10-03T17:34:43.923Z

Yeah, you can start there too. If you can’t find anything, you may want to try downloading the FW image from the manufacturer and see if you can use binwalk to explore the firmware that way.

Hostle · 2024-10-03T17:42:49.709Z

the webui recovery is still intact. I can use it to re-flash the stock image safely. But before I do I figured I will go through what I have dumped already.

from stock firmware

root@GL-B3000:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "0:SBL1"
mtd1: 00080000 00020000 "0:MIBIB"
mtd2: 00040000 00020000 "0:BOOTCONFIG"
mtd3: 00100000 00020000 "0:QSEE"
mtd4: 00040000 00020000 "0:DEVCFG"
mtd5: 00040000 00020000 "0:CDT"
mtd6: 00080000 00020000 "0:APPSBLENV"
mtd7: 00140000 00020000 "0:APPSBL"
mtd8: 00100000 00020000 "0:ART"
mtd9: 00080000 00020000 "0:TRAINING"
mtd10: 00200000 00020000 "CFG"
mtd11: 07800000 00020000 "rootfs"
mtd12: 00361468 0001f000 "kernel"
mtd13: 003e9800 0001f000 "wifi_fw"
mtd14: 02c14000 0001f000 "ubi_rootfs"
mtd15: 03830000 0001f000 "rootfs_data"

would it be in usually ? or is it kind of random

mtd13: 003e9800 0001f000 "wifi_fw"

?

I have the lastest stock firmware here, I will binwalk it and see what I can find the locating before reverting to stock.

Hostle · 2024-10-03T18:30:07.888Z

good guess

hostle@hostle-Satellite-C670:~/bdwan$ ls _mtd13.extracted
0.squashfs  squashfs-root
hostle@hostle-Satellite-C670:~/bdwan$ cd _mtd13.extracted/squashfs-root
hostle@hostle-Satellite-C670:~/bdwan/_mtd13.extracted/squashfs-root$ ls
bdwlan.b10                     m3_fw.b00    q6_fw.b08  q6_fw.b22
bdwlan.b20                     m3_fw.b01    q6_fw.b09  q6_fw.b23
bdwlan.b21                     m3_fw.b02    q6_fw.b10  q6_fw.b25
bdwlan.b22                     m3_fw.flist  q6_fw.b11  q6_fw.b26
bdwlan.b23                     m3_fw.mdt    q6_fw.b13  q6_fw.flist
bdwlan.b24                     q6_fw.b00    q6_fw.b14  q6_fw.mdt
bdwlan.bin                     q6_fw.b01    q6_fw.b15  qcn6122
Data.msc                       q6_fw.b02    q6_fw.b16  qdss_trace_config.bin
firmware_rdp_feature_512P.ini  q6_fw.b03    q6_fw.b17  regdb.bin
firmware_rdp_feature.ini       q6_fw.b04    q6_fw.b18
fw_ini_cfg.bin                 q6_fw.b05    q6_fw.b20
fw_version.txt                 q6_fw.b07    q6_fw.b21
hostle@hostle-Satellite-C670:~/bdwan/_mtd13.extracted/squashfs-root$

ion: 0x0 eeprom_caldata_read_timeout 0s bdf_dnld_method 1 regdb_mandatory 0 rxgainlut_support 0
[   72.704914] cnss[2]: INFO: Downloading BDF: IPQ5018/regdb.bin, size: 24278
[   72.737664] cnss[2]: INFO: Downloading BDF: IPQ5018/bdwlan.b23, size: 131072
[   72.784650] cnss[2]: INFO: Waiting for FW ready. Device: 0xfffc, FW ready timeout: 60 seconds
[   72.811447] cnss[2]: INFO: Downloading BDF: IPQ5018/caldata.bin, size: 131072
[   72.902072] cnss[2]: INFO: FW ready received for device 0xfffc


sion: 0x0 eeprom_caldata_read_timeout 0s bdf_dnld_method 1 regdb_mandatory 0 rxgainlut_support 0
[   74.128034] cnss[42]: INFO: Device BAR Info pa: 0xa1e00000, va: 0x00000000da5a0e67, size: 0x200000
[   74.145814] cnss[42]: INFO: Downloading BDF: qcn6122/regdb.bin, size: 24278
[   74.166158] cnss[42]: INFO: Downloading BDF: qcn6122/bdwlan.b60, size: 131072
[   74.235074] cnss[42]: INFO: Downloading BDF: qcn6122/caldata_2.bin, size: 131072

georgem83 · 2024-10-03T18:38:48.507Z

While you’re at it, check the fw version (there’s a file)

lytr · 2024-10-03T19:13:09.740Z

I've send you ready to use board files in PM.
BDFs from OEM firmware do not require any modifications.

Hostle · 2024-10-03T19:29:08.519Z

WLAN.HK.2.9.r4-00018-QCAHKSWPL_SILICONZ-1 v1

Hostle · 2024-10-03T19:37:53.695Z

i just had i look at what you sent, I assume the bins go to ipq-wifi and than just add the folder to athh11k-firmware in its respective directory ?

/package/firmware/ath11k-firmware/files/IPQ5018_QCN6122/hw1.0/2.9.0.1
    -->WLAN.HK.2.9.r4-00018-QCAHKSWPL_SILICONZ-1

/package/firmware/ipq-wifi/src/
    -->board-glinet_gl-b3000.ipq5018
    -->board-glinet_gl-b3000.ipq6122

and than adjust paths in

/target/linux/qualcommax/ipq50xx/base-files/etc/hotplug.d/firmware/11-ath11k-caldata

Hostle · 2024-10-03T22:32:51.317Z

just dawned on me, the partition scheme I am using in my dts is not complete when comparing against the stock firmware

stock

mtd0: 00080000 00020000 "0:SBL1"
mtd1: 00080000 00020000 "0:MIBIB"
mtd2: 00040000 00020000 "0:BOOTCONFIG"
mtd3: 00100000 00020000 "0:QSEE"
mtd4: 00040000 00020000 "0:DEVCFG"
mtd5: 00040000 00020000 "0:CDT"
mtd6: 00080000 00020000 "0:APPSBLENV"
mtd7: 00140000 00020000 "0:APPSBL"
mtd8: 00100000 00020000 "0:ART"
mtd9: 00080000 00020000 "0:TRAINING"
mtd10: 00200000 00020000 "CFG"
mtd11: 07800000 00020000 "rootfs"
mtd12: 00361468 0001f000 "kernel"
mtd13: 003e9800 0001f000 "wifi_fw"
mtd14: 02c14000 0001f000 "ubi_rootfs"
mtd15: 03830000 0001f000 "rootfs_data"

Current 6.6

root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "0:SBL1"                                                
mtd1: 00020000 00020000 "0:MIBIB"                                               
mtd2: 00040000 00020000 "0:BOOTCONFIG"                                          
mtd3: 00100000 00020000 "0:QSEE"                                                
mtd4: 00040000 00020000 "0:DEVCFG"                                              
mtd5: 00040000 00020000 "0:CDT"                                                 
mtd6: 00080000 00020000 "0:APPSBLENV"                                           
mtd7: 00140000 00020000 "0:APPSBL"                                              
mtd8: 00100000 00020000 "0:ART"                                                 
mtd9: 00020000 00020000 "0:TRAINING"                                            
mtd10: 00200000 00020000 "CFG"                                                  
mtd11: 07000000 00020000 "rootfs"                                               
root@OpenWrt:~#

I will add the remaining partitions.

slh · 2024-10-04T00:34:37.891Z

Consider to check (with an initramfs image) if qcom,smem-part gives you a sensible result.

Hostle · 2024-10-04T13:36:00.816Z

does erase size somehow change the offset ..ie

My offsets match the stock, up until rootfs partition. When I add these remaining 4 partitions using the offsets from the stock, I get the following

[    1.088507] Creating 16 MTD partitions on "spi0.0":
[    1.094577] 0x000000000000-0x000000080000 : "0:SBL1"
[    1.101807] 0x000000080000-0x000000100000 : "0:MIBIB"
[    1.106598] 0x000000100000-0x000000140000 : "0:BOOTCONFIG"
[    1.111000] 0x000000140000-0x000000240000 : "0:QSEE"
[    1.117532] 0x000000240000-0x000000280000 : "0:DEVCFG"
[    1.121646] 0x000000280000-0x0000002c0000 : "0:CDT"
[    1.126841] 0x0000002c0000-0x000000340000 : "0:APPSBLENV"
[    1.131608] 0x000000340000-0x000000480000 : "0:APPSBL"
[    1.138322] 0x000000480000-0x000000580000 : "0:ART"
[    1.143852] 0x000000580000-0x000000600000 : "0:TRAINING"
[    1.146959] 0x000000600000-0x000000800000 : "CFG"
[    1.154864] 0x000000800000-0x000008000000 : "rootfs"
[    1.334369] mtd: setting mtd11 (rootfs) as root device
[    1.335569] mtdsplit: no squashfs found in "rootfs"
[    1.338483] 0x000008000000-0x000008361468 : "kernel"
[    1.343187] mtd: partition "kernel" is out of reach -- disabled
[    1.349572] 0x000008361468-0x00000874ac68 : "wifi_fw"
[    1.354074] mtd: partition "wifi_fw" is out of reach -- disabled
[    1.360347] 0x00000874ac68-0x00000b35ec68 : "ubi_rootfs"
[    1.365390] mtd: partition "ubi_rootfs" is out of reach -- disabled
[    1.371787] 0x00000b35ec68-0x00000eb8ec68 : "rootfs_data"
[    1.376658] mtd: partition "rootfs_data" is out of reach -- disabled

cat proc/mtd produces

mtd0: 00080000 00020000 "0:SBL1"
mtd1: 00080000 00020000 "0:MIBIB"
mtd2: 00040000 00020000 "0:BOOTCONFIG"
mtd3: 00100000 00020000 "0:QSEE"
mtd4: 00040000 00020000 "0:DEVCFG"
mtd5: 00040000 00020000 "0:CDT"
mtd6: 00080000 00020000 "0:APPSBLENV"
mtd7: 00140000 00020000 "0:APPSBL"
mtd8: 00100000 00020000 "0:ART"
mtd9: 00080000 00020000 "0:TRAINING"
mtd10: 00200000 00020000 "CFG"
mtd11: 07800000 00020000 "rootfs"
mtd12: 00000000 00020000 "kernel"
mtd13: 00000000 00020000 "wifi_fw"
mtd14: 00000000 00020000 "ubi_rootfs"
mtd15: 00000000 00020000 "rootfs_data"

stock

mtd9: 00080000 00020000 "0:TRAINING"
mtd10: 00200000 00020000 "CFG"
mtd11: 07800000 00020000 "rootfs"
mtd12: 00361468 0001f000 "kernel"
mtd13: 003e9800 0001f000 "wifi_fw"
mtd14: 02c14000 0001f000 "ubi_rootfs"
mtd15: 03830000 0001f000 "rootfs_data"

so for example starting at my rootfs partition at

 partition@800000 {
				label = "rootfs";
				reg = <0x00800000 0x7800000>; ---> 8000000 next offset
			};

partition@8000000 {
				label = "kernel";
				reg = <0x08000000 0x361468>;  ---> 8361468 next offset
			};

This does not work as we can see. The only thing that changes is the erase size, at the exact address where things fall apart. Hence my long winded question ?

Second thing I notice right away, the original boot logs match mine, only the inspection of cat /proc/mtd shows the extra partitions, which makes me wonder if these partitions are added post boot. Which then begs the question are the really needed ? everything seems to be running just fine without them currently. For now, i have marked them as unnecessary, I will comment them out in the dts and just move on for now.

Hostle · 2024-10-04T15:59:21.459Z

I pushed to my repo --> add glinet b3000 support

Still using the original bins, but everything works great. Boots in under 30 seconds, full functionality. Someone else will have to report on speeds and such. As well as i can test, it maxed out my isp at a whopping 9mbs.

A serial connection is required to play at this point. I'll post the instructions for uboot on the repo if anyone wants to test it out and report on the speeds and such.

Hostle · 2024-10-05T17:19:03.698Z

@lytr @georgem83 Some new results. I've tested the latest commits and wifi is broken on the glinet-b3000

I've tested with the bins that have bin working all along and neither radio comes up

   10.951215] NET: Registered PF_PPPOX protocol family
[   10.972601] ath11k c000000.wifi: ipq5018 hw1.0
[   10.972647] ath11k c000000.wifi: FW memory mode: 2
[   11.079354] remoteproc remoteproc2: powering up pd-1
[   11.080094] remoteproc remoteproc2: Booting fw image ath11k/IPQ5018/hw1.0/q6_fw.mdt, size 1820
[   11.083425] remoteproc remoteproc1: powering up cd00000.remoteproc
[   11.091999] remoteproc remoteproc1: Booting fw image ath11k/IPQ5018/hw1.0/q6_fw.mdt, size 1820
[   13.174761] remoteproc remoteproc1: remote processor cd00000.remoteproc is now up
[   13.193691] remoteproc remoteproc2: remote processor pd-1 is now up
[   13.197720] ath11k soc@0:wifi1@c000000: qcn6122
[   13.198798] ath11k soc@0:wifi1@c000000: FW memory mode: 2
[   13.219881] ath11k c000000.wifi: qmi fail to get qcom,m3-dump-addr, ignore m3 dump mem req
[   13.259439] remoteproc remoteproc3: powering up pd-3
[   13.259716] remoteproc remoteproc3: Booting fw image ath11k/IPQ5018/hw1.0/q6_fw.mdt, size 1820
[   13.274074] remoteproc remoteproc3: remote processor pd-3 is now up
[   13.287716] kmodloader: done loading kernel modules from /etc/modules.d/*
[   13.327604] ath11k c000000.wifi: chip_id 0x0 chip_family 0x4 board_id 0x23 soc_id 0xffffffff
[   13.327662] ath11k c000000.wifi: fw_version 0x270206d0 fw_build_timestamp 2022-08-04 13:28 fw_build_id WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
[   13.370462] ath11k soc@0:wifi1@c000000: qmi ignore invalid mem req type 10
[   13.542195] ath11k soc@0:wifi1@c000000: chip_id 0x0 chip_family 0x4 board_id 0x60 soc_id 0xffffffff
[   13.542269] ath11k soc@0:wifi1@c000000: fw_version 0x270206d0 fw_build_timestamp 2022-08-04 13:28 fw_build_id WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
[   13.649271] ath11k c000000.wifi: failed to fetch board data for bus=ahb,qmi-chip-id=0,qmi-board-id=35,variant=GL-iNet-GL-B3000 from ath11k/IPQ5018/hw1.0/board-2.bin
[   13.649345] ath11k c000000.wifi: failed to fetch board data for bus=ahb,qmi-chip-id=0,qmi-board-id=35 from ath11k/IPQ5018/hw1.0/board-2.bin
[   13.663133] ath11k c000000.wifi: failed to fetch board data for bus=ahb,qmi-chip-id=0,qmi-board-id=35 from ath11k/IPQ5018/hw1.0/board-2.bin
[   13.675347] ath11k c000000.wifi: failed to fetch board.bin from IPQ5018/hw1.0
[   13.687821] ath11k c000000.wifi: qmi failed to fetch board file: -12
[   13.695081] ath11k c000000.wifi: failed to load board data file: -12
[   13.912989] ath11k soc@0:wifi1@c000000: failed to fetch board data for bus=ahb,qmi-chip-id=0,qmi-board-id=96,variant=GL-iNet-GL-B3000 from ath11k/qcn6122/hw1.0/board-2.bin
[   13.913074] ath11k soc@0:wifi1@c000000: failed to fetch board data for bus=ahb,qmi-chip-id=0,qmi-board-id=96 from ath11k/qcn6122/hw1.0/board-2.bin
[   13.927257] ath11k soc@0:wifi1@c000000: failed to fetch board data for bus=ahb,qmi-chip-id=0,qmi-board-id=96 from ath11k/qcn6122/hw1.0/board-2.bin
[   13.940373] ath11k soc@0:wifi1@c000000: failed to fetch board.bin from qcn6122/hw1.0
[   13.953459] ath11k soc@0:wifi1@c000000: qmi failed to fetch board file: -12
[   13.961407] ath11k soc@0:wifi1@c000000: failed to load board data file: -12

tested with bins and firmware @lytr provided, the 5018 comes up qcn6122 can't find bin. I did as you suggested and cheanged the variant in the dts to

qcom,ath11k-calibration-variant = "GL-iNet-GL-B3000";

[   10.380603] kmodloader: loading kernel modules from /etc/modules.d/*
[   10.582281] urngd: v1.0.2 started.
[   10.686989] Loading modules backported from Linux version v6.11-0-g98f7e32f20d2
[   10.687030] Backport generated by backports.git v6.1.110-1-31-g35e7a9061609
[   10.733865] NET: Registered PF_QIPCRTR protocol family
[   10.938216] PPP generic driver version 2.4.2
[   10.940445] NET: Registered PF_PPPOX protocol family
[   10.960157] ath11k c000000.wifi: ipq5018 hw1.0
[   10.960200] ath11k c000000.wifi: FW memory mode: 2
[   11.026117] remoteproc remoteproc2: powering up pd-1
[   11.026913] remoteproc remoteproc2: Booting fw image ath11k/IPQ5018/hw1.0/q6_fw.mdt, size 1820
[   11.030195] remoteproc remoteproc1: powering up cd00000.remoteproc
[   11.038732] remoteproc remoteproc1: Booting fw image ath11k/IPQ5018/hw1.0/q6_fw.mdt, size 1820
[   13.265670] remoteproc remoteproc1: remote processor cd00000.remoteproc is now up
[   13.284745] remoteproc remoteproc2: remote processor pd-1 is now up
[   13.288411] ath11k soc@0:wifi1@c000000: qcn6122
[   13.289821] ath11k soc@0:wifi1@c000000: FW memory mode: 2
[   13.310763] ath11k c000000.wifi: qmi fail to get qcom,m3-dump-addr, ignore m3 dump mem req
[   13.349298] remoteproc remoteproc3: powering up pd-3
[   13.349573] remoteproc remoteproc3: Booting fw image ath11k/IPQ5018/hw1.0/q6_fw.mdt, size 1820
[   13.364132] remoteproc remoteproc3: remote processor pd-3 is now up
[   13.377002] kmodloader: done loading kernel modules from /etc/modules.d/*
[   13.417245] ath11k c000000.wifi: chip_id 0x0 chip_family 0x4 board_id 0x23 soc_id 0xffffffff
[   13.417304] ath11k c000000.wifi: fw_version 0x290d8012 fw_build_timestamp 2023-10-27 11:42 fw_build_id WLAN.HK.2.9.r4-00018-QCAHKSWPL_SILICONZ-1
[   13.460526] ath11k soc@0:wifi1@c000000: qmi ignore invalid mem req type 10
[   13.884183] ath11k soc@0:wifi1@c000000: chip_id 0x0 chip_family 0x4 board_id 0x60 soc_id 0xffffffff
[   13.884238] ath11k soc@0:wifi1@c000000: fw_version 0x290d8012 fw_build_timestamp 2023-10-27 11:42 fw_build_id WLAN.HK.2.9.r4-00018-QCAHKSWPL_SILICONZ-1
[   14.094996] ath11k c000000.wifi: htt event 48 not handled
[   14.128605] ath11k soc@0:wifi1@c000000: qmi failed to load CAL data file:cal-ahb-soc@0:wifi1@c000000-2.bin
[   14.128714] ath11k soc@0:wifi1@c000000: failed to load board data file: -12

georgem83 · 2024-10-05T17:35:31.167Z

Remove qcom,board-id from the wifi nodes in the dts and the ath11k driver will look for board-id 255 (which is the default).
The board file itself is based on the used stock bdwlan file, then mapped and packaged as board-id 255 while it was originally something else just to satisfy the driver.
@hzyitc made a patch to read the board id from the wifi nodes in the dts, but if you use that your board files must also be changed to include the right board ids instead of the default (255)

Hostle · 2024-10-05T17:36:27.683Z

thanks. I'll give that a try now

lytr · 2024-10-05T18:39:48.661Z

A little guide on BDF:

Find the right BDF files in your OEM firmware
Modify if needed (e.g. update regdb)
Create board files using bdencoder:

board-2.json

[
    {
        "board": [
            {
                "names": [
                    "bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=GL-iNet-GL-B3000"
                ],
                "data": "bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=GL-iNet-GL-B3000.bin"
            }
        ],
        "regdb": []
    }
]

The BDF file must be named bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=GL-iNet-GL-B3000.bin

ath11k-bdencoder -c board-2.json -o board-glinet_gl-b3000.ipq5018

Prepare PR with new board files for the firmware_qca-wireless repository
Add new device to ipq-wifi package:

...
ALLWIFIBOARDS:= \
...
	glinet_gl-b3000 \
...
$(eval $(call generate-ipq-wifi-package,glinet_gl-b3000,GL.iNet GL-B3000))
...

Use the right variant in DTS:

qcom,ath11k-calibration-variant = "GL-iNet-GL-B3000";

Hostle · 2024-10-05T20:07:32.012Z

The same process the qcn6122, change id to 255 there to I take it ?

Hostle · 2024-10-05T20:33:25.610Z

lytr:

Modify if needed (e.g. update regdb)

Create board files using bdencoder :

does this error relate to that ??

    for board in cont.boards:
AttributeError: 'int' object has no attribute 'boards'

strings of bwlan.23 does not produce the

bus=ahb,qmi-chip-id=0,qmi-board-id=23

or any valid string "board"

here is the cmd i am trying and resulting error

./qca-swiss-army-knife/tools/scripts/ath11k/ath11k-bdencoder -e ./bdwlan.23 -o board.json
invalid signature found in ./bdwlan.23
Traceback (most recent call last):
  File "/home/hostle/qca-sak/./qca-swiss-army-knife/tools/scripts/ath11k/ath11k-bdencoder", line 862, in <module>
    main()
  File "/home/hostle/qca-sak/./qca-swiss-army-knife/tools/scripts/ath11k/ath11k-bdencoder", line 851, in main
    return cmd_extract(args)
  File "/home/hostle/qca-sak/./qca-swiss-army-knife/tools/scripts/ath11k/ath11k-bdencoder", line 576, in cmd_extract
    for board in cont.boards:
AttributeError: 'int' object has no attribute 'boards'