ath10k OTP loading issues

ath10k OTP loading issues

[André Valentin]

Hi!

I got problems initializing my ath10k PCI card in my Zyxel NBG 6716. It worked until some weeks, now, the driver does not load. I debugged a bit and this is what I got:
Fri Jun 27 08:03:42 2014 kern.info kernel: [62908.290000] ath10k_pci 0000:01:00.0: BAR 0: assigned [mem 0x12000000-0x121fffff 64bit]
Fri Jun 27 08:03:43 2014 kern.info kernel: [62908.610000] ath10k: pci irq legacy irq_mode 0 reset_mode 0
Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.620000] ath10k: boot upload otp to 0x1234 len 6917
Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.780000] ath10k: otp calibration failed: 2
Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.790000] ath10k: failed to run otp: -22
Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.790000] ath10k: could not init core (-22)
Fri Jun 27 08:03:43 2014 kern.err kernel: [62909.060000] ath10k: could not probe fw (-22)
Fri Jun 27 08:03:43 2014 kern.err kernel: [62909.060000] ath10k: failed to register driver core: -22
Fri Jun 27 08:03:43 2014 kern.warn kernel: [62909.060000] ath10k_pci: probe of 0000:01:00.0 failed with error -22


If I remove OTP loading the card initializes fine, but I think I will not have a good performance. So bad idea.
Currently I use compat-wireless-2014-05-22, with some patches form openwrt.
The firmware-2.bin has been checked, it is the same as offered here:
https://github.com/kvalo/ath10k-firmware

Perhaps somebody has a hint for me?

Kind regards,

André

Re: ath10k OTP loading issues

[André Valentin]

Hi Again!

I just saw the old thread about the same point. So I'm trying to look in the flash of my router if the OTP is stored there.
Does this OTP have some kind of magic so I can identify it?

André

On 27.06.2014 10:44, André Valentin wrote:
> Hi!
> 
> I got problems initializing my ath10k PCI card in my Zyxel NBG 6716. It worked until some weeks, now, the driver does not load. I debugged a bit and this is what I got:
> Fri Jun 27 08:03:42 2014 kern.info kernel: [62908.290000] ath10k_pci 0000:01:00.0: BAR 0: assigned [mem 0x12000000-0x121fffff 64bit]
> Fri Jun 27 08:03:43 2014 kern.info kernel: [62908.610000] ath10k: pci irq legacy irq_mode 0 reset_mode 0
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.620000] ath10k: boot upload otp to 0x1234 len 6917
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.780000] ath10k: otp calibration failed: 2
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.790000] ath10k: failed to run otp: -22
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.790000] ath10k: could not init core (-22)
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62909.060000] ath10k: could not probe fw (-22)
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62909.060000] ath10k: failed to register driver core: -22
> Fri Jun 27 08:03:43 2014 kern.warn kernel: [62909.060000] ath10k_pci: probe of 0000:01:00.0 failed with error -22
> 
> 
> If I remove OTP loading the card initializes fine, but I think I will not have a good performance. So bad idea.
> Currently I use compat-wireless-2014-05-22, with some patches form openwrt.
> The firmware-2.bin has been checked, it is the same as offered here:
> https://github.com/kvalo/ath10k-firmware
> 
> Perhaps somebody has a hint for me?
> 
> Kind regards,
> 
> André
> 

Re: ath10k OTP loading issues

[Kalle Valo]

Hi,

please always CC ath10k list, that way you get attention of all ath10k
developers.

André Valentin <avalentin@marcant.net> writes:

> I got problems initializing my ath10k PCI card in my Zyxel NBG 6716.
> It worked until some weeks, now, the driver does not load. I debugged
> a bit and this is what I got:
>
> Fri Jun 27 08:03:42 2014 kern.info kernel: [62908.290000] ath10k_pci 0000:01:00.0: BAR 0: assigned [mem 0x12000000-0x121fffff 64bit]
> Fri Jun 27 08:03:43 2014 kern.info kernel: [62908.610000] ath10k: pci irq legacy irq_mode 0 reset_mode 0
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.620000] ath10k: boot upload otp to 0x1234 len 6917
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.780000] ath10k: otp calibration failed: 2
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.790000] ath10k: failed to run otp: -22
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62908.790000] ath10k: could not init core (-22)
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62909.060000] ath10k: could not probe fw (-22)
> Fri Jun 27 08:03:43 2014 kern.err kernel: [62909.060000] ath10k: failed to register driver core: -22
> Fri Jun 27 08:03:43 2014 kern.warn kernel: [62909.060000] ath10k_pci: probe of 0000:01:00.0 failed with error -22
>
> If I remove OTP loading the card initializes fine, but I think I will
> not have a good performance. So bad idea.

All that was changed recently was that we now check the error code
coming from otp.bin. So you have had this issue all along, it was just
hidden before.

-- 
Kalle Valo

Re: ath10k OTP loading issues

[Kalle Valo]

André Valentin <avalentin@marcant.net> writes:

> I just saw the old thread about the same point. So I'm trying to look
> in the flash of my router if the OTP is stored there. Does this OTP
> have some kind of magic so I can identify it?

MAC addresses are good one to check. Basically it should be similar data
as in board.bin.

-- 
Kalle Valo

Re: ath10k OTP loading issues

[André Valentin]

Hi!

>> have some kind of magic so I can identify it?
> 
> MAC addresses are good one to check. Basically it should be similar data
> as in board.bin.

Of course I already tried this. But no luck. Do you have another idea.
Or is the MAC somehow encrypted ? I searched for the ASCII represantation and
a binary string generated from the MAC bytes.

Thanks,

André

Re: ath10k OTP loading issues

[Kalle Valo]

André Valentin <avalentin@marcant.net> writes:

> Hi!
>
>>> have some kind of magic so I can identify it?
>> 
>> MAC addresses are good one to check. Basically it should be similar data
>> as in board.bin.
>
> Of course I already tried this. But no luck.

How exactly did you search for it? Are you sure you used the correct MAC
address?

> Do you have another idea. Or is the MAC somehow encrypted ?

Nothing special, the MAC address should should be within the first 20
bytes. For example, here's 00:03:07:12:34:56:

$ od -t x1 board.bin  | head -1
0000000 44 08 df 30 02 04 00 03 07 12 34 56 00 00 6a 00

But of course I might be missing something. Or the calibration data is
somehow encrypted on the flash.

-- 
Kalle Valo