wl1271 port

Eyal,

Thanks so much for digging into my logs and verifying the problem. We will be waiting for your fix.

Your help is very appreciated.

Tiegang

Hi Tiegang,

I think that I understand what the issue is, it looks like the AP have to big jitter in the beacon transmission and for that reason the WLAN driver misses beacons. I tried 3 different locations in the log and saw similar behavior. For example please take for example in log ttmvrb-ps-no-sec-ping-beacon-capture-017.apc in the beacons on packet number 25854.

Beacon on packet 25855 is 1034 mSec after Beacon on packet 25854

Beacon on packet 25856 is 996 mSec after Beacon on packet 25855

Beacon on packet 25857 is 2054 mSec after Beacon on packet 25856

Beacon on packet 25858 is 1014 mSec after Beacon on packet 25857

could you please verify that in more logs and verify that? in case the AP jitter is too high then we expect some beacon loss therfore the driver will also miss Broadcast frames (and specifically the ARP request frame).

also please note that we had performed testing with lots of Access point with different vendor and cannot reproduce that issue.

Regards,

Eyal

Eyal,

Thanks for your research into the logs. Unless you posted the file name wrong, I can't see anything wrong with the beacon intervals. Here is what I found,

PKT#    TIME             DELTA TIME    INFO

=====   ==============   ==========    ===============

25851   1285.373819352                 Beacon, SN=3504

25854   1285.478393555   105 ms        Beacon, SN=3508

25855   1285.581775666   103           Beacon, SN=3509

25856   1285.681383133   100           Beacon, SN=3511

25857   1285.886833191   205           Beacon, SN=3513

25858   1285.988239289   102           Beacon, SN=3514

25863   1286.090599060   102           Beacon, SN=3515

25864   1286.193401337   103           Beacon, SN=3516

The beacons are transmitted pretty much in the right time. Packet 25857 looks odd (205 ms after pkt 25856), seems that the AP missed one beacon or the beacon was not captured (since the serial number between the two beacons differs by 2). Anyway, the beacon intervals still look very good. It is hard to understand why the wlan failed to respond to 7 - 8 ARP requests consecutively for a period of 20 seconds.

Thanks for help,

Tiegang

Hi,

Could you please run the command / e p 815 from the CLI menu? i would like to see the statistics of missing beacons. following is the expected log

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance

/, measuremeNt/, Report/, dEbug/, biT/, aboUt, Quit

/ e p 815

\> Driver/, Connection/, Managem[  939.795227] TIWLAN: 537.662518: ------  Ring statistics  ------------------

-

ent/, Show/, Privacy/, scAn/, ro[  939.803894] TIWLAN: 537.671188: numOfTxProcs       = 0

aminG/, qOs/, poWer/, eVents/, B[  939.811859] TIWLAN: 537.679177: numOfPreparedDescs = 20648

t coexsistance/, measuremeNt/, R[  939.820220] TIWLAN: 537.687536: numOfTxXfr         = 0

eport/, dEbug/, biT/, aboUt, Qui[  939.828247] TIWLAN: 537.695544: numOfTxDma         = 0

t

.../dEbug> Print, Fw debug/

[  939.836242] TIWLAN: 537.703535: numOfTxCmplt       = 20648

CuCmd_PrintDriverDebug: FUN_ID: [  939.844573] TIWLAN: 537.711885: numOfRxProcs       = 20363

815

[  939.852905] TIWLAN: 537.720224: numOfRxData        = 0

[  939.858520] TIWLAN: 537.725812: ------  Debug statistics  -------------------

[  939.865753] TIWLAN: 537.733057: debug1 = 198221

[  939.870361] TIWLAN: 537.737656: debug2 = 0

[  939.874542] TIWLAN: 537.741837: debug3 = 0

[  939.878692] TIWLAN: 537.745997: debug4 = 0

[  939.882873] TIWLAN: 537.750176: debug5 = 19

[  939.887084] TIWLAN: 537.754408: debug6 = 19

[  939.891418] TIWLAN: 537.758715: ------  Isr statistics  -------------------

[  939.898468] TIWLAN: 537.765763: IRQs = 439934

[  939.902893] TIWLAN: 537.770206: ------  Rx  statistics  -------------------

[  939.909942] TIWLAN: 537.777251: RxOutOfMem             = 0

[  939.915527] TIWLAN: 537.782830: RxHdrOverflow          = 0

[  939.921112] TIWLAN: 537.788422: RxHWStuck              = 0

[  939.926666] TIWLAN: 537.793967: RxDroppedFrame         = 23

[  939.932342] TIWLAN: 537.799645: RxCompleteDroppedFrame = 0

[  939.937896] TIWLAN: 537.805190: RxAllocFrame           = 0

[  939.943481] TIWLAN: 537.810780: RxDoneQueue            = 24995

[  939.949401] TIWLAN: 537.816701: RxDone                 = 27880

[  939.955322] TIWLAN: 537.822634: RxDefrag               = 48382

[  939.961242] TIWLAN: 537.828564: RxDefragEnd            = 20504

[  939.967163] TIWLAN: 537.834457: RxMic                  = 27845

[  939.973083] TIWLAN: 537.840385: RxMicEnd               = 0

