Changes between Version 8 and Version 9 of Good Design Flow Practice for XPS8.0
- Timestamp:
- Jun 28, 2006, 10:41:15 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Good Design Flow Practice for XPS8.0
v8 v9 5 5 Despite being granted such freedoms, however, XPS can be extremely picky about how things are named and where they are placed -- even the order in which you generate different parts of the system. That said, this section will contain a system of steps and notes, that although some of which may not be required, will help ensure that you avoid any unnecessary errors that might set you back hours or days. 6 6 7 == 1: Project Creation == 7 == 1: Xilinx and EDK Installation == 8 9 Technically, you can install Xilinx XPS and the EDK anywhere and it will function -- you may however notice inconsistencies, such as projects that won't generate, XBD files that can't be found, etc. etc. A tried and true method that will ensure none of this will happen is to perform your installations into the following directories: [[BR]] [[BR]] 10 Xilinx XPS Install Path: [[BR]] 11 {{{ 12 c:\Xilinx 13 }}} 14 Xilinx EDK Install Path: [[BR]] 15 {{{ 16 c:\EDK 17 }}} 18 If you ever perform an update/install a newer version of these toolsets and want to keep the old versions, available -- just rename the old folders from "Xilinx" and "EDK", to "Xilinx7" and "EDK6" for example. If you need to revert to an older installation, you can simply rename the new folders to something such as "Xilinx8" and "EDK7" and rename "Xilinx7" and "EDK6" back to "Xilinx" and "EDK" respectively.[[BR]] 19 The final element to create is your personal EDK user repository for any custom peripherals you create. This '''must''' be created in:[[BR]] 20 {{{ 21 c:\EDK_user_repository 22 }}} 23 This is the only directory for custom peripherals that Xilinx XPS will search every-time you create and '''open''' projects. This is particularly important for opening projects that were ''not'' created on your computer ''and'' require you to manually add new custom peripherals before opening. Because any other peripheral repository directories can ''only'' be searched when creating a new project, or in an already open project, XPS will NOT allow you to open an imported project from someone else that uses new custom peripherals. XPS will complain that it found errors in the project's *.MHS file and ask you to correct them, because it can't find custom peripherals. 24 25 == 2: Project Creation == 8 26 9 27 * Make sure the directory structure and folder that will hold your system file has '''no''' spaces or underscores. [[BR]][[BR]] … … 18 36 * Keep the system name "system.xps," as there's no good reason to modify it 19 37 20 == 2: Base System Builder ==38 == 3: Base System Builder == 21 39 22 40 * Choose the latest WARP board revision[[BR]] … … 28 46 * Choose to create a memory_test. It will generate a properly working linker-script (which you should never touch unless you have to) -- you can rename this file, the project, and fill your code into it.[[BR]] 29 47 30 == 3: Applying Custom Peripherals from the IP catalog into your project ==48 == 4: Applying Custom Peripherals from the IP catalog into your project == 31 49 32 50 * Drag the peripheral into system assembly (or double-click it)[[BR]] … … 36 54 * Fill in UCF file with pin-mappings if needed 37 55 38 == 4: System Generation ==56 == 5: System Generation == 39 57 40 58 * Generate Netlist (Hardware menu)[[BR]] … … 44 62 * Update Bitstream (Device Configuration)[[BR]] 45 63 46 == 5: Making Updates and Changes ==64 == 6: Making Updates and Changes == 47 65 === A: Changes to Hardware === 48 66 If you modify a peripheral's HDL or data files (such as its MPD)...[[BR]]
