Sign in

username:

password:



Not a member?

Search Comp.Arch.FPGA



Search tips

fpga by Keywords

Altera | ASIC | CPLD | Cyclone | DCM | DDR | DSP | Ethernet | ISE | JTAG | Linux | LVDS | Microblaze | ML310 | Modelsim | NIOS | OPB | PCI | Quartus | RocketIO | SDRAM | Spartan | Spartan3 | SRAM | Stratix | Verilog | VHDL | Virtex | Virtex-4 | Virtex-II | Xilinx | XST

Ads

See Also

DSPEmbedded SystemsElectronics

Comp.Arch.FPGA | Post route simulation warning

There are 2 messages in this thread.

You are currently looking at messages 0 to 2.

Post route simulation warning - akshayvreddy - 2010-01-23 18:26:00

When a preformed post route simulation it gave me
this warnings. I amhaving trouble in understanding them and why these warning come up. 

WARNING:Timing:3224 - The clock clkf_4 associated with OFFSET = IN 800 nsBEFORE COMP "clkf_4"; does not clock any
   registered input components.
WARNING:Timing:3225 - Timing constraint OFFSET = IN 800 ns BEFORE COMP"clkf_4"; ignored during timing analysis

Thank you for the help in advance	   
					
---------------------------------------		
Posted through http://www.FPGARelated.com



Re: Post route simulation warning - Muzaffer Kal - 2010-01-24 03:54:00

On Sat, 23 Jan 2010 17:26:13 -0600,
"akshayvreddy"
<akshayvreddy@n_o_s_p_a_m.gmail.com> wrote:

>When a preformed post route simulation it gave me this warnings. I am
>having trouble in understanding them and why these warning come up. 
>
>WARNING:Timing:3224 - The clock clkf_4 associated with OFFSET = IN 800 ns
>BEFORE COMP "clkf_4"; does not clock any
>   registered input components.
>WARNING:Timing:3225 - Timing constraint OFFSET = IN 800 ns BEFORE COMP
>"clkf_4"; ignored during timing analysis
>
>Thank you for the help in advance	   

These outputs are from fpga tools (map and/or par) not from post-route
simulation. Post route simulation means getting the doing a gate level
simulation by annotating the gate level verilog output of PAR with the
SDF generated at the same time.
The first warning is telling you that the clock constraint you
generated in the UCF file has a problem ie the name doesn't match any
clocks or it's not connected to any nets. You probably misspelled it.
The second one is telling you pretty much the same thing ie because
the said clock doesn't clock any flops, the timing constraint is being
ignored during PAR.
-- 
Muzaffer Kal

DSPIA INC.
ASIC/FPGA Design Services

http://www.dspia.com