[  939.978607] TIWLAN: 537.845929: RxXfr                  = 28639

[  939.984558] TIWLAN: 537.851857: RxXfrEnd               = 27880

[  939.990447] TIWLAN: 537.857751: RxCmplt                = 52620

[  939.996368] TIWLAN: 537.863678: RxPreCmplt             = 0

[  940.001953] TIWLAN: 537.869260: RxCmpltTask            = 52602

[  940.007843] TIWLAN: 537.875154: RxPhyHdr               = 74464

[  940.013793] TIWLAN: 537.881094: RxTimeout              = 13361

[  940.019683] TIWLAN: 537.886987: ------  RxFilters statistics  --------------

[  940.026824] TIWLAN: 537.894143: arpFilter    = 0

[  940.031555] TIWLAN: 537.898847: beaconFilter = 0

[  940.036193] TIWLAN: 537.903515: dataFilter   = 0

[  940.040863] TIWLAN: 537.908180: dupFilter    = 1111

[  940.045837] TIWLAN: 537.913146: MCFilter     = 0

[  940.050506] TIWLAN: 537.917813: ibssFilter   = 0

[  940.055206] TIWLAN: 537.922514: ------  Tx  statistics  -------------------

[  940.062286] TIWLAN: 537.929582: numOfTxTemplatePrepared    = 6405

[  940.068420] TIWLAN: 537.935738: numOfTxDataPrepared        = 22220

[  940.074707] TIWLAN: 537.942022: numOfTxTemplateProgrammed  = 7146

[  940.080871] TIWLAN: 537.948179: numOfTxDataProgrammed      = 35075

[  940.087158] TIWLAN: 537.954456: numOfTxBurstProgrammed     = 0

[  940.093078] TIWLAN: 537.960386: numOfTxStarts              = 67052

[  940.099334] TIWLAN: 537.966628: numOfTxImmResp             = 0

[  940.105255] TIWLAN: 537.972556: numOfTxStartTempaltes      = 6947

[  940.111450] TIWLAN: 537.978748: numOfTxStartIntTemplate    = 25493

[  940.117675] TIWLAN: 537.984992: numOfTxStartFwGen          = 2329

[  940.123870] TIWLAN: 537.991184: numOfTxStartData           = 32283

[  940.130126] TIWLAN: 537.997427: numOfTxStartNullFrame      = 0

[  940.136047] TIWLAN: 538.003355: numOfTxExch                = 66177

[  940.142333] TIWLAN: 538.009634: numOfTxRetryTemplate       = 542

[  940.148406] TIWLAN: 538.015704: numOfTxRetryData           = 12398

[  940.154663] TIWLAN: 538.021982: numOfTxExchPending         = 0

[  940.160552] TIWLAN: 538.027875: numOfTxExchExpiry          = 109

[  940.166656] TIWLAN: 538.033978: numOfTxExchMismatch        = 0

[  940.172607] TIWLAN: 538.039907: numOfTxDoneTemplate        = 6405

[  940.178741] TIWLAN: 538.046063: numOfTxDoneData            = 20648

[  940.185028] TIWLAN: 538.052340: numOfTxDoneIntTemplate     = 1572

[  940.191223] TIWLAN: 538.058535: numOfTxPreXfr              = 20648

[  940.197479] TIWLAN: 538.064779: numOfTxXfr                 = 22220

[  940.203735] TIWLAN: 538.071055: numOfTxXfrOutOfMem         = 0

[  940.209655] TIWLAN: 538.076950: numOfTxDmaProgrammed       = 22220

[  940.215911] TIWLAN: 538.083229: numOfTxDmaDone             = 22220

[  940.222198] TIWLAN: 538.089506: ------  Dma  statistics  -------------------

[  940.229309] TIWLAN: 538.096624: RxDMAErrors  = 0

[  940.234008] TIWLAN: 538.101325: TxDMAErrors  = 0

[  940.238677] TIWLAN: 538.105992: ------  Wep statistics  -------------------

[  940.245758] TIWLAN: 538.113057: WepAddrKeyCount   = 0

[  940.250854] TIWLAN: 538.118162: WepDefaultKeyCount= 0

[  940.256011] TIWLAN: 538.123304: WepKeyNotFound    = 27

[  940.261230] TIWLAN: 538.128533: WepDecryptFail    = 0

[  940.266326] TIWLAN: 538.133638: ------------  AES Statistics --------------

[  940.273406] TIWLAN: 538.140703: AesEncryptFail      = 2

[  940.278686] TIWLAN: 538.145984: AesDecryptFail      = 1070

[  940.284240] TIWLAN: 538.151560: AesEncryptPackets   = 20524

[  940.289886] TIWLAN: 538.157191: AesDecryptPackets   = 20504

[  940.295562] TIWLAN: 538.162857: AesEncryptInterrupt = 20630

[  940.301208] TIWLAN: 538.168524: AesDecryptInterrupt = 20504

[  940.306854] TIWLAN: 538.174153: ------  Events  -------------------

[  940.313201] TIWLAN: 538.180519: Calibration   = 75

[  940.318054] TIWLAN: 538.185362: rxMismatch    = 0

