Will need to test again and will revert.
Does setting the value at 0x45c to 0x0 also apply to ipq5018 and qcn9074 or only to qcn6122?
Does setting the value at 0x45c to 0x0 also apply to ipq5018 and qcn9074
It should be set to 0 for them already ?
The following error is cause by this
[ 15.810890] 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
[ 16.097677] qcom-q6-mpd cd00000.remoteproc: fatal error received: err_smem_ver.2.1:
[ 16.097677] QC Image Version : QC_IMAGE_VERSION_STRING=WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
[ 16.097677] Image Variant : IMAGE_VARIANT_STRING=5018.wlanfw2.map_spr_spr_evalQ
[ 16.097677] phyrf_bdf.c:6245 Assertion axis_value == ANTENNACHAIN_AXIS_Z failed param0 :zero,param1 :zero,param2 :zero
[ 16.097677] Thread ID : 0x00000047 Thread name : wlan_platform Process ID : 0x00000003 Process name :wlan2
Are you sure about the address?
Latest QCN6122 BDF from Qualcomm repository has a value of zero at this address:
00000440 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 |................|
00000450 00 00 00 00 00 a1 00 00 00 00 00 00 00 00 00 00 |................|
00000460 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
yes. this is the issue. This value is 3 in 2.4
Oh so the change is from 0x3 to 0x0. Thanks!
You can use this tool to change the value: https://github.com/testuser7/ath_bdf_tool
ath11k_bdf_tool.py -p bdwlan.bin 0x45c 00
2 Likes
What error do you get with this BDF files on MX5500: IPQ5018: Support for Linksys MX2000 Atlas 6 & MX5500 Atlas 6 Pro - #225 by lytr ?
These are OEM BDFs updated to new version.
yes, this is the error I've seen and reported earlier here: Will patch as instructed and test/revert.
On MX2000 or MX5500?
tested on MX2000
Can you test on MX5500?
Updated BDFs for MX2000: https://filetransfer.io/data-package/thUjrjSi#link
0x3 changed to 0x0 for both files.
Some new firmware for IPQ5018/QCN6122: https://filetransfer.io/data-package/hzMVS4rM#link
- 2.8-01357 (MX6200)
- 2.9.r4-00018 (GL-B3000)
1 Like
the link to the updated BDF for MX2000 didn't work for me, but I extracted the bdf using the qca-swiss-army knife, patched the value at 0x45c to 0x0, and repackaged it and it works!
Will check if the ipq5018 bdf will also work with this patch
1 Like
ipq5018 also works with the patch applied, great stuff.
getting some decent throughput too on fast.com:
- ipq5018 (2.4ghz / 40mhz): 150Mbps
- qcn6122 (5ghz / 160mhz): 700Mbps (maxing out ISP connection)
packet steering + software flow offloading enabled
good stuff !
I suppose I'll need to figure this out for the B3000 as well. Still having problems mapping the ports correctly. Nothing config wise seems to have any affect. Could this be related to using the generic bins ?
on MX5500, the patched BDF works well, same throughput as on MX2000.
the BDF for QCN9074 doesn't work, however:
[ 15.582330] ath11k_pci 0001:01:00.0: BAR 0: assigned [mem 0xa0400000-0xa05fffff 64bit]
[ 15.582450] ath11k_pci 0001:01:00.0: enabling device (0000 -> 0002)
[ 15.590297] ath11k_pci 0001:01:00.0: MSI vectors: 16
[ 15.595419] ath11k_pci 0001:01:00.0: qcn9074 hw1.0
[ 15.600523] ath11k_pci 0001:01:00.0: FW memory mode: 2
[ 17.463593] ath11k_pci 0001:01:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
[ 17.463659] ath11k_pci 0001:01:00.0: fw_version 0x290607b9 fw_build_timestamp 2023-10-12 01:21 fw_build_id
[ 17.782989] ath11k_pci 0001:01:00.0: firmware crashed: MHI_CB_EE_RDDM
[ 17.783115] ath11k_pci 0001:01:00.0: ignore reset dev flags 0x8000
[ 28.005083] ath11k_pci 0001:01:00.0: failed to wait board file download request: -110
[ 28.005160] ath11k_pci 0001:01:00.0: qmi failed to load caldata
[ 28.011991] ath11k_pci 0001:01:00.0: failed to load board data file: -110
you just need to test, plug/unplug the cable, and take note of what the kernel log is reporting. Then change the labels in your dts accordingly based on the labels on your routers.
no detection on wan at all
to clarify
wan port --> no detection
lan1 --> wan
lan2 --> lan1
My only other suspicion at this point is related to my post here
assigning the same mac to both dp1 and dp2.
must be dts related, i have tried using the local-mac [00 11 22 33 44 55] for dp2, same outcome. There is some subtle differences in the original dts, but the 6.6 dts won't have it, any changes to the switch node breaks everything and in most cases results in a crash. Paint me puzzled at this point.
Can you try these board files: https://filebin.net/1py7pfhdwphw0gna ?
Updated regdb and fixed QCN9074 board file.
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 ipq5018 and qcn6122 vs the ones you previously shared?