failed to fetch board data QCA6174

[Ryan Hsu]

On 09/12/2017 05:15 PM, Carsten Haitzler wrote:

> On Tue, 12 Sep 2017 23:14:33 +0000 Ryan Hsu <ryanhsu at qti.qualcomm.com> said:
>
>> On 09/12/2017 12:24 AM, Luka Karinja wrote:
>>
>>> [    3.662941] ath10k_pci 0000:05:00.0: qca6174 hw3.2 target 0x05030000
>>> chip_id 0x00340aff sub 0000:0000 
>> Hmm, where did you get this module? it seems like this module is not
>> calibrated or assigned a sub IDs information, that why it cause the failure,
>> since incorrect board file will lead to the firmware crash.
>>
>> You might want to contact your module provider to give you the correct board
>> file (board.bin) and replace it under the same firmware folder for
>> testing/developing.
> I see similar/same issues on an actual product (not some module or dev board).
> a new-ish laptop/tablet that runs windows out of the box. I sent mails to to
> here and linux-wireless too with zero responses on information on what the
> board bin file is and the firmware bin files and how they are created etc. as I
> suspected the key to the issue is somewhere there.
>

Sorry that I overlooked your post earlier (was out during that time and didn't have time to catch up the backlog...)

Your case is different from Luka's, your device do have the id calibrated, just that it is not added to the board-2.bin.

[  124.524661] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 144d:c14f


Here are some general guidance you might want to find out the right board file if it failed at first place.

For you case, your board is calibrated, so from the failure logs, you coudl see above string - sub 144d:c14f, and then either your install package or you could seek the driver online, e.g this might work to your board.
https://drp.su/en/hwids/PCI%5CVEN_168C%26DEV_003E%26SUBSYS_C14F144D%26REV_32

And then extract the file you could see the PCI\VEN_168C&DEV_003E&SUBSYS_C14F144D&REV_32 is using "eeprom_ar6320_3p0_SS_720.bin", so if you could give it a try by renaming it to board.bin under your firmware folder.

And would be appreciated if you could feedback the result.

-- 
Ryan Hsu