[  940.322845] TIWLAN: 538.190152: rxMemEmpty    = 0

[  940.327606] TIWLAN: 538.194906: ----------- PsPoll / Upsd -----------

[  940.334136] TIWLAN: 538.201446: psPollTimeOuts     = 0

[  940.339324] TIWLAN: 538.206640: upsdTimeOuts       = 5404

[  940.344818] TIWLAN: 538.212130: upsdMaxAPturn      = 89207

[  940.350372] TIWLAN: 538.217672: psPollMaxAPturn    = 0

[  940.355590] TIWLAN: 538.222899: psPollUtilization  = 0

[  940.360778] TIWLAN: 538.228094: upsdUtilization    = 108121

[  940.366455] TIWLAN: 538.233756: ----------- Calibrations -------------

[  940.373077] TIWLAN: 538.240386: calStateFail         = 0

[  940.378540] TIWLAN: 538.245844: initCalTotal                       = 1

[  940.383575] TIWLAN: 538.250896: initRadioBandsFail           = 0

[  940.389038] TIWLAN: 538.256351: initRxIqMmFail                 = 0

[  940.394287] TIWLAN: 538.261578: initSetParams                   = 0

[  940.399383] TIWLAN: 538.266684: initTxClpcFail                   = 0

[  940.404602] TIWLAN: 538.271910: tuneCalTotal                     = 0

[  940.409606] TIWLAN: 538.276928: tuneDrpwChanTune                     = 0

[  940.414764] TIWLAN: 538.282068: tuneDrpwLnaTank                        = 0

[  940.419769] TIWLAN: 538.287086: tuneDrpwPdBufFail                      = 0

[  940.425018] TIWLAN: 538.292312: tuneDrpwRTrimFail                      = 0

[  940.430206] TIWLAN: 538.297506: tuneDrpwRxDac                           = 0

[  940.435150] TIWLAN: 538.302471: tuneDrpwRxIf2Gain                      = 0

[  940.440368] TIWLAN: 538.307664: tuneDrpwRxTxLpf                        = 0

[  940.445404] TIWLAN: 538.312716: tuneDrpwTaCal                            = 0

[  940.450347] TIWLAN: 538.317647: tuneDrpwTxMixFreqFail   = 0

[  940.455841] TIWLAN: 538.323138: tuneRxAnaDcFail                         = 0

[  940.461151] TIWLAN: 538.328455: tuneRxIqMmFail                           = 0

[  940.466339] TIWLAN: 538.333648: tuneTxClpcFail                 = 0

[  940.471557] TIWLAN: 538.338876: tuneTxIqMmFail                           = 0

[  940.476776] TIWLAN: 538.344069: tuneTxLOLeakFail            = 0

[  940.482086] TIWLAN: 538.349383: tuneTxPdetFail                 = 0

[  940.487274] TIWLAN: 538.354575: tuneTxPPAFail                 = 0

[  940.492401] TIWLAN: 538.359714: ------  Power management  ----------

[  940.498840] TIWLAN: 538.366138: MissingBcnsCnt    = 1 (percentage <= 0)

[  940.505645] TIWLAN: 538.372943: RcvdBeaconsCnt    = 3406

[  940.511016] TIWLAN: 538.378312: ConnectionOutOfSync    = 1

[  940.511016]

[  940.518096] TIWLAN: 538.385391: Single Missed Beacon           = 63

[  940.524444] TIWLAN: 538.391760: 2 Continuous Missed Beacons    = 7

[  940.530700] TIWLAN: 538.398002: 3 Continuous Missed Beacons    = 0

[  940.536987] TIWLAN: 538.404279: 4 Continuous Missed Beacons    = 0

[  940.543243] TIWLAN: 538.410559: 5 Continuous Missed Beacons    = 0

[  940.549499] TIWLAN: 538.416803: 6 Continuous Missed Beacons    = 0

[  940.555786] TIWLAN: 538.423082: 7 Continuous Missed Beacons    = 0

[  940.562042] TIWLAN: 538.429361: 8 Continuous Missed Beacons    = 0

[  940.568298] TIWLAN: 538.435604: 9 Continuous Missed Beacons    = 0

[  940.574584] TIWLAN: 538.441882: >=10 Continuous Missed Beacons = 0

[  940.574584]

[  940.582366] TIWLAN: 538.449660: RcvdAwakeBeaconsCnt    = 209

[  940.588104] TIWLAN: 538.455403: Single Missed Beacon        [Awake] = 1

[  940.594909] TIWLAN: 538.462211: 2 Continuous Missed Beacons [Awake] = 0

[  940.601623] TIWLAN: 538.468928: 3 Continuous Missed Beacons [Awake] = 0

[  940.608306] TIWLAN: 538.475610: 4 Continuous Missed Beacons [Awake] = 0

[  940.615020] TIWLAN: 538.482324: 5 Continuous Missed Beacons [Awake] = 0

[  940.621734] TIWLAN: 538.489041: 6 Continuous Missed Beacons [Awake] = 0

[  940.628417] TIWLAN: 538.495722: 7 Continuous Missed Beacons [Awake] = 0

