Keithley 2900 Debugging App Note free download

File name 2900 Debugging App Note.pdf

Number 2900 Application Note Series Debugging with Forte Workshop Introduction During the execution of this macro, the macro aborts, as shown in the Messages box in Figure 1. This application note discusses how to debug Keithley Interactive Test Tool (KITT) macros and Keithley User Library Tool (KULT) If the macro was executed successfully, the software would modules using the Forte Workshop Debugger. Two debugging normally return a "Done 1" message and the drain current scenarios are outlined. (n10xp3_ids) value would be displayed in the Results window The Forte Workshop Debugger tool provides many functions (not shown). However, the message returned is "Test Aborted," for troubleshooting coding problems that may arise when using indicating a problem somewhere in the macro. This macro only KITT and the Keithley Test Execution Engine (KTXE). These contains one test module (vth), but most test macros contain functions include, but are not limited to, setting break points, many more modules, which complicates the process of locating single-stepping through code, and analyzing run-time values. the problem. The Debugger is a standard part of the Forte Development This macro aborted due to some coding problem within the Tool set on Keithley's Series S400 and S600 parametric testers. vth routine. One method of locating the source of the problem is Coding problems that occur while developing parametric test to use the C language printf statement throughout the vth mod- programs can cause test programs to crash or abort. These test ule. The printf statement would generate output to the terminal programs can be at the KITT macro or KTXE level. window, making it possible to determine the execution flow of this routine. This application note assumes familiarity with the Keithley Test Environment (KTE) tools discussed here, as well as a work- This note will discuss how the Debugger can be used to ing knowledge of the C programming language. locate the problem. To gain a better understanding of the pro- cess involved, we recommend you create a stand-alone C pro- Debugging Scenarios gram, called a Practice Task. From the Program menu, select the This application note discusses the following debugging "Practice Task..." function as illustrated in Figure 2. scenarios: You will be asked to enter a UNIX file name. KITT will create