Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→The SYnch command
[[File:AN-BELK-001_10.png|600px|thumb|center]]
The SYnch settings are reported below:
* ''<code>Connect''</code>
** Establish a connection to the debugger attached to the defined communication port(s). Several debuggers ports can be specified, separated by space.
* ''<code>MasterGo ON''</code>
** If the program execution is started, the program execution for all other processors which have SlaveGo ON is also started.
* ''<code>MasterBrk ON''</code>
** If the program execution is stopped, the program execution for all other debuggers which have SlaveBrk ON is also stopped.
* ''<code>MasterStep ON''</code>
** If an asm single step is executed, all processors which have SlaveStep ON will also asm single step.
* ''<code>MasterSystemMode ON''</code>
** Invite other TRACE32 instances to perform system mode changes synchronously. System mode changes are typically performed by the commands SYStem.Mode <mode>
* ''<code>SlaveGo ON''</code>
** The program execution is started, if a processor with MasterGo ON starts its program execution.
* ''<code>SlaveBrk ON''</code>
** The program execution is stopped, if a processor with MasterBrk ON stops its program execution.
* ''<code>SlaveStep ON''</code>
** A asm single step is performed, if a processor with MasterStep On performs an asm single step.
* ''<code>SlaveSystemMode ON''</code>
** Synchronize with system mode changes in connected TRACE32 instances.
&core1 SYStem.CONFIG.CTI.Config CORTEXV1
</pre>
===Setting up the Linux debug configuration===
The symbolic information is useful for HLL debugging, or setting breakpoints, stepping through the code, viewing variables, and many other aspects of debugging. The compiler must be configured in order to generate debug symbols. The vmlinux file for the running kernel must be available, in order to load the kernel debug symbols.
