summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 7a9c881)
raw | patch | inline | side by side (parent: 7a9c881)
update firmwares: single role X.3.9.0.122, multi role X.5.7.0.33 R5.xx_Build-10 R5.xx_Build-11 R5.xx_Build-12 R5.xx_Build-13 R5.xx_Build-14 R5.xx_Build-15 R5.xx_Build-16 R5.xx_Build-17 R5.xx_Build-19 R5.xx_Build-20 R5.xx_Build-22 R5.xx_Build-23 R5.xx_Build-24 R5.xx_Build-25 R5.xx_Build-26 R5.xx_Build-27 R5.xx_Build-28 R5.xx_Build-32 R5.xx_Build-34 R5.xx_Build-35 R5.xx_Build-36 R5.xx_Build-37
| author | Ido Reis <idor@ti.com> | |
| Tue, 28 Aug 2012 13:29:38 +0000 (16:29 +0300) | ||
| committer | Ido Reis <idor@ti.com> | |
| Tue, 28 Aug 2012 13:29:38 +0000 (16:29 +0300) |
- Reconfigure internal FW templates in start role for BAR to support multiple
interfaces in SR mode (for JB)
- Bug fix: trigger scan is stuck and next channel is never invoked when
trigger scan process waits to be invoked from the context of tx
exchange and the last tx frame was a management
frame->TxNotifyTriggeredScanCB
- Fix EAPOL rx filtering and handle LastSequenceNumber per link.
- AES fix: Set PN default to 0xFFFF , because some APs send the first packet
with PN 0, and if default is 0 - the FW ignores it
- Update connection monitor - protect TSFMissedThreshold from situations when
the driver set TSFMissedThreshold to 0xFFFFFFFF
- Disconnect FIX- There are pending frames stuck in TX pending queue when: BA
session is established , BA_Expected =1/0. we suggested a fix for this
issue as described below:
the cause of this issue is when the host sends stop role command then
the FW tears down all the current BA session and clears any traffic
still left in TX queues. So during the disconnect process it calls to
Links_RemoveFLIDTxQueueIfTraffic function which marks the link as
pending removal and update the callback
processDisconnect_LinksRemovalCallback to be called once the link is
finally removable , that will finish the disconnect process.
But I saw that the number of frames for the current FLID had never
been zero at the stuck point , and so the callback will not be called.
The disconnect process should not be as I have described above. the
Links_RemoveFLIDTxQueueIfTraffic function should always call to the
callback whether the flid has traffic or not, and just to mark the FLID
as invalid.
- Keep alive fixes:
1.Remove the counter from the code if a frame is stuck in the FW
queues, the Tx watchdog (or Tx monitor) will issue and assert.
2.In the tx exchange callback, not to consider a frame that exceeded
retries or timed-out as a successful transmission indicating keep-live
to the peer.
3.Any frame that passes successfully resets the time stamp sampling
for the purpose of next keep alive.
4.Continue keep alive frames transmissions while they are not enqueued,
not successfully transmitted, and no other frame is successfully
transmitted.
- Increasing BAR Threshold from 10 to 50.
- Disable PHY Clock Gating in export_hdk.c.
- Split the connection scan while in AP mode so beacons will be transmitted in
between the connection scan.
- Enable Cortex Gating during AP/GO roles. The purpose of this functionality
is to gain lower Cortex current consumption while no real activity in
FW. Meaning, when FW is just running in main with no real
interrupts/processes pending, we will allow the Cortex to "go to sleep"
until any new interrupt will be invoked (HW interrupt, timers, etc).
- Adding mDNS Filter
Signed-off-by: Ido Reis <idor@ti.com>
interfaces in SR mode (for JB)
- Bug fix: trigger scan is stuck and next channel is never invoked when
trigger scan process waits to be invoked from the context of tx
exchange and the last tx frame was a management
frame->TxNotifyTriggeredScanCB
- Fix EAPOL rx filtering and handle LastSequenceNumber per link.
- AES fix: Set PN default to 0xFFFF , because some APs send the first packet
with PN 0, and if default is 0 - the FW ignores it
- Update connection monitor - protect TSFMissedThreshold from situations when
the driver set TSFMissedThreshold to 0xFFFFFFFF
- Disconnect FIX- There are pending frames stuck in TX pending queue when: BA
session is established , BA_Expected =1/0. we suggested a fix for this
issue as described below:
the cause of this issue is when the host sends stop role command then
the FW tears down all the current BA session and clears any traffic
still left in TX queues. So during the disconnect process it calls to
Links_RemoveFLIDTxQueueIfTraffic function which marks the link as
pending removal and update the callback
processDisconnect_LinksRemovalCallback to be called once the link is
finally removable , that will finish the disconnect process.
But I saw that the number of frames for the current FLID had never
been zero at the stuck point , and so the callback will not be called.
The disconnect process should not be as I have described above. the
Links_RemoveFLIDTxQueueIfTraffic function should always call to the
callback whether the flid has traffic or not, and just to mark the FLID
as invalid.
- Keep alive fixes:
1.Remove the counter from the code if a frame is stuck in the FW
queues, the Tx watchdog (or Tx monitor) will issue and assert.
2.In the tx exchange callback, not to consider a frame that exceeded
retries or timed-out as a successful transmission indicating keep-live
to the peer.
3.Any frame that passes successfully resets the time stamp sampling
for the purpose of next keep alive.
4.Continue keep alive frames transmissions while they are not enqueued,
not successfully transmitted, and no other frame is successfully
transmitted.
- Increasing BAR Threshold from 10 to 50.
- Disable PHY Clock Gating in export_hdk.c.
- Split the connection scan while in AP mode so beacons will be transmitted in
between the connection scan.
- Enable Cortex Gating during AP/GO roles. The purpose of this functionality
is to gain lower Cortex current consumption while no real activity in
FW. Meaning, when FW is just running in main with no real
interrupts/processes pending, we will allow the Cortex to "go to sleep"
until any new interrupt will be invoked (HW interrupt, timers, etc).
- Adding mDNS Filter
Signed-off-by: Ido Reis <idor@ti.com>
index 7286c5e6a7aa2a1adc369ed265723636ca34deaf..6cc5ebe1ccec658cfa3aea7ddd402c04b7b3109a 100755 (executable)
Binary files a/hw/firmware/wl127x-fw-4-mr.bin and b/hw/firmware/wl127x-fw-4-mr.bin differ
Binary files a/hw/firmware/wl127x-fw-4-mr.bin and b/hw/firmware/wl127x-fw-4-mr.bin differ
index b7b3a8804efe33b64e504abcac0b952aa3d51693..1e2cb7b9738de92776706da2d97cdab4788121d3 100755 (executable)
Binary files a/hw/firmware/wl127x-fw-4-plt.bin and b/hw/firmware/wl127x-fw-4-plt.bin differ
Binary files a/hw/firmware/wl127x-fw-4-plt.bin and b/hw/firmware/wl127x-fw-4-plt.bin differ
index e41475a68a4510bb7e3fb686d4abf93661b01473..9e9025b4d9b65a014b591f2469a6e9ac9788263d 100755 (executable)
Binary files a/hw/firmware/wl127x-fw-4-sr.bin and b/hw/firmware/wl127x-fw-4-sr.bin differ
Binary files a/hw/firmware/wl127x-fw-4-sr.bin and b/hw/firmware/wl127x-fw-4-sr.bin differ
index 267024aa060c917fa3b265176f1da98ce356c7a2..bb306edd3fd63b02382637b8c5e92ca259e84835 100755 (executable)
Binary files a/hw/firmware/wl128x-fw-4-mr.bin and b/hw/firmware/wl128x-fw-4-mr.bin differ
Binary files a/hw/firmware/wl128x-fw-4-mr.bin and b/hw/firmware/wl128x-fw-4-mr.bin differ
index 021f720229a580f65996a074ed6ce12a62a4fe49..98531627829397945db135b46e8ff04c03d6b9ad 100755 (executable)
Binary files a/hw/firmware/wl128x-fw-4-plt.bin and b/hw/firmware/wl128x-fw-4-plt.bin differ
Binary files a/hw/firmware/wl128x-fw-4-plt.bin and b/hw/firmware/wl128x-fw-4-plt.bin differ
index ce44c9680250c5a6c106e6565da8b35d5657b6d2..037e58fa718c46ec5d851f77a57c10522b1cd453 100755 (executable)
Binary files a/hw/firmware/wl128x-fw-4-sr.bin and b/hw/firmware/wl128x-fw-4-sr.bin differ
Binary files a/hw/firmware/wl128x-fw-4-sr.bin and b/hw/firmware/wl128x-fw-4-sr.bin differ