| | 1 | [[TracNav(HardwareUsersGuides/WARPv3/TOC)]] |
| | 2 | = WARP v3 User Guide: Porting Designs from WARP v1/v2 = |
| | 3 | |
| | 4 | This page will be something of a "core dump" for a while, as we post observations, tricks and recommendations for users of WARP v1/v2 hardware looking to use WARP v3. |
| | 5 | |
| | 6 | If you have any related questions or recommendations, please let us know (preferably via the [//forums forums]). |
| | 7 | |
| | 8 | '''Notes:''' |
| | 9 | * The V6 doesn't have an embedded processor, so processor-based designs need to port to MicroBlaze. We're working on the OFDM and WARPLab reference designs and are (so far) impressed by how seamless the PPC->MB transition was. All of the Xilinx-supplied pcores/drivers are agnostic to the underlying processor. The only code changes we made were to accomodate driver changes from XPS 10.1 to 13.4. |
| | 10 | |
| | 11 | * The release of new hardware seemed like a good time to redesign some of the WARP-specific pcores/drivers that we'd developed over the years. The radio controller driver, for example, was in desperate need of re-design. The old driver worked, but had a very inconsistent API (the natural result of having been written by multiple over over the course of many years, as the WARP reference designs became more advanced). The new radio controller and driver provide the same functionality but with a much more compact and consistent API. Same goes for the user IO and EEPROM pcores/drivers. |
| | 12 | |
| | 13 | * more to come.. |
