Changes between Version 44 and Version 45 of WARPLab/Downloads

Timestamp:

May 8, 2013, 12:57:05 PM (11 years ago)

Author:

chunter

Comment:

--

WARPLab/Downloads

@@ -23 +23 @@
 == Reference Design Archive ==
 
-The WARPLab reference design is packaged as a .zip file with the full source code and compiled bitstreams for the reference design. You can view the same source code in the repository ([source:/ResearchApps/PHY/WARPLAB/WARPLab7]). Please note the code in the repository is under active development. Feel free to experiment with it, but we make no guarantees it works until we package and release an updated ref design.
+The WARPLab reference design is packaged as a .zip file with the full source code and compiled bitstreams for the reference design. You can view the latest source code in the repository ([source:/ResearchApps/PHY/WARPLAB/WARPLab7]). Please note the code in the repository is under active development.
 
 The contents of the WARPLab reference design .zip file are explained below.
 
 === Bitstreams_Reference ===
-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 board 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].
+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]. For WARP v3 hardware, compact flash cards may be loaded with the provided .ace files for similar functionality (instructions provided [wiki:howto/CF_Config here]).
  * '''w3''': WARP v3 FPGA bitstreams (see [wiki:howto/SD_Config SD config howto] for help using the .bin file)
- * '''w2''': WARP v2 FPGA bitstreams
+ * '''w2''': WARP v2 FPGA bitstreams (see [wiki:howto/CF_Config CF config howto] for help using the .ace file)
 
 === EDK_Projects ===
 This folder contains EDK projects for various hardware configurations. The WARPLab FPGA design is built with the Xilinx Embedded Development Kit (EDK) software. The hardware design is constructed and implemented in EDK Xilinx Platform Studio (XPS). The software design, running in the MicroBlaze processor, is built in the Xilinx SDK. Opening these EDK projects requires a copy of the [wiki:edk_user_repository WARP edk_user_repository] at the SVN revision in the table above.
 
-If you want to use (but not modify) the reference FPGA design, you only need a bitstream and the reference M code. If you want to modify the MicroBlaze C code, you can download an EDK project in this folder, but only modify the SDK project contained therein. To modify the FPGA hardware design, you will need to modify the XPS project. The WARPLab FPGA design uses custom peripherals designed in Xilinx System Generator, including the warplab_buffers core. You will need MATLAB, Simulink and System Generator to modify these cores.
+If you want to use (but not modify) the reference FPGA design, you only need a bitstream and the reference M code. If you want to modify the MicroBlaze/PPC C code, you can download an EDK project in this folder, but only modify the SDK project contained therein. To modify the FPGA hardware design, you will need to modify the XPS project. The WARPLab FPGA design uses custom peripherals designed in Xilinx System Generator, including the warplab_buffers core. You will need MATLAB, Simulink and System Generator to modify these cores.
 
 Each of these EDK projects are 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.