We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 39377

SPI-3 Link Layer v7.3 - Release Notes and Known Issues for ISE Design Suite 12.4


This Release Notes and Known Issues Answer Record is for the SPI-3 (POS-PHY L3) Link Layer v7.3 Core (released in ISE Design Suite 12.4), and contains the following information:
  • New Features
  • Resolved Issues
  • General Information
  • Known Issues
For installation instructions, general CORE Generator known issues, and design tools requirements, see the IP Release Notes Guide:


New Features
  • ISE 12.4 software support
Resolved Issues
  • (Xilinx Answer 38850) SPI-3 Link Layer v7.2 - Data mismatch between rdat and rx_data in Spartan-6 and Virtex-6 devices
  • (Xilinx Answer 38851) SPI-3 Link Layer v7.2 - Example design simulation testbench monitoring logic not connected
  • (Xilinx Answer 38852) SPI-3 Link Layer v7.2 - Demo testbench data dropped during simulation
  • (Xilinx Answer 38873) SPI-3 Link Layer v7.2 - TSX missing for first addr out of TDAT on Virtex-6 and Spartan-6 devices
General Information
  • Cores configured with independent clocks and direct mode transfer flow-control might encounter hold time issues in hardware on the input DTPA bus unless one of the following conditions are met:
    • Generate TX_CLK using a DCM/MMCM and select an appropriate phase shift for the system to meet timing
    • Ensure the DTPA input data is already center aligned on the clock
    • Transmit the data on the rising edge, and then clock it into the FPGA on the falling edge
  • The Tx and Rx cores are provided with default timing constraints in the UCF file generated with the core. Depending on the core configuration, target architecture, and speed grade, the core might run significantly faster. The user can modify the constraints to meet their performance requirements. As long as all timing constraints are met, the SPI-3 Link Core operates at the user specified rate. Note that the best way to verify timing closure is with user logic, rather than the example design. Implementing only the example design might artificially limit the performance of the SPI-3 Link Core (e.g., if the User Interface is routed to I/O pins).
  • A DCM with a PHASE_SHIFT on its clock is required to meet the OIF specification's 2 ns input timing requirement. This solution is necessary only if the system's timing budget cannot permit the Link Core to exceed the 2 ns input requirement.
Known Issues
  • (Xilinx Answer 34527) - SPI-3 Link Layer Core - Some designs might fail timing
  • (Xilinx Answer 35266) - NCSIM Warnings 12.1:ncelab: *W,SDFINF: Instance XIL_ML_UNUSED_DCM_1/CLKFB not found at scope level < top-level > < sdf name >, line < number >.
AR# 39377
Date Created 12/02/2010
Last Updated 05/19/2012
Status Archive
Type Release Notes
  • SPI-3 Link Layer Interface, Multi-channel