... | ... | @@ -3,15 +3,18 @@ |
|
|
## Repo layout
|
|
|
|
|
|
The repository contains only generic and reusable White Rabbit cores,
|
|
|
which should not be tied to any particular piece of hardware. If there
|
|
|
are any platform dependencies, the platform-specific part should be
|
|
|
clearly separated from the generic part.
|
|
|
which are not be tied to any particular piece of hardware (for example,
|
|
|
the Routing Table Unit belongs to the WR Switch HDL repository, because
|
|
|
it would be of very little use anywhere else). If there are any platform
|
|
|
dependencies, the platform-specific part should be clearly separated
|
|
|
from the generic part.
|
|
|
|
|
|
The repo is organized as follows:
|
|
|
|
|
|
- `modules` - "big" modules, such as the WR Endpoint of WR Core - each
|
|
|
in a separate subdirectory, with dir name matching the name of of
|
|
|
the top level entity. Only platform-independent RTL code is allowed.
|
|
|
- `modules` - "big" modules, such as the WR Endpoint or the WR Core -
|
|
|
each in a separate subdirectory, with dir name matching the name of
|
|
|
of the top level entity. Only platform-independent RTL code is
|
|
|
allowed.
|
|
|
- `platform` - platform dependent code, for example wrappers for
|
|
|
gigabit transceivers or Chipscope cores.
|
|
|
- `sim` - simulation models and header files
|
... | ... | @@ -90,6 +93,16 @@ A very temporary todo list: |
|
|
<td>tbd</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>SoftPLL code optimization</td>
|
|
|
<td>Make the SoftPLL work faster. Currently it consumes quite a lot of the LM32 CPU time.</td>
|
|
|
<td>tbd</td>
|
|
|
</tr>
|
|
|
<tr class="even">
|
|
|
<td>SoftPLL performance optimization</td>
|
|
|
<td>Fine-tune the control algorithm to obtain the lowest jitter and the best stability</td>
|
|
|
<td>Pedro</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>Aux clock DAC control</td>
|
|
|
<td>Define a way of telling the WR Core what type of DAC (or a programmable oscillator, such as Si57x) it has to drive without need for changes inside the WRPC software. That means, what hardware interface (I2C, SPI), part type, PI controller gains and thresholds, etc.</td>
|
|
|
<td>tbd</td>
|
... | ... | |