URL
https://opencores.org/ocsvn/or1k/or1k/trunk
[/] [or1k/] [trunk/] [rc203soc/] [readme.rc200] - Blame information for rev 1775
Go to most recent revision |
Details |
Compare with Previous |
View Log
Line No. |
Rev |
Author |
Line |
1 |
1581 |
jcastillo |
Notes on running this design on an RC200:
|
2 |
|
|
|
3 |
|
|
Building the hardware
|
4 |
|
|
---------------------
|
5 |
|
|
* Synthesise using Synplicity and the script: syn/synplicity/rc200.tcl.
|
6 |
|
|
|
7 |
|
|
* Place-and-route the resulting edif (rc200soc.edf) along with
|
8 |
|
|
the constraint file: backend/xilinx/rc200soc.ucf
|
9 |
|
|
|
10 |
|
|
* Note: I found that with ISE 7.1.04i, and Synplify Pro 8.0 I was unable meet
|
11 |
|
|
the timing for a 50 MHz clock (as selected in the UCF). In practice though
|
12 |
|
|
the error margin is narrow enough for the design to probably work anyway.
|
13 |
|
|
|
14 |
|
|
|
15 |
|
|
Building the software
|
16 |
|
|
---------------------
|
17 |
|
|
* In the jtag server source, comment out the dbg_test() procedure call in
|
18 |
|
|
main(). This prevents initialisation of devices not present in this
|
19 |
|
|
design.
|
20 |
|
|
|
21 |
|
|
* If the or1200_defines.v file is not changed to enable the trace buffer
|
22 |
|
|
(OR1200_DU_TB_IMPLEMENTED), change the gdb source by commenting out the
|
23 |
|
|
call to or1k_read_trace() in remote-or1k.c:or1k_wait().
|
24 |
|
|
|
25 |
|
|
* Modify the board.h file for orpmon or hello-uart programs to reflect
|
26 |
|
|
the 50MHz clock-speed.
|
© copyright 1999-2024
OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.