[  940.635131] TIWLAN: 538.502439: 8 Continuous Missed Beacons [Awake] = 0

[  940.641845] TIWLAN: 538.509155: 9 Continuous Missed Beacons [Awake] = 0

[  940.648529] TIWLAN: 538.515835: >=10 Continuous Missed Beacons [Awake] = 0

Regards,

Eyal

Hi Eyal,

Here are the debug logs from two different APs. Please let me know if you need more info.

======================================================================

1. Netgear MBR624GU in g-only mode, dhcp, wmm, no security

======================================================================

TIWLAN: 2298.528: numOfTxProcs = 0

======================================================================

2. Aruba800 in g-mode, wmm, WPS-PSK/AES

======================================================================

TIWLAN: 1581.059: ------ Ring statistics -------------------

TIWLAN: 1581.065: numOfTxProcs = 0

TIWLAN: 1581.069: numOfPreparedDescs = 294

TIWLAN: 1581.072: numOfTxXfr = 0

TIWLAN: 1581.076: numOfTxDma = 0

TIWLAN: 1581.080: numOfTxCmplt = 294

TIWLAN: 1581.084: numOfRxProcs = 771

TIWLAN: 1581.087: numOfRxData = 0

TIWLAN: 1581.091: ------ Debug statistics -------------------

TIWLAN: 1581.097: debug1 = 98032

TIWLAN: 1581.100: debug2 = 0

TIWLAN: 1581.102: debug3 = 0

TIWLAN: 1581.105: debug4 = 0

TIWLAN: 1581.108: debug5 = 0

TIWLAN: 1581.110: debug6 = 0

TIWLAN: 1581.113: ------ Isr statistics -------------------

TIWLAN: 1581.118: IRQs = 43844

TIWLAN: 1581.121: ------ Rx statistics -------------------

TIWLAN: 1581.127: RxOutOfMem = 0

TIWLAN: 1581.131: RxHdrOverflow = 0

TIWLAN: 1581.135: RxHWStuck = 0

TIWLAN: 1581.139: RxDroppedFrame = 14

TIWLAN: 1581.143: RxCompleteDroppedFrame = 0

TIWLAN: 1581.147: RxAllocFrame = 0

TIWLAN: 1581.151: RxDoneQueue = 1426

TIWLAN: 1581.155: RxDone = 1501

TIWLAN: 1581.159: RxDefrag = 2196

TIWLAN: 1581.164: RxDefragEnd = 695

TIWLAN: 1581.168: RxMic = 1501

TIWLAN: 1581.172: RxMicEnd = 0

TIWLAN: 1581.176: RxXfr = 1511

TIWLAN: 1581.180: RxXfrEnd = 1501

TIWLAN: 1581.185: RxCmplt = 2509

TIWLAN: 1581.189: RxPreCmplt = 0

TIWLAN: 1581.193: RxCmpltTask = 2509

TIWLAN: 1581.197: RxPhyHdr = 33250

TIWLAN: 1581.202: RxTimeout = 177

TIWLAN: 1581.206: ------ RxFilters statistics --------------

TIWLAN: 1581.211: arpFilter = 0

TIWLAN: 1581.214: beaconFilter = 0

TIWLAN: 1581.218: dataFilter = 0

TIWLAN: 1581.221: dupFilter = 1

TIWLAN: 1581.224: MCFilter = 0

TIWLAN: 1581.227: ibssFilter = 0

TIWLAN: 1581.230: ------ Tx statistics -------------------

TIWLAN: 1581.236: numOfTxTemplatePrepared = 698

TIWLAN: 1581.240: numOfTxDataPrepared = 428

TIWLAN: 1581.245: numOfTxTemplateProgrammed = 808

TIWLAN: 1581.249: numOfTxDataProgrammed = 428

TIWLAN: 1581.254: numOfTxBurstProgrammed = 408

TIWLAN: 1581.258: numOfTxStarts = 2121

TIWLAN: 1581.265: numOfTxImmResp = 0

TIWLAN: 1581.268: numOfTxStartTempaltes = 807

TIWLAN: 1581.272: numOfTxStartIntTemplate = 886

TIWLAN: 1581.277: numOfTxStartFwGen = 166

TIWLAN: 1581.281: numOfTxStartData = 262

TIWLAN: 1581.286: numOfTxStartNullFrame = 0

TIWLAN: 1581.290: numOfTxExch = 2121

TIWLAN: 1581.295: numOfTxRetryTemplate = 110

TIWLAN: 1581.299: numOfTxRetryData = 72

TIWLAN: 1581.304: numOfTxExchPending = 34

TIWLAN: 1581.308: numOfTxExchExpiry = 1

TIWLAN: 1581.312: numOfTxExchMismatch = 0

TIWLAN: 1581.317: numOfTxDoneTemplate = 698

TIWLAN: 1581.321: numOfTxDoneData = 294

TIWLAN: 1581.326: numOfTxDoneIntTemplate = 134

TIWLAN: 1581.330: numOfTxPreXfr = 294

TIWLAN: 1581.335: numOfTxXfr = 428

TIWLAN: 1581.340: numOfTxXfrOutOfMem = 0

TIWLAN: 1581.344: numOfTxDmaProgrammed = 428

