Re: QCA6174 hw2.1?
Hi Corin, the dissect.py script seems to work better than the disassemble.py: [ 6483.455435] ath10k_pci :03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [ 6483.600747] ath10k_pci :03:00.0: Direct firmware load for ath10k/cal-pci-:03:00.0.bin failed with error -2 [ 6484.772417] ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [ 6484.772433] ath10k_pci :03:00.0: qca6174 hw2.1 (0x0501, 0x003405ff) fw killer-n1525-fw api 4 htt 0.0 wmi 4 cal otp max_sta 32 [ 6484.772435] ath10k_pci :03:00.0: debug 1 debugfs 0 tracing 0 dfs 0 testmode 0 [ 6484.77] ath10k_pci :03:00.0: firmware register dump: [ 6484.77] ath10k_pci :03:00.0: [00]: 0x0501 0x15B3 0x0095186B 0x00955B31 [ 6484.77] ath10k_pci :03:00.0: [04]: 0x0095186B 0x00060130 0x0010 0x0040AF04 [ 6484.77] ath10k_pci :03:00.0: [08]: 0x0018 0x0001 0x0001 0x00412250 [ 6484.77] ath10k_pci :03:00.0: [12]: 0x0009 0x 0x0096C09C 0x0096C0A7 [ 6484.77] ath10k_pci :03:00.0: [16]: 0x0096BDBC 0x009286B6 0x 0x [ 6484.77] ath10k_pci :03:00.0: [20]: 0x4095186B 0x0040E160 0x0041F82C 0x0001 [ 6484.77] ath10k_pci :03:00.0: [24]: 0x80936238 0x0040E1C0 0x 0xC095186B [ 6484.77] ath10k_pci :03:00.0: [28]: 0x80936361 0x0040E1E0 0x 0x0041C8DC [ 6484.77] ath10k_pci :03:00.0: [32]: 0x80934A67 0x0040E200 0x00436DF0 0x0040E250 [ 6484.77] ath10k_pci :03:00.0: [36]: 0x809A5C92 0x0040E250 0x004275B0 0x0001 [ 6484.77] ath10k_pci :03:00.0: [40]: 0x809A5CEA 0x0040E290 0x00426F40 0x0004 [ 6484.77] ath10k_pci :03:00.0: [44]: 0x809A5DCA 0x0040E2B0 0x00426F40 0x0041C8DC [ 6484.77] ath10k_pci :03:00.0: [48]: 0x800A0909 0x0040E2D0 0x00426F40 0x004275A0 [ 6484.77] ath10k_pci :03:00.0: [52]: 0x800A024A 0x0040E2F0 0x0041ABB0 0x00420440 [ 6484.77] ath10k_pci :03:00.0: [56]: 0x809287D9 0x0040E310 0x 0x0040 [ 6485.765040] ath10k_pci :03:00.0: failed to receive control response completion, polling.. [ 6486.765027] ath10k_pci :03:00.0: ctl_resp never came in (-110) [ 6486.765032] ath10k_pci :03:00.0: failed to connect to HTC: -110 [ 6486.828658] ath10k_pci :03:00.0: could not init core (-110) [ 6486.828689] ath10k_pci :03:00.0: could not probe fw (-110) [ 6486.831175] ath10k_pci :03:00.0: cannot restart a device that hasn't been started Well, at least it loads correctly. This should be the firmware crash fixed in the patches, it's time to test kvalo's kernel sources. On 26/04/2015 05:51, Corin Lawson wrote: Hi Gabriele, I think we have the same card (the vendor and device ids are the determining factor): $ lspci -n -s 05:00.0 05:00.0 0280: 168c:003e (rev 20) Without the skip_otp option I get this in dmesg: [18396.622576] ath10k_pci :05:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0 [18396.768593] ath10k_pci :05:00.0: Direct firmware load for ath10k/cal-pci-:05:00.0.bin failed with error -2 [18396.847975] ath10k_pci :05:00.0: otp calibration failed: 3 [18396.847977] ath10k_pci :05:00.0: failed to run otp: -22 [18396.847978] ath10k_pci :05:00.0: could not init core (-22) [18396.847995] ath10k_pci :05:00.0: could not probe fw (-22) Which is different to your messages. I'm taking a guess here, but those DMAR messages seem to indicate that the firmware is attempting to write to the wrong part of memory (i.e. wrong firmware). Using kvalo's kernel fork is probably a good step (it contains those necessary patches). If you still don't get it working, then my only other idea is to try that dissect.py gist I mentioned previously. Here are the commands that worked for me: # python dissect.py drivers/Production/Windows8.1-x64/k1525w81/qca61x420.bin # python assemble.py killer-n1525-fw 0 fw-2.bin fw-1.bin 4 /lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin The dissect.py script produced fw-1.bin which is the otp file and fw-2.bin which is the correct firmware (don't quote me on that, but it worked for me). As for your board.bin file, you need to check the .inf file that comes with your drivers. I'm not sure what the structure of that file is... for all I know I could be using the wrong board file... I hope this helps, otherwise you've reached the limits of my experience :) Maybe someone else on the list has a better idea? Cheers, Corin On Sat, Apr 25, 2015 at 10:58 PM, Gabriele Martino g.mart...@gmx.com wrote: On 25/04/2015 05:47, Corin Lawson wrote: I also had problems with calibration, I had to pass skip_otp=y to the module: $ cat /etc/modprobe.d/ath10k.conf options ath10k_core skip_otp=y Hi Corin, I removed ath10k_pci, ath10k_core and ath before loading ath10k_core with skip_otp=1, but nothing happened: [ 1808.473874] ath10k_pci :03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [
Re: attempting mesh on ath10k
On Fri, Apr 24, 2015 at 06:38:02PM -0700, Ben Greear wrote: I have IBSS support working, and at least non-encrypted raw transmit can work in my firmware, though raw tx requires Michal's RFC patch he posted some time ago. (Michal's RFC patch is in my repo.) So I got a bit further. I was still getting a crash with CT firmware, but, suspecting that we pass something invalid in assoc message for mesh, I forced peer-aid = 1 and then it no longer crashes shortly after adding the first peer on either CT or QCA firmware. I pushed that hack into my repo for now -- I think we want to rethink how and when AIDs are generated in mesh. # iw dev wlan0 station dump Station 00:03:7f:10:4e:2d (on wlan0) inactive time: 400 ms rx bytes: 34019 rx packets: 959 tx bytes: 152 tx packets: 3 tx retries: 0 tx failed: 0 signal: -27 dBm signal avg: -26 dBm tx bitrate: 6.0 MBit/s rx bitrate: 9.0 MBit/s mesh llid: 220 mesh plid: 455 mesh plink: ESTAB mesh local PS mode: ACTIVE mesh peer PS mode: ACTIVE mesh non-peer PS mode: ACTIVE authorized: yes authenticated: yes preamble: long WMM/WME:yes MFP:no TDLS peer: no So, progress! There's still an issue with datapath -- while it looks like we can establish plinks, I couldn't get unicast traffic flowing even if manually setting up mpaths and arp table entries. I haven't yet got all of my 5 ghz capable gear in the same room to monitor and see where the problem lies. -- Bob Copeland %% http://bobcopeland.com/ ___ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
Re: QCA6174 hw2.1?
Just tried the kvalo's kernel. NetworkManager connected flawlessly at boot to my WPA2 home network on 2.4GHz. Will try 5GHz later. iwconfig reports a fixed 1Mb/s bitrate, but I can copy files to my nas (smb share) at about 3.3MB/s. That's a reasonable speed for b/g wireless. iwconfig: wlp3s0IEEE 802.11abgn ESSID:W-I-SEE-YOU-N Mode:Managed Frequency:2.412 GHz Access Point: 40:16:7E:2C:79:90 Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=59/70 Signal level=-51 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:42 Missed beacon:0 iwlist scan (part of): wlp3s0Scan completed : Cell 01 - Address: 40:16:7E:2C:79:90 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=60/70 Signal level=-50 dBm Encryption key:on ESSID:W-I-SEE-YOU-N Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Master Extra:tsf=0005244f5a5d Extra: Last beacon: 33ms ago IE: Unknown: 000D572D492D5345452D594F552D4E IE: Unknown: 010882848B962430486C IE: Unknown: 030101 IE: Unknown: 2A0104 IE: Unknown: 2F0104 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK dmesg output: [2.212106] ath10k_pci :03:00.0: enabling device ( - 0002) [2.212558] ath10k_pci :03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [2.368318] ath10k_pci :03:00.0: Direct firmware load for ath10k/cal-pci-:03:00.0.bin failed with error -2 [2.368971] ath10k_pci :03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2 [2.368974] ath10k_pci :03:00.0: failed to load spec board file, falling back to generic: -2 [2.369252] ath10k_pci :03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2 [2.369270] ath10k_pci :03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2 [3.559021] ath10k_pci :03:00.0: qca6174 hw2.1 (0x0501, 0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32 [3.559024] ath10k_pci :03:00.0: debug 1 debugfs 0 tracing 0 dfs 0 testmode 0 [3.623733] ath: EEPROM regdomain: 0x6c [3.623735] ath: EEPROM indicates we should expect a direct regpair map [3.623736] ath: Country alpha2 being used: 00 [3.623737] ath: Regpair used: 0x6c [3.638102] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0 [7.523617] ath10k_pci :03:00.0: no channel configured; ignoring frame(s)! [7.627173] ath10k_pci :03:00.0: no channel configured; ignoring frame(s)! [ 12.149947] wlp3s0: authenticate with 40:16:7e:2c:79:90 [ 12.183915] wlp3s0: send auth to 40:16:7e:2c:79:90 (try 1/3) [ 12.185559] wlp3s0: authenticated [ 12.186043] wlp3s0: associate with 40:16:7e:2c:79:90 (try 1/3) [ 12.189402] wlp3s0: RX AssocResp from 40:16:7e:2c:79:90 (capab=0x411 status=0 aid=3) [ 12.192174] wlp3s0: associated [ 313.912952] wlp3s0: AP 40:16:7e:2c:79:90 changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz) [ 313.912955] wlp3s0: AP 40:16:7e:2c:79:90 changed bandwidth in a way we can't support - disconnect [ 318.709453] wlp3s0: authenticate with 40:16:7e:2c:79:90 [ 318.750807] wlp3s0: send auth to 40:16:7e:2c:79:90 (try 1/3) [ 318.752541] wlp3s0: authenticated [ 318.753030] wlp3s0: associate with 40:16:7e:2c:79:90 (try 1/3) [ 318.756524] wlp3s0: RX AssocResp from 40:16:7e:2c:79:90 (capab=0x411 status=0 aid=1) [ 318.759082] wlp3s0: associated I'm using the board file eeprom_qca9377_1p0_NFA435_olpc.bin. Regards, Gabriele On 26/04/2015 16:10, Gabriele Martino wrote: Hi Corin, the dissect.py script seems to work better than the disassemble.py: [ 6483.455435] ath10k_pci :03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [ 6483.600747] ath10k_pci :03:00.0: Direct firmware load for ath10k/cal-pci-:03:00.0.bin failed with error -2 [ 6484.772417] ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [ 6484.772433] ath10k_pci :03:00.0: qca6174 hw2.1 (0x0501, 0x003405ff) fw killer-n1525-fw api 4 htt 0.0 wmi 4 cal otp max_sta 32 [ 6484.772435] ath10k_pci :03:00.0: debug 1 debugfs 0 tracing 0 dfs 0 testmode 0 [ 6484.77] ath10k_pci :03:00.0: firmware register dump: [
Tips to debug Firmware crash
Hi All, I am an active developer of Atheros drivers for the last 10 years. I have been working on QCA 10.2.2 driver for the last few months and trying to understand the architecture of this offloading model. Though this forum is nothing to do with Atheros provided drivers, I took the liberty of posting the question to see if Ath10k community could help me. Sorry if I violated any guidelines. There is some problem at firmware level about which I am clueless. Whenever there is a crash in firmware the 5GHz interface goes down completely and there will not be any transmissions or receptions from the interface from then. What all I see on the console is some log message Target Asserted . I don't get any stack trace to see in which function it crashed. Can any of you please let me know if there is a way to dump the stack trace and debug the firmware crash? Thanks Regards Venkat -- If you rest, you rust ___ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
Re: First QCA6174 firmware release
On 25 April 2015 at 20:22, Oscar Rydberg oscarrydb...@gmail.com wrote: Olaf Dreyer olaf at dreyero.de writes: I have a new Acer Aspire VN7-591 Laptop with a Qualcom Atheros QCNF344 wireless chip, which is shown by lspci as: Qualcomm Atheros Device 003e (rev 20) Subsystem: Foxconn International, Inc. Device e08e I have installed the linux-next kernel from today 8:00 UTC. I was able to load the ath10k_pci driver, but the driver complains about missing firmware. I installed a firmware from here: https://github.com/kvalo/ath10k- firmware under /lib/firmware/ath10k/QCA6174/hw2.1/ But also the card is not working. The output from dmesg is: [ 9360.538767] ath10k_pci :07:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0 [ 9360.788588] ath10k_pci :07:00.0: Direct firmware load for ath10k/cal-pci-:07:00.0.bin failed with error -2 [ 9362.729118] ath10k_pci :07:00.0: unable to write to the device [ 9362.729120] ath10k_pci :07:00.0: failed to download normal firmware: -110 [ 9362.729121] ath10k_pci :07:00.0: could not init core (-110) [ 9362.729156] ath10k_pci :07:00.0: could not probe fw (-110) I would like to know, as Austin Hendrix wrote it at 8 Feb 14:12 2015 too, where can I find the firmware on the internet / my Windows7 partition and how can I prepare the needed files. Many thanks, Olaf Hi did you advance anything on this? Trying to run a QCA6164 card myself on a Lenovo 3-14 laptop. Sems I've gotten as far as you. Prepared Ath10k hw2.1 board.bin and firmware-4.bin for hw2.1 using windows binary driver. (And assemble.py, disassemble.py tools linked elsewhere) Board.bin seems to load and execute fine. But after that when loading firmware-4.bin, it ends up with Unable to write to the device. I see it starts sending firmware-4.bin and first 256 bytes ce_send fine. 2nd ce_send 256 bytes seem to also ce_send fine, however after that bmi_wait times out. (-110) You're most likely trying to push something that isn't an actual firmware blob to the device. You might be interested in the other thread: http://lists.infradead.org/pipermail/ath10k/2015-April/005072.html Michał ___ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
Re: Ath10 Firmware
On 25 April 2015 at 11:14, Sunder Kumaresan sunder.kumare...@aricent.com wrote: Hi, Will Ath10 firmware work for big endian processor ? is it endian agnostic ? It works for little endian processor. You probably mean ath10k driver - not firmware. Firmware is run on the device chip itself and you can't really change that in any way. As far as the driver goes it is endian agnostic - some routers supported by OpenWRT have big-endian MIPS CPUs and ath10k works there just fine. Michał ___ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
