close
Warning:
Can't synchronize with repository "(default)" (/common/SVN/crkit does not appear to be a Subversion repository.). Look in the Trac log for more information.
- Timestamp:
-
Nov 17, 2010, 7:21:09 PM (13 years ago)
- Author:
-
khanhle
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v55
|
v56
|
|
11 | 11 | |
12 | 12 | |
13 | | In our reference environment, we are using two drive partitions : C:\ partition for OS and software applications, and D:\ for data files. |
| 13 | In our reference environment, we are using two drive partitions : `C:\` partition for OS and software applications, and `D:\` for data files. |
14 | 14 | If you are not using the same drive partitions or directory structures, then you will need to modify the links to the appropriate |
15 | 15 | folders/files according to your particular environment. In the following, we have assumed that all the above software have been installed successfully on your machine. |
16 | 16 | |
17 | 17 | === C: Partition === |
18 | | In C:\ , do the following steps :[[BR]] |
19 | | 1. Create 'hw' folder, and 'xlib' subfolder e.g c:\hw and c:\hw\xlib. xlib contains the Xilinx precompiled libraries for Modelsim. Those libraries are used only for simulation purposes. [[BR]] |
20 | | 2. Compile Xilinx ISE and EDK libraries into c:\hw\xlib\ise10.1 and c:\hw\xlib\edk10.1, respectively. Each time Xilinx ISE or Modelsim version has been updated then the libraries will need to be recompiled. [wiki:Software/Firmware/Framework/tutorial/config/xlib How to compile Xilinx libraries.][[BR]] |
| 18 | In `C:\` , do the following steps :[[BR]] |
| 19 | 1. Create 'hw' folder, and 'xlib' subfolder e.g `c:\hw` and `c:\hw\xlib`. xlib contains the Xilinx precompiled libraries for Modelsim. Those libraries are used only for simulation purposes. [[BR]] |
| 20 | 2. Compile Xilinx ISE and EDK libraries into `c:\hw\xlib\ise10.1` and `c:\hw\xlib\edk10.1`, respectively. Each time Xilinx ISE or Modelsim version has been updated then the libraries will need to be recompiled. [wiki:Software/Firmware/Framework/tutorial/config/xlib How to compile Xilinx libraries.][[BR]] |
21 | 21 | |
22 | 22 | === D: Partition === |
… |
… |
|
24 | 24 | 1. Create '''crkit_svn''' folder e.g. d:\crkit_svn, this is the location for CRKit svn folder. [wiki:Software/Firmware/Framework/tutorial/config/svn How to synchronize with CRKit SVN.] [[BR]] |
25 | 25 | 2. Create '''hw''' folder e.g. d:\hw [[BR]] |
26 | | 3. Create '''hw\cr_build''' subfolder e.g. d:\hw\cr_build. Location for Xilinx ISE place/route project files will be located [[BR]] |
27 | | 4. Create '''hw\simulink''' subfolder e.g. d:\hw\simulink. Location for the MATLAB/Simulink generated files [[BR]] |
28 | | 5. Create '''hw\host''' subfolder e.g. d:\hw\host. Location for Visual Studio host software [[BR]] |
| 26 | 3. Create '''hw\cr_build''' subfolder e.g. `d:\hw\cr_build`. Location for Xilinx ISE place/route project files will be located [[BR]] |
| 27 | 4. Create '''hw\simulink''' subfolder e.g. `d:\hw\simulink`. Location for the MATLAB/Simulink generated files [[BR]] |
| 28 | 5. Create '''hw\host''' subfolder e.g. `d:\hw\host`. Location for Visual Studio host software [[BR]] |
29 | 29 | |
30 | 30 | === Modelsim === |
… |
… |
|
33 | 33 | === Windows Environment Variable === |
34 | 34 | Add following Windows environment variables (for MATLAB/Simulink) :[[BR]] |
35 | | 1. MODELSIM_WORK_HOME = d:\hw [[BR]] |
36 | | 2. XILINX_ISE_MODELS = c:\hw\xlib\ise10.1 [[BR]] |
| 35 | 1. MODELSIM_WORK_HOME = `d:\hw` [[BR]] |
| 36 | 2. XILINX_ISE_MODELS = `c:\hw\xlib\ise10.1` [[BR]] |
37 | 37 | [[BR]] |
38 | 38 | |
… |
… |
|
42 | 42 | Perform following steps : [[BR]] |
43 | 43 | |
44 | | 1. Copy .bash_profile from 'd:\crkit_svn\design\trunk\setup' to 'c:\Documents and Settings\YOUR_USER_ACCOUNT' . The shell will pick up the |
| 44 | 1. Copy .bash_profile from `d:\crkit_svn\design\trunk\setup` to `c:\Documents and Settings\YOUR_USER_ACCOUNT` . The shell will pick up the |
45 | 45 | variables each time the shell is started. [[BR]] |
46 | 46 | 2. If not using the same directory structures as described above, then edit .bash_profile to link to the appropriate folder locations. [[BR]] |