TIWLAN: 1581.348: numOfTxDmaDone = 428

TIWLAN: 1581.353: ------ Dma statistics -------------------

TIWLAN: 1581.359: RxDMAErrors = 0

TIWLAN: 1581.362: TxDMAErrors = 0

TIWLAN: 1581.365: ------ Wep statistics -------------------

TIWLAN: 1581.370: WepAddrKeyCount = 0

TIWLAN: 1581.374: WepDefaultKeyCount= 0

TIWLAN: 1581.377: WepKeyNotFound = 0

TIWLAN: 1581.381: WepDecryptFail = 0

TIWLAN: 1581.385: ------------ AES Statistics --------------

TIWLAN: 1581.390: AesEncryptFail = 0

TIWLAN: 1581.394: AesDecryptFail = 0

TIWLAN: 1581.398: AesEncryptPackets = 290

TIWLAN: 1581.402: AesDecryptPackets = 695

TIWLAN: 1581.405: AesEncryptInterrupt = 290

TIWLAN: 1581.409: AesDecryptInterrupt = 695

TIWLAN: 1581.413: ------ Events -------------------

TIWLAN: 1581.418: Calibration = 7

TIWLAN: 1581.421: rxMismatch = 0

TIWLAN: 1581.425: rxMemEmpty = 0

TIWLAN: 1581.428: ----------- PsPoll / Upsd -----------

TIWLAN: 1581.433: psPollTimeOuts = 32

TIWLAN: 1581.437: upsdTimeOuts = 0

TIWLAN: 1581.440: upsdMaxAPturn = 0

TIWLAN: 1581.444: psPollMaxAPturn = 12753

TIWLAN: 1581.448: psPollUtilization = 544

TIWLAN: 1581.452: upsdUtilization = 0

TIWLAN: 1581.455: ----------- Calibrations -------------

TIWLAN: 1581.460: calStateFail = 0

TIWLAN: 1581.464: initCalTotal = 1

TIWLAN: 1581.468: initRadioBandsFail = 0

TIWLAN: 1581.472: initRxIqMmFail = 0

TIWLAN: 1581.475: initSetParams = 0

TIWLAN: 1581.479: initTxClpcFail = 0

TIWLAN: 1581.483: tuneCalTotal = 0

TIWLAN: 1581.486: tuneDrpwChanTune = 0

TIWLAN: 1581.490: tuneDrpwLnaTank = 0

TIWLAN: 1581.493: tuneDrpwPdBufFail = 0

TIWLAN: 1581.497: tuneDrpwRTrimFail = 0

TIWLAN: 1581.501: tuneDrpwRxDac = 0

TIWLAN: 1581.504: tuneDrpwRxIf2Gain = 0

TIWLAN: 1581.508: tuneDrpwRxTxLpf = 0

TIWLAN: 1581.511: tuneDrpwTaCal = 0

TIWLAN: 1581.514: tuneDrpwTxMixFreqFail = 0

TIWLAN: 1581.518: tuneRxAnaDcFail = 0

TIWLAN: 1581.522: tuneRxIqMmFail = 0

TIWLAN: 1581.526: tuneTxClpcFail = 0

TIWLAN: 1581.529: tuneTxIqMmFail = 0

TIWLAN: 1581.533: tuneTxLOLeakFail = 0

TIWLAN: 1581.537: tuneTxPdetFail = 0

TIWLAN: 1581.541: tuneTxPPAFail = 0

TIWLAN: 1581.544: ------ Power management ----------

TIWLAN: 1581.549: MissingBcnsCnt = 1088 (percentage <= 7)

TIWLAN: 1581.554: RcvdBeaconsCnt = 13756

TIWLAN: 1581.558: ConnectionOutOfSync = 0

TIWLAN: 1581.563: Single Missed Beacon = 837

TIWLAN: 1581.571: 2 Continuous Missed Beacons = 98

TIWLAN: 1581.572: 3 Continuous Missed Beacons = 9

TIWLAN: 1581.577: 4 Continuous Missed Beacons = 2

TIWLAN: 1581.582: 5 Continuous Missed Beacons = 4

TIWLAN: 1581.587: 6 Continuous Missed Beacons = 0

TIWLAN: 1581.591: 7 Continuous Missed Beacons = 0

TIWLAN: 1581.596: 8 Continuous Missed Beacons = 0

TIWLAN: 1581.601: 9 Continuous Missed Beacons = 0

TIWLAN: 1581.605: >=10 Continuous Missed Beacons = 0

TIWLAN: 1581.610: RcvdAwakeBeaconsCnt = 8

TIWLAN: 1581.614: Single Missed Beacon [Awake] = 0

TIWLAN: 1581.619: 2 Continuous Missed Beacons [Awake] = 0

TIWLAN: 1581.625: 3 Continuous Missed Beacons [Awake] = 0

TIWLAN: 1581.630: 4 Continuous Missed Beacons [Awake] = 0

TIWLAN: 1581.635: 5 Continuous Missed Beacons [Awake] = 0

TIWLAN: 1581.640: 6 Continuous Missed Beacons [Awake] = 0

TIWLAN: 1581.645: 7 Continuous Missed Beacons [Awake] = 0

