Changes between Version 13 and Version 14 of 802.11/Usage


Ignore:
Timestamp:
Oct 11, 2013, 1:24:48 PM (11 years ago)
Author:
chunter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 802.11/Usage

    v13 v14  
    55= 802.11 Reference Design: Usage =
    66
    7 By default, the Reference Design implements an 802.11 compatible access point with SSID "WARP-AP". To use the design in this configuration:
     7The 802.11 Reference Design contains two implementations that share much of the same MAC and PHY. These implementations are an AP that can be joined by 802.11 devices and a station (STA) that can be used to join 802.11 APs (WARP or otherwise).
     8
     9== 802.11 AP ==
     10
     11By default, the AP Reference Design implements an 802.11 compatible access point with SSID "WARP-AP". To use the design in this configuration:
    812
    9131. Plug ETH A from a WARP v3 board into a router whose WAN port is connected to the Internet. The 802.11 Reference Design is not a router -- it does not have a DHCP server to issue IP addresses to associated stations. It will, however, pass DHCP requests and responses through its Ethernet portal, so connecting WARP v3 to a router will allow DHCP to occur on client stations.
    10 1. Download the 802.11 Reference Design and program a WARP v3 board with the provided bitstream.
     141. Download the 802.11 Reference Design and program a WARP v3 board with the provided bitstream for the AP implementation.
    11151. Use any 802.11 device (such as a computer or smartphone) to join the unsecured network with SSID of "WARP-AP." At this point, the 802.11 device should be able to access the network.
     16
     17== 802.11 STA ==
     18
     19By default, the STA Reference Design will attempt to associate with an AP that is advertising an SSID of "WARP-AP." The stock AP Reference Design meets this criteria, so programming one board with the AP design followed by programming another board with the STA design is sufficient to create a connection. Alternatively, the UART menu on the station can be used to perform an active scan and display the list of all nearby APs and their SSIDs. This menu can then be used to attempt association to one of those APs. TO use this design,
     20
     211. Plug ETH A from a WARP v3 board into a single Ethernet device such as a laptop or desktop PC. The STA design will bridge the Ethernet link of that device to the 802.11 wireless link. NOTE: do not plug ETH A into a switch if that switch has more than one Ethernet device on it. The current STA implementation assumes that all traffic it receives over Ethernet comes from a single source.
     221. Download the 802.11 Reference Design and program a WARP v3 board with the provided bitstream for the STA implementation.
     231. Use the UART menu to associate with a nearby AP.
     241. Access the wireless network with the device that is plugged into ETH A.
     25
     26== Using the UART Menu ==
     27
     28Both the AP and STA implementations include extensive control of parameters via UART. The instructions [wiki:howto/USB_UART provided here] show how to connect to the USB UART on WARP v3. The 802.11 Reference Design uses a baud rate of 115200 for all UART interactions.
     29
     30=== AP UART Capabilities ===
     31
     32 * Change the advertised SSID
     33 * Change the channel
     34 * Change the rate used for unicast transmissions
     35 * Print the current status of transmit queues
     36 * Enter an interactive AP menu where
     37  * individual station statistics can be observed (e.g. last received power, packet counts, etc)
     38  * traffic can be locally generated for any number of connected stations
     39
     40
     41=== STA UART Capabilities ===
     42
     43 * Perform an active scan and details about nearby access points
     44 * Associate with an access point displayed during the active scan
     45 * Change the rate used for unicast transmissions
     46 * Enter an interactive STA menu where
     47  * statistics about the associated AP can be observed (e.g. last received power, packet counts, etc)
     48  * traffic can be locally generated for the associated AP
     49
     50
     51
    1252
    1353== Creating the SDK Workspace ==
     
    20601. Launch Xilinx SDK and select {{{<xps_proj>/SDK_Workspace}}} as the active workspace
    21611. Select Xilinx Tools -> Repositories. In Local Repositories click New, then select {{{<xps_proj>/}}} and click OK.
    22 1. Import the 5 SDK projects provided by the reference design
     621. Import the 7 SDK projects provided by the reference design
    2363  1. Select File -> Import
    2464  1. Expand General -> Existing Projects into Workspace, click Next
     
    2969wlan_bsp_cpu_low
    3070wlan_mac_ap
     71wlan_mac_sta
    3172wlan_mac_dcf
    3273wlan_mac_shared
    3374wlan_xps_vXX_hw_platform  <- the version number in this project name will change between releases
    3475}}}
    35   1. Ensure all 6 projects are checked and click Finish
     76  1. Ensure all 7 projects are checked and click Finish
    3677  1. In the SDK Project Explorer:
    3778    1. Right click on the {{{wlan_mac_ap}}} project and select Change Referenced BSP. In the dialog box select {{{wlan_bsp_cpu_high}}} then click OK
    3879    1. Right click on the {{{wlan_mac_dcf}}} project and select Change Referenced BSP. In the dialog box select {{{wlan_bsp_cpu_low}}} then click OK
    3980    1. Right click on the {{{wlan_mac_ap}}} project and select Clean Project
     81    1. Right click on the {{{wlan_mac_sta}}} project and select Clean Project
    4082    1. Right click on the {{{wlan_mac_dcf}}} project and select Clean Project
    41831. Both software projects should now build to completion. Watch the console for the message {{{elfcheck passed}}}