BUG 10603 - pulled sophia text references from manual, some images may still contain references
--- a/core/com.nokia.carbide.cpp.doc.user/.project Mon Jan 25 10:09:42 2010 -0600
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>com.nokia.carbide.cpp.doc.user</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- <buildCommand>
- <name>org.eclipse.pde.ManifestBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>org.eclipse.pde.SchemaBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- </buildSpec>
- <natures>
- <nature>org.eclipse.pde.PluginNature</nature>
- </natures>
-</projectDescription>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Tue Jan 26 12:01:35 2010 -0600
@@ -21,7 +21,6 @@
<li><b><a href="attach_process.htm">Symbian OS Attach to Process</a></b> —used to debug processes running on a target device for which a symbol file is available. This is available only for TRK and stop mode debugging. This launch configuration is not available for emulator debugging. Stop mode and TRK can both attach to a process from the <a href="../../reference/view_symbian_kernel.htm">Symbian OS Data</a> view.</li>
<li><b>Symbian OS Crash Debugger</b> —used to launch an interactive command-line session with the Symbian OS crash debugger when the device crashes </li>
<li><b><a href="emulation.htm">Symbian OS Emulation</a> </b>—used to run or debug executables on an emulator. </li>
- <li><b><a href="sophia.htm">Symbian OS Sophia</a> </b> (<i>only available in OEM Edition</i>)—is an external debugger that the Carbide debugger communicates with, to debug any Symbian OS module on a target using a JTAG connection.</li>
<li><b><a href="stop_mode.htm">Symbian OS System TRK</a></b> (<i>not available Developer Editions</i>) —used to run or debug applications or ROM code on a target device using the System TRK on-device debug agent. System TRK is an application that runs on reference boards and prototype phones and allows you to debug your executables. The debugger will download files to the phone prior to launching.</li>
<li><b><a href="trace32.htm">Symbian OS Trace32</a></b> (<i>only available in OEM Edition</i>)—is an external debugger that the Carbide debugger communicates with, to debug any Symbian OS module on a target using a JTAG connection.</li>
</ul>
@@ -32,6 +31,6 @@
<li><a href="wiz_new_launch_config.htm">New Launch Configuration Wizard</a></li>
<li><a href="wnd_debug_configuration.htm">Debug</a> dialog </li>
</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm Tue Jan 26 12:01:35 2010 -0600
@@ -15,7 +15,6 @@
<li><a href="run_mode.htm">Application TRK</a></li>
<li><a href="attach_process.htm">Attach to Process</a></li>
<li><a href="emulation.htm">Emulation</a></li>
- <li><a href="sophia.htm">Sophia (STI)</a></li>
<li><a href="stop_mode.htm">System TRK</a></li>
<li><a href="trace32.htm">Trace32</a></li>
</ul>
@@ -23,6 +22,6 @@
<ul>
<li><a href="launch_configs_overview.htm">Launch Configuration Overview</a></li>
</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Tue Jan 26 12:01:35 2010 -0600
@@ -1,155 +1,154 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Carbide Debugger panes</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Debugger panes</h2>
-<p>The options shown in the <b>Debugger</b> page differ based upon the type of launch configuration. Generally, the options fall into these choices: </p>
-<ul>
- <li><a href="#emulator_mode">Emulation Debugger page</a> (Emulation) </li>
- <li><a href="#trk_runmode">Run-mode Debugger page</a> (Application TRK) </li>
- <li><a href="#trk_stopmode">Stop-mode Debugger page</a> (System TRK, Trace32, Sophia, Attach to Process) </li>
-</ul>
-<h3><a name="emulator_mode" id="emulator_mode"></a>Emulation Debugger page </h3>
-<p>The <b>Symbian OS <a href="emulation.htm">Emulation</a></b> launch configurations the <b>Debugger</b> page to specify entry point breaks and which logs to output to the Console view.</p>
-<p align="center"><img src="images/page_debugger_emulation.png" width="638" height="205"></p>
-<p class="figure">Figure 1 - Debugger page showing emulation options </p>
-<h5>Table 1. Debugger page — emulation options </h5>
-<table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Option</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Break at entry point </b></td>
- <td>Select to halt program execution at a specified
- function or address. Enter the desired function
- name or address in the corresponding field. If you
- enter an address, ensure that it is correct and within
- your program.</td>
- </tr>
- <tr>
- <td><b>View program output </b></td>
- <td><p>Enable to direct standard output messages to the Emulation Program Output Console in the <a href="../../reference/view_log.htm">Console</a> view. </p>
- <p class="note"><b>NOTE</b> In the <span class="code">epoc.ini</span> file the option <span class="code">LogToFile</span> must also be set to <span class="code">1</span>.</p></td>
- </tr>
- <tr>
- <td><b>View emulator output </b></td>
- <td><p>Enable to output emulator messages to the Emulator Output Console in the Console view. </p>
- <p class="note"><b>NOTE</b> In the <span class="code">epoc.ini</span> file the option <span class="code">LogToDebugger</span> must also be set to <span class="code">1</span>.</p></td>
- </tr>
- <tr>
- <td><b>View Windows system messages </b></td>
- <td>Enable to output Windows system messages to the Windows System Messages Console in the Console view. </td>
- </tr>
-</table>
-<h3><a name="trk_runmode" id="trk_runmode"></a>Run-mode Debugger page </h3>
-<p>In a run-mode launch configuration like <b><a href="run_mode.htm">Application TRK</a></b>, you can specify an entry break point and how messages are handled as well as define the default instruction set. </p>
-<p align="center"><img src="images/page_debugger_run_mode.png" width="686" height="247"></p>
-<p class="figure">Figure 2 - Debugger page showing run-mode options </p>
-<h5>Table 2. Debugger page — run-mode options </h5>
-<table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Option</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><p><b>Break at entry point</b></p> </td>
- <td><p>When checked, break at the specified entry point entered into the text field. For .EXE targets, the default entry point is set to <span class="code">E32Main</span>. By default, the <b>Break at entry point</b> option is unchecked for all other target types.</p></td>
- </tr>
- <tr>
- <td><b>View program output </b></td>
- <td><p>Enable to direct standard output messages to the <b>TRK Program Output Console</b> in the <a href="../../reference/view_log.htm">Console</a> view. </p>
- <p class="note"><b>NOTE</b> In the <span class="code">epoc.ini</span> file the option <span class="code">LogToFile</span> must also be set to <span class="code">1</span>.</p>
- </td>
- </tr>
- <tr>
- <td><b>View messages between Carbide and debug agent </b></td>
- <td><p>When checked, show the communications between Carbide and the target device in the <b> TRK Communication Log Console</b> of the Console view. </p>
- <p class="note"><b>NOTE</b> You can pin the TRK Communication Log view so that it does not lose focus. </p></td>
- </tr>
- <tr>
- <td><b>Message retry delay (ms) </b></td>
- <td>Enter the delay time in milliseconds (ms) between 100 and 10000 the debugger should wait for a response. The default Message Retry Delay value is 2000. </td>
- </tr>
- <tr>
- <td><p><b>Default Instructon Set </b></p> </td>
- <td><p>Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. The options are: </p>
- <ul>
- <li>Auto (examine code at current PC location) </li>
- <li>ARM (32-bit) </li>
- <li>THUMB (16-bit) </li>
- </ul>
- <p>By default the Instruction Set option uses ARM 32-bit.</p></td>
- </tr>
-</table>
-<h3><a name="trk_stopmode" id="trk_stopmode"></a>Stop-mode Debugger page </h3>
-<p>In stop-mode launch configurations like <b><a href="stop_mode.htm">System TRK</a></b>, <b><a href="trace32.htm">Trace32</a></b>, <b><a href="sophia.htm">Sophia</a></b>, and <a href="attach_process.htm"><b>Attach to Process</b></a>, use the <b>Startup Options</b> to attach to a target and debug or run from the specified start address. Then use <b>Target Options</b> to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session. </p>
-<p align="center"><img src="images/page_debugger_stop_mode.png" width="642" height="401"></p>
-<p class="figure">Figure 3 - Debugger page showing stop-mode options </p>
-<h5>Table 3. Debugger page — stop-mode options </h5>
-<table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="25%" scope="col">Group</th>
- <th width="38%" scope="col">Option</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td> </td>
- <td><p><b>Break at entry point</b></p></td>
- <td><p>When checked, break at the specified entry point entered into the text field. For .EXE targets, the default entry point is set to <span class="code">E32Main</span>. By default, the <b>Break at entry point</b> option is unchecked for all other target types.</p></td>
- </tr>
- <tr>
- <td rowspan="5"><b>Startup Options </b></td>
- <td><b>Soft attach </b></td>
- <td>Enable the <b>Soft attach</b> option to attach a debug session to a target and debug from the specified start address instead of the target's default start address. When enabled the downloaded image option is ignored. </td>
- </tr>
- <tr>
- <td><b>Debug from start address </b></td>
- <td>Enable the <b>Debug from start addres</b>s option to debug from the target's default start address. </td>
- </tr>
- <tr>
- <td><b>Run from start address </b></td>
- <td>Enable the <b>Run from start addres</b>s option to run from the target's default start address. </td>
- </tr>
- <tr>
- <td><b>Start address (hex) </b></td>
- <td>Enter in hexidecimal format (<span class="code">0x0</span>) the starting address to use during the debug session. </td>
- </tr>
- <tr>
- <td><b>Reset target at the start of each debug session </b></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>
- <td><b>Target Options </b></td>
- <td><b>Target Processor </b></td>
- <td>A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.</td>
- </tr>
- <tr>
- <td> </td>
- <td><b>Target initialization file </b></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.</p>
- <p> Click Browse to select a script file using a standard file selection dialog box. When using T32, most of the initialization is done in the CMM script file. With other debug protocols like Sophia, you can specify the initialization file, which can be run after connecting to the target. </p></td>
- </tr>
- <tr>
- <td> </td>
- <td><b>Memory configuration file </b></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>
-</table>
-
-<h4>Other references</h4>
-<ul>
- <li><a href="run_mode.htm">Application TRK Launch Configuration</a></li>
- <li><a href="emulation.htm">Emulation Launch Configuration</a></li>
- <li><a href="stop_mode.htm">System TRK Launch Configuration </a></li>
-</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Carbide Debugger panes</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/></head>
+<body bgcolor="#FFFFFF">
+<h2>Debugger panes</h2>
+<p>The options shown in the <b>Debugger</b> page differ based upon the type of launch configuration. Generally, the options fall into these choices: </p>
+<ul>
+ <li><a href="#emulator_mode">Emulation Debugger page</a> (Emulation) </li>
+ <li><a href="#trk_runmode">Run-mode Debugger page</a> (Application TRK) </li>
+ <li><a href="#trk_stopmode">Stop-mode Debugger page</a> (System TRK, Trace32, Attach to Process) </li>
+</ul>
+<h3><a name="emulator_mode" id="emulator_mode"></a>Emulation Debugger page </h3>
+<p>The <b>Symbian OS <a href="emulation.htm">Emulation</a></b> launch configurations the <b>Debugger</b> page to specify entry point breaks and which logs to output to the Console view.</p>
+<p align="center"><img src="images/page_debugger_emulation.png" width="638" height="205"></p>
+<p class="figure">Figure 1 - Debugger page showing emulation options </p>
+<h5>Table 1. Debugger page — emulation options </h5>
+<table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="38%" scope="col">Option</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Break at entry point </b></td>
+ <td>Select to halt program execution at a specified
+ function or address. Enter the desired function
+ name or address in the corresponding field. If you
+ enter an address, ensure that it is correct and within
+ your program.</td>
+ </tr>
+ <tr>
+ <td><b>View program output </b></td>
+ <td><p>Enable to direct standard output messages to the Emulation Program Output Console in the <a href="../../reference/view_log.htm">Console</a> view. </p>
+ <p class="note"><b>NOTE</b> In the <span class="code">epoc.ini</span> file the option <span class="code">LogToFile</span> must also be set to <span class="code">1</span>.</p></td>
+ </tr>
+ <tr>
+ <td><b>View emulator output </b></td>
+ <td><p>Enable to output emulator messages to the Emulator Output Console in the Console view. </p>
+ <p class="note"><b>NOTE</b> In the <span class="code">epoc.ini</span> file the option <span class="code">LogToDebugger</span> must also be set to <span class="code">1</span>.</p></td>
+ </tr>
+ <tr>
+ <td><b>View Windows system messages </b></td>
+ <td>Enable to output Windows system messages to the Windows System Messages Console in the Console view. </td>
+ </tr>
+</table>
+<h3><a name="trk_runmode" id="trk_runmode"></a>Run-mode Debugger page </h3>
+<p>In a run-mode launch configuration like <b><a href="run_mode.htm">Application TRK</a></b>, you can specify an entry break point and how messages are handled as well as define the default instruction set. </p>
+<p align="center"><img src="images/page_debugger_run_mode.png" width="686" height="247"></p>
+<p class="figure">Figure 2 - Debugger page showing run-mode options </p>
+<h5>Table 2. Debugger page — run-mode options </h5>
+<table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="38%" scope="col">Option</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><p><b>Break at entry point</b></p> </td>
+ <td><p>When checked, break at the specified entry point entered into the text field. For .EXE targets, the default entry point is set to <span class="code">E32Main</span>. By default, the <b>Break at entry point</b> option is unchecked for all other target types.</p></td>
+ </tr>
+ <tr>
+ <td><b>View program output </b></td>
+ <td><p>Enable to direct standard output messages to the <b>TRK Program Output Console</b> in the <a href="../../reference/view_log.htm">Console</a> view. </p>
+ <p class="note"><b>NOTE</b> In the <span class="code">epoc.ini</span> file the option <span class="code">LogToFile</span> must also be set to <span class="code">1</span>.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><b>View messages between Carbide and debug agent </b></td>
+ <td><p>When checked, show the communications between Carbide and the target device in the <b> TRK Communication Log Console</b> of the Console view. </p>
+ <p class="note"><b>NOTE</b> You can pin the TRK Communication Log view so that it does not lose focus. </p></td>
+ </tr>
+ <tr>
+ <td><b>Message retry delay (ms) </b></td>
+ <td>Enter the delay time in milliseconds (ms) between 100 and 10000 the debugger should wait for a response. The default Message Retry Delay value is 2000. </td>
+ </tr>
+ <tr>
+ <td><p><b>Default Instructon Set </b></p> </td>
+ <td><p>Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. The options are: </p>
+ <ul>
+ <li>Auto (examine code at current PC location) </li>
+ <li>ARM (32-bit) </li>
+ <li>THUMB (16-bit) </li>
+ </ul>
+ <p>By default the Instruction Set option uses ARM 32-bit.</p></td>
+ </tr>
+</table>
+<h3><a name="trk_stopmode" id="trk_stopmode"></a>Stop-mode Debugger page </h3>
+<p>In stop-mode launch configurations like <b><a href="stop_mode.htm">System TRK</a></b>, <b><a href="trace32.htm">Trace32</a></b>,<b> </b>and <a href="attach_process.htm"><b>Attach to Process</b></a>, use the <b>Startup Options</b> to attach to a target and debug or run from the specified start address. Then use <b>Target Options</b> to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session. </p>
+<p align="center"><img src="images/page_debugger_stop_mode.png" width="642" height="401"></p>
+<p class="figure">Figure 3 - Debugger page showing stop-mode options </p>
+<h5>Table 3. Debugger page — stop-mode options </h5>
+<table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="25%" scope="col">Group</th>
+ <th width="38%" scope="col">Option</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td> </td>
+ <td><p><b>Break at entry point</b></p></td>
+ <td><p>When checked, break at the specified entry point entered into the text field. For .EXE targets, the default entry point is set to <span class="code">E32Main</span>. By default, the <b>Break at entry point</b> option is unchecked for all other target types.</p></td>
+ </tr>
+ <tr>
+ <td rowspan="5"><b>Startup Options </b></td>
+ <td><b>Soft attach </b></td>
+ <td>Enable the <b>Soft attach</b> option to attach a debug session to a target and debug from the specified start address instead of the target's default start address. When enabled the downloaded image option is ignored. </td>
+ </tr>
+ <tr>
+ <td><b>Debug from start address </b></td>
+ <td>Enable the <b>Debug from start addres</b>s option to debug from the target's default start address. </td>
+ </tr>
+ <tr>
+ <td><b>Run from start address </b></td>
+ <td>Enable the <b>Run from start addres</b>s option to run from the target's default start address. </td>
+ </tr>
+ <tr>
+ <td><b>Start address (hex) </b></td>
+ <td>Enter in hexidecimal format (<span class="code">0x0</span>) the starting address to use during the debug session. </td>
+ </tr>
+ <tr>
+ <td><b>Reset target at the start of each debug session </b></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>
+ <td><b>Target Options </b></td>
+ <td><b>Target Processor </b></td>
+ <td>A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.</td>
+ </tr>
+ <tr>
+ <td> </td>
+ <td><b>Target initialization file </b></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.</p>
+ <p> Click Browse to select a script file using a standard file selection dialog box. 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> </td>
+ <td><b>Memory configuration file </b></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>
+</table>
+
+<h4>Other references</h4>
+<ul>
+ <li><a href="run_mode.htm">Application TRK Launch Configuration</a></li>
+ <li><a href="emulation.htm">Emulation Launch Configuration</a></li>
+ <li><a href="stop_mode.htm">System TRK Launch Configuration </a></li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Tue Jan 26 12:01:35 2010 -0600
@@ -13,7 +13,7 @@
<ul>
<li><a href="#emulator_mode">Emulation Main page</a> (Emulation) </li>
<li><a href="#run_mode">Run-mode Main page</a> (Application TRK) </li>
- <li><a href="#stop_mode">Stop-Mode Main page</a> (System TRK, Sophia, Trace32) </li>
+ <li><a href="#stop_mode">Stop-Mode Main page</a> (System TRK, Trace32) </li>
</ul>
<h3><a name="emulator_mode" id="emulator_mode"></a>Emulation Main page </h3>
<p>The <b>Symbian OS <a href="emulation.htm">Emulation</a></b> launch configuration uses the <b>Main</b> page to define the process to be launched by the emulator. </p>
@@ -88,7 +88,7 @@
</tr>
</table>
<h3><a name="stop_mode" id="stop_mode"></a>Stop-mode Main page </h3>
-<p>The <b>Symbian OS <a href="stop_mode.htm">System TRK</a>, <a href="sophia.htm">Sophia</a></b>, and <b><a href="trace32.htm">Trace32</a> </b> launch configurations uses the <b>Main</b> page to defines the project and the executable to launch on the target device. </p>
+<p>The <b>Symbian OS <a href="stop_mode.htm">System TRK</a></b> and <b><a href="trace32.htm">Trace32</a> </b> launch configurations uses the <b>Main</b> page to defines the project and the executable to launch on the target device. </p>
<p align="center"><img src="images/page_main_stop_mode.png" width="556" height="301"></p>
<p class="figure">Figure 3. Main page (<i>TRACE32 shown</i>)</p>
<h5>Table 3. Stop-mode Main page — items</h5>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/sophia.htm Mon Jan 25 10:09:42 2010 -0600
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>Sophia Launch Configuration</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h2>Sophia Launch Configuration</h2>
-<p>Select the <b>Symbian OS Sophia </b> target interface (STI) launch configuration (<i>only available in OEM Edition</i>) to debug any Symbian OS module on a target using a JTAG connection. The external Sophia debugger communicates with the Carbide debugger and enables stop mode debugging of the target device. </p>
-<p>If the <a href="wiz_new_launch_config.htm">New Launch Configuration Wizard</a> was used to create an Sophia launch configuration no changes are usually needed. To modify the launch configuration settings, select the <b>Run > Open Debug Dialog...</b> menu option to open the <b>Debug</b> dialog. Select the Sophia configuration and click a tab to set specific options. Click <b>Apply</b> to save any option modifications. Click <b>Debug</b> to launch a debugging session using the new settings.</p>
-<p align="center"><img src="../images/wnd_debug_sophia_launch_config.png" width="654" height="480"></p>
-<p class="figure">Figure 1. Sophia launch configuration in the Debug dialog </p>
-<p>The Sophia launch configuration panes include:</p>
-<ul>
- <li>The <a href="page_main.htm">Main</a> tab defines the project to be launched. Enter the name of the project in the Project field, and the executable name in the Executable field.</li>
- <li>The <a href="page_connection.htm">Connection</a> tab defines the Sophia Target Interface, EJ_Debug type, and JTAG TCLK Frequency.</li>
- <li>The <a href="page_debugger.htm">Debugger</a> tab defines debug configurations, such as entry point to begin debugging, target options, and instruction set.</li>
- <li>The <a href="page_rom_image.htm">ROM Image</a> tab allows you to define startup options and ROM image and ROM log file download information.</li>
- <li>The <a href="page_executables.htm">Executables</a> tab allows you to specify which executables that you want to debug that are part of the project.</li>
- <li>The <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_run_dbg_srce.htm">Source</a> tab (<i>standard CDT page</i>) defines the location of source files used to display source when debugging an application. By default, these settings are derived from the associated project's build path. You may override these settings here. </li>
- <li>The <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_run_dbg_comm.htm">Common</a> tab (<i>standard CDT page</i>) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file.</li>
-</ul>
-<h4>Other references</h4>
-<ul>
- <li><a href="launch_configs_overview.htm">Launch Configuration Overview</a></li>
-</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-</body>
-</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm Tue Jan 26 12:01:35 2010 -0600
@@ -9,7 +9,7 @@
<body>
<h2>System TRK Launch Configuration (Stop-mode) </h2>
-<p>Select the <b>Symbian OS System TRK </b> launch configuration (<i>only available in OEM Edition</i>) provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS <a href="sophia.htm">Sophia</a> or <a href="trace32.htm">Trace32</a> launch configuration is created. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options. </p>
+<p>Select the <b>Symbian OS System TRK </b> launch configuration (<i>only available in OEM Edition</i>) provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS <a href="trace32.htm">Trace32</a> launch configuration is created. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options. </p>
<p>If the <a href="wiz_new_launch_config.htm">New Launch Configuration Wizard</a> was used to create the System TRK launch configuration no changes are usually needed. To modify the launch configuration settings, select the <b>Run > Open Debug Dialog...</b> menu option to open the <b>Debug</b> dialog. Select the System TRK configuration and click a tab to set specific options. Click <b>Apply</b> to save any option modifications. Click <b>Debug</b> to launch a debugging session using the new settings.</p>
<p align="center"><img src="../images/wnd_debug_trace32_launch_config.png" width="832" height="640"></p>
<p class="figure">Figure 1. System TRK launch configuration in the Debug dialog </p>
@@ -26,6 +26,6 @@
<ul>
<li><a href="launch_configs_overview.htm">Launch Configuration Overview</a></li>
</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Tue Jan 26 12:01:35 2010 -0600
@@ -32,8 +32,7 @@
<li><a href="#EXE_SEL">Executable Selection</a></li>
<li><a href="#BLD_OPT">Build Option Selection</a></li>
<li><a href="#FINISH">New Launch Configuration</a></li>
- </ul>
- </td>
+ </ul> </td>
</tr>
<tr>
<td><b>Application TRK and System TRK</b></td>
@@ -50,13 +49,6 @@
</ul> </td>
</tr>
<tr>
- <td><b>Sophia STI</b></td>
- <td><ul>
- <li><a href="#SOPHIA">Sophia Initialization Settings</a></li>
- <li><a href="#ROM_IMG">Symbian ROM Image Settings</a></li>
- </ul> </td>
- </tr>
- <tr>
<td><b>Attach to Process</b></td>
<td><ul>
<li><a href="#TRK_CONN">TRK Connection Settings</a></li>
@@ -104,21 +96,16 @@
<p> This page only appears when creating a Trace32 launch configuration. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_trace32.png" width="438" height="533"></p>
<p class="figure">Figure 9 - <b>Trace32 Initialization Settings</b> page </p>
-<h3><a name="SOPHIA" id="SOPHIA"></a>Sophia STI Initialization Settings</h3>
-<p>Use the <b>Sophia STI Initialization Settings</b> page to specify the target interface, <a href="sophia.htm">initialization</a> file, and target processor of the target device. Enter the Sophia Target Interface and Target Initialization File paths, choose a Target Processor, then click <b>Next</b>. </p>
-<p>This page only appears when creating a Sophia STI launch configuration. </p>
-<p align="center"><img src="../../images/icons/wiz_launch_config_sophia.png" width="438" height="533"></p>
-<p class="figure">Figure 10 - Sophia STI Initialization Settings page </p>
<h3><a name="ROM_IMG" id="ROM_IMG"></a>Symbian ROM Image Settings</h3>
<p>Use the <b>Symbian ROM Image Settings</b> page to specify the method of <a href="page_debugger.htm">debugging</a>, the start address, and the <a href="page_rom_image.htm">ROM Image</a> and Log File locations. </p>
-<p>This page appears when creating a Trace32 or Sophia STI launch configuration. </p>
+<p>This page appears when creating a Trace32 launch configuration. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_rom_image.png" width="438" height="533"></p>
-<p class="figure">Figure 11 - Symbian ROM Image Settings page</p>
+<p class="figure">Figure 10 - Symbian ROM Image Settings page</p>
<h5>Other references</h5>
<ul>
<li><a href="../../projects/launch/launch_configs_overview.htm">Launch Configuration</a> </li>
</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm Tue Jan 26 12:01:35 2010 -0600
@@ -35,6 +35,9 @@
</ul>
<p align="center"><img src="../images/view_remote_connections.png" width="588" height="177"></p>
<p class="figure">Figure 1 - Remote Connections view</p>
+<p>When the view is closed or another perspective opened, a small display item appears in the lower-left corner of the perspective. Click the connection name to open the drop-down menu where you can open the Remote Connections view or switch between connections.</p>
+<p align="center"><img src="../images/tab_remote_conns.png"></p>
+<p class="figure">Figure 2. Remote Connections tab </p>
<h3>Remote Connections view toolbar icons</h3>
<p>The following commands appear on the toolbar within the Remote Connections view: </p>
<table width="100%" border="0" cellpadding="2" cellspacing="0">
@@ -106,7 +109,7 @@
<h3>Remote Connections view context menu options</h3>
<p>Based on the current selection, one or more of the following commands appear on the context menu when you right-click within the Remote Connections view. For example, if no connections are defined, only the <b>New Connection</b> command is available on the context menu. Right-click on a connection name and the additional <b>Enable Service Testing</b> and <b>Disable Service Testing</b> are available.</p>
<p align="center"><img src="../images/context_menu_remote_conn_view.png" width="211" height="104"></p>
-<p class="figure">Figure 2 - Remote Connections context menu</p>
+<p class="figure">Figure 3 - Remote Connections context menu</p>
<table width="100%" border="0" cellpadding="2" cellspacing="0">
<tr>
<th width="30%" scope="col">Item</th>
@@ -163,7 +166,7 @@
<li><a href="wnd_new_conn_install_tab.htm">Install latest TRK</a></li>
<li><a href="../../tasks/trk/trk_plug_n_play_01.htm">Plug-n-Play TRK Setup</a></li>
</ul>
-<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.htm</a></div>
</body>
</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Tue Jan 26 12:01:35 2010 -0600
@@ -52,7 +52,7 @@
<tr valign="top">
<td class="Cell"><p> <b>Debug process or thread</b> </p></td>
<td class="Cell"><div align="center"><img src="images/view_symbianOSbtn_debug.png" width="22" height="20" alt="" /></div></td>
- <td class="Cell"><p> Click the <b>Debug</b> button to attach to the process and debug the selected process or thread. Or right-click an item and choose <b>Debug</b>. This applys to both TRK (run mode) and Sophia/Trace32 (stop mode).</p>
+ <td class="Cell"><p> Click the <b>Debug</b> button to attach to the process and debug the selected process or thread. Or right-click an item and choose <b>Debug</b>. This applies to both TRK (run mode) and Trace32 (stop mode).</p>
</td>
</tr>
<tr valign="top">
@@ -108,7 +108,7 @@
<li><a href="../tasks/debugger/view_symbian_kernel_set.htm">Setting Symbian OS View Refresh Rate</a><br />
</li>
</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Tue Jan 26 12:01:35 2010 -0600
@@ -8,14 +8,14 @@
</head>
<body bgcolor="#FFFFFF" dir="ltr">
<h2>Stop Mode Debug Example</h2>
-<p>This example shows how to create and build an application and debug it on a device using JTAG debug software and Lauterbach or Sophia hardware.</p>
+<p>This example shows how to create and build an application and debug it on a device using JTAG debug software and Lauterbach hardware.</p>
<p>The basic steps include:</p>
<ul>
<li>Verify that your SDK or customer kit is recognized in the <a href="../../reference/SDKPreferences.html">SDK preferences</a> panel.</li>
<li>Create project or <a href="../ImportingProjects.html">Import</a> the project's bld.inf file into Carbide.c++</li>
<li>Specify your <a href="../../reference/ROM_build_settings.html">ROM build settings</a> for the selected project</li>
<li><a href="../projects/prj_build.htm">Build</a> your Project with the ARMV5 Debug Build Configuration</li>
-<li>Create a <a href="../../projects/launch/wiz_new_launch_config.htm">launch configuration</a> for <a href="../../projects/launch/trace32.htm">Trace32</a> or <a href="../../projects/launch/sophia.htm">Sophia</a></li>
+<li>Create a <a href="../../projects/launch/wiz_new_launch_config.htm">launch configuration</a> for <a href="../../projects/launch/trace32.htm">Trace32</a></li>
<li><a href="work_debug_act_debug.htm">Launch</a> the debugger</li>
</ul>
<p>With stop mode debugging you can use the Carbide.c++ IDE and a JTAG interface to communicate between the debugger and a board to debug any target type within the Symbian OS.</p>
@@ -29,9 +29,8 @@
<ul>
<li><a href="stop_mode_debug_precond.htm">Stop Mode On-Device Debugging Preconditions</a></li>
<li><a href="../../projects/launch/trace32.htm">Symbian OS Trace32 Support</a></li>
-<li><a href="../../projects/launch/sophia.htm">Symbian OS Sophia Target Interface Support</a></li>
</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_jtag.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_jtag.htm Tue Jan 26 12:01:35 2010 -0600
@@ -1,70 +1,49 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<title>Stop Mode On-Device Debugging</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF" dir="ltr">
-<h2>Installing JTAG</h2>
-<div class="step">
- <h4>Install the JTAG Software</h4>
- <h5>Using Lauterbach Hardware </h5>
- <ol>
- <li>Program Lauterbach with Proper License</li>
- <p>You will need a Trace32 (Lauterbach), a USB cable, and a Lauterbach power supply. You will need to program the Lauterbach with licenses for the particular processors you will be targeting.</p>
- <p>Older Lauterbachs have Xscale for Lubbock and ARM9 for H2/Renesas licenses installed on them already. Newer Lauterbachs should have ARM9 for H2/Renesas and ARM11 for H4 licenses installed on them already. If you don’t have the proper license installed on the Lauterbach for the processor you want to work with, you will receive an error when launching a debug session.</p>
- <li> Run the Trace32 Installer
- <ul>
- <li>Run the <span class="code">Setup.bat</span> file. During installation select the following options:<br /><br />
- <b>Product Type:</b> In-Circuit Debugger<br />
- <b>ICD interface Type:</b> USB Interface<br />
- <b>Selection of license for new software:</b> License key not necessary<br />
- <b>CPU selection:</b> ICD ARM7 ARM9 ARM10 ARM11 ICD XSCALE</li>
- </ul>
- </li>
- <li>Install the USB Drivers </li>
- <ol type="a">
- <li>Place a Trace32 CD into the host machine.</li>
- <li>Plug in the USB connector from the Lauterbach into the host machine.</li>
- <li>Once the host machine detects the connection, install the drivers from the CD.</li>
- </ol>
- <li>Copy Trace32 License File to T32 Folder</li>
- <p>The newer Lauterbachs require a license file in the T32 folder. Copy the trace32 license file called license.t32 to your C:\T32 folder.</p>
-
- <li>Copy Trace32 Configuration File</li>
- <p>For H4 board: Copy the trace32 configuration file for the non-ARM11 processor, called config_arm11.t32, to your C:\T32 folder. You can also modify the default config_arm11.t32 file. This file needs to be modified to specify the port number and also enable T32 to support debugger commands outside T32. Carbide.c++ provides specific T32 config files in the support folder. The default config file will be called carbideconfig.t32.</p>
- <li>Set up the Board</li>
- <p>Power up the board. You should now be able to download the image.</p>
- </ol>
-
- <h5>Using Sophia Hardware </h5>
- <ol>
- <li>If needed, install the following Watchpoint debugger software:<br />
- <p>Watchpoint ARM9<br />
- Watchpoint ARM11<br />
- CodeWarrior - Watchpoint Connection tool<br />
- Driver for USB dongle for STI ARM<br />
- Watchpoint ARM9 Help Files</p></li>
- <li>Setup Watchpoint</li>
- <p>Copy and unzip Watchpoint project and initialization files to any directory on your PC.</p>
- <li>Establish Target Connection
- <ol type="a">
- <li>Plug USB dongle into your PC, and install the drivers if necessary.</li>
- <li>Connect Sophia EJ-Debug JTAG device to the Jtag on the mother board (make sure SW3-7 is off) and to PC via USB cable.</li>
- <li>When Windows prompts you for a driver, navigate to your WATCHPOINT\US_ARM9 or WATCHPOINT\US_ARM11 installation.</li>
- <li>Open the WatchPoint project file. If it launches successfully, you have established a connection.</li>
- </ol>
- <p>After successfully opening the project file, make sure that for the H4 target, the Jtag clock is set to 8.33MHz. This can be done from the Resource menu of WatchPoint. Select the ‘ICE Configuration’ option and then select the ‘Clock’ tab. Check the 8.33 MHz radio button and apply the settings.</p>
- </li>
- </ol>
-</div>
-<h5>Related Tasks</h5>
-<ul>
- <li><a href="stop_mode_debug_precond.htm">Stop Mode On-Device Debugging Preconditions</a></li>
- <li><a href="stop_mode_debug_launchcfg.htm">Defining a Stop Mode Debug Configuration</a></li>
-</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<title>Stop Mode On-Device Debugging</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF" dir="ltr">
+<h2>Installing JTAG</h2>
+<div class="step">
+ <h4>Install the JTAG Software</h4>
+ <h5>Using Lauterbach Hardware </h5>
+ <ol>
+ <li>Program Lauterbach with Proper License</li>
+ <p>You will need a Trace32 (Lauterbach), a USB cable, and a Lauterbach power supply. You will need to program the Lauterbach with licenses for the particular processors you will be targeting.</p>
+ <p>Older Lauterbachs have Xscale for Lubbock and ARM9 for H2/Renesas licenses installed on them already. Newer Lauterbachs should have ARM9 for H2/Renesas and ARM11 for H4 licenses installed on them already. If you don’t have the proper license installed on the Lauterbach for the processor you want to work with, you will receive an error when launching a debug session.</p>
+ <li> Run the Trace32 Installer
+ <ul>
+ <li>Run the <span class="code">Setup.bat</span> file. During installation select the following options:<br /><br />
+ <b>Product Type:</b> In-Circuit Debugger<br />
+ <b>ICD interface Type:</b> USB Interface<br />
+ <b>Selection of license for new software:</b> License key not necessary<br />
+ <b>CPU selection:</b> ICD ARM7 ARM9 ARM10 ARM11 ICD XSCALE</li>
+ </ul>
+ </li>
+ <li>Install the USB Drivers </li>
+ <ol type="a">
+ <li>Place a Trace32 CD into the host machine.</li>
+ <li>Plug in the USB connector from the Lauterbach into the host machine.</li>
+ <li>Once the host machine detects the connection, install the drivers from the CD.</li>
+ </ol>
+ <li>Copy Trace32 License File to T32 Folder</li>
+ <p>The newer Lauterbachs require a license file in the T32 folder. Copy the trace32 license file called license.t32 to your C:\T32 folder.</p>
+
+ <li>Copy Trace32 Configuration File</li>
+ <p>For H4 board: Copy the trace32 configuration file for the non-ARM11 processor, called config_arm11.t32, to your C:\T32 folder. You can also modify the default config_arm11.t32 file. This file needs to be modified to specify the port number and also enable T32 to support debugger commands outside T32. Carbide.c++ provides specific T32 config files in the support folder. The default config file will be called carbideconfig.t32.</p>
+ <li>Set up the Board</li>
+ <p>Power up the board. You should now be able to download the image.</p>
+ </ol>
+</div>
+<h5>Related Tasks</h5>
+<ul>
+ <li><a href="stop_mode_debug_precond.htm">Stop Mode On-Device Debugging Preconditions</a></li>
+ <li><a href="stop_mode_debug_launchcfg.htm">Defining a Stop Mode Debug Configuration</a></li>
+</ul>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Tue Jan 26 12:01:35 2010 -0600
@@ -1,301 +1,280 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<title>Stop Mode On-Device Debugging</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</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 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>
- <li>Access the Debug window
- <ol type="a">
- <li>If necessary, import a project's .mmp or .inf file in Carbide.c++.</li>
- <li>Select the Project in the C/C++ Project view that you want to debug.</li>
- <li>Select the Run > Debug… menu option to display the Debug launch configuration window.</li>
- <li>Define a debug launch configuration to communicate with the on-device debug agent or protocol interface.</li>
- <li>In the Debug window, define the type of debug launch configuration to use when debugging programs on the target device.</li>
- </ol>
- </li>
- <p align="center"><img src="images/Debug_Config_window.png" width="704" height="455" /></p>
- <p align="left" class="figure">Figure 1 - Debug Configurations</p>
- <p>Select either a Symbian OS Sophia or Symbian OS Trace32 configuration type for stop mode on-device debugging and click the New launch configuration icon. The following pages require review and possible option settings:</p>
- <ul>
- <li> Main - defines the project to be launched on the target device</li>
- <li>Connection - specifies the method used to transfer files to the target device</li>
- <li> Debugger - provides control over entry points, message handling, and instruction set default settings</li>
- <li> ROM Image- specifies startup options and ROM log and image files </li>
- <li>Source - specifies the source lookup paths </li>
- <li>Common - specifies general launch configuration settings </li>
- </ul>
- <p>Click <b>Debug</b> after all the preference panels have been set. The Debug window closes and the Carbide.c++ debugger begins a debugging session using the new configuration. The next time you click the Debug icon, this debug launch configuration is used to start a debug session.</p>
- <li>Define Main Tab Settings</li>
- <p>The Main pane shown in Figure 2 defines the project to be launched on the target device. Table 1 defines the fields.</p>
- <p><img src="images/Debug_Config_main.png" width="836" height="555" /></p>
- <p class="figure">Figure 2 - Debug Window - Main Tab</p>
- <p>Table 1. Main pane</p>
- <table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Item</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <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>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>
- </table>
- <p></p>
- <li> Define Connection Tab Settings</li>
- <p><img src="images/Debug_Config_connection.png" width="804" height="309" /></p>
- <p class="figure">Figure 3 - Debug Window - Connection Tab</p>
- <p>Table 2 - Connection pane</p>
- <table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Item</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <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><!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 />
- PBI=USB<br />
- RCL=NETASSIST<br />
- PACKLEN=1024<br />
- PORT=20000</p></td>
- </tr>
- <tr>
- <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></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><!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">
- </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>
- <p></p>
- <li>Define Debugger Tab Settings</li>
- <p align="center"><img src="images/Debug_Config_debugger.png" width="594" height="297" /></p>
- <p class="figure">Figure 4 - Debug Window - Debugger tab</p>
- <p>Table 3 - Debugger pane</p>
- <table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Item</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Break at entry point</b></td>
- <td><p>When checked, break at the specified entry point entered in the text field. For .EXE targets, the default entry point is set to <span class="code">E32Main</span>. By default, the <b>Break at entry point</b> option is unchecked for all other target types.</p></td>
- </tr>
- <tr>
- <td><b>Target Processor </b></td>
- <td>A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.</td>
- </tr>
- <tr>
- <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Target Initialization File</b></font></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 like Sophia, you can specify the initialization file, which can be run after connecting to the target.</p></td>
- </tr>
- <tr>
- <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <p><b><font size="2" style="font-size: 9pt"><font face="Georgia, serif">Memory Configuration File</font></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><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <p><b><font size="2" style="font-size: 9pt"><font face="Georgia, serif">Reset target at the start of each debug session</font></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>
- <td><p><b>Default Instructon Set </b></p></td>
- <td><p>Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. This can happen at addresses for which we have no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code. The options are:</p>
- <ul>
- <li>Auto (examine code at current PC location) </li>
- <li>ARM (32-bit) </li>
- <li>THUMB (16-bit) </li>
- </ul>
- <p>By default the Instruction Set option uses ARM 32-bit.</p></td>
- </tr>
- </table>
- <p></p>
- <li>Define ROM Image Tab</li>
- <p align="center"><img src="images/Debug_Config_ROM.png" width="594" height="481" /></p>
- <p class="figure">Figure 5 - Debug Window - ROM Image Tab</p>
- <p>Table 4 - ROM Image pane</p>
- <table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Item</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <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">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Start Address</b></font></font></p></td>
- <td><p>Enter the physical address in memory where the Symbian OS start code begins execution. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x8000000 is a valid entry.</p>
- <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><!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">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Debug from Start address</b></font></font></p></td>
- <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><!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">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Run from start address</b></font></font></p></td>
- <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><!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">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Symbian ROM Log file</b></font></font></p></td>
- <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><!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">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Symbian OS Kit EPOC32 Directory</b></font></font></p></td>
- <td class="note"><p>Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory.</p>
- <p class="note"><b>NOTE</b> Always include the epoc32 folder in this path.</p></td>
- </tr>
- <tr>
- <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">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Log unresolved modules</b></font></font></p></td>
- <td class="note"><p>Check this box to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session.</p>
- <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><!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">
- </font></b><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>Debug non-XIP Executables</b></font></font></p></td>
- <td><p>Check this box to debug a project, or a dynamically loaded module, that is loaded from NAND-Flash or other removable media (MMC, memory stick, etc.) at run time and executed in RAM. Use this option to debug modules that work fine when executed in place as part of the ROM image, but sometimes fail when placed in NAND-Flash or other removable media.</p>
- <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><!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">
- </font></b><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Symbian ROM Image</b></font></font></p></td>
- <td>Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window.</td>
- </tr>
- <tr>
- <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Download Address (hex) </b></font></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><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Ask for download at the start of each debug session</b></font></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>
- <p> </p>
- </ol>
- <h3>Sophia Target Interface Connection</h3>
- <p>The following Connection pane is specific to the Sophia Target Interface and is shown in a Sophia Launch Configuration only. Other panes are same as Trace32 panes.</p>
- <p align="center"><img src="images/Debug_Config_sophia.png" width="819" height="305" /></p>
- <p class="figure">Figure 6 - Sophia Connection Window</p>
- <p>Table 5 - Sophia Connection Window</p>
- <table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Item</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <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">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Sophia Target Interface (WTI.dll) location</b></font></font></p></td>
- <td>Specifies the location of a Sophia dll that the debugger will load and interface with in order to communicate with the Sophia JTAG interface. The preference panel will try to determine this value from the registry or some other means and auto fill it when possible.</td>
- </tr>
- <tr>
- <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">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <b>EJ_Debug Type </b></font></font></p></td>
- <td><p>Sophia Systems' EJ-Debug is a compact, USB-powered JTAG emulator. Select the EJ_Debug type. Options include:</p>
- <ul>
- <li>Auto (automatically detects target CPU) </li>
- <li>ARM9 (target CPU) </li>
- <li>ARM11 (target CPU)</li>
- <li>ARM9_11 (target CPU)</li>
- <li>ARM7_9_11 (target CPU)</li>
- </ul></td>
- </tr>
- <tr>
- <td><b>JTAG TCLK Frequency</b></td>
- <td>Select the JTAG TCLK frequency. Options include:
- <ul>
- <li>Auto</li>
- <li>33 MHz</li>
- <li>16 MHz</li>
- <li>8 MHz</li>
- <li>500 KHz </li>
- </ul></td>
- </tr>
- <tr>
- <td><b>View messages between Carbide and STI</b></td>
- <td>The View Messages between Carbide and STI check box allows you to specify if the debug protocol messages between Carbide and STI should be logged in a Communication Log console window.</td>
- </tr>
- </table>
-
-</div>
-<h5>Related Tasks</h5>
-<ul>
- <li><a href="stop_mode_debug_precond.htm">Stop Mode On-Device Debugging Preconditions</a></li>
-</ul>
-
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<title>Stop Mode On-Device Debugging</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<style type="text/css">
+<!--
+.style1 {font-size: 1em}
+-->
+</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 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>
+ <li>Access the Debug window
+ <ol type="a">
+ <li>If necessary, import a project's .mmp or .inf file in Carbide.c++.</li>
+ <li>Select the Project in the C/C++ Project view that you want to debug.</li>
+ <li>Select the Run > Debug… menu option to display the Debug launch configuration window.</li>
+ <li>Define a debug launch configuration to communicate with the on-device debug agent or protocol interface.</li>
+ <li>In the Debug window, define the type of debug launch configuration to use when debugging programs on the target device.</li>
+ </ol>
+ </li>
+ <p align="center"><img src="images/Debug_Config_window.png" width="704" height="455" /></p>
+ <p align="left" class="figure">Figure 1 - Debug Configurations</p>
+ <p>Select either a Symbian OS Trace32 configuration type for stop mode on-device debugging and click the New launch configuration icon. The following pages require review and possible option settings:</p>
+ <ul>
+ <li> Main - defines the project to be launched on the target device</li>
+ <li>Connection - specifies the method used to transfer files to the target device</li>
+ <li> Debugger - provides control over entry points, message handling, and instruction set default settings</li>
+ <li> ROM Image- specifies startup options and ROM log and image files </li>
+ <li>Source - specifies the source lookup paths </li>
+ <li>Common - specifies general launch configuration settings </li>
+ </ul>
+ <p>Click <b>Debug</b> after all the preference panels have been set. The Debug window closes and the Carbide.c++ debugger begins a debugging session using the new configuration. The next time you click the Debug icon, this debug launch configuration is used to start a debug session.</p>
+ <li>Define Main Tab Settings</li>
+ <p>The Main pane shown in Figure 2 defines the project to be launched on the target device. Table 1 defines the fields.</p>
+ <p><img src="images/Debug_Config_main.png" width="836" height="555" /></p>
+ <p class="figure">Figure 2 - Debug Window - Main Tab</p>
+ <p>Table 1. Main pane</p>
+ <table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="38%" scope="col">Item</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <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>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>
+ </table>
+ <p></p>
+ <li> Define Connection Tab Settings</li>
+ <p><img src="images/Debug_Config_connection.png" width="804" height="309" /></p>
+ <p class="figure">Figure 3 - Debug Window - Connection Tab</p>
+ <p>Table 2 - Connection pane</p>
+ <table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="38%" scope="col">Item</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <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><!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 />
+ PBI=USB<br />
+ RCL=NETASSIST<br />
+ PACKLEN=1024<br />
+ PORT=20000</p></td>
+ </tr>
+ <tr>
+ <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></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><!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">
+ </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>
+ <p></p>
+ <li>Define Debugger Tab Settings</li>
+ <p align="center"><img src="images/Debug_Config_debugger.png" width="594" height="297" /></p>
+ <p class="figure">Figure 4 - Debug Window - Debugger tab</p>
+ <p>Table 3 - Debugger pane</p>
+ <table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="38%" scope="col">Item</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Break at entry point</b></td>
+ <td><p>When checked, break at the specified entry point entered in the text field. For .EXE targets, the default entry point is set to <span class="code">E32Main</span>. By default, the <b>Break at entry point</b> option is unchecked for all other target types.</p></td>
+ </tr>
+ <tr>
+ <td><b>Target Processor </b></td>
+ <td>A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.</td>
+ </tr>
+ <tr>
+ <td>
+ <span class="style1">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </span>
+ <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 specify the initialization file, which can be run after connecting to the target.</p></td>
+ </tr>
+ <tr>
+ <td>
+ <span class="style1">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </span>
+ <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="style1">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </span>
+ <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>
+ <td><p><b>Default Instructon Set </b></p></td>
+ <td><p>Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. This can happen at addresses for which we have no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code. The options are:</p>
+ <ul>
+ <li>Auto (examine code at current PC location) </li>
+ <li>ARM (32-bit) </li>
+ <li>THUMB (16-bit) </li>
+ </ul>
+ <p>By default the Instruction Set option uses ARM 32-bit.</p></td>
+ </tr>
+ </table>
+ <p></p>
+ <li>Define ROM Image Tab</li>
+ <p align="center"><img src="images/Debug_Config_ROM.png" width="594" height="481" /></p>
+ <p class="figure">Figure 5 - Debug Window - ROM Image Tab</p>
+ <p>Table 4 - ROM Image pane</p>
+ <table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="38%" scope="col">Item</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><span class="style1">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </span>
+ <p class="style1"><font face="Georgia, serif">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Start Address</b></font></p></td>
+ <td><p>Enter the physical address in memory where the Symbian OS start code begins execution. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x8000000 is a valid entry.</p>
+ <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">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </span>
+ <p class="style1"><font face="Georgia, serif">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Debug from Start address</b></font></p></td>
+ <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">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </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">
+ <b>Run from start address</b></font></p></td>
+ <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">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </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">
+ <b>Symbian ROM Log file</b></font></p></td>
+ <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">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </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">
+ <b>Symbian OS Kit EPOC32 Directory</b></font></p></td>
+ <td class="note"><p>Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory.</p>
+ <p class="note"><b>NOTE</b> Always include the epoc32 folder in this path.</p></td>
+ </tr>
+ <tr>
+ <td><span class="style1">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </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">
+
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Log unresolved modules</b></font></p></td>
+ <td class="note"><p>Check this box to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session.</p>
+ <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">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </span>
+ <p class="style1"><b>
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </b><font face="Georgia, serif">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Debug non-XIP Executables</b></font></p></td>
+ <td><p>Check this box to debug a project, or a dynamically loaded module, that is loaded from NAND-Flash or other removable media (MMC, memory stick, etc.) at run time and executed in RAM. Use this option to debug modules that work fine when executed in place as part of the ROM image, but sometimes fail when placed in NAND-Flash or other removable media.</p>
+ <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">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </span>
+ <p class="style1"><b>
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ </b><font face="Georgia, serif">
+ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+ <b>Symbian ROM Image</b></font></p></td>
+ <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">
+ <!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>
+ <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">
+ <!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>
+ <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>
+ </ol>
+</div>
+<h5>Related Tasks</h5>
+<ul>
+ <li><a href="stop_mode_debug_precond.htm">Stop Mode On-Device Debugging Preconditions</a></li>
+</ul>
+
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+
+</body>
+</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm Tue Jan 26 12:01:35 2010 -0600
@@ -16,7 +16,7 @@
<li>Install the GCCE or RVCT 2.2 or greater compiler (not included with Carbide.c++).</li>
<li>Install the TechView Devkit</li>
<li>Install Board Support Package (BSP) for your target board</li>
-<li>Install JTAG software and drivers for <a href="http://www.lauterbach.com">Trace32</a> or <a href="http://www.sophia.com">Sophia</a> I/F tool support</li>
+<li>Install JTAG software and drivers for <a href="http://www.lauterbach.com">Trace32</a> support</li>
<li>Connect JTAG interface between PC and hardware</li>
<li>Verify that your SDK or customer kit is recognized in the <a href="../../reference/SDKPreferences.html">SDK preferences</a> panel.</li>
<li>Build your <a href="../../reference/ROM_build_settings.html">ROM Image</a></li>
@@ -25,8 +25,7 @@
<h5>Related Tasks</h5>
<ul>
<li><a href="../../projects/launch/trace32.htm">Symbian OS Trace32 Support</a></li>
-<li><a href="../../projects/launch/sophia.htm">Symbian OS Sophia Target Interface Support</a></li>
</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Tue Jan 26 12:01:35 2010 -0600
@@ -18,15 +18,14 @@
<p class="note"><b>NOTE</b> You cannot debug ROM DLLs using Application TRK. </p>
</blockquote>
<ul>
- <li>In Sophia or Trace32 you must specify the ROM log file in the ROM Image tab of the <a href="../../projects/launch/trace32.htm">Trace32</a> or <a href="../../projects/launch/sophia.htm">Sophia</a> launch configuration</li>
+ <li>In Trace32 you must specify the ROM log file in the ROM Image tab of the <a href="../../projects/launch/trace32.htm">Trace32</a> launch configuration</li>
</ul>
<h5>Other references </h5>
<ul>
<li><a href="prj_import_exe.htm">Importing Executables for Debugging</a></li>
<li><a href="../../projects/launch/trace32.htm">Symbian OS Trace32 Support</a></li>
- <li><a href="../../projects/launch/sophia.htm">Symbian OS Sophia Target Interface Support</a></li>
</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/index.xml Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/index.xml Tue Jan 26 12:01:35 2010 -0600
@@ -601,10 +601,6 @@
<topic href="html/tasks/start/carbide_deploying.htm" label="Uploading"/>
</entry>
- <entry keyword="Sophia">
- <topic href="html/projects/launch/sophia.htm"/>
- </entry>
-
<entry keyword="Starting the Debugger">
<topic href="html/tasks/debugger/work_debug_act_start.htm"/>
</entry>
--- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Mon Jan 25 10:09:42 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Jan 26 12:01:35 2010 -0600
@@ -155,7 +155,6 @@
<topic label="Application TRK" href="html/projects/launch/run_mode.htm" />
<topic label="Attach to Process" href="html/projects/launch/attach_process.htm" />
<topic label="Emulation" href="html/projects/launch/emulation.htm" />
- <topic label="Sophia (STI)" href="html/projects/launch/sophia.htm" />
<topic label="System TRK" href="html/projects/launch/stop_mode.htm" />
<topic label="Trace32" href="html/projects/launch/trace32.htm" />
<anchor id="launch_config_ANCHOR"/>
@@ -306,15 +305,6 @@
<topic label="Source" href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_run_dbg_srce.htm" />
<topic label="Commmon" href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_run_dbg_comm.htm/" />
</topic>
- <topic label="3. Sophia Target Interface Support" href="html/projects/launch/sophia.htm" >
- <topic label="Main" href="html/projects/launch/page_main.htm" />
- <topic label="Connection" href="html/projects/launch/page_connection.htm" />
- <topic label="Debugger" href="html/projects/launch/page_debugger.htm" />
- <topic label="ROM Image" href="html/projects/launch/page_rom_image.htm" />
- <topic label="Executables" href="html/projects/launch/page_executables.htm" />
- <topic label="Source" href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_run_dbg_srce.htm" />
- <topic label="Commmon" href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/reference/cdt_u_run_dbg_comm.htm/" />
- </topic>
<topic label="4. Using Soft Attach" href="html/tasks/debugger/soft_attach_debug.htm" />
</topic>
<topic label="Building a ROM Image File" href="html/reference/ROM_build_settings.html" />