TIWLAN: 1581.650: 8 Continuous Missed Beacons [Awake] = 0

TIWLAN: 1581.655: 9 Continuous Missed Beacons [Awake] = 0

TIWLAN: 1581.661: >=10 Continuous Missed Beacons [Awake] = 0

Regards,

Tiegang

Hi,

So with the Netgear you get:

TIWLAN: 2299.013: MissingBcnsCnt = 574 (percentage <= 2)

IWLAN: 2299.018: RcvdBeaconsCnt = 21192

TIWLAN: 2299.026: Single Missed Beacon = 508

TIWLAN: 2299.034: 2 Continuous Missed Beacons = 22

TIWLAN: 2299.036: 3 Continuous Missed Beacons = 7

With Aruba

TIWLAN: 1581.549: MissingBcnsCnt = 1088 (percentage <= 7)

TIWLAN: 1581.554: RcvdBeaconsCnt = 13756

TIWLAN: 1581.558: ConnectionOutOfSync = 0

TIWLAN: 1581.563: Single Missed Beacon = 837

TIWLAN: 1581.571: 2 Continuous Missed Beacons = 98

TIWLAN: 1581.572: 3 Continuous Missed Beacons = 9

TIWLAN: 1581.577: 4 Continuous Missed Beacons = 2

TIWLAN: 1581.582: 5 Continuous Missed Beacons = 4

So we can see that there lots of missing beacons with Aruba, the firmware is getting wake however sometimes is not receiving beacons. Have you tried that in clean environment that is in a place were no much Access point around (like in chamber)?

can you measure the current consumption drown by the 1271? if so then by that we can verify that the 1271 is waking up in acurate interval (should be every beacon) and that there is no issues with the fast clock that may cause un accurate waking up times. the current plot will show around 90mA while waking up to recive the beacon and then aroun 1 mA between beacons.

any way there is a major difference between in the missing beacons between the Netgear and the Aruba that has to be consider

Regards,

Eyal 

Eyal,

Thanks. I will get more logs in a cleaner environment. I do have a few more questions,

1. Suppose the firmware wakes up in accurate interval, how am I going to know if it wakes up at the correct time? The waking up could be out of sync with the beacon?

2. Do you think that the sleep clock may drift away? Do you do any dynamic correction or calibration to the slow clock?

3. You mentioned that the fast clock may affect the waking up time. Could you explain?

Just FYI, I set the AP to convert broadcast ARP requests into unicast, then I rarely see the missing of the first few pings. Could you comment on this?

Regards,

Tiegang

Hi Tiegang

There are several mechanism that should align the wakeup time of the 1271 module to the Access beacon. First every time the firmware receives beacon it uses the TBTT (time between beacons) field in the beacon to fix make adaptation to the calculation of the next wakeup (or time when the next beacon is expected). In addition there a mechanism to track the Access point access point and to overcome some amount of jitter of the Access point.

as for the slow clock, in case using a high PPM clock generator then it is possible that the wake up time will not be correct and we will see a beacon miss, also in my previous response I meant slow clock and not fast clock, since when the 1271 is in ELP then the slow clock is the Active clock and it is the one that is being used to calculate the time to wake up from ELP and receive the next beacon

Regards,

Eyal

Eyal,

I got some more debug info from a clean environment. The device was left there in idle state. The AP is from Aruba Networks. I still see 1% beacons missing. Do you really think that the AP is to blame?

TIWLAN: 16274.923: ------ Ring statistics -------------------

TIWLAN: 16274.923: numOfTxProcs = 0

Hi T. Li

From your response it is not clear if you see the ARP issue in clear environment, I assume that you did not try it since you mentioned that you left the AP in Idle, based on the statistic there is very good improvement (although the number is still high for clean environment) and might also proved that the Aruba has big jitter in Beacons in noisy environment and I am sure that if you try the Netgear AP then the results will be much lower.

However to be on the safe side we can try alternative way which is to measure the current consumption of the 1271 chip and according to the result see the waking for beacons period and if we see that the wake up period is constant over time and matches the beacon time period then we can assume that there is no issue with the wake up time, in order to measure the current consumption you will have to use a current probe with Oscilloscope with memory so we can have the capture over time.

Regards,

Eyal

Hi.  Has this issue been resolved?  Seeing similar issue in a design I am working on.

Hi James,

There was no further discussion on the subject, can you provide more details on the Platform and Operating system you are using? In addition what is the issue that you see and in what scenario?

Thanks,

Eyal

Hi Eyal.

Environment is :

• Android Gingerbread tablet
• OMAP 4430
• WL1271 inside a Murata BT/WIFI module

With power save enabled in the tiwlan.ini file, we have extremely poor wifi performance and notice that there are "recoveries" going on in the kernel log.  Usually watchdog timer expiries followed by recovery.   We can tell when it goes bad by monitoring the wifi current and also by the browser basically hanging up and not finishing loading a page.  When current drops down to it's "idle" current of about 2mA we know we've hit the problem.  The AP is a Cisco Linksys E1000 and is sitting right beside the unit.

With power save disabled, we get really good wifi performance and no recoveries.

Specific flags we are changing in the INI are:

Failed settings:

• dot11PowerMode = 0 (auto)
• defaultPowerLevel = 0 (ELP)
• powerSavePowerLevel = 0 (ELP)

Rock solid settings (apart from the fact it consumes 87mA ALL the time :) which we clearly cannot live with):

• dot11PowerMode = 1 (active)
• defaultPowerLevel = 2 (awake)
• powerSavePowerLevel = 2 (awake)

Thanks in advance for your help,

Jamie

The power saving issue I had is still open. I had my APs to convert the broadcast/multicast packets into unicasts and the situation becomes much better.

Lately I do see the recoveries (due to ps failure) being triggered when the systen gets busy and the driver just don't recover successfully. I am debugging this issue now.

Hi,

can you verify the following parameters in the ini file?

BeaconReceiveTime = 50

DcoItrimEnabled = 0  # 0 - Disabled  1 - Enabled
DcoItrimModerationTimeout = 50000

PowerMgmtHangOverPeriod = 10    #in mSec units

RxBroadcastInPs = 1

PsPollDeliveryFailureRecoveryPeriod = 20  # Time in Ms to stay ACTIVE ('0' to disable feature)
ConsecutivePsPollDeliveryFailureThreshold = 4   # Number of failed PsPoll's to start ACTIVE time out

Regards,

Eyal

Eyal,

Yes, they are all been set exactly the same as yours.

Just for testing, I've also tried to set the following but made no difference

PsPollDeliveryFailureRecoveryPeriod = 30             # 20  # Time in Ms to stay ACTIVE ('0' to disable feature)
ConsecutivePsPollDeliveryFailureThreshold = 5   #4     # Number of failed PsPoll's to start ACTIVE time out

 Regards,

Tiegang

Eyal, would you be able to tell me exactly what the causes for "HW_WD_EXPIRE" can be?  I know that this condition is generated by the WL1271 hardware/firmware.  My assumption is that it occurs when the FW stops feeding the HW watchdog inside the WL1271 (ie. FW has gone a bit crazy) and the HW fires off this condition to initiate a recovery process that is done by the WLAN driver on the OMAP side.

We really need to know the reasons for this particular event (HW_WD_EXPIRE).   Can you enumerate the mechanisms that the WL1271 will initiate this HW_WD_EXPIRE to the host OMAP?  Are there conditions other than "insane firmware no longer feeding the watchdog" that this can occur? Please be as detailed as you can.  We are trying to see what, if anything, in our environment or test conditions could possibly cause this.  (Yes we are investigating the usual clock/voltage/noise etc.. things.. we just need information on this particular event for now.)

Thanks,

Jamie

I am still having problems with operating the wifi in power saving mode. The symptoms are

1. Not responding to the first 3-7 pings from remote if the device has been in idle for a while.

2. Can't maintain a stable FTP session. It times out frequently.

3. The station disconnects/re-connects quite often.

I am posting three logs from the driver. Please help me to diagnose the problems. What I see from the log are

1. High percentage of beacon loss.

2. High rate of TX retries

3. High rate of RX timeouts

4. High rate of AES decryption failures.

5. High percentage of PsPoll/UPSD timeouts

These seem all related to the power saving to me.

***************************************************

LOG-1 Netgear AP, FTP receiving, Office environment

***************************************************

Thanks for help!

Tiegang

Hi Tiegang,

Since it is winCE than i am not familiar with the commands, however do you know how to set the power management configuration and to work in Active mode? although usually it should not have such an effect for the issues you see.

in addition did you try to perform Calibration? that could explain some of the issues that you see especially transmission. in addition did you try to work in a place were there are no much WiFi traffic around since it looks like you work in very crowded place (WiFi concerns)

Regards,

Eyal

Hi, Eyal,

Wifi in ACTIVE mode works much better than in PS mode.

Wifi does perform better in an environment with less traffric.

The tests I posted were done on a standalone network with only one AP. The environment is not clean but it is a typical office building.

Regarding to the calibration you suggested, do I need to perform the cal everytime when the device is booted up? I thought it should be done only once and the cal data is stored on the device for later use.

Also do you have a good set of the settings (the parameters in the .ini file) for WL127x to operate in power saving mode? Do you have any suggestion for AP settings as well? We have full control of the APs and network.

Thanks for help.

Tiegang

Hi Eyal,

I've attached a WireShark capture from a ping session. The AID is 1. Could you help me to see why are there missed pings?

Another question for you. For this particular wlan, which power save works bettwr, PSPoll or UPSD?

I really need help from you guys.

Thanks,

Tiegang

7607.WireShark_Ping_AID-1.rar

Hi TL,

I read this long thread. Just to keep things clear, there are 2 versions of WLAN out there:

• MCP driver set - TI code. Versions look like M5, M6, MCP2.5, MCP3, Full MLME driver set. There are couple of already exists porting to it: Linux, ThreadX, WinCE, WinMB, QNX. 
• NLCP - Open source community driver. Works only on Linux. Versions are R4, R5... Will be impossible to port to WinCE/WM/Compact (Since the MLME manage the open-source hostapd/wpa-supplicant)

In the MCP version there is no issue with PS.

Thanks,

Elad.

Hi, Elad,

I am using M6. I've been having trouble with PS since M5, especially in the environment where there are more APs and STAs around. If I have the PS turned off, everything seem work OK.

By the way, how do you know thare is no issue with PS? I am just curious.

Regards,

Tiegang

Hi T. Li,

Actually I posted this message as a replay to the beginning of the thread, and it posted at the end.

I took a look at your sniffer log (WireShark-ping-aid-1), seeing packets 1336 & 1337 and the fact that the WLAN is not polling the unicast is not so good.

The reason why i said what I have said is because I pass driver certification for M6, driver version "6.1.0.0.131" (Your original one) and I have tested both UPSD and legacy PS very carefully.

The issue that the WLAN don't poll the unicast that waits it is a FW issue apperantly. Which FW are you using?

Why won't you move up to higher SW version?

- Elad

Hi Elad,

Thanks for your reply. You are exactly right on the WLAN missing packet problem in the log. Actually the situation can be much worse if I don't set my APs to convert broadcast ARPs into unicast.

I am using the latest firmware I could find, version 6.1.0.1.349. This issue also exists in earlier versions of FW.  The driver is based on v6.1.0.1.149 which is also the latest release as I know.

 Regards,

Tiegang

I, like Jamie above, would like to better understand the causes for the HW_WD_EXPIRE.  I have checked all the suggestions for this issue, and we have done all that was recommended.

We are trying to determine if there is something we're doing from the host OMAP that could be causing the situation.

Thanks for any support,

Dennis O'Brien, EQware

Vineet,

MMC card is not an I/O card and is only used for storage. To access Wl1271 you need SDIO driver. From hardware standpoint it is the same controller.  thanks,

Saurabh

Dennis,

HW_WD_EXPIRE is due to hardware watchdog expiration on WLAN firmware. Host should kick in recovery mechanism on receiving h/w expiration interrupt

-At what frequency does the device get these interrupts ?

-What release are you using ?

-What steps have you taken to address this issue ?

Saurabh

Saurabh,

Thank you for your prompt response.

We see the issue periodically.  At times, the module appears to be in some unusuall state and we see the HW_WD_EXPIRE about every 5 minutes.

We are using the wilink-6.1.0.0.149 package from TI.  It contains:

TIWLAN: 3468.372157: CHIP VERSION... set 1273 chip top registers

TIWLAN: 3468.378688: Working on a 1273 PG 2.0 board.

TIWLAN: 3468.383418: Starting to process NVS...

TIWLAN: 3468.387721: NVS found, EEPROM Image addr=0xcef6f200, EEPROM Len=0x0x1d4

TIWLAN: 3468.395137: Chip ID is 0x4030111.

TIWLAN: 3468.399287: FEM Type 1

TIWLAN: 3468.402491: Starting to download firmware...

TIWLAN: 3468.454798: Starting to download firmware...

TIWLAN: 3468.471492: Starting to download firmware...

TIWLAN: 3468.476435: Starting to download firmware...

TIWLAN: 3468.485163: Starting to download firmware...

TIWLAN: 3468.491938: Starting to download firmware...

TIWLAN: 3468.497584: Finished downloading firmware.

TIWLAN: 3468.502253: Firmware running.

TIWLAN: 3468.525538:

TIWLAN: 3468.527583: --------------------------------------------------------------------

TIWLAN: 3468.535548: Driver Version  : WiLink_Driver_6.1.0.0.130

TIWLAN: 3468.541346: Firmware Version: Rev 6.1.0.1.349

TIWLAN: 3468.546260: Station ID      : 01-23-45-67-89-AB

TIWLAN: 3468.551356: --------------------------------------------------------------------

The reason we are asking for a better understanding of the possible causes of module HW_WD_EXPIRE, is so that we might be able to try something.  As is, we don't know why it is occurring and, therefore, don't know what we could do to address the issue.

Again, thank you in advance.  Your support is very much appreciated.

Dennis O'Brien, EQware

Hi Dennis,

You are using an old version of TI proprietary WiLink Driver. I recommend that you move to more recent version of proprietary driver or move to our latest offering i.e open source linux wireless driver ( this might require some porting effort). To checkif it is not an isolated issue, do you see hardware watchdog issue when device is connected to AP? If yes, can you please try connecting to another AP to check if it is an IOP issue. thanks,

saurabh

Saurabh,

Sorry for the slow response...

We usually see this issue when NOT connected to an AP.  As a matter of fact, I'm not sure if we see the when connected to an AP - I've only see it when NOT connected.

Could you supply a more information on why the firmware would have this issue?  Could there be something we're doing from the OMAP interface that is causing this?

Thanks for any help you can give.

Dennis

Saurabh,

Update - I reviewed older logs of the HW_WD_EXPIRE and found that it also does occur when connected to an AP.

So, we have see the HW_WD_EXPIRE event both when connected and when not connected to an AP.

Dennis

Hi Dennis,

WLAN firmware watchdog can expire due to multiple reasons  - it is self recovery mechanism for the firmware. Since you are using very old version of  WLAN driver/firmware, I suggest you upgrade to more recent version of driver/firmware. thanks,

saurabh