06-18-2014 06:40 PM
vivado version: 2013.4
FPGA version: v7
I found sometimes the signal name will be changed from HardWare Maneger Navigator.
It will be inconvenient in debugging process.
So how can I preserve the natual signal name (BTW, I insert ila core at design code--by instance it in code)?
06-18-2014 07:58 PM
I found that (* KEEP = "TRUE" *) in the source has some nasty side-effects in Vivado, so I removed them all. Now I open the synthesized design and use the TCL Console to find the nets with get_nets or I track down renamed nets with the synthesized schematic.
If there is a better way, I am interested in hearing it.
06-18-2014 09:51 PM
06-18-2014 09:58 PM
That is what I try to do in the XDC file, but get_nets will not find it if the synthesizer has already renamed it.
Are you suggesting put something like (* MARK_DEBUG = "TRUE" *) in the source? I haven't tried that yet.
06-18-2014 10:04 PM
It looks like this has been fixed in 2014.2 with options for 2014.1 and earlier:
Option 1 is what I am using.
Not sure Option 2 will give a usable design, but worth a try: it is easy to do and undo.
Not sure of the side effects of Option 3, but like Option 2 it might leave to an unusable design, though on a more limited scale, depending on what cells you mark.
06-18-2014 10:14 PM
According to the AR, it is recommended that you migrate to Vivado 2014.2 and then move forward with your design.
To give a try, put MARK_DEBUG on signals in your RTL which you want to debug so that synthesizer tool can preserve the corresponding signal in the netlist. In case tool still renames and unable to find the signal, you are having 3 Options in AR as a workaround.
06-19-2014 02:53 AM
I insert ila core in my code.
If add the attribute before singal specification, then the ila core if need to be add into code too?
06-19-2014 04:29 AM
06-19-2014 09:11 AM
Has anyone tried option 2: set -flatten_hierarchy to "none". When I just did it with Vivado 2014.1 I got 1500 warnings about undriven pins--but they are not undriven: the design would not work at all if they were undriven, in simulation or silicon. Setting -flatten_hierachy back to "rebuilt" and all those warnings go away.