6651 - DELAYF of ECP5/ECP5-5G
The minimum width check for LOADN/MOVE/DIRECTION signal is 2,500 ps.
The delay setting is effective only after minimum time of 810 ps after the falling edge of MOVE signal.
Related Articles
6498 - XO/ECP: What is the expected GPLL input clock tR and tF requirements for XO2, XO3, ECP3 and ECP5 ?
For XO2, XO3 and ECP3/ECP5 the expected rise/fall time are shown below: Parameter Descriptions Conditions Max (ns) tR Input clock rise time 10% to 90% 1.0 tF Input clock fall time 90% to 10% 1.0
1904 - [ispClock 5400D] Are ispClock products suitable for ITU-T G.8262 applications?
No. Although ispClock products have excellent jitter specifications, the dynamics of their PLLs are very different from those used in data transmission applications (such as those based on ITU-T G.8262). The key difference is in PLL loop bandwidth. ...
2657 - ECP3: Why do I get a netsanitycheck Place and Route (PAR) error when a MUX drives the clock of a IDDR/ODDR component?
Description: The netsanitycheck error indicates general routing is used to drive the IDDR and/or ODDR components. The logic must be modified to use dedicated clock resources: Solution 1: Do not use generic logic (e.g. MUX implemented by LUTs) to ...
3812 - How to find the number of gates available for a Lattice device?
Lattice does not have any data regarding the gate counts for a device. Only the Look-Up Table (LUT) counts are available for a device. The reason is that an LUT can be configured in an end design either as INVERTER or 4 input AND gate. The actual ...
3999 - ispMACH4000 : For ispMACH4000 devices, is the bus-keeper option a global constraint for all the I/Os? When configuring I/O as bus-keeper, what is the signal status on power up?
For the ispMACH 4000V/B/C/Z devices, the bus-keeper option is a global constraint for all I/Os. For ispMACH4000 ZE devices, it is available on per-pin basis. During power up, the I/Os are at default state. After the device enters user mode, the I/Os ...