2. Support
  3. AR# 4571: 6.1i iMPACT - What is the difference between "concurrent" and "sequential" programming modes?
  4. AR# 45714: Aurora 64B66B V6.2 ? Timing simulation failures & TRACE errors

AR# 45714

Aurora 64B66B V6.2 ? Timing simulation failures & TRACE errors

Description

This Answer record provides solution for the following issues seen with Aurora 64B66B V6.2

  1. X's seen on signals during timing simulation of the core
  2. No Channel UP in timing simulation
  3. TRACE reports timing errors

Solution

  1. GT REFCLK period in UCF differs with GT REFCLK period of DEMO_TB because of rounding of digits. This results in signals being driven to 'X' & design does not get CHANNEL UP for data transfer.To work around this issue, use the GT REFCLK value period from UCF for CLOCKPERIOD_1 and CLOCKPERIOD_1 parameters/constants in DEMO_TB.
  2. Make sure all the transceivers are placed continuously in multi-lane design. This helps ISE software tools meet timing easily
  3. Check if a standard GT REFCLK value is available for required Line rate
  4. In <USER_COMPONENT_NAME>_wrapper.v[hd] file add the following code:

-------------------------------------------------------------------------

always @(posedge rxrecclk_64_i)
begin
if(!resetdone_i)
begin
rx_resetdone_r1 <= `DLY 1'b0;
rx_resetdone_r2 <= `DLY 1'b0;
end
else
begin
rx_resetdone_r1 <= `DLY resetdone_i;
rx_resetdone_r2 <= `DLY rx_resetdone_r1;
end
end

-----------------------------------------------------------------------

Note: Commented portion of above code is already available in the delivered RTL
AR# 45714
Date 01/09/2012
Status Active
Type Known Issues
Devices More Less
IP