... | ... | @@ -47,61 +47,6 @@ Every core distribution is organized with the following directories |
|
|
In some specific cases there might be more directories. See the
|
|
|
documentation for each core.
|
|
|
|
|
|
## On line documentation
|
|
|
|
|
|
The *ebone* script may be used to display the documentation.
|
|
|
|
|
|
$ ebone -doc
|
|
|
|
|
|
Displaying documentation for core ...
|
|
|
0\) Ebone script man page
|
|
|
1\) Ebone getting started
|
|
|
2\) Ebone specifications
|
|
|
3\) BIF user's guide
|
|
|
4\) PicoBlaze user's guide from XILINX
|
|
|
5\) Others
|
|
|
Enter your choice )
|
|
|
...
|
|
|
|
|
|
If you know the core name (for ex. *ebs\_core\_32*) just do
|
|
|
|
|
|
$ ebone -doc ebs\_core\_32
|
|
|
|
|
|
to display its documentation.
|
|
|
|
|
|
Even an incomplete core name may be enough for the documentation tool to
|
|
|
find out the correct document. In case several cores may fit, the exact
|
|
|
core names are listed, as next example shows.
|
|
|
|
|
|
$ ebone -doc ebs\_
|
|
|
Displaying documentation for core like 'ebs\_' ...
|
|
|
ebs\_pkg
|
|
|
ebs\_bram
|
|
|
ebs\_fifo
|
|
|
ebs\_i2c
|
|
|
ebs\_mif
|
|
|
ebs\_mif\_sp6
|
|
|
ebs\_picoblaze
|
|
|
ebs\_regs
|
|
|
ebs\_fspi
|
|
|
ebs\_spi
|
|
|
ebs\_sysm
|
|
|
sebone32
|
|
|
sebone64
|
|
|
ebs\_bif
|
|
|
|
|
|
## Up-loading a core or updating a design
|
|
|
|
|
|
Use the ebone script. Try:
|
|
|
|
|
|
$ ebone -h
|
|
|
|
|
|
$ ebone -up -h
|
|
|
|
|
|
The script operates only in the directory in which it is invoked from.
|
|
|
To update a hierarchical design *ebone -up* must be run in every design
|
|
|
source sub-directory.
|
|
|
|
|
|
## What else?
|
|
|
|
|
|
- [On line documentation and cores updates](DocUp)
|
... | ... | |