Tips & Tricks

Cadence Tips and Tricks

Set # of sig figs on schematic annotation

Sometimes the number of significant figures on schematic annotations (node voltages, for example) is very high and it becomes difficult to read. To fix this, type the following into the icfb window:

envSetVal("auCore.misc" "labelDigits" 'int 5)

Change the number 5 to your desired number of sig figs. To make this change permanent, add the line to your ~/.cdsenv file.

Disable "What's New" Window

You may not have noticed, but a simple graphical method has been included in icfb to disable the "What's New" window which pops up every time you start. When the window opens, simply choose Edit->Off at Startup and you will never bothered by the windows again.

Save operating point information over a DC sweep

You may notice that DC operating point information (gm, gds, etc.) does not get saved over a DC sweep. One way to work around this is to replicate the sweep using the parametric sweep tool. In some cases, however, this may constrain your simulation setup. If you simply want the op information to be saved for every point in a sweep, follow these directions:

• Make a new text file (saveop.scs, for example) in a directory to which you have read-write access.
• Add the following line to the file, replacing N0 with the name of the device whos operating point you wish to save:

save N0:oppoint

• Save the file. Return to your ADE window, navigate to Setup->Model Libraries; now the file you just made to the list.
• Run your simulation and find the saved data in the Results Browser (under the Tools menu in the ADE). You can also access the data with equations (i.e. getData("M0:vdsat" ?result 'dc)).
• You can, of course, have multiple lines in the file for multiple devices. For large simulations, consider saving disk space by modifying the file to save only the parameters of interest (i.e, N0:gm). More information about the save command can be found in the spectre documentation or by running spectre -h save at the terminal.

Locked Files in Cadence

If you try to open an old file and Cadence says you can't edit the file, it is because this file has become "locked." This usually happens as a result of Cadence crashing while the file was open.

To unlock the file, you need to search for and remove (using the rm command) a file that ends in ".cdslck". You will often have to look through directories and subdirectories to find this file, but look in directories that have the same name as the cellview in question. For example if you are having trouble opening the schematic in cellview "Inverter" in library "myLib" then you would go to the folder myLib/Inverter/ and look for all files ending in ".cdslck".

As an alternative to manually searching through the directories you can use the command (from the directory where you start cadence):

find . -name "*.cdslck"

Before you run this command close all open shcematics and layouts. Then simply remove all files that appear.

To remove all cdslck files, you can use the command rm together with searching(from the directory where you start cadence):

find . -name "*.cdslck" -exec rm -f {} \;

Reference: https://secure.engr.oregonstate.edu/wiki/ams/index.php/Cadence/TipsAndTricks#toc11

Automatically Open the Library Manager

In some Cadence environments, the library manager does not open automatically upone starting Cadence. In order to change this behavior you can simply add the line:

ddsOpenLibManager()

to your .cdsinit file.

Other Tips and Tricks

Make Nautilus (file manager) behave like a browser

Nautilus is the default file manager on the lab computers. You have likely noticed that, with the default settings, it spawns a new windows each time you open a folder. If you find this annoying, you can change its behavior with the following steps:

• Open the preferences dialogue (Edit->Preferences)
• Click on the behavior tab
• Tick the always open in browser windows option

Firefox profile lock (error message with "Firefox is currently running...")

Frequently, if you do not close firefox properly, it will give an error message next time you try to open it. To fix this problem, navigate to ~/.mozilla/firefox and look for a folder with a mix of numbers and letters followed by "Default User". In this folder, you will find an invisible file called .parentlock; delete this file and the problem should be fixed.