openSession ( "TCI6488EVM_XDS510USB/C64PLUS_F2A" ) debugSessionF2B = debugServer. openSession ( "TCI6488EVM_XDS510USB/C64PLUS_F1C" ) debugSessionF2A = debugServer. openSession ( "TCI6488EVM_XDS510USB/C64PLUS_F1B" ) debugSessionF1C = debugServer. openSession ( "TCI6488EVM_XDS510USB/C64PLUS_F1A" ) debugSessionF1B = debugServer. traceWrite ( "Opening a debug session for all TCI6488 cores." ) debugSessionF1A = debugServer. traceWrite ( "Done!" ) // Open a debug session for each TCI6488 CPU script. traceWrite ( "Configuring debug server for TCI6488 EVM." ) debugServer. getServer ( "DebugServer.1" ) // Configure target for a TCI6488 EVM with SD XDS510 USB emulator script. Get the Debug Server and start a Debug Session debugServer = script. It is also useful to use the example scripts as a baseline for creating your own scripts (by referencing it or simply copying and then "gutting" it to use as a template). The examples are well commented and should give you an understanding of the basic steps needed to create the scripting environment and start a debug session for a specified target, in addition to highlighting some of the DSS APIs available. It is strongly encouraged for new users to open up the DSS basic examples and slowly walk through them to get an understanding of how DSS works. Test Server (TestServer) - demonstrates how to use DSS to set-up a debug test server and have remote clients send debug commands via TCP/IP socket connection.Īvailability of examples vary per CCS version.Loadti (loadti) - a generic command-line loader which can load/run an executable.DVT basic examples (DVTExamples) - Sample script for collecting and exporting function profiling data.DSS basic examples (DebugServerExamples) - These sample scripts which perform basic memory and breakpoint operations.The examples are meant to demonstrate and highlight some of the capabilities of DSS. For instance, if you open the Console window the first time you debug a script, Chrome DevTools will open with the Console window open in each subsequent debugging session.DSS ships with several examples. And, your Chrome DevTools environment is retained between debugging session. Notice in the above example, the variable being watched is a SuiteScript object so all available members of that object are displayed.Ĭhrome DevTools supports keyboard shortcuts for nearly all actions available in the debugger. To add a variable or enter an expression to evaluate, click the plus (+) button on the Watch window header and enter the variable name or expression. Use the Watch window, on the JavaScript debugging pane, to see values of variables within your script and to evaluate expressions on-the-fly: You can de-minify the source (that is, add appropriate white space and new lines) by using the button located at the bottom of the source window. Sometimes source code will be displayed minified when it is displayed on the Sources tab: Be aware that if you use the Console tab on the left side of the debugger, the source window closes. The console can be displayed in the main debugger window or on the bottom pane of the debugger by clicking the corresponding Console tab. You can also select a point in the call stack and resume execution from that point. To view the call stack, click the Call Stack header on the JavaScript debugging pane: Values of SuiteScript and JavaScript objects can be viewed by expanding the Local, Closure, or Global sections of the JavaScript debugging pane: View and edit local, closure, and global properties To restart execution from a point in the call stack:Įxpand the Call Stack section of the JavaScript Debugging pane.Ĭlick the line of code in the call stack where you want to resume execution. Restart execution from a line within the call stack To resume execution, click the resume execution button: When script debugging is paused, you will see the Debugger paused message: ![]() To pause execution, click the pause button. The code pointer moves out of the function to the line after the function call. To step out of a line of code, click the step out button. Clicking the step into button when the code pointer is at a SuiteScript module will move the code pointer to the next line, effectively skipping over the SuiteScript module. Note that you cannot step into a SuiteScript module. The code pointer moves into the function. To step into a line of code, click the step into button. To step over a line of code, click the step over button. When all breakpoints are disabled, the breakpoints list is grayed out: Note that break points must first be set to disable/re-enable them. To re-enable all breakpoints, click the re-enable breakpoints button. A disabled breakpoint marker appears grayed-out: To disable all breakpoints, click the disable breakpoints button. If this happens, simply remove the breakpoints that you no longer need. There may be times when breakpoints “stick” between debugging sessions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |