Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

help me problem in optimization process

Status
Not open for further replies.

sarmad88

Junior Member level 2
Junior Member level 2
Joined
Feb 12, 2013
Messages
20
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Visit site
Activity points
1,474
help me to solve problem in optimization process

hi
why when i use type array signal with initial value in my code the utilization summary (number of slices ) become 0%
please how can overcome this problem?????
Is there a way to stop the optimization process in ISE14.1??????????? Because it trimmed many important signals system and this signal no appear when make modify conection in chipscope program to debug the signal
please any one help me to overcome this problem
 

either use (* keep = "true" *) in front of the signal declaration (for verilog) or the equivalent attribute statement in VHDL to tell ISE to not optimize the signal away. The other option is to turn off trimming of loadless signals, which could have adverse effects on resource utilization.
 

You can edit in synthesis preferences also. But it is not recommendable.until or unless you didnt used a signal well, it wont get trim by tool. Because In your post itself you have mentioned all are important signal.
One more point when you are going to use chipscope, please check you have selected soft synthesis. in that time also, it will trim like this.
 

sarmad88,

You could instantiate the CS cores in your design and selectively compile them with some debug switch. In verilog I typically just put an:

Code Verilog - [expand]
1
2
3
`ifdef CS_DEBUG_MODULE
    // CS instantances go here
 `endif



This way I can enable disable useful debug code when I need to check stuff in the lab.
 

You really should look into why the signals were trimmed -- normal reasons like "equivalent register removal" or register-balancing/retiming are ok. bad reasons like "unconnected output" or "tied to constant" or "equivalent to register that is also constant" indicate some issue in the HDL. often a missing clock/reset, incorrect reset polarity, or unconnected outputs of some module.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top