Questions about QCA6174 firmwares

Questions about QCA6174 firmwares

[Wonsup Yoon]

Hi,

If you don't mind, I'd like ask a few questions regarding QCA6174 firmwares.

1. I've notice that QCA6174 hw3.0 4.4.1 firmwares have 4 versions (none, c1, c2, c3). Are there any differences? Which one is newest or correct?

2. My QCA6174 seems to have a compatibility issue with a recent firmware. I've tested theses firmware versions, but only the oldest one works.

RM.4.4.1.c2-00057-QCARMSWP-1 (debian oldstable's stock firmware, 20190114-2, work's fine):

ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
ath10k_pci 0000:01:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:01:00.0.bin (-2)
ath10k_pci 0000:01:00.0: firmware: failed to load ath10k/cal-pci-0000:01:00.0.bin (-2)
usbcore: registered new interface driver ath3k
ath10k_pci 0000:01:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/firmware-6.bin
ath10k_pci 0000:01:00.0: qca6174 hw3.0 target 0x05020000 chip_id 0x003409ff sub 168c:3361
ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
ath10k_pci 0000:01:00.0: firmware ver RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a
ath10k_pci 0000:01:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/board-2.bin
ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
ath10k_pci 0000:01:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1


WLAN.RM.4.4.1-00157-QCARMSWPZ-1 (debian stable's stock firmware, 20210315-3):

ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
ath10k_pci 0000:01:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:01:00.0.bin (-2)
ath10k_pci 0000:01:00.0: firmware: failed to load ath10k/cal-pci-0000:01:00.0.bin (-2)
ath10k_pci 0000:01:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/firmware-6.bin
ath10k_pci 0000:01:00.0: qca6174 hw3.0 target 0x05020000 chip_id 0x003409ff sub 168c:3361
ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 90eebefb
ath10k_pci 0000:01:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/board-2.bin
ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 318825bf
ath10k_pci 0000:01:00.0: wmi unified ready event not received
ath10k_pci 0000:01:00.0: device has crashed during init
ath10k_pci 0000:01:00.0: device has crashed during init
ath10k_pci 0000:01:00.0: failed to wait for target init: -70
ath10k_pci 0000:01:00.0: could not init core (-110)
ath10k_pci 0000:01:00.0: could not probe fw (-110)



WLAN.RM.4.4.1-00288- (most recent version?):

ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
ath10k_pci 0000:01:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:01:00.0.bin (-2)
ath10k_pci 0000:01:00.0: firmware: failed to load ath10k/cal-pci-0000:01:00.0.bin (-2)
ath10k_pci 0000:01:00.0: firmware: direct-loading firmware ath10k/QCA6174/hw3.0/firmware-6.bin
ath10k_pci 0000:01:00.0: qca6174 hw3.0 target 0x05020000 chip_id 0x003409ff sub 168c:3361
ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00288- api 6 features wowlan,ignore-otp,mfp crc32 bf907c7c
ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 318825bf
ath10k_pci 0000:01:00.0: wmi unified ready event not received
ath10k_pci 0000:01:00.0: device has crashed during init
ath10k_pci 0000:01:00.0: device has crashed during init
ath10k_pci 0000:01:00.0: failed to wait for target init: -70
ath10k_pci 0000:01:00.0: could not init core (-110)
ath10k_pci 0000:01:00.0: could not probe fw (-110)



Kernel: Linux XXXX 5.10.0-16-amd64 #1 SMP Debian 5.10.127-2 (2022-07-23) x86_64 GNU/Linux

My lspci info:

01:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 30)
	Subsystem: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:3361]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 150
	IOMMU group: 12
	Region 0: Memory at 7fc00000 (64-bit, non-prefetchable) [size=2M]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
		Address: fee005f8  Data: 0000
		Masking: 000000fe  Pending: 00000000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via message, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [148 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00
	Capabilities: [178 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [180 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=50us PortTPowerOnTime=10us
		L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
			   T_CommonMode=0us LTR1.2_Threshold=81920ns
		L1SubCtl2: T_PwrOn=10us
	Kernel driver in use: ath10k_pci
	Kernel modules: ath10k_pci


Best Regards,
Wonsup Yoon
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Questions about QCA6174 firmwares

[Brett Mastbergen]

On Wed, Aug 10, 2022 at 10:56:38AM +0900, Wonsup Yoon wrote:
> Hi,
> 
> If you don't mind, I'd like ask a few questions regarding QCA6174 firmwares.
> 
> 1. I've notice that QCA6174 hw3.0 4.4.1 firmwares have 4 versions (none, c1, c2, c3). Are there any differences? Which one is newest or correct?
> 
> 2. My QCA6174 seems to have a compatibility issue with a recent firmware. I've tested theses firmware versions, but only the oldest one works.
> 

I have observed the same firmware crashes with those versions with my QCA6174 module (JWW6051).  Would love to know if RM.4.4.1.c2-00057-QCARMSWP-1 is the correct version to use, or if there is another newer version that I should be using.

Thanks,
brett

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

RE: Re: Questions about QCA6174 firmwares

[Wonsup Yoon]

Hi,

I'm currently using the latest "c3" version, and it works fine.
Firmware version: WLAN.RM.4.4.1.c3-00230 .

But I'm still curious what the "c" version means.

Best regards,
Wonsup Yoon

-----Original Message-----
From:  "Brett Mastbergen" <brett.mastbergen@protectli.com>
To:     "Wonsup Yoon" <pusnow@kaist.ac.kr>; 
Cc:      <ath10k@lists.infradead.org>; 
Sent:  2022-08-16 (화) 04:59:57 (UTC+09:00)
Subject: Re: Questions about QCA6174 firmwares

On Wed, Aug 10, 2022 at 10:56:38AM +0900, Wonsup Yoon wrote:
> Hi,
> 
> If you don't mind, I'd like ask a few questions regarding QCA6174 firmwares.
> 
> 1. I've notice that QCA6174 hw3.0 4.4.1 firmwares have 4 versions (none, c1, c2, c3). Are there any differences? Which one is newest or correct?
> 
> 2. My QCA6174 seems to have a compatibility issue with a recent firmware. I've tested theses firmware versions, but only the oldest one works.
> 

I have observed the same firmware crashes with those versions with my QCA6174 module (JWW6051).  Would love to know if RM.4.4.1.c2-00057-QCARMSWP-1 is the correct version to use, or if there is another newer version that I should be using.

Thanks,
brett
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Re: Questions about QCA6174 firmwares

[Brett Mastbergen]

On Tue, Aug 16, 2022 at 02:41:43PM +0900, Wonsup Yoon wrote:
> Hi,
> 
> I'm currently using the latest "c3" version, and it works fine.
> Firmware version: WLAN.RM.4.4.1.c3-00230 .
> 
> But I'm still curious what the "c" version means.

Yea, and if the "c" version would ever be "promoted" to be the QCA6174 firmware version in the linux-firmware repo again.  Because as it is right now, I think there is a bunch of QCA6174 hardware out there that broke when the QCA6174 firmware-6.bin in linux-firmware went to WLAN.RM.4.4.1-00140-QCARMSWPZ-1 (and up).  And since most distros pick up recent linux-firmware, most current distros have the broken version.
> 
> Best regards,
> Wonsup Yoon
> 
> -----Original Message-----
> From:  "Brett Mastbergen" <brett.mastbergen@protectli.com>
> To:     "Wonsup Yoon" <pusnow@kaist.ac.kr>; 
> Cc:      <ath10k@lists.infradead.org>; 
> Sent:  2022-08-16 (화) 04:59:57 (UTC+09:00)
> Subject: Re: Questions about QCA6174 firmwares
> 
> On Wed, Aug 10, 2022 at 10:56:38AM +0900, Wonsup Yoon wrote:
> > Hi,
> > 
> > If you don't mind, I'd like ask a few questions regarding QCA6174 firmwares.
> > 
> > 1. I've notice that QCA6174 hw3.0 4.4.1 firmwares have 4 versions (none, c1, c2, c3). Are there any differences? Which one is newest or correct?
> > 
> > 2. My QCA6174 seems to have a compatibility issue with a recent firmware. I've tested theses firmware versions, but only the oldest one works.
> > 
> 
> I have observed the same firmware crashes with those versions with my QCA6174 module (JWW6051).  Would love to know if RM.4.4.1.c2-00057-QCARMSWP-1 is the correct version to use, or if there is another newer version that I should be using.
> 
> Thanks,
> brett

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Questions about QCA6174 firmwares

[Kalle Valo]

(sorry for the delay, this got piled up with other email and I missed it)

Brett Mastbergen <brett.mastbergen@protectli.com> writes:

> On Wed, Aug 10, 2022 at 10:56:38AM +0900, Wonsup Yoon wrote:
>> Hi,
>> 
>> If you don't mind, I'd like ask a few questions regarding QCA6174 firmwares.
>> 
>> 1. I've notice that QCA6174 hw3.0 4.4.1 firmwares have 4 versions
>> (none, c1, c2, c3). Are there any differences? Which one is newest
>> or correct?

IIRC c1, c2 and c3 have different features but I can't recall what they
are. The recommendation is to use the mainline branch 4.4.1 from [1] and
that's the branch which I update to linux-firmware as well.

>> 2. My QCA6174 seems to have a compatibility issue with a recent
>> firmware. I've tested theses firmware versions, but only the oldest
>> one works.
>> 
>
> I have observed the same firmware crashes with those versions with my
> QCA6174 module (JWW6051). Would love to know if
> RM.4.4.1.c2-00057-QCARMSWP-1 is the correct version to use, or if
> there is another newer version that I should be using.

It looks like these crashes only certain devices, can you provide more
info on what devices exactly they happen? The more information the
better.

And apparently older firmware works but newer crashes? It would help to
solve the problem if finding out from [1] what's the latest release
which still works and the earliest release which is broken.

Kalle

[1] https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Questions about QCA6174 firmwares

[Kalle Valo]

Kalle Valo <kvalo@kernel.org> writes:

> (sorry for the delay, this got piled up with other email and I missed it)
>
> Brett Mastbergen <brett.mastbergen@protectli.com> writes:
>
>> On Wed, Aug 10, 2022 at 10:56:38AM +0900, Wonsup Yoon wrote:
>>> Hi,
>>> 
>>> If you don't mind, I'd like ask a few questions regarding QCA6174 firmwares.
>>> 
>>> 1. I've notice that QCA6174 hw3.0 4.4.1 firmwares have 4 versions
>>> (none, c1, c2, c3). Are there any differences? Which one is newest
>>> or correct?
>
> IIRC c1, c2 and c3 have different features but I can't recall what they
> are. The recommendation is to use the mainline branch 4.4.1 from [1] and
> that's the branch which I update to linux-firmware as well.
>
>>> 2. My QCA6174 seems to have a compatibility issue with a recent
>>> firmware. I've tested theses firmware versions, but only the oldest
>>> one works.
>>> 
>>
>> I have observed the same firmware crashes with those versions with my
>> QCA6174 module (JWW6051). Would love to know if
>> RM.4.4.1.c2-00057-QCARMSWP-1 is the correct version to use, or if
>> there is another newer version that I should be using.
>
> It looks like these crashes only certain devices, can you provide more
> info on what devices exactly they happen? The more information the
> better.
>
> And apparently older firmware works but newer crashes? It would help to
> solve the problem if finding out from [1] what's the latest release
> which still works and the earliest release which is broken.

I didn't notice that Peter (CCed) had also reported a similar issue:

https://lore.kernel.org/all/IA0PR20MB5731A6A9BAFB17E886DF2097B0889@IA0PR20MB5731.namprd20.prod.outlook.com/

He reports that WLAN.RM.4.4.1-00132-QCARMSWP-1 is the latest working
release. Can I then assume that WLAN.RM.4.4.1-00140-QCARMSWPZ-1 is the
first broken release? It would be good if everyone can verify these two
releases to make sure that we are looking at the same bug.

The releases are available here:

https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k