Simulator Configuration Guide for Synopsys Models

Appendix B: Using Custom Memory ModelsSimulator Configuration GuideControlling Message OutputThere are three ways to control messaging for custom memory models:1. Specify Message Settings when you specify message categories (except Fatal).2. Use the message_level generic or parameter.3. Use a command stream or testbench command.By default, custom memory models display all the general message categories (Fatal,Error, Warning, Info, Timing, and X-handling). If you set a generic or parameter for amodel instance, that setting overrides the default behavior. In turn, if the commandstream or testbench interface is used, it overrides the generic or parameter value.Message Level ConstantsCustom memory models provide constants for setting message levels on eachinstantiated model. The constants described in Table 39 are defined in mempro_pkg.v(for Verilog simulators) and mempro_pkg.vhd (for VHDL simulators).You can combine these constants to get any combination of messages. The followingVerilog and VHDL code fragments define a model instantiation having timing,X-handling, and warning (as well as fatal) messages enabled.Verilogbank1.message_level = `SLM_XHANDLING | `SLM_TIMING | `SLM_WARNING,VHDLTable 39: Custom Memory Model Message ConstantsConstantValue a DescriptionSLM_ERROR 1 Fatal and error messages generated.SLM_WARNING 2 Fatal and warning messages generated.SLM_TIMING 4 Fatal and timing messages generated.SLM_XHANDLING 8 Fatal and X-handling messages generated.SLM_INFO 16 Fatal messages generated. Note: Using this bit can addlarge amounts of memory cycle information to thetranscript, considerably slowing simulation.SLM_ALL_MSGS 2 32 −1 All message types generated.SLM_NO_MSGS 0 Only fatal messages generated.a. Note that bits 5 through 31 are unused but reserved.message_level => (SLM_TIMING + SLM_XHANDLING + SLM_WARNING),284 Synopsys, Inc. October 6, 2003