... | ... | @@ -8,6 +8,8 @@ |
|
|
|
|
|
## Brand Neutral
|
|
|
|
|
|
Xilinx biased.
|
|
|
|
|
|
<table>
|
|
|
<tbody>
|
|
|
<tr class="odd">
|
... | ... | @@ -19,15 +21,15 @@ |
|
|
</tr>
|
|
|
<tr class="even">
|
|
|
<td>Code Fetch</td>
|
|
|
<td>OK</td>
|
|
|
<td>OK</td>
|
|
|
<td>OK</td>
|
|
|
<td>OK</td>
|
|
|
<td>YES</td>
|
|
|
<td>YES</td>
|
|
|
<td>YES</td>
|
|
|
<td>YES</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>Project Gen</td>
|
|
|
<td>OK</td>
|
|
|
<td>OK</td>
|
|
|
<td>YES</td>
|
|
|
<td>YES</td>
|
|
|
<td>N.A.??</td>
|
|
|
<td>N.A.</td>
|
|
|
</tr>
|
... | ... | @@ -35,12 +37,37 @@ |
|
|
<td>Simulation</td>
|
|
|
<td>ISIM</td>
|
|
|
<td>Modelsim</td>
|
|
|
<td>YES</td>
|
|
|
<td>YES</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>Synthesis</td>
|
|
|
<td>YES</td>
|
|
|
<td>YES</td>
|
|
|
<td>NO</td>
|
|
|
<td>NO</td>
|
|
|
</tr>
|
|
|
</tbody>
|
|
|
</table>
|
|
|
|
|
|
Auto:
|
|
|
This only considers ISE
|
|
|
synthesis.
|
|
|
|
|
|
## Device Support
|
|
|
|
|
|
### Xilinx
|
|
|
The way in wich xise calculates the family requires a constant database update as new device families are introduced in the market (e.g. Zynq family)
|
|
|
|
|
|
Some naming schemes are not supported in the current automatic
|
|
|
calculation (Spartan3E, Spartan3AN...). A more complex mechanism is
|
|
|
required.
|
|
|
|
|
|
Quick workaround
|
|
|
Add family as an optional parameter, in this way we are not limiting the
|
|
|
use of new devices. If not family option value is provided in the
|
|
|
manifest, try to get the family name from the device parameter.
|
|
|
|
|
|
## Remote Synthesis
|
|
|
|
|
|
Simulation
|
... | ... | |