Comment
Author: Admin | 2025-04-28
Hello Reuben.If you register on support.cadence.com using your corporate email address, you will get access to our Rapid Adoption Kits (RAKs) and tutorials. These will lead you step by step through the different aspects of the Incisive flow. To aid your searches, be aware that "ncsim" is a legacy name for the simulator, and if you're trying to use the legacy commands "ncvlog", "ncelab", "ncsim" then you would be well advised to replace these with the single "irun" command which wraps up the entire compile, elab and simulation process into one easy step. It's much simpler to use!To answer your specific points though: to probe waveforms you must elaborate the design with read access enabled for the signals you want to dump. We usually do that with the irun option "-access +r" (you can pass this to ncelab directly too). Then once you've loaded the simulation, and before you start simulating, either use the GUI or the Tcl commands to "probe" signals to the waveform file. From the GUI you do it by selecting a module in the hierarchy (e.g. the top level), right click on it and "Create Probe". You then have options for which types of signals (ports, internal, memories etc) and whether to probe more than one level of hierarchy. Watch out: the default in the GUI is to send all probed signals to the waveform window and that's probably not what you want for a big design!From Tcl, you can simply do "probe -create -shm -all -depth to_cells" to probe everything in the design excluding cell libraries. Simply replace with your actual top-level module name.Note that you must probe signals before simulating if you want the simulator to record their values! :)For coverage, you elaborate with either "-coverage B:E:T:U:F", where each letter turns on a different
Add Comment