I'm using the TiWi-R2 (WL1271) and a ported Linux driver. When I issue the scan command, the device sends probe requests and I can see them with my sniffer. It also receives both beacons and probe responses just fine.
However, packets which are sent by writing them to the SLV_MEM_DATA register don't actually get sent. They are not seen by the sniffer they way the probe requests generated by the scan request are.
I write the increasing (with each packet) count to the HOST_WR_ACCESS register. Shortly thereafter, I get an interrupt and the fw status intr value indicates that it is a data interrupt.
Everything that chip reports back for the transmit done interrupt seems to indicated that the packet was sent:
- The tx_results_counter in the fw status increases by one for each packet
- The status field of thetx_hw_res_descr is 0 (success). This field seems to be updated after the transmit because the id field matches the one in tx_hw_descr which I wrote with the data to SLV_MEM_DATA.
The packets that I am attempting to transmit are probe requests. The 802.11 stack sends its own probe requests after the scan complete is indicated. Since the probe requests from the stack are different from those that are generated internally by the wl1271 as part of a scan request (different extended supported rates tag) I can distinguish the two.
What could the driver be doing which could cause the firmware to indicate that it sent out the frame without actually doing so?
Thanks,
Steve
