Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2

From: Michal Kazior <michal.kazior@tieto.com>
To: Sven Schnelle <svens@stackframe.org>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
Date: Mon, 9 Jun 2014 07:40:46 +0200	[thread overview]
Message-ID: <CA+BoTQm7XA7f3pd0am2eCuJYuHMJfko8XCc2t=n__vpYe3C0nQ@mail.gmail.com> (raw)
In-Reply-To: <5393781C.8090403@stackframe.org>

On 7 June 2014 22:37, Sven Schnelle <svens@stackframe.org> wrote:
> Hi Michal,
>
> Am 05.06.2014 14:20, schrieb Michal Kazior:
>
>> This seems to confirm otp fails to load with error code 2. The assert
>> stack trace points to copy engine in ROM image. Wierd. Anyway, I've
>> extracted firmware files from TP-Link Archer C7 original rootfs. Can you
>> give it a try, please? See the OpenWRT ticket:
>> https://dev.openwrt.org/ticket/16589
>
>
> i tried, but the result doesn't look better:
>
> [    9.640000] ath10k: pci irq legacy irq_mode 0 reset_mode 0
> [    9.730000] ath10k: otp calibration failed: 2
> [   10.540000] ath10k: UART prints enabled
> [   10.600000] ath10k: qca988x hw2.0 (0x4100016c, 0x043202ff) fw
> 10.1.467-tplink-a-c7 api 2 htt 2.1
>
> I removed the error return in ath10k, that's why the firmware starts even
> with the otp error. I don't see the Assertion failure with this otp
> firmware:
>
> CLI>build_version=0x11, rom_version=0x41020000, ram_version=0x11,
> stack_size=6348
> reset reason=0x5
>
> Image startup of Normal mode
> Mac address is : 00:03:7f:4f:00:16
> alloc rem: 197492
> **WMI Service Ready **
> NUM_DEV=16
> TGT_VER: 4100016C
> RegDomain: 0, CfgCtl: 224 - 224
> ar_wal_peer_attach: num_peer_entries 145, num_tid_entries 443
> allocated 64 tids at 0x439a28 (each 96 bytes)
> allocated 379 tids in IRAM at 0x9baf34 (each 96 bytes)
> allocated 64 stateless tids at 0x43b250 (each 40 bytes)
> ### turn on Tx completion index tracking ###
> **WMI Ready **

Thanks for testing.

> Just to be sure, here are the md5sums of the firmware files i'm using:
>
> root@OpenWrt:/# md5sum /lib/firmware/ath10k/QCA988X/hw2.0/*
> 710fb9b582eda3d23728dee757d9ff85
> /lib/firmware/ath10k/QCA988X/hw2.0/board.bin

The attached board.bin in the ticket should be:

  419d73569cb0effc0a8b380f8e4dd197  board.bin

But it might be worth using the data found in mtd4 @ 0x5000-0x5844 as
board.bin (see my other mail) instead.

Michał

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