15

---

OCEAN 4.4.6 Issues

---

For the 4.4.6 release of OCEAN, there are some restrictions and requirements.

The netlist file that you specify for the Spectre^® circuit simulator interface with the design command must be netlist. The full path can be specified. For example, /usr/netlist is acceptable. The netlistHeader and netlistFooter files are searched in the same directory where the netlist is located. Cadence recommends that you use the netlist generated from the Virtuoso® Analog Design Environment. Netlists from other sources can also be used, as long as they contain only connectivity. You might be required to make slight modifications.

• Cadence recommends full paths for the Spectre simulator model files, definition files, and stimulus files.
• The Cadence SPICE circuit simulator is still used to parse netlists for socket interfaces (spectreS and cdsSpice, for example). Therefore, the netlist that you specify with the design command must be in Cadence SPICE syntax. Cadence recommends that you use the raw netlist generated from the Virtuoso® Analog Design Environment. Netlists from other sources can also be used, as long as they can pass through Cadence SPICE. You might be required to make slight modifications.
• Any presimulation commands that you specify are appended to the final netlist (as is currently the case in the design environment). Therefore, if you have control cards already in your netlist, and specify simulation setup commands, you might duplicate control cards, which causes a warning or an error from the simulator. You might want to remove control cards from your netlist file to avoid the warnings.
• Models, include files, stimulus files, and PWLF files must be found according to the path specified with the path command.