Changes between Version 30 and Version 31 of 802.11/Usage

Oct 23, 2014, 1:22:00 PM (10 years ago)



  • 802.11/Usage

    v30 v31  
    55The 802.11 Reference Design is intended as a starting point for a wide variety of research projects. The sections below describe the default behaviors of the reference design and give pointers on where to start for customizing the design for your application.
    7  1. [wiki:./SDK Creating the SDK Workspace]
    9 == Reference Design Archive ==
    11 The Mango 802.11 Reference Design is packaged as a .zip file with the full source code and compiled bitstreams for the reference design. The latest release is available on the [wiki:../Download Dowload] page. You can view the latest source code in the repository ([source:/ReferenceDesigns/w3_802.11]). Please note the code in the repository is under active development.
    13 The contents of the 802.11 Reference Design .zip file are explained below.
    15 === LICENSE.txt ===
    16 This file explains terms under which the 802.11 Reference Design is released.
    18 === Bitstreams_Reference ===
    19 Bitstreams are fully-built designs that are ready to be downloaded onto WARP hardware. Files ending with the extension '.bit' may be downloaded using the Xilinx tool iMPACT. Files ending with the extension .bin may loaded onto an SD card so that the WARP v3 hardware will automatically be programmed whenever it is powered on and has the SD card inserted. Details on how to configure an SD card with a '.bin' file are [wiki:howto/SD_Config provided here].
    21 === EDK_Projects ===
    22 This folder contains an EDK project built with the Xilinx Embedded Development Kit (EDK) software. The hardware design is constructed and implemented in EDK Xilinx Platform Studio (XPS). The software designs, running in two MicroBlaze processors, are built in the Xilinx SDK. Opening the EDK project requires a copy of the [wiki:edk_user_repository WARP edk_user_repository] at the SVN revision in the table above.
    24 The EDK projects is a combination of an XPS project along with Eclipse software projects that can be imported into an SDK workspace. These software projects are present in the 'SDK_Workspace' subfolder of every XPS project -- we recommend using this folder as the location of the SDK Workspace. These projects can then be imported "in place" and will not need to be copied.
    26 === SysGen_Reference===
    27 This folder contains the source System Generator models for the PHY Rx, Tx, AGC and MAC-DCF. Each sub-folder also contains the init scripts and support files required by each model. These scripts and models are configured to run in simulation as-is. To run a simulation, open MATLAB, cd to one of the model directories (wlan_phy_rx_pmd, for example), open the .mdl file and click Run.
    29 === Python_Reference===
    30 This folder contains the reference version of the wlan_exp Python package and associated example scripts. See the [wiki:../wlan_exp/GettingStarted wlan_exp Getting Started] page for details on installing the wlan_exp package from this folder.
     7 * [wiki:./SDK Creating the SDK Workspace]
     8 * [wiki:./UserIO User I/O]
     9 * [wiki:./UART UART]
     10 * [wiki:./AP AP application]
     11 * [wiki:./STA STA application]
     12 * [wiki:./IBSS IBSS application]
    33 = AP vs STA Applications =
    35 The 802.11 Reference Design contains two implementations that share the same low-level MAC and PHY. These implementations are an access point (AP) that can be joined by 802.11 devices and a station (STA) that can join 802.11 APs (WARP or otherwise).
    37 == 802.11 AP ==
    39 By default, the AP Reference Design implements an 802.11 compatible access point with SSID "WARP-AP". To use the design in this configuration:
    41 1. Connect the WARP v3 ETH A interface to a local network, ideally one with a DHCP server and internet access. 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 pass DHCP requests and responses through its Ethernet portal to the wired network.
    42 1. Download the 802.11 Reference Design and program a WARP v3 board with the provided bitstream for the AP implementation.
    43 1. Use an 802.11 device (such as a computer or smartphone) to join the open network with SSID of "WARP-AP." The 802.11 device should associated successfully and communicate with the wired network (and internet, if the wired network has internet access).
    45 == 802.11 STA ==
    47 By default the Reference Design STA application will attempt to associate with an AP advertising the SSID of "WARP-AP." Programming one node with the AP design and one (or more) nodes with the STA design will automatically create a wireless network of associated nodes. The STA and AP node LEDs indicate association status (details below).
    49 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,
    51 1. 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 with other devices, especially other WARP v3 nodes running the STA application. This can create a circular bridge (wired-wireless-wired) that will behave badly.
    52 1. Download the 802.11 Reference Design and program a WARP v3 board with the provided bitstream for the STA implementation.
    53 1. Use the UART menu to associate with a nearby AP.
    54 1. Access the wireless network from the device that is plugged into ETH A.
    56 == Using the UART Menu ==
    58 Both 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. Because the 802.11 Reference Design contains two processors each with their own ability to print to UART, the User I/O dip switch on the board is used to select which UART output is driving the USB UART port on the board. The below menus assume you are connected to the UART that is driven by CPU_HIGH. To make this selection, ensure that the right-most dip switch in the User I/O section of the board is set to "up."
    60 === AP UART Capabilities ===
    62  * Change the advertised SSID
    63  * Change the channel
    64  * Change the rate used for unicast transmissions
    65  * Print the current status of transmit queues
    66  * Enter an interactive AP menu where
    67   * individual station statistics can be observed (e.g. last received power, packet counts, etc)
    68   * traffic can be locally generated for any number of connected stations
    70 === STA UART Capabilities ===
    72  * Perform an active scan and details about nearby access points
    73  * Associate with an access point displayed during the active scan
    74  * Change the rate used for unicast transmissions
    75  * Enter an interactive STA menu where
    76   * statistics about the associated AP can be observed (e.g. last received power, packet counts, etc)
    77   * traffic can be locally generated for the associated AP
    79 == LEDs ==
    80 The 802.11 Reference Design AP and STA implementations use the WARP v3 board LEDs as status indicators.
    82  * '''Green LEDs:''' increment for every error-free packet reception that passes the node's address filter
    83  * '''Red LEDs:''' increment on Rx PHY events with good SIGNAL field but bad payload checksum. Note: packets that are not detected or packets that are detected but contain a bad SIGNAL field are not displayed in any way in the LED bank.
    84  * '''Hex Displays:'''
    85   * AP: the AP hex displays blink slowly to indicate the AP is accepting new association requests. The number of active associations is displayed.
    86   * STA: the STA displays the node's current AID (association ID), as assigned by the AP. The STA displays 00 when not associated with an AP.
    90 == Debugging Software ==
    92 The dual-processor architecture of the 802.11 Reference Design presents some challenges in debugging the software applications.
    94 The usual debugging tools in the Xilinx SDK work fine with dual-processor designs. The Reference Design includes one instance of the mdm pcore. The mdm is connected to both MicroBlaze debug ports. The PC-side debug tools can connect to either MB via the mdm and xmd.
    96 Each MicroBlaze processor has an xps_uartlite peripheral mapped to stdin/stdout. The WARP v3 hardware has only one USB-UART transceiver. The Reference Design includes a uart_mux core which allows either xps_uartlite to connect to the USB-UART transceiver. By default the mux is controlled by the LSB of the user DIP switch on the WARP v3 board. A 0 (switch down) selects the UART for CPU Low.