Changes between Version 40 and Version 41 of WARPLab6


Ignore:
Timestamp:
Aug 31, 2012, 11:31:45 AM (12 years ago)
Author:
chunter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WARPLab6

    v40 v41  
    33= WARPLab Framework Overview =
    44
    5 WARPLab is a framework which brings together WARP and MATLAB. With WARPLab, you can interact with WARP nodes directly from the MATLAB workspace and signals generated in MATLAB can be transmitted in real-time over-the-air using WARP nodes. This facilitates rapid prototyping of physical layer (PHY) algorithms.
     5WARPLab is a framework which brings together WARP and MATLAB. With WARPLab, you can interact with WARP nodes directly from the MATLAB workspace and signals generated in MATLAB can be transmitted in real-time over-the-air using WARP nodes. This facilitates rapid prototyping of physical layer (PHY) algorithms directly in Matlab M-Code.
    66
    77The WARPLab setup is shown in the following figure.
    88
    99[[Image(warplab_architecture.png)]]
     10
     11WARPLab is very flexible, supporting any combination of WARP v1, v2, or v3 hardware. Furthermore, any number of radios on each WARP board are also supported.
    1012
    1113The design flow for a new PHY is the following:
    … …  
    1820== Example Setup ==
    1921
    20 Up to 16 WARP nodes and a host computer running MATLAB are connected to a switch via Ethernet links. The Ethernet links are used to transfer data to and from the WARP nodes. While the over-the-air transmission is real-time, the communication between the PC and the boards takes significantly longer. Check the [wiki:WARPLab/Benchmarks benchmarks] page for its performance characterization.
     22Up to 16 WARP nodes and a host computer running MATLAB are connected to a switch via Ethernet links. The Ethernet links are used to transfer data to and from the WARP nodes. While the over-the-air transmission is real-time, the communication between the PC and the boards takes longer.
    2123
    2224[[Image(warplab_setup.png)]]
    … …  
    2527
    2628In order to allow rapid prototyping, the WARPLab framework provides the following.
    27  * [wiki:WARPLab/RefDesign WARPLab XPS Reference Design]: The bitstream ('.bit' file) to program the WARP nodes and the WARPLab Xilinx Platform Studio (XPS) Reference Design to generate this bitstream are provided.
     29 * [wiki:WARPLab/RefDesign WARPLab XPS Reference Design]: The bitstream ('.bit' file) to program the WARP nodes and the WARPLab Embedded Development Kit (EDK) Reference Design to generate this bitstream are provided.
    2830 * [wiki:WARPLab/Releases WARPLab Reference M-Code]: M-Code functions that facilitate interaction with WARP nodes directly from MATLAB workspace are provided.
    2931 * [wiki:WARPLab/Releases WARPLab Examples]: M-Code examples that show how to use the WARPLab Reference M-Code are provided.
    3032
    31 The WARPLab framework facilitates experimental evaluation of PHY layer algorithms. However, some novel algorithms may require features not provided in the WARPLab framework. Users are encouraged to modify/extend the WARPLab XPS Reference Design and WARPLab Reference M-Code if this is required in order to meet experiment requirements. For example, if part of the signal processing cannot be done offline in MATLAB but must be done in real-time, then this signal processing can be implemented in FPGA logic by modifying the WARPLab XPS Reference Design. Depending on the experiment, the users may also have to modify the WARPLab Reference M-Code. The vanilla architecture is described [wiki:WARPLab/Architecture here] and [wiki:WARPLab/ExtendingWARPLab extending WARPLab] explains some of the steps needed to modify the system. Specifications of the radio parameters controllable from M-code are listed [wiki:WARPLab/Specifications here].
     33The WARPLab framework facilitates experimental evaluation of PHY layer algorithms. However, some novel algorithms may require features not provided in the WARPLab framework. Users are encouraged to modify/extend the WARPLab EDK Reference Design and WARPLab Reference M-Code if this is required in order to meet experiment requirements. For example, if part of the signal processing cannot be done offline in MATLAB but must be done in real-time, then this signal processing can be implemented in FPGA logic by modifying the WARPLab XPS Reference Design. Depending on the experiment, the users may also have to modify the WARPLab Reference M-Code. The vanilla architecture is described [wiki:WARPLab/Architecture here] and [wiki:WARPLab/ExtendingWARPLab extending WARPLab] explains some of the steps needed to modify the system. Specifications of the radio parameters controllable from M-code are listed [wiki:WARPLab/Specifications here].
    3234
    3335