URL
https://opencores.org/ocsvn/eco32/eco32/trunk
[/] [eco32/] [trunk/] [stdalone/] [README] - Blame information for rev 293
Go to most recent revision |
Details |
Compare with Previous |
View Log
Line No. |
Rev |
Author |
Line |
1 |
98 |
hellwig |
There are four different ways to run a standalone program.
|
2 |
97 |
hellwig |
|
3 |
|
|
1. Simulator: Load the program with the '-l' command-line option
|
4 |
|
|
into the simulated memory; use '-a 0x10000' to set the load
|
5 |
|
|
address. Each Makefile has a target 'run' to automate this.
|
6 |
|
|
|
7 |
|
|
2. Simulator: Pack the program onto a simulated disk (this will
|
8 |
|
|
happen automatically if you use the Makefile target 'run-sim'
|
9 |
|
|
in the subdirectory build/run). Boot this disk. Choose the
|
10 |
|
|
partition with the bootable EOS32 file system, and enter
|
11 |
|
|
'/boot/' as the 'path to kernel'.
|
12 |
|
|
|
13 |
|
|
3. FPGA: Load the program with the help of the load server. Type
|
14 |
98 |
hellwig |
'loadserv ' on the PC side, and
|
15 |
|
|
'load 1' on the FPGA side (which runs the machine monitor).
|
16 |
97 |
hellwig |
|
17 |
98 |
hellwig |
4. FPGA: Pack the program onto a simulated disk and make the disk
|
18 |
|
|
available for use with the help of the disk server (this will
|
19 |
97 |
hellwig |
happen automatically if you use the Makefile target 'run-server'
|
20 |
98 |
hellwig |
in the subdirectory build/run). Type 'boot 1' on the FPGA side
|
21 |
|
|
(which runs the machine monitor), and proceed as in 2.
|
© copyright 1999-2024
OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.