Mercurial Mercurial > oss > FCL > sftools > dev > ide > carbidecpp / comparison
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | file | latest | revisions | annotate | diff | comparison | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm
branchRCL_2_4
changeset 817 41b05da1d19f
parent 0 fb279309251b
equal deleted inserted replaced
811:cc0961d7c88d 817:41b05da1d19f 
     3 <head>
 
     3 <head>
 
     4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 
     4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 
     5 <meta http-equiv="Content-Style-Type" content="text/css" />
 
     5 <meta http-equiv="Content-Style-Type" content="text/css" />
 
     6 <title>Stop Mode On-Device Debugging</title>
 
     6 <title>Stop Mode On-Device Debugging</title>
 
     7 <link rel="StyleSheet" href="../../../book.css" type="text/css"/>
 
     7 <link rel="StyleSheet" href="../../../book.css" type="text/css"/>
 
       
     8 <style type="text/css">
 
       
     9 <!--
 
       
    10 .style1 {font-size: 1em}
 
       
    11 -->
 
       
    12 </style>
 
     8 </head>
 
    13 </head>
 
     9 <body bgcolor="#FFFFFF" dir="ltr">
 
    14 <body bgcolor="#FFFFFF" dir="ltr">
 
    10 <h2> Defining a Stop Mode Debug Configuration</h2>
 
    15 <h2> Defining a Stop Mode Debug Configuration</h2>
 
    11 <p>After installing all necessary software such as Perl, JTAG, compilers, Devkits and SDKs and creating your project, you will need to define a Debug launch configuration for your project. For this example, we will define a Trace32 launch configuration. For new projects that do not have a launch configuration, a New Launch Configuration Wizard will appear and allow you to define settings. You can also cancel the wizard and define a launch configuration from the following instructions.</p>
 
    16 <p>After installing all necessary software such as Perl, JTAG, compilers, Devkits and SDKs and creating your project, you will need to define a Debug launch configuration for your project. For this example, we will define a Trace32 launch configuration. For new projects that do not have a launch configuration, a New Launch Configuration Wizard will appear and allow you to define settings. You can also cancel the wizard and define a launch configuration from the following instructions.</p>
 
    12 <div class="step">
 
    17 <div class="step">
 
    21           <li>In the Debug window, define the type of debug launch configuration to use when debugging programs on the target device.</li>
 
    26           <li>In the Debug window, define the type of debug launch configuration to use when debugging programs on the target device.</li>
 
    22       </ol>
 
    27       </ol>
 
    23   </li>
 
    28   </li>
 
    24     <p align="center"><img src="images/Debug_Config_window.png" width="704" height="455" /></p>
 
    29     <p align="center"><img src="images/Debug_Config_window.png" width="704" height="455" /></p>
 
    25     <p align="left" class="figure">Figure 1 - Debug Configurations</p>
 
    30     <p align="left" class="figure">Figure 1 - Debug Configurations</p>
 
    26     <p>Select either a Symbian OS Sophia or Symbian OS Trace32 configuration type for stop mode on-device debugging and click the New launch configuration icon. The following pages require review and possible option settings:</p>
 
    31     <p>Select either a Symbian OS Trace32 configuration type for stop mode on-device debugging and click the New launch configuration icon. The following pages require review and possible option settings:</p>
 
    27     <ul>
 
    32     <ul>
 
    28       <li> Main - defines the project to be launched on the target device</li>
 
    33       <li> Main - defines the project to be launched on the target device</li>
 
    29         <li>Connection - specifies the method used to transfer files to the target device</li>
 
    34         <li>Connection - specifies the method used to transfer files to the target device</li>
 
    30         <li> Debugger - provides control over entry points, message handling, and instruction set default settings</li>
 
    35         <li> Debugger - provides control over entry points, message handling, and instruction set default settings</li>
 
    31         <li> ROM Image- specifies startup options and ROM log and image files </li>
 
    36         <li> ROM Image- specifies startup options and ROM log and image files </li>
 
   111       <tr>
 
   116       <tr>
 
   112         <td><b>Target Processor </b></td>
 
   117         <td><b>Target Processor </b></td>
 
   113         <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>
 
   118         <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>
 
   114       </tr>
 
   119       </tr>
 
   115       <tr>
 
   120       <tr>
 
   116         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   121         <td>
 
   117             <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Target Initialization File</b></font></font></p></td>
 
   122           <span class="style1">
 
       
   123           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   124           </span>
 
       
   125         <p class="style1"><font face="Georgia, serif"><b>Target Initialization File</b></font></p></td>
 
   118         <td><p>Check this box to have the debugger run an initialization script when the debug session starts. For example, if a target device requires initialization for the debugger to be able to read and write memory or registers, you can specify an initialization script here. Click Browse to select a script file using a standard file selection dialog box.</p>
 
   126         <td><p>Check this box to have the debugger run an initialization script when the debug session starts. For example, if a target device requires initialization for the debugger to be able to read and write memory or registers, you can specify an initialization script here. Click Browse to select a script file using a standard file selection dialog box.</p>
 
   119             <p>When using T32, most of the initialization is done in the CMM script file. With other debug protocols like Sophia, you can specify the initialization file, which can be run after connecting to the target.</p></td>
 
   127             <p>When using T32, most of the initialization is done in the CMM script file. With other debug protocols you  specify the initialization file, which can be run after connecting to the target.</p></td>
 
   120       </tr>
 
   128       </tr>
 
   121       <tr>
 
   129       <tr>
 
   122         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   130         <td>
 
   123             <p><b><font size="2" style="font-size: 9pt"><font face="Georgia, serif">Memory Configuration File</font></font></b></p></td>
 
   131           <span class="style1">
 
       
   132           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   133           </span>
 
       
   134         <p class="style1"><b><font face="Georgia, serif">Memory Configuration File</font></b></p></td>
 
   124         <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>
 
   135         <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>
 
   125       </tr>
 
   136       </tr>
 
   126       <tr>
 
   137       <tr>
 
   127         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   138         <td>
 
   128             <p><b><font size="2" style="font-size: 9pt"><font face="Georgia, serif">Reset target at the start of each debug session</font></font></b></p></td>
 
   139           <span class="style1">
 
       
   140           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   141           </span>
 
       
   142         <p class="style1"><b><font face="Georgia, serif">Reset target at the start of each debug session</font></b></p></td>
 
   129         <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>
 
   143         <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>
 
   130       </tr>
 
   144       </tr>
 
   131       <tr>
 
   145       <tr>
 
   132         <td><p><b>Default Instructon Set </b></p></td>
 
   146         <td><p><b>Default Instructon Set </b></p></td>
 
   133         <td><p>Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. This can happen at addresses for which we have no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code. The options are:</p>
 
   147         <td><p>Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. This can happen at addresses for which we have no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code. The options are:</p>
 
   148       <tr>
 
   162       <tr>
 
   149         <th width="38%" scope="col">Item</th>
 
   163         <th width="38%" scope="col">Item</th>
 
   150         <th width="62%" scope="col">Explanation</th>
 
   164         <th width="62%" scope="col">Explanation</th>
 
   151       </tr>
 
   165       </tr>
 
   152       <tr>
 
   166       <tr>
 
   153         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   167         <td><span class="style1">
 
   154           <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   168           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   155             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   169           </span>
 
   156             </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Start Address</b></font></font></p></td>
 
   170           <p class="style1"><font face="Georgia, serif">
 
       
   171             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   172             <b>Start Address</b></font></p></td>
 
   157         <td><p>Enter the physical address in memory where the Symbian OS start code begins execution. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x8000000 is a valid entry.</p>
 
   173         <td><p>Enter the physical address in memory where the Symbian OS start code begins execution. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x8000000 is a valid entry.</p>
 
   158           <p class="note"><b>NOTE</b> The address entered in this field must match the start address specified in the source code used to build the Symbian OS ROM image to be debugged. The Start address must match the Download address.</p></td>
 
   174           <p class="note"><b>NOTE</b> The address entered in this field must match the start address specified in the source code used to build the Symbian OS ROM image to be debugged. The Start address must match the Download address.</p></td>
 
   159       </tr>
 
   175       </tr>
 
   160       <tr>
 
   176       <tr>
 
   161         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   177         <td><span class="style1">
 
   162           <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   178           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   163             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   179           </span>
 
   164             </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Debug from Start address</b></font></font></p></td>
 
   180           <p class="style1"><font face="Georgia, serif">
 
       
   181             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   182             <b>Debug from Start address</b></font></p></td>
 
   165         <td>Select this option to have the debugger halt the program at the address specified in Start Address once the target initialization is done and the OS is downloaded; if the user has chosen to download the OS. You can then step through start-up code or run the target in bare-board mode.</td>
 
   183         <td>Select this option to have the debugger halt the program at the address specified in Start Address once the target initialization is done and the OS is downloaded; if the user has chosen to download the OS. You can then step through start-up code or run the target in bare-board mode.</td>
 
   166       </tr>
 
   184       </tr>
 
   167       <tr>
 
   185       <tr>
 
   168         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   186         <td><span class="style1">
 
   169           <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   187           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   170             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   188           </span>
 
   171             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   189           <p class="style1"><font face="Georgia, serif">
 
   172             </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Run from start address</b></font></font></p></td>
 
   190             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   191             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   192             <b>Run from start address</b></font></p></td>
 
   173         <td>Select this option to have the debugger start the code at the address specified in Start Address once the target initialization is done. If you have breakpoints set, the debugger stops at the first breakpoint encountered. You can click the Break button to halt the device.</td>
 
   193         <td>Select this option to have the debugger start the code at the address specified in Start Address once the target initialization is done. If you have breakpoints set, the debugger stops at the first breakpoint encountered. You can click the Break button to halt the device.</td>
 
   174       </tr>
 
   194       </tr>
 
   175       <tr>
 
   195       <tr>
 
   176         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   196         <td><span class="style1">
 
   177             <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   197           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   178               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   198             </span>
 
   179               </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   199           <p class="style1"><font face="Georgia, serif">
 
   180               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   200               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   181           </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Symbian ROM Log file</b></font></font></p></td>
 
   201               
       
   202             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   203             <b>Symbian ROM Log file</b></font></p></td>
 
   182         <td>Check the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images. In the first text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.</td>
 
   204         <td>Check the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images. In the first text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.</td>
 
   183       </tr>
 
   205       </tr>
 
   184       <tr>
 
   206       <tr>
 
   185         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   207         <td><span class="style1">
 
   186             <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   208           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   187               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   209             </span>
 
   188               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   210           <p class="style1"><font face="Georgia, serif">
 
   189               <b>Symbian OS Kit EPOC32 Directory</b></font></font></p></td>
 
   211               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   212               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   213               <b>Symbian OS Kit EPOC32 Directory</b></font></p></td>
 
   190         <td class="note"><p>Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory.</p>
 
   214         <td class="note"><p>Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory.</p>
 
   191             <p class="note"><b>NOTE</b> Always include the epoc32 folder in this path.</p></td>
 
   215             <p class="note"><b>NOTE</b> Always include the epoc32 folder in this path.</p></td>
 
   192       </tr>
 
   216       </tr>
 
   193       <tr>
 
   217       <tr>
 
   194         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   218         <td><span class="style1">
 
   195             <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   219           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   196               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   220             </span>
 
   197               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   221           <p class="style1"><font face="Georgia, serif">
 
   198               </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   222               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   199               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   223               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   200           </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Log unresolved modules</b></font></font></p></td>
 
   224               
       
   225             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   226             <b>Log unresolved modules</b></font></p></td>
 
   201         <td class="note"><p>Check this box to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session.</p>
 
   227         <td class="note"><p>Check this box to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session.</p>
 
   202             <p class="note"><b>NOTE</b> You cannot perform source-level debugging on components that do not include symbolic information.</p></td>
 
   228             <p class="note"><b>NOTE</b> You cannot perform source-level debugging on components that do not include symbolic information.</p></td>
 
   203       </tr>
 
   229       </tr>
 
   204       <tr>
 
   230       <tr>
 
   205         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   231         <td><span class="style1">
 
   206             <p><b><font size="2" style="font-size: 9pt">
 
   232           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   207               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   233             </span>
 
   208               </font></b><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   234           <p class="style1"><b>
 
   209               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   235               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   210               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   236               </b><font face="Georgia, serif">
 
   211               <b>Debug non-XIP Executables</b></font></font></p></td>
 
   237               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   238               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   239               <b>Debug non-XIP Executables</b></font></p></td>
 
   212         <td><p>Check this box to debug a project, or a dynamically loaded module, that is loaded from NAND-Flash or other removable media (MMC, memory stick, etc.) at run time and executed in RAM. Use this option to debug modules that work fine when executed in place as part of the ROM image, but sometimes fail when placed in NAND-Flash or other removable media.</p>
 
   240         <td><p>Check this box to debug a project, or a dynamically loaded module, that is loaded from NAND-Flash or other removable media (MMC, memory stick, etc.) at run time and executed in RAM. Use this option to debug modules that work fine when executed in place as part of the ROM image, but sometimes fail when placed in NAND-Flash or other removable media.</p>
 
   213             <p class="note"> <b>NOTE</b> Selecting this option will affect debugging performance. When the debugger needs to load a module (DLL, EXE, etc.) it will stop the target, read information from it, then restart it.</p></td>
 
   241             <p class="note"> <b>NOTE</b> Selecting this option will affect debugging performance. When the debugger needs to load a module (DLL, EXE, etc.) it will stop the target, read information from it, then restart it.</p></td>
 
   214       </tr>
 
   242       </tr>
 
   215       <tr>
 
   243       <tr>
 
   216         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   244         <td><span class="style1">
 
   217           <p><b><font size="2" style="font-size: 9pt">
 
   245           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   218             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   246           </span>
 
   219             </font></b><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
   247           <p class="style1"><b>
 
   220             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   248             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   221             </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Symbian ROM Image</b></font></font></p></td>
 
   249             </b><font face="Georgia, serif">
 
       
   250             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   251             <b>Symbian ROM Image</b></font></p></td>
 
   222         <td>Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window.</td>
 
   252         <td>Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window.</td>
 
   223       </tr>
 
   253       </tr>
 
   224       <tr>
 
   254       <tr>
 
   225         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   255         <td><span class="style1">
 
   226           <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Download Address (hex) </b></font></font></p></td>
 
   256           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   257           </span>
 
       
   258           <p class="style1"><font face="Georgia, serif"><b>Download Address (hex) </b></font></p></td>
 
   227         <td><p>Enter the physical address in memory at which the debugger should place the ROM image. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x000FFF00 is a valid entry.</p>
 
   259         <td><p>Enter the physical address in memory at which the debugger should place the ROM image. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x000FFF00 is a valid entry.</p>
 
   228           <p class="note"> <b>NOTE</b> The address entered in this field must match the download address specified in the source code used to build the Symbian OS ROM image to be debugged. If you leave this field blank, the debugger does not download the ROM image to the device at the beginning of the debug session. The Download address must match the Start address.</p></td>
 
   260           <p class="note"> <b>NOTE</b> The address entered in this field must match the download address specified in the source code used to build the Symbian OS ROM image to be debugged. If you leave this field blank, the debugger does not download the ROM image to the device at the beginning of the debug session. The Download address must match the Start address.</p></td>
 
   229       </tr>
 
   261       </tr>
 
   230       <tr>
 
   262       <tr>
 
   231         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
   263         <td><span class="style1">
 
   232           <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Ask for download at the start of each debug session</b></font></font></p></td>
 
   264           <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   265           </span>
 
       
   266           <p class="style1"><font face="Georgia, serif"><b>Ask for download at the start of each debug session</b></font></p></td>
 
   233         <td>Check this box to have the debugger display a dialog box at the beginning of every debug session that lets you choose whether or not you want the debugger to download the ROM image to the device.</td>
 
   267         <td>Check this box to have the debugger display a dialog box at the beginning of every debug session that lets you choose whether or not you want the debugger to download the ROM image to the device.</td>
 
   234       </tr>
 
   268       </tr>
 
   235     </table>
 
   269     </table>
 
   236     <p>&nbsp;</p>
 
       
   237   </ol>
 
   270   </ol>
 
   238     <h3>Sophia Target Interface Connection</h3>
 
       
   239     <p>The following Connection pane is specific to the Sophia Target Interface and is shown in a Sophia Launch Configuration only. Other panes are same as Trace32 panes.</p>
 
       
   240     <p align="center"><img src="images/Debug_Config_sophia.png" width="819" height="305" /></p>
 
       
   241     <p class="figure">Figure 6 - Sophia Connection Window</p>
 
       
   242     <p>Table 5 -  Sophia Connection Window</p>
 
       
   243     <table width="94%"  border="0" cellpadding="2" cellspacing="0">
 
       
   244       <tr>
 
       
   245         <th width="38%" scope="col">Item</th>
 
       
   246         <th width="62%" scope="col">Explanation</th>
 
       
   247       </tr>
 
       
   248       <tr>
 
       
   249         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   250           <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
       
   251             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   252             </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
       
   253             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   254             </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
       
   255             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   256             </font></font><font face="Georgia, serif"><font size="2" style="font-size: 9pt"><b>Sophia Target Interface (WTI.dll) location</b></font></font></p></td>
 
       
   257         <td>Specifies the location of a Sophia dll that the debugger will load and interface with in order to communicate with the Sophia JTAG interface. The preference panel will try to determine this value from the registry or some other means and auto fill it when possible.</td>
 
       
   258       </tr>
 
       
   259       <tr>
 
       
   260         <td><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   261           <p><font face="Georgia, serif"><font size="2" style="font-size: 9pt">
 
       
   262             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   263             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   264             <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 
       
   265             <b>EJ_Debug Type </b></font></font></p></td>
 
       
   266         <td><p>Sophia Systems' EJ-Debug is a compact, USB-powered JTAG emulator. Select the EJ_Debug type. Options include:</p>
 
       
   267           <ul>
 
       
   268             <li>Auto (automatically detects target CPU) </li>
 
       
   269             <li>ARM9 (target CPU) </li>
 
       
   270             <li>ARM11 (target CPU)</li>
 
       
   271             <li>ARM9_11 (target CPU)</li>
 
       
   272             <li>ARM7_9_11 (target CPU)</li>
 
       
   273         </ul></td>
 
       
   274       </tr>
 
       
   275       <tr>
 
       
   276         <td><b>JTAG TCLK Frequency</b></td>
 
       
   277         <td>Select the JTAG TCLK frequency. Options include:
 
       
   278           <ul>
 
       
   279             <li>Auto</li>
 
       
   280             <li>33 MHz</li>
 
       
   281             <li>16 MHz</li>
 
       
   282             <li>8 MHz</li>
 
       
   283             <li>500 KHz </li>
 
       
   284         </ul></td>
 
       
   285       </tr>
 
       
   286       <tr>
 
       
   287         <td><b>View messages between Carbide and STI</b></td>
 
       
   288         <td>The View Messages between Carbide and STI check box allows you to specify if the debug protocol messages between Carbide and STI should be logged in a Communication Log console window.</td>
 
       
   289       </tr>
 
       
   290     </table>
 
       
   291 
       
   292 </div>
 
   271 </div>
 
   293 <h5>Related Tasks</h5>
 
   272 <h5>Related Tasks</h5>
 
   294 <ul>
 
   273 <ul>
 
   295   <li><a href="stop_mode_debug_precond.htm">Stop Mode On-Device Debugging Preconditions</a></li>
 
   274   <li><a href="stop_mode_debug_precond.htm">Stop Mode On-Device Debugging Preconditions</a></li>
 
   296 </ul>
 
   275 </ul>
 
   297 
   276 
   298 <div id="footer">Copyright &copy; 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>
 
   277 <div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 
   299 
   278 
   300 </body>
 
   279 </body>
 
   301 </html>
 
   280 </html>
FCL/sftools/dev/ide/carbidecpp