{"id":36557,"date":"2004-10-01T00:04:17","date_gmt":"2004-10-01T00:04:17","guid":{"rendered":"https:\/\/silvaco.com\/%e6%9c%aa%e5%88%86%e7%b1%bb\/a-sophisticated-verilog-a-debugger\/"},"modified":"2021-10-13T10:36:13","modified_gmt":"2021-10-13T17:36:13","slug":"a-sophisticated-verilog-a-debugger","status":"publish","type":"post","link":"https:\/\/silvaco.com\/zh-hans\/simulation-standard-zh-hans\/a-sophisticated-verilog-a-debugger\/","title":{"rendered":"A Sophisticated Verilog-A Debugger"},"content":{"rendered":"
\n

A Sophisticated Verilog-A Debugger<\/h1>\n

During the elaboration of a\u00a0Verilog-A<\/em><\/strong>\u00a0model, debugging a module can be very useful for detecting non-physical behavior or fine-tuning the model. The SILVACO\u00a0Verilog-A<\/em><\/strong>\u00a0debugger has been designed to meet these needs. It is available since version 2.6.0.R of\u00a0SmartSpice<\/em><\/strong>\u00a0and works along with SILVACO C-Interpreter. It allows iteration-per-iteration\u00a0Verilog-A<\/em><\/strong>\u00a0modules debugging. The debugger is tracing all the\u00a0Verilog-A<\/em><\/strong>\u00a0instantiations of the design, either instances of the\u00a0SmartSpice<\/em><\/strong>\u00a0netlist or in other\u00a0Verilog-A<\/em><\/strong>\u00a0modules.<\/p>\n

The BSIM4\u00a0Verilog-A<\/em><\/strong>\u00a0model (bsim4.va) and the adder design (adder.in) used as an example are freely available on SILVACO website.<\/p>\n

It can be enabled by setting in the input deck:<\/p>\n

\n

.OPTIONS va_mode=debug<\/span><\/p>\n<\/blockquote>\n

The debugger appears when the simulation of this input deck is launched. The simulation stops at the first instruction (a breakpoint at the first instruction is always set by default). In the case of BSIM4 model, the first instruction encountered is the initial_step event in the analog block. The layout of the main window at startup<\/p>\n

The\u00a0Verilog-A<\/em><\/strong>\u00a0source code is displayed in an editor window. Syntax highlighting is available and its colors are fully customizable. Line numbers can be displayed by checking the \u201cShow line number\u201d box in the Properties dialog window (Edit > Properties…).<\/p>\n

The console window is at the bottom of the main window. The error messages are printed in this area and the user can enter commands manually.<\/p>\n

In this example (Figure 2. The console window), a breakpoint has been set at line 2699 (the end of the initial_step block) and the simulation has been started with the cont command. The edit window has now the aspect.<\/p>\n<\/div><\/section><\/div>

<\/div>