Changes between Version 7 and Version 8 of WARPLab6/ExtendingWARPLab

Timestamp:

Sep 22, 2009, 8:36:01 AM (15 years ago)

Author:

mduarte

Comment:

--

WARPLab6/ExtendingWARPLab

@@ -3 +3 @@
 == Extending WARPLab ==
 
-The WAPLAB framework facilitates experimental evaluation of PHYsical (PHY) layer algorithms. However, some novel algorithms may require features not provided in the WARPLab framework. Users are encouraged to modify 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 to 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 WAPLAB framework facilitates experimental evaluation of PHYsical (PHY) layer algorithms. However, some novel algorithms may require features not provided in the WARPLab framework. Users are encouraged to modify 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.
 
 === WARPLab Design Flow - Sysgen to XPS ===
@@ -19 +19 @@
 === WARPLab Design Flow - C code and M-Code ===
  * Commands or actions to be executed by the WARP nodes are sent from MATLAB using the 'warplab_' functions provided in the WARPLab Reference M-Code. The possible commands/actions that can be executed are identified by an ID (or opcode) in the 'warplab_defines.m' and 'warplab_defines.h' files. The 'warplab_defines.m' is part of the WARPLab Reference M-Code and the 'warplab_defines.h' is part of the WARPLab XPS Reference Design (src folder).
- * The WARPLab C code (warplab_mimo_2x2.c for 2x2 MIMO bitstream and warplab_mimo_4x4.c for 4x4 MIMO bitstream) implements an infinite loop that is listening to Ethernet packets. When an Ethernet packet is received the ID (or opcode) of the command/action to be executed is read from the received packet, based on the ID the C code enters a specific CASE statement, when the CASE statement executed the code returns to its initial state of listening to Ethernet packets.
+ * The WARPLab C code (warplab_mimo_2x2.c for 2x2 MIMO bitstream and warplab_mimo_4x4.c for 4x4 MIMO bitstream) implements an infinite loop that is listening to Ethernet packets. When an Ethernet packet is received the ID (or opcode) of the command/action to be executed is read from the received packet, based on the ID the C code enters a specific CASE statement, when the CASE statement is executed the code returns to its initial state of listening to Ethernet packets.