This Release Note is for the SPI-4.2 (POS-PHY L4) v7.4 Core released in 8.1i IP Update 1; it contains the following information:
- New Features
- Bug Fixes
- Known Issues
For installation instructions and design tools requirements, see (Xilinx Answer 22155)
A patch is needed to address v7.4 issues. See (Xilinx Answer 23155)
New Features in v7.4
- Support of Continuous Dynamic Alignment in the Sink Core.
- Support of a new signal pin (SrcOofOverride) to assist in board-level debugging.
- Supports the inversion of Sink SPI-4.2 Inputs to assist in board-level debugging.
Bug Fixes in v7.4
CR 217100: Sink core goes Empty when 1 packet is left in sink (FIFO)
CR 218335: Sink core duplicates data on the FIFO user interface
CR 218336: Signal SnkFFBurstErr is asserted unexpectedly
- Version 7.4 of the SPI-4.2 Core supports only the Virtex-4 family. For Virtex-II and Virtex-II Pro designs, use the latest version of the v6.x series of the SPI-4.2 Core, available from the SPI-4.2 IP lounge: http://www.xilinx.com/bvdocs/ipcenter/data_sheet/spi4_2_product_spec.pdf
- the Version 7.4 Core is compatible with ISE 8.1i Service Pack 1.
- If you are using multiple SPI-4.2 Cores in a single device, you must generate the core with unique component name for each instance. See the "Multiple Core Instantiation" section under the "Special Design Consideration" chapter of the SPI-4.2 User Guide.
(Xilinx Answer 22704) Migrating an SPI4.2 design from v7.3 to v7.4
(Xilinx Answer 22703) Migrating SPI4.2 design from v6.2 to v7.4
(Xilinx Answer 21386) When do I use Global Clocking vs Regional Clocking?
(Xilinx Answer 21069) When using Dynamic Phase Alignment or the SPI Core, RDClk must be running at least 220 MHz minimum.
(Xilinx Answer 20430) What is the power consumption of SPI-4.2 Core?
(Xilinx Answer 15500) How do I edit the SPI-4.2 (PL4) UCF file so that the TSClk is skewed by 180 degrees in the DCM?
(Xilinx Answer 20017) Which I/O Standards are supported for the SPI-4.2 Core?
(Xilinx Answer 21959) When I simulate an SPI-4.2 design with DCM standby logic, only timing simulation with SDF is supported.
(Xilinx Answer 22392) When using a Source Core with Slave Clocking, use clocks from another Master Source core, not the general-purpose clock from the Sink core.
Known Issues in v7.4
A patch is needed to address v7.4 issues, see (Xilinx Answer 23155)
Core Generation Issues
(Xilinx Answer 15493) When I generate an SPI-4.2 (PL4) Core through CORE Generator, the following errors occur:
"ERROR:Failure to create .sym symbol file. Cannot post process ASY symbol file. File C:\test\5_2i\pl4_core.asy does not exist."
"ERROR: Did not generate ISE symbol file for core <pl4_core>."
Constraints and Implementation Issues
(Xilinx Answer 20000) When implementing an SPI-4.2 design through NGDBuild, several "WARNING" and "INFO" messages appear.
(Xilinx Answer 21439) When implementing an SPI-4.2 design through MAP, several "WARNING" and "INFO" messages appear.
(Xilinx Answer 21320) When implementing an SPI-4.2 design through PAR, several "WARNING" and "INFO" messages appear.
(Xilinx Answer 21363) For a Virtex-4 design, PAR has problems completely routing the SPI4.2 design.
(Xilinx Answer 20280) Placement failures occur in PAR when the SPI-4.2 FIFO Status signals' I/O Standard is set to LVTTL I/O.
(Xilinx Answer 20040) Timing Analyzer (TRCE) reports "0 items analyzed."
(Xilinx Answer 19999) "ERROR:BitGen:169 - This design contains one or more evaluation cores for which bitstream generation is not supported."
(Xilinx Answer 20319) When running implementation, undefined I/O (single-ended) defaults to LVCMOS causing WARNINGS in NGDBuild.
(Xilinx Answer 20017) The SPI-4.2 Core signals default to LVDS without the internal device termination. If internal termination is needed, it must be defined in the UCF. In v7.3, this is predefined in the "wrapper.ucf" file. However, it must be uncommented. For a complete list of supported I/O, see (Xilinx Answer 20017).
(Xilinx Answer 21958) When implementing an SPI-4.2 design through NGDBuild, an error occurs on the DIFF_TERM constraint.
General Simulation Issues
(Xilinx Answer 21409) When using Dynamic Phase Alignment, the PhaseAlignComplete signal is not asserted and SnkOof is never de-asserted.
(Xilinx Answer 21319) When running timing simulation on a SPI4.2 Design Example, several "TDat Error: Data Mismatch" messages are reported.
(Xilinx Answer 21321) When running timing simulation on a SPI4.2 design with a Sink core set to Dynamic Alignment mode, several "Error: */X_ISERDES SETUP Low - - VIOLATION ON D WITH RESPECT TO CLK" messages are reported.
(Xilinx Answer 21322) When running timing simulation on a SPI4.2 design, several, SETUP, HOLD, and RECOVERY violations occur.
(Xilinx Answer 21362) When running Verilog timing simulation, TDat output is always "0000" and no training pattern is sent after reset.
(Xilinx Answer 20030) When simulating an SPI-4.2 design, multiple warning messages are expected at the beginning of the simulation.
(Xilinx Answer 15578) When simulating an SPI-4.2 (PL4) Core using NC-Verilog (by Cadence) or VCS (by Synopsys), unusual and inconsistent behavior occurs.
(Xilinx Answer 21316) When running timing simulation using the design example, DIP2 mismatch errors occur in the simulator.
(Xilinx Answer 21959) When simulating an SPI-4.2 design with DCM standby logic, only timing simulation with SDF is supported.
(Xilinx Answer 20796) When targeting a Virtex-4 design with the SPI4.2 Core, a silicon issue exists.
(Xilinx Answer 20022) When fixed static alignment is used, it is necessary to determine the best IOBDELAY (ISERDES) value or the best DCM setting (PHASE SHIFT) to ensure that the target system contains the maximum system margin and performs across voltage, temperature, and process (multiple chips) variations.
(Xilinx Answer 15442) An SPI-4.2 (PL4) Sink core with dynamic alignment fails to activate PhaseAlignComplete, goes out of sync, or reports a DIP4 error.
- When I open the SPI4.2 GUI in COREGen using the Hardware timeout evaluation license, it displays a pop-up message. The message indicates that the Hardware timeout lasts for 6-8 hours. However, the core will run only 2 hours.
SPI- 4.2 (PL4) v7.3 KNOWN ISSUES
- The SPI-4.2 v7.3 Core is now obsolete. Please upgrade to the latest version of the core.
For information on existing SPI-4.2 v7.3 issues, see (Xilinx Answer 21918).
SPI- 4.2 (PL4) v7.2 KNOWN ISSUES
- The SPI-4.2 v7.2 Core is now obsolete. Please upgrade to the latest version of the core.
For information on existing SPI-4.2 v7.2 issues, see (Xilinx Answer 21032).
SPI- 4.2 (PL4) v7.1 KNOWN ISSUES
- The SPI-4.2 v7.1 Core is now obsolete. Please upgrade to the latest version of the core.
For information on existing SPI-4.2 v7.1 issues, see (Xilinx Answer 20274).