--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/app_trk_installation.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/app_trk_installation.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,71 +1,71 @@
-<!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>Installation Pane</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Installation Pane</h2>
-<p>The Debug or launch configuration window's <b>Installation</b> pane specifies the .sis file to install on the target device when using Application TRK. This is required when using the TRK debug agent with 9.x based SDK’s.</p>
-<p align="center"><img src="../images/panel_trk_installation.png" width="598" height="224" /></p>
-<p class="figure">Figure 1 - Debug window's Installation pane</p>
-<h5>Table 1. Installation pane —items </h5>
-<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><p><b>Installation file </b></p>
- <p> </p></td>
- <td><p>Enter the complete path to the .sis or .pkg file to install on the target device or click Browse to use the standard file selection dialog.</p>
- </td>
- </tr>
- <tr>
- <td><b>Download directory </b></td>
- <td>The directory on the target device to download the file into before installing it. The default directory value is <span class="code">C:\data\</span>. </td>
- </tr>
- <tr>
- <td><b>Install each launch even if installer file has not changed </b></td>
- <td>Enable this option to force an update of the installed file even if no changes have been detected. This ensures a clean program install for each debug session. </td>
- </tr>
- <tr>
- <td><b>Do not show installer UI on the phone </b></td>
- <td>Use this option to specify if the installer UI on the target device is shown when installing the file. Disabling this option may require interaction with the installer UI on the target device, slowing down the install process. The default setting is <span class="code">on</span>. </td>
- </tr>
- <tr>
- <td><b>Install to drive </b></td>
- <td>A list of common drives where files may be installed to. The default drive setting is <span class="code">C</span>. </td>
- </tr>
-</table>
-
-<div class="step">
- <h4>To access the Installation Pane</h4>
- <ol>
- <li>Select the Run > Debug... menu item</li>
- <p>The <b>Debug</b> window appears. </p>
- <li>Select a Symbian OS Application TRK configuration in the Configurations list</li>
- <li>Click Installer tab</li>
- <p>The Installation pane appears (Figure 1). </p>
- </ol>
-</div>
-<h5>Common concepts</h5>
- <ul>
- <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
- <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK)</a></li>
-</ul>
-<h5 align="left">Common references </h5>
-<ul>
- <li><a href="page_trk_main.htm">Main Pane</a></li>
- <li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
- <li><a href="page_connection.htm">Connection Pane</a></li>
- <li><a href="page_file_transfer.htm">File Transfer Pane</a></li>
- <li><a href="page_executables.htm">Executables Pane</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>Installation Pane</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Installation Pane</h2>
+<p>The Debug or launch configuration windows <b>Installation</b> pane specifies the .sis file to install on the target device when using Application TRK. This is required when using the TRK debug agent with 9.x based SDK’s.</p>
+<p align="center"><img src="../images/panel_trk_installation.png" width="598" height="224" /></p>
+<p class="figure">Figure 1 - Debug windows Installation pane</p>
+<h5>Table 1. Installation pane —items </h5>
+<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><p><b>Installation file </b></p>
+ <p> </p></td>
+ <td><p>Enter the complete path to the .sis or .pkg file to install on the target device or click Browse to use the standard file selection dialog.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><b>Download directory </b></td>
+ <td>The directory on the target device to download the file into before installing it. The default directory value is <span class="code">C:\data\</span>. </td>
+ </tr>
+ <tr>
+ <td><b>Install each launch even if installer file has not changed </b></td>
+ <td>Enable this option to force an update of the installed file even if no changes have been detected. This ensures a clean program install for each debug session. </td>
+ </tr>
+ <tr>
+ <td><b>Do not show installer UI on the phone </b></td>
+ <td>Use this option to specify if the installer UI on the target device is shown when installing the file. Disabling this option may require interaction with the installer UI on the target device, slowing down the install process. The default setting is <span class="code">on</span>. </td>
+ </tr>
+ <tr>
+ <td><b>Install to drive </b></td>
+ <td>A list of common drives where files may be installed to. The default drive setting is <span class="code">C</span>. </td>
+ </tr>
+</table>
+
+<div class="step">
+ <h4>To access the Installation Pane</h4>
+ <ol>
+ <li>Select the Run > Debug... menu item</li>
+ <p>The <b>Debug</b> window appears. </p>
+ <li>Select a Symbian OS Application TRK configuration in the Configurations list</li>
+ <li>Click Installer tab</li>
+ <p>The Installation pane appears (Figure 1). </p>
+ </ol>
+</div>
+<h5>Common concepts</h5>
+ <ul>
+ <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
+ <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK)</a></li>
+</ul>
+<h5 align="left">Common references </h5>
+<ul>
+ <li><a href="page_trk_main.htm">Main Pane</a></li>
+ <li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
+ <li><a href="page_connection.htm">Connection Pane</a></li>
+ <li><a href="page_file_transfer.htm">File Transfer Pane</a></li>
+ <li><a href="page_executables.htm">Executables Pane</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/reference/launch_configs/emulator_debugger.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_debugger.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,73 +1,73 @@
-<!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>Debugger Pane</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Debugger Pane</h2>
-<p>The <b>Debug/Run</b> window's <b>Debugger</b> pane provides control entry point breaks and which consoles are active to show logs. </p>
-<p align="center"><img src="../images/panel_debug_debugger.png" width="639" height="278" /></p>
-<p class="figure">Figure 1 - Debug window's Debugger tab</p>
-<h5>Table 1. Debugger pane —items </h5>
-<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>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="../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>
-
-<div class="step">
- <h4>To access the Debug window </h4>
- <ol>
- <li>Select the Run > Debug... menu item</li>
- <p>The Debug window appears. </p>
- <li>Select a Configuration setting</li>
- <li>Click Debugger tab </li>
- <p>The Debugger pane appears (Figure 1). </p>
- </ol>
-</div>
-<h5>Common concepts</h5>
- <ul>
- <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
- </ul>
-<h5 align="left">Common tasks</h5>
-<ul>
- <li><a href="../../tasks/start/carbide_debugging.htm">Debugging a Program</a> (Example)</li>
- <li><a href="../../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
-</ul>
-<h5 align="left">Common references </h5>
-<ul>
- <li><a href="../perspective_debug.htm">Debug Perspective</a></li>
- <li><a href="../wnd_debug_configuration.htm">Debug Window </a> </li>
- <li><a href="../view_debug.htm">Debug View</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>
+<!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>Debugger Pane</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Debugger Pane</h2>
+<p>The <b>Debug/Run</b> windows <b>Debugger</b> pane provides control entry point breaks and which consoles are active to show logs. </p>
+<p align="center"><img src="../images/panel_debug_debugger.png" width="639" height="278" /></p>
+<p class="figure">Figure 1 - Debug windows Debugger tab</p>
+<h5>Table 1. Debugger pane —items </h5>
+<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>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="../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>
+
+<div class="step">
+ <h4>To access the Debug window </h4>
+ <ol>
+ <li>Select the Run > Debug... menu item</li>
+ <p>The Debug window appears. </p>
+ <li>Select a Configuration setting</li>
+ <li>Click Debugger tab </li>
+ <p>The Debugger pane appears (Figure 1). </p>
+ </ol>
+</div>
+<h5>Common concepts</h5>
+ <ul>
+ <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
+ </ul>
+<h5 align="left">Common tasks</h5>
+<ul>
+ <li><a href="../../tasks/start/carbide_debugging.htm">Debugging a Program</a> (Example)</li>
+ <li><a href="../../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
+</ul>
+<h5 align="left">Common references </h5>
+<ul>
+ <li><a href="../perspective_debug.htm">Debug Perspective</a></li>
+ <li><a href="../wnd_debug_configuration.htm">Debug Window </a> </li>
+ <li><a href="../view_debug.htm">Debug View</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>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_exceptions.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_exceptions.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,59 +1,59 @@
-<!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>x86 Exceptions Pane</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>x86 Exceptions Pane </h2>
-<p> The <b>Debug/Run</b> window's <b>x86 Exceptions</b> pane lists all the exceptions that the debugger is able to catch. If you want the debugger to catch all the exceptions, enable all of the options in this view. However, if you prefer to handle only certain exceptions, enable only those options that reflect the exceptions you prefer to handle.</p>
-<p align="center"><img src="../images/panel_debug_x86_exceptions.png" width="627" height="270" /></p>
-<p align="center" class="figure">Figure 1 - x86 Exceptions pane</p>
-<h5>Table 1. x86 Exceptions pane —items </h5>
-<table width="88%" 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>Check All </b></td>
- <td>Enables catching all exceptions.</td>
- </tr>
- <tr>
- <td><b>Clear All </b></td>
- <td>Disables catching all exceptions.</td>
- </tr>
-</table>
-<div class="step">
- <h4>To access the x86 Exceptions pane</h4>
- <ol>
- <li>Select the Run > Run... or Run > Debug... menu item</li>
- <p>The Debug window (Figure 1) appears. </p>
- <li>Select a Configuration setting</li>
- <li>Click x86 Exceptions tab </li>
- <p>The x86 Exceptions pane appears. </p>
- </ol>
-</div>
-<h5>Common concepts</h5>
- <ul>
- <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
- </ul>
- <h5 align="left">Common tasks</h5>
- <ul>
- <li><a href="../../tasks/start/carbide_debugging.htm">Debugging a Program</a> (Example)</li>
- <li><a href="../../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
- </ul>
- <h5 align="left">Common references </h5>
- <ul>
- <li><a href="../perspective_debug.htm">Debug Perspective</a></li>
- <li><a href="../wnd_debug_configuration.htm">Debug Window </a> </li>
- <li><a href="../view_debug.htm">Debug View</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>x86 Exceptions Pane</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>x86 Exceptions Pane </h2>
+<p> The <b>Debug/Run</b> windows <b>x86 Exceptions</b> pane lists all the exceptions that the debugger is able to catch. If you want the debugger to catch all the exceptions, enable all of the options in this view. However, if you prefer to handle only certain exceptions, enable only those options that reflect the exceptions you prefer to handle.</p>
+<p align="center"><img src="../images/panel_debug_x86_exceptions.png" width="627" height="270" /></p>
+<p align="center" class="figure">Figure 1 - x86 Exceptions pane</p>
+<h5>Table 1. x86 Exceptions pane —items </h5>
+<table width="88%" 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>Check All </b></td>
+ <td>Enables catching all exceptions.</td>
+ </tr>
+ <tr>
+ <td><b>Clear All </b></td>
+ <td>Disables catching all exceptions.</td>
+ </tr>
+</table>
+<div class="step">
+ <h4>To access the x86 Exceptions pane</h4>
+ <ol>
+ <li>Select the Run > Run... or Run > Debug... menu item</li>
+ <p>The Debug window (Figure 1) appears. </p>
+ <li>Select a Configuration setting</li>
+ <li>Click x86 Exceptions tab </li>
+ <p>The x86 Exceptions pane appears. </p>
+ </ol>
+</div>
+<h5>Common concepts</h5>
+ <ul>
+ <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
+ </ul>
+ <h5 align="left">Common tasks</h5>
+ <ul>
+ <li><a href="../../tasks/start/carbide_debugging.htm">Debugging a Program</a> (Example)</li>
+ <li><a href="../../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
+ </ul>
+ <h5 align="left">Common references </h5>
+ <ul>
+ <li><a href="../perspective_debug.htm">Debug Perspective</a></li>
+ <li><a href="../wnd_debug_configuration.htm">Debug Window </a> </li>
+ <li><a href="../view_debug.htm">Debug View</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/reference/launch_configs/emulator_main.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_main.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,52 +1,52 @@
-<!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>Main Pane (Emulator)</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Main Pane (Emulator) </h2>
-<p>The emulator <b>Main</b> pane defines the process to be launched by the emulator. </p>
-<p>The behavior that occurs when launching a debug session varies based upon the <a href="../SDKPreferences.html">SDK</a>. Normally, <a href="../../tasks/debugger/work_debug_act_start.htm">starting</a> a debug session launches the emulator (<span class="code">epoc.exe</span>) and you must then navigate to your application and open it. However, starting a debug session for an .exe file will, in most cases, launch the .exe directly. This starts the emulator and then opens your application automatically. Note that some SDKs do not support this behavior. In those cases you must still open your application in the emulator manually.</p>
-<p align="center"><img src="../images/panel_debug_main.png" width="639" height="278" /></p>
-<p class="figure">Figure 1 - Debug window's emulator's Main tab </p>
-<h5>Table 1. Emulator Main pane —items </h5>
-<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>Project</b></td>
- <td><p>The project to associate with this debug launch configuration. Click <b>Browse</b> to select a different project. </p> </td>
- </tr>
- <tr>
- <td><b>Process to launch </b></td>
- <td>The path to the emulator or executable to launch. For Symbian OS 9.1 the emulator path is required. For Symbian OS 9.2 and later the path to the executable should be used. Click <b>Browse</b> to select a different emulator. </td>
- </tr>
-</table>
-
-<div class="step">
- <h4>To access the Main Pane</h4>
- <ol>
- <li>Select the Run > Debug... menu item</li>
- <p>The Debug window appears. </p>
- <li>Select a Symbian OS System emulator configuration in the Configurations list </li>
- <li>Click Main tab </li>
- <p>The Main pane appears (Figure 1). </p>
- </ol>
-</div>
-<h5>Other references</h5>
- <ul>
- <li><a href="../wnd_debug_configuration.htm">Debug window</a></li>
- <li><a href="../../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
- <li><a href="run_mode_overview.htm">Run-mode overview</a></li>
- <li><a href="stop_mode_overview.htm">Stop-mode 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>
+<!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>Main Pane (Emulator)</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Main Pane (Emulator) </h2>
+<p>The emulator <b>Main</b> pane defines the process to be launched by the emulator. </p>
+<p>The behavior that occurs when launching a debug session varies based upon the <a href="../SDKPreferences.html">SDK</a>. Normally, <a href="../../tasks/debugger/work_debug_act_start.htm">starting</a> a debug session launches the emulator (<span class="code">epoc.exe</span>) and you must then navigate to your application and open it. However, starting a debug session for an .exe file will, in most cases, launch the .exe directly. This starts the emulator and then opens your application automatically. Note that some SDKs do not support this behavior. In those cases you must still open your application in the emulator manually.</p>
+<p align="center"><img src="../images/panel_debug_main.png" width="639" height="278" /></p>
+<p class="figure">Figure 1 - Debug windows emulator's Main tab </p>
+<h5>Table 1. Emulator Main pane —items </h5>
+<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>Project</b></td>
+ <td><p>The project to associate with this debug launch configuration. Click <b>Browse</b> to select a different project. </p> </td>
+ </tr>
+ <tr>
+ <td><b>Process to launch </b></td>
+ <td>The path to the emulator or executable to launch. For Symbian OS 9.1 the emulator path is required. For Symbian OS 9.2 and later the path to the executable should be used. Click <b>Browse</b> to select a different emulator. </td>
+ </tr>
+</table>
+
+<div class="step">
+ <h4>To access the Main Pane</h4>
+ <ol>
+ <li>Select the Run > Debug... menu item</li>
+ <p>The Debug window appears. </p>
+ <li>Select a Symbian OS System emulator configuration in the Configurations list </li>
+ <li>Click Main tab </li>
+ <p>The Main pane appears (Figure 1). </p>
+ </ol>
+</div>
+<h5>Other references</h5>
+ <ul>
+ <li><a href="../wnd_debug_configuration.htm">Debug window</a></li>
+ <li><a href="../../tasks/projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
+ <li><a href="run_mode_overview.htm">Run-mode overview</a></li>
+ <li><a href="stop_mode_overview.htm">Stop-mode 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>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_connection.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_connection.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,81 +1,81 @@
-<!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>Connection Pane</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Connection Pane</h2>
-<p>The <b>Connection</b> pane specifies the method used to transfer files to the target device. Once a Serial Port type is chosen, the remaining options contain default values for the specific connection type. Users can change these remaining options to match the target device's communication specifications. </p>
-<p align="center"><img src="../images/panel_trk_connection.png" width="598" height="224" /></p>
-<p class="figure">Figure 1 - Debug window's Connection pane</p>
-<h5>Table 1. <span class="figure">Connection</span> pane —items </h5>
-<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>Serial Port </b></td>
- <td><p>Select the serial port option to use for this launch or launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. Note that for USB and BT can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device. </p>
- <p>If you are using a USB connection, the connected phone's name should appear in the menu to help identify which port is being used. </p></td>
- </tr>
- <tr>
- <td><b>Baud Rate </b></td>
- <td>Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps). </td>
- </tr>
- <tr>
- <td><b>Data Bits </b></td>
- <td>Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8. </td>
- </tr>
- <tr>
- <td><b>Parity</b></td>
- <td>Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None. </td>
- </tr>
- <tr>
- <td><b>Stop Bits </b></td>
- <td>Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 1.</td>
- </tr>
- <tr>
- <td><b>Flow Control </b></td>
- <td>Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None. </td>
- </tr>
-</table>
-
-<div class="step">
- <h4>To access the Connection Pane</h4>
- <ol>
- <li>Select the Run > Debug... menu item</li>
- <p>The <b>Debug</b> window appears. </p>
- <li>Select a Symbian OS Application TRK configuration in the Configurations list </li>
- <li>Click Connection tab </li>
- <p>The <b>Connection</b> pane appears (Figure 1). </p>
- </ol>
-</div>
-<h5>Common concepts</h5>
- <ul>
- <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
- <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
- </ul>
-<h5 align="left">Common tasks</h5>
-<ul>
- <li><a href="../../tasks/trk/trk_connection_bluetooth.htm">Bluetooth Connection Setup</a></li>
- <li><a href="../../tasks/trk/trk_install_usb.htm">Installing On-device Debug Agents using USB</a></li>
- <li><a href="../../tasks/trk/trk_install_bluetooth.htm">Installing On-device Debug Agents using BlueTooth</a> </li>
- <li><a href="../../tasks/trk/trk_connection_usb.htm">USB Connection Setup</a></li>
-</ul>
-<h5 align="left">Common references</h5>
-<ul>
- <li><a href="page_trk_main.htm">Main Pane</a></li>
- <li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
- <li><a href="page_file_transfer.htm">File Transfer Pane </a></li>
- <li><a href="app_trk_installation.htm">Installation Pane</a></li>
- <li><a href="page_executables.htm">Executables Pane</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>Connection Pane</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Connection Pane</h2>
+<p>The <b>Connection</b> pane specifies the method used to transfer files to the target device. Once a Serial Port type is chosen, the remaining options contain default values for the specific connection type. Users can change these remaining options to match the target device's communication specifications. </p>
+<p align="center"><img src="../images/panel_trk_connection.png" width="598" height="224" /></p>
+<p class="figure">Figure 1 - Debug windows Connection pane</p>
+<h5>Table 1. <span class="figure">Connection</span> pane —items </h5>
+<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>Serial Port </b></td>
+ <td><p>Select the serial port option to use for this launch or launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. Note that for USB and BT can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device. </p>
+ <p>If you are using a USB connection, the connected phone's name should appear in the menu to help identify which port is being used. </p></td>
+ </tr>
+ <tr>
+ <td><b>Baud Rate </b></td>
+ <td>Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps). </td>
+ </tr>
+ <tr>
+ <td><b>Data Bits </b></td>
+ <td>Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8. </td>
+ </tr>
+ <tr>
+ <td><b>Parity</b></td>
+ <td>Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None. </td>
+ </tr>
+ <tr>
+ <td><b>Stop Bits </b></td>
+ <td>Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 1.</td>
+ </tr>
+ <tr>
+ <td><b>Flow Control </b></td>
+ <td>Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None. </td>
+ </tr>
+</table>
+
+<div class="step">
+ <h4>To access the Connection Pane</h4>
+ <ol>
+ <li>Select the Run > Debug... menu item</li>
+ <p>The <b>Debug</b> window appears. </p>
+ <li>Select a Symbian OS Application TRK configuration in the Configurations list </li>
+ <li>Click Connection tab </li>
+ <p>The <b>Connection</b> pane appears (Figure 1). </p>
+ </ol>
+</div>
+<h5>Common concepts</h5>
+ <ul>
+ <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
+ <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
+ </ul>
+<h5 align="left">Common tasks</h5>
+<ul>
+ <li><a href="../../tasks/trk/trk_connection_bluetooth.htm">Bluetooth Connection Setup</a></li>
+ <li><a href="../../tasks/trk/trk_install_usb.htm">Installing On-device Debug Agents using USB</a></li>
+ <li><a href="../../tasks/trk/trk_install_bluetooth.htm">Installing On-device Debug Agents using BlueTooth</a> </li>
+ <li><a href="../../tasks/trk/trk_connection_usb.htm">USB Connection Setup</a></li>
+</ul>
+<h5 align="left">Common references</h5>
+<ul>
+ <li><a href="page_trk_main.htm">Main Pane</a></li>
+ <li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
+ <li><a href="page_file_transfer.htm">File Transfer Pane </a></li>
+ <li><a href="app_trk_installation.htm">Installation Pane</a></li>
+ <li><a href="page_executables.htm">Executables Pane</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/reference/launch_configs/page_executables.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_executables.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,73 +1,73 @@
-<!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>Executables Pane</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Executables Pane</h2>
-<p>The <b>Executables</b> pane specifies which executables to debug with your project based on the chosen rule. The Executables pane gives you project level control over the executables associated with it. The pane shows all the executables in the workspace or those imported into the Executables view from outside the workspace that can be debugged by this project. See the <a href="../view_executables.htm">Executables</a> view for information on controlling executables from the workspace. </p>
-<p align="center"><img src="../images/panel_trk_exes.png" width="598" height="224" /></p>
-<p class="figure">Figure 1 - Debug window's Executables pane</p>
-<h5>Table 1. Executable pane —items </h5>
-<table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="32%" scope="col">Item</th>
- <th width="68%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Load symbols for these executables and target them for debugging </b></td>
- <td><p>Select the rule which govern the executable support used by this project for debugging purposes. The options include: </p>
- <ul>
- <li><b>Executables in the workspace from this SDK</b> — shows all executables in the workspace built using the specified SDK. This is the default setting. </li>
- <li><b>Executables built by this project</b> — shows only the executables built by this project using the specified SDK</li>
- <li><b>Executables selected below</b> — shows only the executables chosen by the user. Initial list display uses the All Executables listing. </li>
- <li><b>All executables (slows launch)</b> — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td><b>Executables list </b></td>
- <td>Shows all the executables associated with this project. </td>
- </tr>
- <tr>
- <td><b>Add...</b></td>
- <td>Opens the <b>Select an executable file</b> dialog which can locate and select executable files and add them to the project's executables list. </td>
- </tr>
- <tr>
- <td><b>Select All </b></td>
- <td>Enables all the executables in the list for debugging. </td>
- </tr>
- <tr>
- <td><b>Unselect All </b></td>
- <td>Disables all the executables in the list from debugging. </td>
- </tr>
-</table>
-<div class="step">
- <h4>To access the Executables Pane</h4>
- <ol>
- <li>Select the Run > Open Debug Dialog... menu item</li>
- <p>The <b>Debug</b> window appears. </p>
- <li>Select a Symbian OS Application TRK configuration in the Configurations list</li>
- <li>Click Executables tab </li>
- <p>The Executables pane appears (Figure 1).</p>
- </ol>
-</div>
-<h5>Common concepts</h5>
- <ul>
- <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
- <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
-</ul>
-<h5 align="left">Common references</h5>
-<ul><li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
- <li><a href="page_connection.htm">Connection Pane</a></li>
- <li><a href="page_file_transfer.htm">File Transfer Pane </a></li>
- <li><a href="app_trk_installation.htm">Installation Pane</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>
+<!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>Executables Pane</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Executables Pane</h2>
+<p>The <b>Executables</b> pane specifies which executables to debug with your project based on the chosen rule. The Executables pane gives you project level control over the executables associated with it. The pane shows all the executables in the workspace or those imported into the Executables view from outside the workspace that can be debugged by this project. See the <a href="../view_executables.htm">Executables</a> view for information on controlling executables from the workspace. </p>
+<p align="center"><img src="../images/panel_trk_exes.png" width="598" height="224" /></p>
+<p class="figure">Figure 1 - Debug windows Executables pane</p>
+<h5>Table 1. Executable pane —items </h5>
+<table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="32%" scope="col">Item</th>
+ <th width="68%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Load symbols for these executables and target them for debugging </b></td>
+ <td><p>Select the rule which govern the executable support used by this project for debugging purposes. The options include: </p>
+ <ul>
+ <li><b>Executables in the workspace from this SDK</b> — shows all executables in the workspace built using the specified SDK. This is the default setting. </li>
+ <li><b>Executables built by this project</b> — shows only the executables built by this project using the specified SDK</li>
+ <li><b>Executables selected below</b> — shows only the executables chosen by the user. Initial list display uses the All Executables listing. </li>
+ <li><b>All executables (slows launch)</b> — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. </li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><b>Executables list </b></td>
+ <td>Shows all the executables associated with this project. </td>
+ </tr>
+ <tr>
+ <td><b>Add...</b></td>
+ <td>Opens the <b>Select an executable file</b> dialog which can locate and select executable files and add them to the project's executables list. </td>
+ </tr>
+ <tr>
+ <td><b>Select All </b></td>
+ <td>Enables all the executables in the list for debugging. </td>
+ </tr>
+ <tr>
+ <td><b>Unselect All </b></td>
+ <td>Disables all the executables in the list from debugging. </td>
+ </tr>
+</table>
+<div class="step">
+ <h4>To access the Executables Pane</h4>
+ <ol>
+ <li>Select the Run > Open Debug Dialog... menu item</li>
+ <p>The <b>Debug</b> window appears. </p>
+ <li>Select a Symbian OS Application TRK configuration in the Configurations list</li>
+ <li>Click Executables tab </li>
+ <p>The Executables pane appears (Figure 1).</p>
+ </ol>
+</div>
+<h5>Common concepts</h5>
+ <ul>
+ <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
+ <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
+</ul>
+<h5 align="left">Common references</h5>
+<ul><li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
+ <li><a href="page_connection.htm">Connection Pane</a></li>
+ <li><a href="page_file_transfer.htm">File Transfer Pane </a></li>
+ <li><a href="app_trk_installation.htm">Installation Pane</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>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_file_transfer.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_file_transfer.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,85 +1,85 @@
-<!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>TRK File Transfer Pane</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>File Transfer Pane</h2>
-<p>The <b>File Transfer</b> pane displays an auto-populated list of files for System TRK that the IDE transfers to the target device at the start of each launch. Users can add, edit, or delete files in the list. By default, any file added is automatically checked for downloading to the device. Users can uncheck a file to remove it from the download list without removing the file itself. Any missing files are marked with a warning icon and a message appears describing the issue making it easy to see potential file problems prior to attempting a download.</p>
-<p>System TRK users can use this panel to download any type of file, like bitmaps, HTML, sounds, and more, to the phone and applicable to Application TRK for transfering any files outside of the installation file.</p>
-<p align="center"><img src="../images/panel_trk_file_transfer.png" width="598" height="224" /></p>
-<p class="figure">Figure 1 - Debug window's File Transfer pane</p>
-<h5>Table 1. <span class="figure">File Transfer</span> pane —items </h5>
-<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>File transfer list </b></td>
- <td><p>The File transfer list displays the project files that are moved to the target device for launch and debugging purposes. It contains these columns:</p>
- <ul>
- <li><b>Enabled</b>—a checkmark indicates that the IDE should transfer the specified file to the target directory. If unchecked, do not transfer the file. </li>
- <li><b>File to transfer</b>—the path and filename to a file on the host machine to be transfered </li>
- <li><b>Target path</b>—the path to the target directory where transfered files are placed on the device </li>
- </ul></td>
- </tr>
- <tr>
- <td><b>Add</b></td>
- <td>Click to add a file to the file transfer list.</td>
- </tr>
- <tr>
- <td><b>Edit...</b></td>
- <td>Click to edit the selected file in the file transfer list. </td>
- </tr>
- <tr>
- <td><b>Remove</b></td>
- <td>Click to remove the selected file from the file transfer list. </td>
- </tr>
- <tr>
- <td><b>Select All</b></td>
- <td>Click to select all the files in the file transfer list.</td>
- </tr>
- <tr>
- <td><b>Deselect All</b></td>
- <td>Click to unselect all the files in the file transfer list.</td>
- </tr>
-</table>
-
-<div class="step">
- <h4>To access the File Tansfer Pane</h4>
- <ol>
- <li>Select the Run > Debug... menu item</li>
- <p>The <b>Debug</b> window appears. </p>
- <li>Select a Symbian OS Application TRK configuration in the Configurations list </li>
- <li>Click File Transfer tab </li>
- <p>The <b>File Transfer</b> pane appears (Figure 1). </p>
- </ol>
-</div>
-<h5>Common concepts</h5>
- <ul>
- <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
- <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
- </ul>
-<h5 align="left">Common tasks</h5>
-<ul>
- <li><a href="../../tasks/trk/trk_connection_bluetooth.htm">Bluetooth Connection Setup</a></li>
- <li><a href="../../tasks/trk/trk_install_usb.htm">Installing On-device Debug Agents using USB</a></li>
- <li><a href="../../tasks/trk/trk_install_bluetooth.htm">Installing On-device Debug Agents using BlueTooth</a> </li>
- <li><a href="../../tasks/trk/trk_connection_usb.htm">USB Connection Setup</a></li>
-</ul>
-<h5 align="left">Common references </h5>
-<ul>
- <li><a href="page_trk_main.htm">Main Pane</a></li>
- <li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
- <li><a href="page_connection.htm">Connection Pane</a></li>
- <li><a href="app_trk_installation.htm">Installation Pane</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>
+<!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>TRK File Transfer Pane</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>File Transfer Pane</h2>
+<p>The <b>File Transfer</b> pane displays an auto-populated list of files for System TRK that the IDE transfers to the target device at the start of each launch. Users can add, edit, or delete files in the list. By default, any file added is automatically checked for downloading to the device. Users can uncheck a file to remove it from the download list without removing the file itself. Any missing files are marked with a warning icon and a message appears describing the issue making it easy to see potential file problems prior to attempting a download.</p>
+<p>System TRK users can use this panel to download any type of file, like bitmaps, HTML, sounds, and more, to the phone and applicable to Application TRK for transfering any files outside of the installation file.</p>
+<p align="center"><img src="../images/panel_trk_file_transfer.png" width="598" height="224" /></p>
+<p class="figure">Figure 1 - Debug windows File Transfer pane</p>
+<h5>Table 1. <span class="figure">File Transfer</span> pane —items </h5>
+<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>File transfer list </b></td>
+ <td><p>The File transfer list displays the project files that are moved to the target device for launch and debugging purposes. It contains these columns:</p>
+ <ul>
+ <li><b>Enabled</b>—a checkmark indicates that the IDE should transfer the specified file to the target directory. If unchecked, do not transfer the file. </li>
+ <li><b>File to transfer</b>—the path and filename to a file on the host machine to be transfered </li>
+ <li><b>Target path</b>—the path to the target directory where transfered files are placed on the device </li>
+ </ul></td>
+ </tr>
+ <tr>
+ <td><b>Add</b></td>
+ <td>Click to add a file to the file transfer list.</td>
+ </tr>
+ <tr>
+ <td><b>Edit...</b></td>
+ <td>Click to edit the selected file in the file transfer list. </td>
+ </tr>
+ <tr>
+ <td><b>Remove</b></td>
+ <td>Click to remove the selected file from the file transfer list. </td>
+ </tr>
+ <tr>
+ <td><b>Select All</b></td>
+ <td>Click to select all the files in the file transfer list.</td>
+ </tr>
+ <tr>
+ <td><b>Deselect All</b></td>
+ <td>Click to unselect all the files in the file transfer list.</td>
+ </tr>
+</table>
+
+<div class="step">
+ <h4>To access the File Tansfer Pane</h4>
+ <ol>
+ <li>Select the Run > Debug... menu item</li>
+ <p>The <b>Debug</b> window appears. </p>
+ <li>Select a Symbian OS Application TRK configuration in the Configurations list </li>
+ <li>Click File Transfer tab </li>
+ <p>The <b>File Transfer</b> pane appears (Figure 1). </p>
+ </ol>
+</div>
+<h5>Common concepts</h5>
+ <ul>
+ <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
+ <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
+ </ul>
+<h5 align="left">Common tasks</h5>
+<ul>
+ <li><a href="../../tasks/trk/trk_connection_bluetooth.htm">Bluetooth Connection Setup</a></li>
+ <li><a href="../../tasks/trk/trk_install_usb.htm">Installing On-device Debug Agents using USB</a></li>
+ <li><a href="../../tasks/trk/trk_install_bluetooth.htm">Installing On-device Debug Agents using BlueTooth</a> </li>
+ <li><a href="../../tasks/trk/trk_connection_usb.htm">USB Connection Setup</a></li>
+</ul>
+<h5 align="left">Common references </h5>
+<ul>
+ <li><a href="page_trk_main.htm">Main Pane</a></li>
+ <li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
+ <li><a href="page_connection.htm">Connection Pane</a></li>
+ <li><a href="app_trk_installation.htm">Installation Pane</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>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_debugger.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_debugger.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,133 +1,133 @@
-<!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>Debugger panes for TRK </title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Debugger panes for TRK </h2>
-<p>The <b>Debug/Run</b> window's <b>Debugger</b> panes for TRK provides control over entry points, message handling, and instruction set default settings.</p>
-<p>Different options are available in the Debugger pane based on the type of TRK launch configuration, including:</p>
-<ul><li><a href="#trk_runmode">Run mode debugging</a></li>
- <li><a href="#trk_stopmode">Stop mode debugging</a> </li>
-</ul>
-<h3><a name="trk_runmode" id="trk_runmode"></a>Run-mode Debugger pane </h3>
-<p>In run-mode you can control message handling and instruction sets. </p>
-<p align="center"><img src="../images/page_run_mode_debugger.png" width="596" height="244"></p>
-<p class="figure">Figure 1 - Debug window's Debugger pane for run mode debugging </p>
-<h5>Table 1. Debugger pane — run-mode options </h5>
-<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><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>When checked, show the contents of any program output in the <b> TRK Progam Output Console</b> in a <a href="../view_log.htm">Console</a> view. </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>
- <p> </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>
-<p> </p>
-<h3><a name="trk_stopmode" id="trk_stopmode"></a>Stop-mode Debugger pane</h3>
-<p>In stop-mode 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/panel_trk_debugger.png" width="611" height="389" /></p>
-<p class="figure">Figure 2 - Debug window's Debugger pane for stop mode debugging </p>
-<h5>Table 2. Debugger pane — stop-mode options </h5>
-<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><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>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 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><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><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>
-
-<div class="step">
- <h4>To access the Debugger Pane</h4>
- <ol>
- <li>Select the Run > Debug... menu item</li>
- <p>The <b>Debug</b> window appears. </p>
- <li>Select a Symbian OS Application TRK configuration in the Configurations list</li>
- <li>Click Debugger tab </li>
- <p>The <b>Debugger</b> pane appears (Figure 1). </p>
- </ol>
-</div>
-<h5>Common concepts</h5>
- <ul>
- <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
- <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
-</ul>
-<h5 align="left">Common references </h5>
-<ul>
- <li><a href="page_trk_main.htm">Main Pane</a></li>
- <li><a href="page_connection.htm">Connection Pane</a></li>
- <li><a href="page_file_transfer.htm">File Transfer Pane </a></li>
- <li><a href="app_trk_installation.htm">Installation Pane</a></li>
- <li><a href="page_executables.htm">Executables Pane</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>Debugger panes for TRK </title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Debugger panes for TRK </h2>
+<p>The <b>Debug/Run</b> windows <b>Debugger</b> panes for TRK provides control over entry points, message handling, and instruction set default settings.</p>
+<p>Different options are available in the Debugger pane based on the type of TRK launch configuration, including:</p>
+<ul><li><a href="#trk_runmode">Run mode debugging</a></li>
+ <li><a href="#trk_stopmode">Stop mode debugging</a> </li>
+</ul>
+<h3><a name="trk_runmode" id="trk_runmode"></a>Run-mode Debugger pane </h3>
+<p>In run-mode you can control message handling and instruction sets. </p>
+<p align="center"><img src="../images/page_run_mode_debugger.png" width="596" height="244"></p>
+<p class="figure">Figure 1 - Debug windows Debugger pane for run mode debugging </p>
+<h5>Table 1. Debugger pane — run-mode options </h5>
+<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><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>When checked, show the contents of any program output in the <b> TRK Progam Output Console</b> in a <a href="../view_log.htm">Console</a> view. </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>
+ <p> </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>
+<p> </p>
+<h3><a name="trk_stopmode" id="trk_stopmode"></a>Stop-mode Debugger pane</h3>
+<p>In stop-mode 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/panel_trk_debugger.png" width="611" height="389" /></p>
+<p class="figure">Figure 2 - Debug windows Debugger pane for stop mode debugging </p>
+<h5>Table 2. Debugger pane — stop-mode options </h5>
+<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><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>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 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><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><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>
+
+<div class="step">
+ <h4>To access the Debugger Pane</h4>
+ <ol>
+ <li>Select the Run > Debug... menu item</li>
+ <p>The <b>Debug</b> window appears. </p>
+ <li>Select a Symbian OS Application TRK configuration in the Configurations list</li>
+ <li>Click Debugger tab </li>
+ <p>The <b>Debugger</b> pane appears (Figure 1). </p>
+ </ol>
+</div>
+<h5>Common concepts</h5>
+ <ul>
+ <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
+ <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
+</ul>
+<h5 align="left">Common references </h5>
+<ul>
+ <li><a href="page_trk_main.htm">Main Pane</a></li>
+ <li><a href="page_connection.htm">Connection Pane</a></li>
+ <li><a href="page_file_transfer.htm">File Transfer Pane </a></li>
+ <li><a href="app_trk_installation.htm">Installation Pane</a></li>
+ <li><a href="page_executables.htm">Executables Pane</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/reference/launch_configs/page_trk_main.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_main.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,62 +1,62 @@
-<!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>Main Pane</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/></head>
-<body bgcolor="#FFFFFF">
-<h2>Main Pane</h2>
-<p>The <b>Main</b> pane defines the project and the process to launch on the target device. </p>
-<p align="center"><img src="../images/panel_trk_main.png" width="593" height="251" /></p>
-<p class="figure">Figure 1 - Debug window's Main pane</p>
-<h5>Table 1. Main pane —items </h5>
-<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>Project</b></td>
- <td><p>The project to associate with this launch configuration. Click Browse to select a different project. </p> </td>
- </tr>
- <tr>
- <td><b>Remote process to launch </b></td>
- <td><p>The absolute path of the remote executable to launch on the target device. The binary to debug may be stored on one of several memory locations, the most common are:</p>
- <ul>
- <li><b>RAM</b> (default) — programs running in RAM are launched from <span class="code">c:\sys\bin\</span> </li>
- <li><b>ROM</b> — programs running in ROM are launched from <span class="code">z:\sys\bin\</span></li>
- <li><b>Memory cards</b> — programs running on a memory card are launched from <span class="code">e:\sys\bin\</span> </li>
- </ul>
- <p>In the event a program is not launching, verify that the<b> </b>path is correct for the memory location where the binary resides.</p>
- </td>
- </tr>
-</table>
-
-<div class="step">
- <h4>To access the Main Pane</h4>
- <ol>
- <li>Select the Run > Debug... menu item</li>
- <p>The <b>Debug</b> window appears. </p>
- <li>Select a Symbian OS Application TRK configuration in the Configurations list</li>
- <li>Click Main tab </li>
- <p>The Main pane appears (Figure 1). </p>
- </ol>
-</div>
-<h5>Common concepts</h5>
- <ul>
- <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
- <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
-</ul>
-<h5 align="left">Common references</h5>
-<ul><li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
- <li><a href="page_connection.htm">Connection Pane</a></li>
- <li><a href="page_file_transfer.htm">File Transfer Pane </a></li>
- <li><a href="app_trk_installation.htm">Installation Pane</a></li>
- <li><a href="page_executables.htm">Executables Pane</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>
+<!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>Main Pane</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/></head>
+<body bgcolor="#FFFFFF">
+<h2>Main Pane</h2>
+<p>The <b>Main</b> pane defines the project and the process to launch on the target device. </p>
+<p align="center"><img src="../images/panel_trk_main.png" width="593" height="251" /></p>
+<p class="figure">Figure 1 - Debug windows Main pane</p>
+<h5>Table 1. Main pane —items </h5>
+<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>Project</b></td>
+ <td><p>The project to associate with this launch configuration. Click Browse to select a different project. </p> </td>
+ </tr>
+ <tr>
+ <td><b>Remote process to launch </b></td>
+ <td><p>The absolute path of the remote executable to launch on the target device. The binary to debug may be stored on one of several memory locations, the most common are:</p>
+ <ul>
+ <li><b>RAM</b> (default) — programs running in RAM are launched from <span class="code">c:\sys\bin\</span> </li>
+ <li><b>ROM</b> — programs running in ROM are launched from <span class="code">z:\sys\bin\</span></li>
+ <li><b>Memory cards</b> — programs running on a memory card are launched from <span class="code">e:\sys\bin\</span> </li>
+ </ul>
+ <p>In the event a program is not launching, verify that the<b> </b>path is correct for the memory location where the binary resides.</p>
+ </td>
+ </tr>
+</table>
+
+<div class="step">
+ <h4>To access the Main Pane</h4>
+ <ol>
+ <li>Select the Run > Debug... menu item</li>
+ <p>The <b>Debug</b> window appears. </p>
+ <li>Select a Symbian OS Application TRK configuration in the Configurations list</li>
+ <li>Click Main tab </li>
+ <p>The Main pane appears (Figure 1). </p>
+ </ol>
+</div>
+<h5>Common concepts</h5>
+ <ul>
+ <li><a href="../../concepts/debugger_about.htm">About the Debugger</a></li>
+ <li><a href="../../concepts/trk.htm">Target Resident Kernel (TRK) </a></li>
+</ul>
+<h5 align="left">Common references</h5>
+<ul><li><a href="page_trk_debugger.htm">Debugger Pane</a></li>
+ <li><a href="page_connection.htm">Connection Pane</a></li>
+ <li><a href="page_file_transfer.htm">File Transfer Pane </a></li>
+ <li><a href="app_trk_installation.htm">Installation Pane</a></li>
+ <li><a href="page_executables.htm">Executables Pane</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>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/open_cmd_window.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/open_cmd_window.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,20 +1,20 @@
-<!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>Open Command Window</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Open Command Window</h2>
-<p>Launches a Microsoft Window's <b>Command Prompt </b> set to the workspace directory. </p>
-<h5>Other references</h5>
-<ul>
- <li><a href="menus.htm">Carbide Menus</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>Open Command Window</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Open Command Window</h2>
+<p>Launches a Microsoft Windows <b>Command Prompt </b> set to the workspace directory. </p>
+<h5>Other references</h5>
+<ul>
+ <li><a href="menus.htm">Carbide Menus</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/reference/menus/open_explorer_window.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/open_explorer_window.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,20 +1,20 @@
-<!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>Show in Explorer</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Show in Explorer</h2>
-<p>Launches a Microsoft Window's <b>Explorer</b> window set to the workspace directory.</p>
-<h5>Other references</h5>
-<ul>
- <li><a href="menus.htm">Carbide Menus</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>Show in Explorer</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Show in Explorer</h2>
+<p>Launches a Microsoft Windows <b>Explorer</b> window set to the workspace directory.</p>
+<h5>Other references</h5>
+<ul>
+ <li><a href="menus.htm">Carbide Menus</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/reference/panel_debug_exceptions.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,59 +1,59 @@
-<!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>x86 Exceptions Pane</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>x86 Exceptions Pane </h2>
-<p> The Debug or launch configuration window's x86 Exceptions pane lists all the exceptions that the debugger is able to catch. If you want the debugger to catch all the exceptions, enable all of the options in this view. However, if you prefer to handle only certain exceptions, enable only those options that reflect the exceptions you prefer to handle.</p>
-<p align="center"><img src="images/panel_debug_x86_exceptions.png" width="839" height="522" /></p>
-<p align="center" class="figure">Figure 1 - x86 Exceptions pane </p>
-<h5>Table 1. x86 Exceptions pane —items </h5>
-<table width="88%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Item</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td>Check All </td>
- <td>Enables catching all exceptions.</td>
- </tr>
- <tr>
- <td>Clear All </td>
- <td>Disables catching all exceptions.</td>
- </tr>
-</table>
-<div class="step">
- <h4>To access the x86 Exceptions pane</h4>
- <ol>
- <li>Select the Run > Debug... menu item</li>
- <p>The Debug window (Figure 1) appears. </p>
- <li>Select a Configuration setting</li>
- <li>Click x86 Exceptions tab </li>
- <p>The x86 Exceptions pane appears. </p>
- </ol>
-</div>
-<h5>Common concepts</h5>
- <ul>
- <li><a href="../concepts/debugger_about.htm">About the Debugger</a></li>
- </ul>
- <h5 align="left">Common tasks</h5>
- <ul>
- <li><a href="../tasks/start/carbide_debugging.htm">Debugging a Program</a> (Example)</li>
- <li><a href="../tasks/projects/prj_debug_config.htm">Creating a Debug Configuration</a></li>
- </ul>
- <h5 align="left">Common references </h5>
- <ul>
- <li><a href="perspective_debug.htm">Debug Perspective</a></li>
- <li><a href="wnd_debug_configuration.htm">Debug Window </a> </li>
- <li><a href="view_debug.htm">Debug View</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>x86 Exceptions Pane</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>x86 Exceptions Pane </h2>
+<p> The <b>Debug</b> or launch configuration windows <b>x86 Exceptions</b> pane lists all the exceptions that the debugger is able to catch. If you want the debugger to catch all the exceptions, enable all of the options in this view. However, if you prefer to handle only certain exceptions, enable only those options that reflect the exceptions you prefer to handle.</p>
+<p align="center"><img src="images/panel_debug_x86_exceptions.png" width="627" height="270" /></p>
+<p align="center" class="figure">Figure 1 - x86 Exceptions pane </p>
+<h5>Table 1. x86 Exceptions pane —items </h5>
+<table width="88%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="38%" scope="col">Item</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td>Check All </td>
+ <td>Enables catching all exceptions.</td>
+ </tr>
+ <tr>
+ <td>Clear All </td>
+ <td>Disables catching all exceptions.</td>
+ </tr>
+</table>
+<div class="step">
+ <h4>To access the x86 Exceptions pane</h4>
+ <ol>
+ <li>Select the Run > Debug... menu item</li>
+ <p>The Debug window (Figure 1) appears. </p>
+ <li>Select a Configuration setting</li>
+ <li>Click x86 Exceptions tab </li>
+ <p>The x86 Exceptions pane appears. </p>
+ </ol>
+</div>
+<h5>Common concepts</h5>
+ <ul>
+ <li><a href="../concepts/debugger_about.htm">About the Debugger</a></li>
+ </ul>
+ <h5 align="left">Common tasks</h5>
+ <ul>
+ <li><a href="../tasks/start/carbide_debugging.htm">Debugging a Program</a> (Example)</li>
+ <li><a href="../tasks/projects/prj_debug_config.htm">Creating a Debug Configuration</a></li>
+ </ul>
+ <h5 align="left">Common references </h5>
+ <ul>
+ <li><a href="perspective_debug.htm">Debug Perspective</a></li>
+ <li><a href="wnd_debug_configuration.htm">Debug Window </a> </li>
+ <li><a href="view_debug.htm">Debug View</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/tasks/debugger/run_mode_debug_07.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_07.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,76 +1,76 @@
-<!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>Debugger Settings</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Run Mode On-Device Debugging</h2>
-<p>To implement run mode on-device debugging the following tasks need to be completed.</p>
-<ol>
- <li><a href="run_mode_debug.htm">Install device connection software</a></li>
- <li><a href="run_mode_debug_01.htm">Install Perl</a></li>
- <li><a href="run_mode_debug_02.htm">Install an SDK</a></li>
- <li><a href="run_mode_debug_03.htm">Setup environment variables</a></li>
- <li><a href="run_mode_debug_04.htm">Setup a virtual drive for Techview and Cust Kits</a></li>
- <li><a href="run_mode_debug_05.htm">Set the default kit in Devices.xml </a></li>
- <li><a href="run_mode_debug_06.htm">Install the SISX file on the target device</a></li>
- <li><b>Configure TRK connection on the device</b></li>
- <li><a href="run_mode_debug_08.htm">Create a launch configuration</a></li>
-</ol>
-<div class="step">
-<h4><a name="runConfig" id="runConfig"> </a>Configure TRK Connection on the Device</h4>
-<h5>Connecting with Bluetooth</h5>
- <ol>
- <li>On the device make sure the Bluetooth port is turned on</li>
- <li>On the phone launch TRK.</li>
- <p>The location of the TRK on-device debug agent will vary based on the phone. On some phones it will be in the Installed folder, on others it may be in the My Own folder.</p>
- <li>TRK will ask which host you want to pair with. When requested, select your computer from the available Bluetooth devices list.</li>
- <li>After the host and phone are paired, TRK should be connected. Verify that TRK is running.</li>
- <li>On the PC:
- <ol type="a">
- <li>Right click on the Bluetooth icon in the System tray and select Advanced Configuration</li>
- <li>Click the Local Services tab</li>
- <li>Write down the Bluetooth COM Port number from the Local Services tab (Figure 1).</li>
- <p>The Port number will be used when configuring the TRK launch configuration. The Bluetooth COM Port number in the Local Services tab should match the COM port used in the Connections tab of the TRK launch configuration.</p>
- <li>Click OK to close the Bluetooth Configuration window</li>
- <p align="center"><img src="images/Bluetooth_localservices.png" width="460" height="437" /></p>
- <p class="figure">Figure 1. Bluetooth Configuration window's Local Services panel</p>
- </ol>
- </li>
- </ol>
-<h5>Connecting with PC Suite</h5>
-
- <ol>
- <li>Connect the USB cable to the PC and then to the target device</li>
- <li>On the device select PC suite from the USB mode list</li>
- <li>Launch the TRK agent</li>
- <p>The location of the TRK on-device debug agent will vary based on the phone. On some phones it will be in the Installed folder, on others it may be in My Own folder.</p>
- <li>Halt the Bluetooth device search by pressing Cancel</li>
- <li>Click Options > Settings > Connection</li>
- <li>Change Connection type to USB and set connection options (Figure 2) </li>
- <li>Select Back and start the TRK again and you should be connected</li>
- <p align="center"><img src="images/TRK_USB_settings.png" width="211" height="250" /></p>
- <p class="figure">Figure 2. USB Connection Settings</p>
- <li>On the PC</li>
- <ol type="a">
- <li>Open Window's Computer Management by right-clicking My Computer and select Manage from the context menu to open the Computer Management window.</li>
- <li>Select System Tools > Device Manager > Ports (COM & LPT) to display all active ports</li>
- <li>Locate the S60 Phone USB (COMxx) item in the list</li>
-
- <p align="center"><img src="images/comp_manage_ports.png" width="507" height="546" /> </p>
- <p class="figure">Figure 3. Device Manager - Ports</p>
-
- <li>Write down the port ID and Communication Port Properties.</li>
- <p>The COM Port number in the Device Manager window should match the COM port used in the Connections tab of the TRK launch configuration.</p>
- <li>Close the Device Manager window </li>
- </ol>
- </ol>
- </div>
-<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>Debugger Settings</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Run Mode On-Device Debugging</h2>
+<p>To implement run mode on-device debugging the following tasks need to be completed.</p>
+<ol>
+ <li><a href="run_mode_debug.htm">Install device connection software</a></li>
+ <li><a href="run_mode_debug_01.htm">Install Perl</a></li>
+ <li><a href="run_mode_debug_02.htm">Install an SDK</a></li>
+ <li><a href="run_mode_debug_03.htm">Setup environment variables</a></li>
+ <li><a href="run_mode_debug_04.htm">Setup a virtual drive for Techview and Cust Kits</a></li>
+ <li><a href="run_mode_debug_05.htm">Set the default kit in Devices.xml </a></li>
+ <li><a href="run_mode_debug_06.htm">Install the SISX file on the target device</a></li>
+ <li><b>Configure TRK connection on the device</b></li>
+ <li><a href="run_mode_debug_08.htm">Create a launch configuration</a></li>
+</ol>
+<div class="step">
+<h4><a name="runConfig" id="runConfig"> </a>Configure TRK Connection on the Device</h4>
+<h5>Connecting with Bluetooth</h5>
+ <ol>
+ <li>On the device make sure the Bluetooth port is turned on</li>
+ <li>On the phone launch TRK.</li>
+ <p>The location of the TRK on-device debug agent will vary based on the phone. On some phones it will be in the Installed folder, on others it may be in the My Own folder.</p>
+ <li>TRK will ask which host you want to pair with. When requested, select your computer from the available Bluetooth devices list.</li>
+ <li>After the host and phone are paired, TRK should be connected. Verify that TRK is running.</li>
+ <li>On the PC:
+ <ol type="a">
+ <li>Right click on the Bluetooth icon in the System tray and select Advanced Configuration</li>
+ <li>Click the Local Services tab</li>
+ <li>Write down the Bluetooth COM Port number from the Local Services tab (Figure 1).</li>
+ <p>The Port number will be used when configuring the TRK launch configuration. The Bluetooth COM Port number in the Local Services tab should match the COM port used in the Connections tab of the TRK launch configuration.</p>
+ <li>Click OK to close the Bluetooth Configuration window</li>
+ <p align="center"><img src="images/Bluetooth_localservices.png" width="460" height="437" /></p>
+ <p class="figure">Figure 1. Bluetooth Configuration windows Local Services panel</p>
+ </ol>
+ </li>
+ </ol>
+<h5>Connecting with PC Suite</h5>
+
+ <ol>
+ <li>Connect the USB cable to the PC and then to the target device</li>
+ <li>On the device select PC suite from the USB mode list</li>
+ <li>Launch the TRK agent</li>
+ <p>The location of the TRK on-device debug agent will vary based on the phone. On some phones it will be in the Installed folder, on others it may be in My Own folder.</p>
+ <li>Halt the Bluetooth device search by pressing Cancel</li>
+ <li>Click Options > Settings > Connection</li>
+ <li>Change Connection type to USB and set connection options (Figure 2) </li>
+ <li>Select Back and start the TRK again and you should be connected</li>
+ <p align="center"><img src="images/TRK_USB_settings.png" width="211" height="250" /></p>
+ <p class="figure">Figure 2. USB Connection Settings</p>
+ <li>On the PC</li>
+ <ol type="a">
+ <li>Open Windows Computer Management by right-clicking My Computer and select Manage from the context menu to open the Computer Management window.</li>
+ <li>Select System Tools > Device Manager > Ports (COM & LPT) to display all active ports</li>
+ <li>Locate the S60 Phone USB (COMxx) item in the list</li>
+
+ <p align="center"><img src="images/comp_manage_ports.png" width="507" height="546" /> </p>
+ <p class="figure">Figure 3. Device Manager - Ports</p>
+
+ <li>Write down the port ID and Communication Port Properties.</li>
+ <p>The COM Port number in the Device Manager window should match the COM port used in the Connections tab of the TRK launch configuration.</p>
+ <li>Close the Device Manager window </li>
+ </ol>
+ </ol>
+ </div>
+<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/tasks/debugger/run_mode_debug_08.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,187 +1,187 @@
-<!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>Debugger Settings</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Run Mode On-Device Debugging</h2>
-<p>To implement run mode on-device debugging the following tasks need to be completed.</p>
-<ol>
- <li><a href="run_mode_debug.htm">Install device connection software</a></li>
- <li><a href="run_mode_debug_01.htm">Install Perl</a></li>
- <li><a href="run_mode_debug_02.htm">Install an SDK</a></li>
- <li><a href="run_mode_debug_03.htm">Setup environment variables</a></li>
- <li><a href="run_mode_debug_04.htm">Setup a virtual drive for Techview and Cust Kits</a></li>
- <li><a href="run_mode_debug_05.htm">Set the default kit in Devices.xml </a></li>
- <li><a href="run_mode_debug_06.htm">Install the SISX file on the target device</a></li>
- <li><a href="run_mode_debug_07.htm">Configure TRK connection on the device</a></li>
- <li><b>Create a launch configuration</b></li>
-</ol>
-<div class="step">
-<h4><a name="runLaunch" id="runLaunch"> </a>Creating a Launch Configuration setup</h4>
-<ol>
- <li>Import the MMP or INF file</li>
- <li>Select the Project in the C/C++ Project pane you want to debug</li>
- <li>From the IDE select Run > Debug…</li>
- <li>The <a href="../projects/wiz_new_launch_config.htm">New Launch Configuration Wizard</a> appears</li>
- <p>To communicate between the Carbide.c++ debugger and the on-device debug agent or protocol interface you must define a debug launch configuration. The Debug window is where you define the type of debug launch configuration to use when debugging programs on the target device (Figure 4).</p>
- <p><img src="images/Debug_Config_main.png" width="830" height="506" /></p>
- <p class="figure">Figure 4. Debug Window</p>
- <li>Select either a Symbian OS Application TRK or Symbian OS System TRK configuration type for on-device debugging and click New</li>
- <p>For debug launch configurations using the TRK debug agent, the following pages require review and possible option settings:</p>
- <ul>
- <li><b>Main</b> - defines the project to be launched on the target device</li>
- <li>Arguments (<i>Eclipse</i>) - defines the arguments to be passed to the application and to the virtual machine</li>
- <li><b>Debugger</b> - provides control over entry points, message handling, and instruction set default settings</li>
- <li><b>Connection</b> - specifies the method used to transfer files to the target device</li>
- <li><b>File Transfer</b> - files transfered to the target device at the start of each launch</li>
- <li><b>Installation</b> - specifies the .sis or .pkg file to install on the target device</li>
- <li>Executables - specifies which executables are debugged by your project</li>
- <li>Source (<i>Eclipse</i>) - defines the location of source files used to display source when debugging </li>
- <li>Common (<i>Eclipse</i>) - defines general information about the launch configuration</li>
- </ul>
- <p>Click Debug 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>
-</ol>
- <h5>Main Tab</h5>
- <p>The Main pane defines the project to be launched on the target device. Table 1 defines the fields.</p>
- <p align="center"><img src="images/Debug_Config_main_run.png" width="594" height="255" /></p>
- <p class="figure">Figure 5. 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><b>Project</b></td>
- <td><p>The project to associate with this debug launch configuration. Click Browse to select a different project. </p></td>
- </tr>
- <tr>
- <td><b>Remote process to launch</b></td>
- <td>The absolute path of the remote process to launch on the target device.</td>
- </tr>
- </table>
- </ol>
- <h5>Debugger Tab</h5>
- <p>The Debug or launch configuration window's Debugger pane provides control over entry points, message handling, and instruction set default settings.</p>
- <p align="center"><img src="images/Debug_Config_debugger_run.png" width="594" height="255" /></p>
- <p class="figure">Figure 6. Debug window's Debugger Pane </p>
- <p>Table 2. 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 E32Main. By default, the Break at entry point option is unchecked for all other target types.</p></td>
- </tr>
- <tr>
- <td><b>View program output </b></td>
- <td>When checked, show the contents of any unframed messages from the communications port in a Console view.</td>
- </tr>
- <tr>
- <td><b>View messages between Carbide and debug agent</b></td>
- <td><p>When checked, show the communications between the PC and the target device in a Console view when the TRK Communciation message log is visible.</p>
- <p class="note"><b>NOTE</b> You can pin the TRK Communication message 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 that the debugger should wait for a response. The default Message retry delay value is 2000.</td>
- </tr>
- <tr>
- <td><b>Default Instructon Set</b></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>
- Auto (examine code at current PC location)<br />
- ARM (32-bit)<br />
- THUMB (16-bit)<br />
- <br />
- By default the Instruction Set option uses ARM 32-bit.</td>
- </tr>
- </table>
-
- <h5>Connection Tab</h5>
- <p>Select the Connection tab that is available for TRK. Specify the Serial port for your configuration. The Connection pane specifies the method used to transfer files to the target device. Once the <b>Current Connection to Target</b> type is selected, the remaining options contain default values for the specific connection type. You can change these options to match the target device's communication specifications.</p>
- <p align="center"><img src="images/Debug_Config_connection_run.png" width="594" height="280" /></p>
- <p class="figure">Figure 7. Debug window's Connection pane using PC Suite</p>
- <p>Table 3. 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><b>Current Connection to Target </b></td>
- <td>Choose the connection type to use when communicating with a device. </td>
- </tr>
- <tr>
- <td><b>Serial Port</b></td>
- <td><p>Select the serial port option to use for the launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again.</p>
- <p class="note"><b>NOTE</b> USB and Bluetooth can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device.</p></td>
- </tr>
- <tr>
- <td><b>Baud Rate</b></td>
- <td>Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).</td>
- </tr>
- <tr>
- <td><b>Data Bits</b></td>
- <td><p>Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.</p> </td>
- </tr>
- <tr>
- <td><b>Parity</b></td>
- <td>Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.</td>
- </tr>
- <tr>
- <td><b>Stop Bits</b></td>
- <td><p>Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 2.</p> </td>
- </tr>
- <tr>
- <td><b>Flow Control</b></td>
- <td>Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.</td>
- </tr>
- </table>
- <h5>Installation Tab</h5>
- <p>For Application TRK select the Installation tab. The Installation pane specifies the .sis file to install on the target device. This is used by Application TRK because Application TRK downloads all files via a SIS file. This is required when using the TRK debug agent with 9.x based SDK’s.</p>
- <p align="center"><img src="images/Debug_Config_installation_run.png" width="595" height="280" /></p>
- <p class="figure">Figure 8. Debug window's Installation pane</p>
- <p>Table 4. Installation 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>Installation file </b></td>
- <td><p>Browse to and select the file to be installed.</p> </td>
- </tr>
- <tr>
- <td><b>Download directory </b></td>
- <td>Specify directory to receive download. </td>
- </tr>
- <tr>
- <td><b>Install each launch even if installer file has not changed </b></td>
- <td><p>Check this option to always install the .sis file. </p></td>
- </tr>
- <tr>
- <td><b>Do not show installer UI on the phone </b></td>
- <td>Check this option to hide the installer interface on the phone. </td>
- </tr>
- <tr>
- <td><b>Install to drive: </b></td>
- <td><p>Select drive on phone to install the .sis file. </p></td>
- </tr>
- </table>
- <h5>File Transfer Tab</h5>
- <p>For System TRK select the File Transfer pane. The File Transfer pane displays a list of files the Carbide IDE transfers to the target device at the start of each launch. By default, any file added is automatically checked for downloading to the device.</p>
- <p class="note"><b>NOTE</b> If debugging a DLL from an application and using System TRK, ensure that the DLL is included so that it is deployed to the device with the application. It is not added by default.</p>
- <p align="center"><img src="images/Debug_Config_filetransfer_run.png" width="595" height="280" /></p>
- <p class="figure">Figure 9. Debug window's File Transfer pane </p>
-</div>
-<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>Debugger Settings</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Run Mode On-Device Debugging</h2>
+<p>To implement run mode on-device debugging the following tasks need to be completed.</p>
+<ol>
+ <li><a href="run_mode_debug.htm">Install device connection software</a></li>
+ <li><a href="run_mode_debug_01.htm">Install Perl</a></li>
+ <li><a href="run_mode_debug_02.htm">Install an SDK</a></li>
+ <li><a href="run_mode_debug_03.htm">Setup environment variables</a></li>
+ <li><a href="run_mode_debug_04.htm">Setup a virtual drive for Techview and Cust Kits</a></li>
+ <li><a href="run_mode_debug_05.htm">Set the default kit in Devices.xml </a></li>
+ <li><a href="run_mode_debug_06.htm">Install the SISX file on the target device</a></li>
+ <li><a href="run_mode_debug_07.htm">Configure TRK connection on the device</a></li>
+ <li><b>Create a launch configuration</b></li>
+</ol>
+<div class="step">
+<h4><a name="runLaunch" id="runLaunch"> </a>Creating a Launch Configuration setup</h4>
+<ol>
+ <li>Import the MMP or INF file</li>
+ <li>Select the Project in the C/C++ Project pane you want to debug</li>
+ <li>From the IDE select Run > Debug…</li>
+ <li>The <a href="../projects/wiz_new_launch_config.htm">New Launch Configuration Wizard</a> appears</li>
+ <p>To communicate between the Carbide.c++ debugger and the on-device debug agent or protocol interface you must define a debug launch configuration. The Debug window is where you define the type of debug launch configuration to use when debugging programs on the target device (Figure 4).</p>
+ <p><img src="images/Debug_Config_main.png" width="830" height="506" /></p>
+ <p class="figure">Figure 4. Debug Window</p>
+ <li>Select either a Symbian OS Application TRK or Symbian OS System TRK configuration type for on-device debugging and click New</li>
+ <p>For debug launch configurations using the TRK debug agent, the following pages require review and possible option settings:</p>
+ <ul>
+ <li><b>Main</b> - defines the project to be launched on the target device</li>
+ <li>Arguments (<i>Eclipse</i>) - defines the arguments to be passed to the application and to the virtual machine</li>
+ <li><b>Debugger</b> - provides control over entry points, message handling, and instruction set default settings</li>
+ <li><b>Connection</b> - specifies the method used to transfer files to the target device</li>
+ <li><b>File Transfer</b> - files transfered to the target device at the start of each launch</li>
+ <li><b>Installation</b> - specifies the .sis or .pkg file to install on the target device</li>
+ <li>Executables - specifies which executables are debugged by your project</li>
+ <li>Source (<i>Eclipse</i>) - defines the location of source files used to display source when debugging </li>
+ <li>Common (<i>Eclipse</i>) - defines general information about the launch configuration</li>
+ </ul>
+ <p>Click Debug 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>
+</ol>
+ <h5>Main Tab</h5>
+ <p>The Main pane defines the project to be launched on the target device. Table 1 defines the fields.</p>
+ <p align="center"><img src="images/Debug_Config_main_run.png" width="594" height="255" /></p>
+ <p class="figure">Figure 5. 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><b>Project</b></td>
+ <td><p>The project to associate with this debug launch configuration. Click Browse to select a different project. </p></td>
+ </tr>
+ <tr>
+ <td><b>Remote process to launch</b></td>
+ <td>The absolute path of the remote process to launch on the target device.</td>
+ </tr>
+ </table>
+
+ <h5>Debugger Tab</h5>
+ <p>The Debug or launch configuration windows Debugger pane provides control over entry points, message handling, and instruction set default settings.</p>
+ <p align="center"><img src="images/Debug_Config_debugger_run.png" width="594" height="255" /></p>
+ <p class="figure">Figure 6. Debug windows Debugger Pane </p>
+ <p>Table 2. 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 E32Main. By default, the Break at entry point option is unchecked for all other target types.</p></td>
+ </tr>
+ <tr>
+ <td><b>View program output </b></td>
+ <td>When checked, show the contents of any unframed messages from the communications port in a Console view.</td>
+ </tr>
+ <tr>
+ <td><b>View messages between Carbide and debug agent</b></td>
+ <td><p>When checked, show the communications between the PC and the target device in a Console view when the TRK Communciation message log is visible.</p>
+ <p class="note"><b>NOTE</b> You can pin the TRK Communication message 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 that the debugger should wait for a response. The default Message retry delay value is 2000.</td>
+ </tr>
+ <tr>
+ <td><b>Default Instructon Set</b></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>
+ Auto (examine code at current PC location)<br />
+ ARM (32-bit)<br />
+ THUMB (16-bit)<br />
+ <br />
+ By default the Instruction Set option uses ARM 32-bit.</td>
+ </tr>
+ </table>
+
+ <h5>Connection Tab</h5>
+ <p>Select the Connection tab that is available for TRK. Specify the Serial port for your configuration. The Connection pane specifies the method used to transfer files to the target device. Once the <b>Current Connection to Target</b> type is selected, the remaining options contain default values for the specific connection type. You can change these options to match the target device's communication specifications.</p>
+ <p align="center"><img src="images/Debug_Config_connection_run.png" width="594" height="280" /></p>
+ <p class="figure">Figure 7. Debug windows Connection pane using PC Suite</p>
+ <p>Table 3. 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><b>Current Connection to Target </b></td>
+ <td>Choose the connection type to use when communicating with a device. </td>
+ </tr>
+ <tr>
+ <td><b>Serial Port</b></td>
+ <td><p>Select the serial port option to use for the launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again.</p>
+ <p class="note"><b>NOTE</b> USB and Bluetooth can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device.</p></td>
+ </tr>
+ <tr>
+ <td><b>Baud Rate</b></td>
+ <td>Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).</td>
+ </tr>
+ <tr>
+ <td><b>Data Bits</b></td>
+ <td><p>Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.</p> </td>
+ </tr>
+ <tr>
+ <td><b>Parity</b></td>
+ <td>Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.</td>
+ </tr>
+ <tr>
+ <td><b>Stop Bits</b></td>
+ <td><p>Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 2.</p> </td>
+ </tr>
+ <tr>
+ <td><b>Flow Control</b></td>
+ <td>Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.</td>
+ </tr>
+ </table>
+ <h5>Installation Tab</h5>
+ <p>For Application TRK select the Installation tab. The Installation pane specifies the .sis file to install on the target device. This is used by Application TRK because Application TRK downloads all files via a SIS file. This is required when using the TRK debug agent with 9.x based SDK’s.</p>
+ <p align="center"><img src="images/Debug_Config_installation_run.png" width="595" height="280" /></p>
+ <p class="figure">Figure 8. Debug windows Installation pane</p>
+ <p>Table 4. Installation 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>Installation file </b></td>
+ <td><p>Browse to and select the file to be installed.</p> </td>
+ </tr>
+ <tr>
+ <td><b>Download directory </b></td>
+ <td>Specify directory to receive download. </td>
+ </tr>
+ <tr>
+ <td><b>Install each launch even if installer file has not changed </b></td>
+ <td><p>Check this option to always install the .sis file. </p></td>
+ </tr>
+ <tr>
+ <td><b>Do not show installer UI on the phone </b></td>
+ <td>Check this option to hide the installer interface on the phone. </td>
+ </tr>
+ <tr>
+ <td><b>Install to drive: </b></td>
+ <td><p>Select drive on phone to install the .sis file. </p></td>
+ </tr>
+ </table>
+ <h5>File Transfer Tab</h5>
+ <p>For System TRK select the File Transfer pane. The File Transfer pane displays a list of files the Carbide IDE transfers to the target device at the start of each launch. By default, any file added is automatically checked for downloading to the device.</p>
+ <p class="note"><b>NOTE</b> If debugging a DLL from an application and using System TRK, ensure that the DLL is included so that it is deployed to the device with the application. It is not added by default.</p>
+ <p align="center"><img src="images/Debug_Config_filetransfer_run.png" width="595" height="280" /></p>
+ <p class="figure">Figure 9. Debug windows File Transfer pane </p>
+</div>
+<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/tasks/trk/trk_connection_bluetooth.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,53 +1,53 @@
-<!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>Bluetooth Connectivity Setup</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Bluetooth Connection Setup</h2>
-<p>The on-device debug agent software supports the use of Bluetooth to debug programs running on a target device. To enable communication with a Bluetooth device, a connection must be established between the PC and the device. The on-device debug agent requires a dedicated COM port in order to talk with the device. In some cases, other programs that use the same COM port number will interfere with the TRK debug agent, essentially "fighting" over control of the COM port. Follow the steps below to setup a Bluetooth connection with the Bluetooth enabled device. </p>
-<p class="note"><b>NOTE</b> Ensure that no other program has commandeered the Bluetooth connection. For example, some phone connectivity programs will not release a COM port unless specifically told to do so. </p>
-<p class="note"><b>NOTE</b> Most problems with on-target debugging setup occur here, so be careful when performing each of these steps.</p>
-<div class="step">
- <h4>Setting up a Bluetooth Connection for On-device Debugging </h4>
- <p class="note"><b>NOTE</b> This example shows how to setup a Bluetooth connection on a PC running Windows XP SP2 with an internal Bluetooth device. The actions to setup Bluetooth connections may be different on your version of Windows. Refer to the OS documentation for information on configuring Bluetooth connections. Ensure that the correct Bluetooth drivers are installed.</p>
- <ol>
- <li>Open the Bluetooth Configuration window (Start > Settings > Control Panel > Bluetooth Configuration)</li>
- <li>Verify the following settings in the Accessibility tab (Figure 1):
- <ul>
- <li>The option "Let other Bluetooth devices discover this computer" is checkmarked</li>
- <li>The option "Allow" is set to "All Devices" </li>
- </ul>
- </li>
- <p align="center"><img src="images/wnd_bluetooth_config.png" width="462" height="438" /></p>
- <p class="figure">Figure 1. Bluetooth Configuration window's Accessibility panel </p>
- <li>Write down the Bluetooth COM Port number from the Local Services tab (Figure 2) for later use</li>
- <p>The Bluetooth COM Port number in the Local Services tab
- should match the COM port used in the <a href="../../reference/launch_configs/page_connection.htm">Connections</a> tab of the TRK <a href="../../reference/launch_configs/run_mode_overview.htm">launch<br />
- configuration</a>.</p>
- <p align="center"><img src="images/wnd_bluetooth_config_services.png" width="460" height="437" /></p>
- <p class="figure">Figure 2. Bluetooth Configuration window's Local Services panel </p>
- <li>Click OK to close the Bluetooth Configuration window</li>
- <li>Download the Application TRK or System TRK SISX file to the device</li>
- </ol>
-</div>
- <h5>Related concepts</h5>
- <ul>
- <li><a href="../../concepts/trk.htm">On-device Debugging </a></li>
- </ul>
- <h5>Related references</h5>
- <ul>
- <li><a href="../../reference/launch_configs/run_mode_overview.htm">Debug Window (On-device Debugging) Overview</a></li>
- </ul>
- <h5>Related tasks</h5>
- <ul>
- <li><a href="trk_install_bluetooth.htm">Installing On-device Debug Agents using Bluetooth </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>Bluetooth Connectivity Setup</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Bluetooth Connection Setup</h2>
+<p>The on-device debug agent software supports the use of Bluetooth to debug programs running on a target device. To enable communication with a Bluetooth device, a connection must be established between the PC and the device. The on-device debug agent requires a dedicated COM port in order to talk with the device. In some cases, other programs that use the same COM port number will interfere with the TRK debug agent, essentially "fighting" over control of the COM port. Follow the steps below to setup a Bluetooth connection with the Bluetooth enabled device. </p>
+<p class="note"><b>NOTE</b> Ensure that no other program has commandeered the Bluetooth connection. For example, some phone connectivity programs will not release a COM port unless specifically told to do so. </p>
+<p class="note"><b>NOTE</b> Most problems with on-target debugging setup occur here, so be careful when performing each of these steps.</p>
+<div class="step">
+ <h4>Setting up a Bluetooth Connection for On-device Debugging </h4>
+ <p class="note"><b>NOTE</b> This example shows how to setup a Bluetooth connection on a PC running Windows XP SP2 with an internal Bluetooth device. The actions to setup Bluetooth connections may be different on your version of Windows. Refer to the OS documentation for information on configuring Bluetooth connections. Ensure that the correct Bluetooth drivers are installed.</p>
+ <ol>
+ <li>Open the Bluetooth Configuration window (Start > Settings > Control Panel > Bluetooth Configuration)</li>
+ <li>Verify the following settings in the Accessibility tab (Figure 1):
+ <ul>
+ <li>The option "Let other Bluetooth devices discover this computer" is checkmarked</li>
+ <li>The option "Allow" is set to "All Devices" </li>
+ </ul>
+ </li>
+ <p align="center"><img src="images/wnd_bluetooth_config.png" width="462" height="438" /></p>
+ <p class="figure">Figure 1. Bluetooth Configuration windows Accessibility panel </p>
+ <li>Write down the Bluetooth COM Port number from the Local Services tab (Figure 2) for later use</li>
+ <p>The Bluetooth COM Port number in the Local Services tab
+ should match the COM port used in the <a href="../../reference/launch_configs/page_connection.htm">Connections</a> tab of the TRK <a href="../../reference/launch_configs/run_mode_overview.htm">launch<br />
+ configuration</a>.</p>
+ <p align="center"><img src="images/wnd_bluetooth_config_services.png" width="460" height="437" /></p>
+ <p class="figure">Figure 2. Bluetooth Configuration windows Local Services panel </p>
+ <li>Click OK to close the Bluetooth Configuration window</li>
+ <li>Download the Application TRK or System TRK SISX file to the device</li>
+ </ol>
+</div>
+ <h5>Related concepts</h5>
+ <ul>
+ <li><a href="../../concepts/trk.htm">On-device Debugging </a></li>
+ </ul>
+ <h5>Related references</h5>
+ <ul>
+ <li><a href="../../reference/launch_configs/run_mode_overview.htm">Debug Window (On-device Debugging) Overview</a></li>
+ </ul>
+ <h5>Related tasks</h5>
+ <ul>
+ <li><a href="trk_install_bluetooth.htm">Installing On-device Debug Agents using Bluetooth </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/tasks/trk/trk_connection_usb.htm Mon Jun 29 16:00:45 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm Mon Jun 29 16:12:23 2009 -0500
@@ -1,55 +1,55 @@
-<!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>USB Connectivity Setup</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>USB Connection Setup</h2>
-<p>On-device debugging supports the use of USB to debug programs running on a target device. To enable communication with a USB device, a connection must be established between the PC and the device. Doing that requires one of the following USB connectivity cables to physically connect the PC to the device:</p>
-<ul>
- <li>DKU-2</li>
- <li>CA-53 </li>
-</ul>
-<div class="step">
- <h4>Setting up a USB Connection for On-device Debugging </h4>
- <ol>
- <li>Install the latest USB connectivity software, for example, S60 devices use Nokia PC Suite</li>
- <li>Connect the USB connectivity cable to your PC and then the target device</li>
- <li>For S60 devices, select PC-Suite from the USB Mode list when the target device is connected</li>
- <li>Download the Application TRK or System TRK SISX file to the device</li>
- <li>On the PC
- (optional)</li>
- </ol>
- <ol>
- <ol type="a">
- <li>Open the Window's Computer Management (Windows XP) </li>
- <p>Right-click <b>My Computer</b> and select <b>Manage</b> from the context menu to open the <b>Computer Management</b> window. Select <b>System Tools > Device Manager > Ports (COM & LPT)</b> to display all active ports. </p>
- <li>Locate the S60 Phone USB (COMx) item in the list (Figure 2) </li>
- <p align="center"><img src="../../reference/images/wnd_win_device_mgr.png" width="502" height="339" /></p>
- <p class="figure">Figure 2. Device Manager showing Ports (COM & LPT) section</p>
- <li>The USB COM Port number should match the COM port used in the <a href="../../reference/launch_configs/page_connection.htm">Connections</a> tab of the TRK launch
- configuration.</li>
- <li>Close the Device Manager window</li>
- </ol>
- </ol>
-</div>
-<h5>Related concepts</h5>
-<ul>
- <li><a href="../../concepts/trk.htm">On-device Debugging </a></li>
-</ul>
-<h5>Related references</h5>
-<ul>
- <li><a href="../../reference/launch_configs/run_mode_overview.htm">Debug Window (On-device Debugging) Overview</a></li>
-</ul>
-<h5>Related tasks</h5>
-<ul>
- <li><a href="trk_install_usb.htm">Installing On-device Debug Agents using USB</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>USB Connectivity Setup</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>USB Connection Setup</h2>
+<p>On-device debugging supports the use of USB to debug programs running on a target device. To enable communication with a USB device, a connection must be established between the PC and the device. Doing that requires one of the following USB connectivity cables to physically connect the PC to the device:</p>
+<ul>
+ <li>DKU-2</li>
+ <li>CA-53 </li>
+</ul>
+<div class="step">
+ <h4>Setting up a USB Connection for On-device Debugging </h4>
+ <ol>
+ <li>Install the latest USB connectivity software, for example, S60 devices use Nokia PC Suite</li>
+ <li>Connect the USB connectivity cable to your PC and then the target device</li>
+ <li>For S60 devices, select PC-Suite from the USB Mode list when the target device is connected</li>
+ <li>Download the Application TRK or System TRK SISX file to the device</li>
+ <li>On the PC
+ (optional)</li>
+ </ol>
+ <ol>
+ <ol type="a">
+ <li>Open the Windows Computer Management (Windows XP) </li>
+ <p>Right-click <b>My Computer</b> and select <b>Manage</b> from the context menu to open the <b>Computer Management</b> window. Select <b>System Tools > Device Manager > Ports (COM & LPT)</b> to display all active ports. </p>
+ <li>Locate the S60 Phone USB (COMx) item in the list (Figure 2) </li>
+ <p align="center"><img src="../../reference/images/wnd_win_device_mgr.png" width="502" height="339" /></p>
+ <p class="figure">Figure 2. Device Manager showing Ports (COM & LPT) section</p>
+ <li>The USB COM Port number should match the COM port used in the <a href="../../reference/launch_configs/page_connection.htm">Connections</a> tab of the TRK launch
+ configuration.</li>
+ <li>Close the Device Manager window</li>
+ </ol>
+ </ol>
+</div>
+<h5>Related concepts</h5>
+<ul>
+ <li><a href="../../concepts/trk.htm">On-device Debugging </a></li>
+</ul>
+<h5>Related references</h5>
+<ul>
+ <li><a href="../../reference/launch_configs/run_mode_overview.htm">Debug Window (On-device Debugging) Overview</a></li>
+</ul>
+<h5>Related tasks</h5>
+<ul>
+ <li><a href="trk_install_usb.htm">Installing On-device Debug Agents using USB</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>