UPGRADE YOUR BROWSER

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!

cancel
Showing results for 
Search instead for 
Did you mean: 
Observer danbo.liang
Observer
3,320 Views
Registered: ‎03-20-2012

Why this naming rule will report error?

Hi All,

in my design, there are 2 similar signals, one is ssn[2] and another is ssn_2, the port define is below:

input [2:0] ssn;

output       ssn_2;

 

when synthesize, ISE will report error "the net ssn_2 is not found", why?

0 Kudos
3 Replies
Scholar drjohnsmith
Scholar
3,313 Views
Registered: ‎07-09-2009

Re: Why this naming rule will report error?

Hi

 

1001 resons,

    the most likely I gues is that  the signal is not used in th edesign,

               and is optimised away, a fairly common mistake.

 

It does raise the question of the naming convention yoru using,

     try changing ssn_2 to ssn_b

 

if ssn_b is reported as missing, its benn optimised away,

    if it reports ssn_2, oops....

 

<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos
Observer danbo.liang
Observer
3,301 Views
Registered: ‎03-20-2012

Re: Why this naming rule will report error?

Hi

Actually, the signal is used.

After change ssn_2 to ssn_b, it is OK.

 

So I doubt that ssn_2 and ssn[2] are treated as same in ISE naming convention.

0 Kudos
Scholar drjohnsmith
Scholar
3,299 Views
Registered: ‎07-09-2009

Re: Why this naming rule will report error?

an interesting quirk

 

but at least you have a work around.

 

<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos