01-15-2010 12:03 PM - edited 01-15-2010 08:46 PM
Hi,
I'm using Spartan 3E Starter Kit Board, and now I want to make simulation using Hardware Co-simulation, but after XFLOW run, it showed that there was 1 timing constraint not met.
I have done some search before making this post. Although there were some topics about this error before, but I still find it so confusing for me to understand this situation.
When I finish my design with model in MATLAB (3 Mult, 2 AddSub and 1 Delay), I create SGBD Builder exactly as Performing Hardware-in-the-Loop PDF file guide. After that, I generate and it show 1 timing constraint not met:
----------------------------------------------------------------------------------------------------------
Constraint | Check | Worst Case | Best Case | Timing | Timing
| | Slack | Achievable | Errors | Score
----------------------------------------------------------------------------------------------------------
* TS_hwcosim_sys_clk = PERIOD TIMEGRP "hwco | SETUP | 5.086ns| 14.914ns| 0| 0
sim_sys_clk" 50 MHz HIGH 50% | HOLD | -3.743ns| | 5420| 11072268
----------------------------------------------------------------------------------------------------------
TS_J_TO_U = MAXDELAY FROM TIMEGRP "J_CLK" | SETUP | 10.315ns| 4.685ns| 0| 0
TO TIMEGRP "U_CLK" 15 ns | | | | |
----------------------------------------------------------------------------------------------------------
TS_clk_70d40e76 = PERIOD TIMEGRP "clk_70d | MINPERIOD | 18.348ns| 1.652ns| 0| 0
40e76" 20 ns HIGH 50% | | | | |
----------------------------------------------------------------------------------------------------------
NET "jtag_iface/drck1" PERIOD = 30 ns HIG | SETUP | 22.981ns| 7.019ns| 0| 0
H 50% | HOLD | 0.974ns| | 0| 0
----------------------------------------------------------------------------------------------------------
I thought using hardware co-simulation that means System Generator automatically match Timing Constraint, if it needs to be changed, should I change in file SGBD Builder s3e_starter.ucf in folder \Xilinx\DSP_Tools\nt\sysgen\plugins\compilation\Hardware Co-Simulation\s3e_starterkit?
03-21-2011 11:57 AM
total path delay should be less than clock period (20 ns in this case for Spartan 3E) and thus slck variable shoild not be negative.
09-01-2011 03:31 AM
I have got the same problem. Has anyone found a solution?