--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Mon Apr 12 14:47:08 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Tue Apr 13 15:55:45 2010 -0500
@@ -8,14 +8,12 @@
<style type="text/css">
<!--
.style1 {font-size: 1em}
-.style5 {font-size: 1em; font-family: Verdana, Ariel, Helvetica, sans-serif; }
-.style7 {font-size: 1em; font-weight: bold; }
-->
</style>
</head>
<body bgcolor="#FFFFFF" dir="ltr">
<h2> Defining a Stop Mode Debug Configuration</h2>
-<p>After installing all necessary software such as Perl, JTAG, compilers, Devkits and SDKs and creating your project, you will need to define a Debug launch configuration for your project. For this example, we'll define a Trace32 launch configuration. For new projects that do not have a launch configuration, a New Launch Configuration Wizard will appear and allow you to define settings. You can also cancel the wizard and define a launch configuration from the following instructions.</p>
+<p>After installing all necessary software such as Perl, JTAG, compilers, Devkits and SDKs and creating your project, you will need to define a Debug launch configuration for your project. For this example, we will define a Trace32 launch configuration. For new projects that do not have a launch configuration, a New Launch Configuration Wizard will appear and allow you to define settings. You can also cancel the wizard and define a launch configuration from the following instructions.</p>
<div class="step">
<h4>Define a Launch Configuration </h4>
<ol>
@@ -51,11 +49,11 @@
<th width="62%" scope="col">Explanation</th>
</tr>
<tr>
- <td><span class="style7">Project</span></td>
+ <td>Project</td>
<td><p>The project to associate with this debug launch configuration. Click Browse to select a different project.</p></td>
</tr>
<tr>
- <td><span class="style7">Executable</span></td>
+ <td>Executable</td>
<td><span
style="font-weight: normal;">This is the name of the executable that is linked to the project. </span>Click <b>Browse</b> to select a different executable.</td>
</tr>
@@ -71,17 +69,13 @@
<th width="62%" scope="col">Explanation</th>
</tr>
<tr>
- <td><span class="style5">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </span>
- <p class="style5"><b>Trace32 Executable</b></p></td>
+ <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Trace32 Executable</b></font></font></p></td>
<td><p>Specify the path to the Trace32 executable. The default path assumes that the Trace32 executable is installed in the default location: C:\T32\T32marm.exe.</p></td>
</tr>
<tr>
- <td><span class="style5">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </span>
- <p class="style5"><b>Trace32 Configuration File</b></p></td>
+ <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Trace32 Configuration File</b></font></font></p></td>
<td>Specify the path to the config.t32 file or other custom configuration file. The default path assumes that the Trace32 configuration file is installed in the default location: C:\T32\config.t32.
<p>For arm11 processors copy the trace32 configuration file for non-ARM11 processor (config_arm11.t32) to your C:\T32 folder and specify it in the edit box.</p>
<p>You can modify the config.t32 file to support UDP (User Datagram Protocol) connections by adding the following lines: <br />
@@ -91,21 +85,17 @@
PORT=20000</p></td>
</tr>
<tr>
- <td><span class="style5">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </span>
- <p class="style5">
+ <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Trace32 Initialization Script</b></p></td>
+ <b>Trace32 Initialization Script</b></font></font></p></td>
<td><p>Specify the path to the initialization <span class="code">cmm</span> file. This script will be run in T32 after connecting to T32. You can specify your own scripts for the targets used.</p></td>
</tr>
<tr>
- <td><span class="style5">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </span>
- <p class="style5"><b>
+ <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <p><b><font size="2" style="font-size: 9pt">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- View messages between Carbide and Trace32</b></p></td>
+ </font></b><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>View messages between Carbide and Trace32</b></font></font></p></td>
<td>Enable to log communications with Trace32 to the console window.</td>
</tr>
</table>
@@ -129,27 +119,27 @@
</tr>
<tr>
<td>
- <span class="style5">
+ <span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style5"><b>Target Initialization File</b></p></td>
+ <p class="style1"><font face="Georgia, serif"><b>Target Initialization File</b></font></p></td>
<td><p>Check this box to have the debugger run an initialization script when the debug session starts. For example, if a target device requires initialization for the debugger to be able to read and write memory or registers, you can specify an initialization script here. Click Browse to select a script file using a standard file selection dialog box.</p>
- <p>When using T32, most of the initialization is done in the CMM script file. With other debug protocols you can specify the initialization file, which can be run after connecting to the target.</p></td>
+ <p>When using T32, most of the initialization is done in the CMM script file. With other debug protocols you specify the initialization file, which can be run after connecting to the target.</p></td>
</tr>
<tr>
<td>
- <span class="style5">
+ <span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style5"><b>Memory Configuration File</b></p></td>
+ <p class="style1"><b><font face="Georgia, serif">Memory Configuration File</font></b></p></td>
<td>Controls whether the debugger uses a memory configuration file when a debug session starts. The Carbide debugger uses this configuration file to know which memory is accessible, readable, and writable on the target.</td>
</tr>
<tr>
<td>
- <span class="style5">
+ <span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style5"><b>Reset target at the start of each debug session</b></p></td>
+ <p class="style1"><b><font face="Georgia, serif">Reset target at the start of each debug session</font></b></p></td>
<td>Forces the Carbide IDE to reset the target at the start of each debug session. This ensures that the debugging session uses the most up-to-date program code.</td>
</tr>
<tr>
@@ -174,8 +164,7 @@
<th width="62%" scope="col">Explanation</th>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
<p class="style1"><font face="Georgia, serif">
@@ -185,8 +174,7 @@
<p class="note"><b>NOTE</b> The address entered in this field must match the start address specified in the source code used to build the Symbian OS ROM image to be debugged. The Start address must match the Download address.</p></td>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
<p class="style1"><font face="Georgia, serif">
@@ -195,8 +183,7 @@
<td>Select this option to have the debugger halt the program at the address specified in Start Address once the target initialization is done and the OS is downloaded; if the user has chosen to download the OS. You can then step through start-up code or run the target in bare-board mode.</td>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
<p class="style1"><font face="Georgia, serif">
@@ -206,10 +193,9 @@
<td>Select this option to have the debugger start the code at the address specified in Start Address once the target initialization is done. If you have breakpoints set, the debugger stops at the first breakpoint encountered. You can click the Break button to halt the device.</td>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </span>
+ </span>
<p class="style1"><font face="Georgia, serif">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
@@ -218,10 +204,9 @@
<td>Check the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images. In the first text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.</td>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </span>
+ </span>
<p class="style1"><font face="Georgia, serif">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
@@ -230,10 +215,9 @@
<p class="note"><b>NOTE</b> Always include the epoc32 folder in this path.</p></td>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </span>
+ </span>
<p class="style1"><font face="Georgia, serif">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
@@ -244,10 +228,9 @@
<p class="note"><b>NOTE</b> You cannot perform source-level debugging on components that do not include symbolic information.</p></td>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </span>
+ </span>
<p class="style1"><b>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</b><font face="Georgia, serif">
@@ -258,8 +241,7 @@
<p class="note"> <b>NOTE</b> Selecting this option will affect debugging performance. When the debugger needs to load a module (DLL, EXE, etc.) it will stop the target, read information from it, then restart it.</p></td>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
<p class="style1"><b>
@@ -270,20 +252,18 @@
<td>Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window.</td>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif"><b>Download Address (hex) </b></font></p></td>
+ <p class="style1"><font face="Georgia, serif"><b>Download Address (hex) </b></font></p></td>
<td><p>Enter the physical address in memory at which the debugger should place the ROM image. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x000FFF00 is a valid entry.</p>
<p class="note"> <b>NOTE</b> The address entered in this field must match the download address specified in the source code used to build the Symbian OS ROM image to be debugged. If you leave this field blank, the debugger does not download the ROM image to the device at the beginning of the debug session. The Download address must match the Start address.</p></td>
</tr>
<tr>
- <td>
- <span class="style1">
+ <td><span class="style1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
</span>
- <p class="style1"><font face="Georgia, serif"><b>Ask for download at the start of each debug session</b></font></p></td>
+ <p class="style1"><font face="Georgia, serif"><b>Ask for download at the start of each debug session</b></font></p></td>
<td>Check this box to have the debugger display a dialog box at the beginning of every debug session that lets you choose whether or not you want the debugger to download the ROM image to the device.</td>
</tr>
</table>