# HG changeset patch # User fturovic # Date 1264534916 21600 # Node ID 8121a281245cc1f42ffe6be46ed9fb413b758255 # Parent d0f3375bb257e17c45096b25b680f4dc5bb7384a BUG 10603 - removed sophia text references from 3.0 diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/book.css --- a/core/com.nokia.carbide.cpp.doc.user/book.css Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/book.css Tue Jan 26 13:41:56 2010 -0600 @@ -5,30 +5,29 @@ */ /* Add whitespace around entire display to avoid crowding edges of view */ -/* 20070523-Removed top margin size to close gap between location breadcrumbs and page title */ html { margin: 2px 10px 10px 10px; } -/* Set default font to serif style, 12-pt and plain */ +/* 20091007 added verdana and ariel to list to match SFO website fonts choices */ body, p, table { - font-family: Verdana, Helvetica, sans-serif; - font-size: 13px; + font-family: Verdana, Ariel, Helvetica, sans-serif; + font-size: 1.0em; font-weight: normal; } -/* Use sans-serif fonts for all title styles */ h1, h2, h3, h4, h5, h6, strong, em { - font-family: Verdana, Helvetica, sans-serif; + font-family: Verdana, Ariel, Helvetica, sans-serif; color: #000000; } -h1 { font-size:20px } -h2 { font-size:18px } -h3 { font-size:16px } -h4 { font-size:14px } -h5 { font-size:13px } -h6 { font-size:12px } +/* 20091007 - changed sizes to use em versus px */ +h1 { font-size: 1.3em } +h2 { font-size: 1.2em } +h3 { font-size: 1.1em } +h4 { font-size: 1.0em } +h5 { font-size: 0.9em } +h6 { font-size: 0.8em } /* For headlines at the top of a view, add space */ /* 20090224-changed green fade to gold header image */ @@ -38,6 +37,10 @@ padding:10px 0px 10px 12px; } +/* 20091007 SFO styling added */ +h1.NavTitle { font-size: 1.2em } +h3 .NavListTitle { font-size: 1.1em } + li { margin-bottom:8px; margin-top:8px; @@ -48,21 +51,22 @@ padding-top:10px; margin-top:20px; border-top:1px solid #999; - font-family: Verdana, Helvetica, sans-serif; - font-size: 11px; - color:#333; + font-family: Verdana, Ariel, Helvetica, sans-serif; + font-size: 0.8em; + color: #333333; } .listing { + background-color: #ffe869; font-family: "Courier New", Courier, mono; + font-size: 1.1em; color: #000000; - background-color: #FFFFCC; margin: 5px 0px; } .code, pre { font-family: "Courier New", Courier, mono; - font-size: 13px; + font-size: 1.1em; color: #000000; } @@ -88,7 +92,6 @@ table { border: solid #999 1px; table-layout: auto; - font-size: 13px; } td, th { @@ -97,11 +100,8 @@ vertical-align:top; } -/* 20070522-replaced gray with green background to match gradiant color for title */ th { - background-color:#FFC550; /* background-color:#acd79b; - background-color:#999; - color:#FFF; */ + background-color: #ffd62c; } div.ol.p { @@ -118,11 +118,9 @@ font-weight:normal; } -/* Make all H4 and H5 items appear in bold gray against a light green background */ div h5, div h4 { padding:5px 0px 5px 12px; - background-color:#FDCB2F; - /* background-color: #EEE; */ + background-color: #ffd62c; font-weight:bold; color: #000000; } @@ -130,8 +128,6 @@ /* Notes stand out using a light top & bottom borders with dark gray text */ p.note { - /* color: #03C; */ - /* background-color: #FFFF99; */ color: #333; padding: 5px; margin-left: 1em; @@ -143,11 +139,12 @@ /* Figure/Listing/Table titles are centered and gray */ p.figure { - color: #333; + color: #026690; text-align: center; font-weight: bold; } + /* highly visible red background and white text for things that need fixing before release */ /* SHOULD NOT BE PRESENT IN RELEASED PRODUCTS */ .fix { @@ -163,14 +160,14 @@ } .titleSmall { - font-family: Helvetica, sans-serif; - font-size: 11px; + font-family: Verdana, Ariel, Helvetica, sans-serif; + font-size: 0.8em; } .plain { - font-family: Helvetica, sans-serif; - font-size: 12px; + font-family: Verdana, Ariel, Helvetica, sans-serif; + font-size: 0.9em; font-style: normal; line-height: normal; font-weight: normal; @@ -179,6 +176,6 @@ text-decoration: none; } -a:link { color: #0033CC } +a:link { color: #026690 } a:visited { color: #555555 } -a:hover { color: #0033CC } +a:hover { color: #FFD62C } diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Jan 26 13:41:56 2010 -0600 @@ -16,11 +16,28 @@

Carbide.c++ bugs fixed

This is a comprehensive list of bugs fixed by release:

-

Bugs Fixed in v2.2.0

+

Bugs Fixed in v2.5.0

+ +

Bugs Fixed in v2.4.0

+ +

Bugs Fixed in v2.3.0

+ +

Bugs Fixed in v2.2.0

- + \ No newline at end of file diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/cheatsheets/stop_mode_cs.xml --- a/core/com.nokia.carbide.cpp.doc.user/html/cheatsheets/stop_mode_cs.xml Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/cheatsheets/stop_mode_cs.xml Tue Jan 26 13:41:56 2010 -0600 @@ -1,22 +1,22 @@ - - - - - - Follow these steps to install on-device stop mode debug software and compilers, create ROM images, and define launch configurations. - - - - - - Before you begin stop mode debugging, make sure all preconditions are met. - - - - - - Define debug launch configurations for the selected project. - - - - + + + + + + Follow these steps to install on-device stop mode debug software and compilers, create ROM images, and define launch configurations. + + + + + + Before you begin stop mode debugging, make sure all preconditions are met. + + + + + + Define debug launch configurations for the selected project. + + + + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/context_help/carbide_debug_dialogs_help.xml --- a/core/com.nokia.carbide.cpp.doc.user/html/context_help/carbide_debug_dialogs_help.xml Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/context_help/carbide_debug_dialogs_help.xml Tue Jan 26 13:41:56 2010 -0600 @@ -237,15 +237,6 @@ - - - Specify the settings for Sophia debugging. - - - - - - Specify the ROM image details. @@ -287,12 +278,6 @@ - - Specify Sophia configuration information. - - - - Specify Trace32 configuration information. diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/context_help/eclipse_dialogs_help.xml --- a/core/com.nokia.carbide.cpp.doc.user/html/context_help/eclipse_dialogs_help.xml Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/context_help/eclipse_dialogs_help.xml Tue Jan 26 13:41:56 2010 -0600 @@ -1,376 +1,370 @@ - - - - - - - - - - - - - - - - - - - - - - The Debug view shows the target debugging information in a tree hierarchy. - - - - - - - - - Use the Variables view to manipulate the variables or variable hierarchy used in source code. - - - - - - - - - - Use the Breakpoints view to examine, enable or disable the breakpoints in one or more build configurations. - - - - - - - - - Use the Expressions view to monitor and manipulate variables, structures, and arrays. - - - - - - - - - - - - - Use the Registers view to view general, FPU, and host-specific registers of the host computer, not the target device. - - - - - - - - - - - Use the Memory view to inspect and change process memory. - - - - - - - - - Specify where the debugger should look for source files. - - - - - - Specify where the debugger should store the debug configuration. - - - - - Select a launch type to create a launch configuration. - - - - - - - - Review launch configuration information. - - - - - - Specify Sophia configuration information. - - - - - - Specify Trace32 configuration information. - - - - - - Specify TRK connection information. - - - - - Specify ROM image information. - - - - - - Specify SIS information. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use the Debug or Run panels to create launch configurations for your applications. - - - - - - - - - - Use the environment pane to add or remove environment variables. - - - - - - - - - - - - - - - - - - - - - Select the project, class, or file to create. - - - - - - - - - - Select the type of file to import for debugging. - - - - - - - - Import an executable for debugging. - - - - - - - - Use the Console view to show the output of a process and provide keyboard input to a process. - - - - - - - - - - - - - - - - - Use the Console view to show the output of a process and provide keyboard input to a process. - - - - - - - - - - - - - - Select the project type to create. - - - - - - - - - - - Configuration details of this Carbide.c++ installation. May include useful information that should be included with a bug report. - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + The Debug view shows the target debugging information in a tree hierarchy. + + + + + + + + + Use the Variables view to manipulate the variables or variable hierarchy used in source code. + + + + + + + + + + Use the Breakpoints view to examine, enable or disable the breakpoints in one or more build configurations. + + + + + + + + + Use the Expressions view to monitor and manipulate variables, structures, and arrays. + + + + + + + + + + + + + Use the Registers view to view general, FPU, and host-specific registers of the host computer, not the target device. + + + + + + + + + + + Use the Memory view to inspect and change process memory. + + + + + + + + + Specify where the debugger should look for source files. + + + + + + Specify where the debugger should store the debug configuration. + + + + + Select a launch type to create a launch configuration. + + + + + + + + Review launch configuration information. + + + + + + Specify Trace32 configuration information. + + + + + + Specify TRK connection information. + + + + + Specify ROM image information. + + + + + + Specify SIS information. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Use the Debug or Run panels to create launch configurations for your applications. + + + + + + + + + + Use the environment pane to add or remove environment variables. + + + + + + + + + + + + + + + + + + + + + Select the project, class, or file to create. + + + + + + + + + + Select the type of file to import for debugging. + + + + + + + + Import an executable for debugging. + + + + + + + + Use the Console view to show the output of a process and provide keyboard input to a process. + + + + + + + + + + + + + + + + + Use the Console view to show the output of a process and provide keyboard input to a process. + + + + + + + + + + + + + + Select the project type to create. + + + + + + + + + + + Configuration details of this Carbide.c++ installation. May include useful information that should be included with a bug report. + + + + + + + + + + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger.htm Tue Jan 26 13:41:56 2010 -0600 @@ -19,13 +19,13 @@

 

 

 

-

Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
+

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html

Carbide.c++ User Guide

-

Version 2.2.0, August, 2009

+

Version 2.5.0, Jan, 2010

 

diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/breakpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/breakpoints.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/breakpoints.htm Tue Jan 26 13:41:56 2010 -0600 @@ -4,31 +4,63 @@ -Breakpoints Overview - +Breakpoints + -

Breakpoints Overview

-

A breakpoint is a marker set on a specific line of source code and is designed to suspend program execution. Breakpoints are shown in the UI both with the associated source code in an editor view as well as a dedicated Breakpoints view.

-

When a breakpoint is encountered during program execution, the debugger suspends execution and the Debug perspective appears so you can examine the executable's current state, check register and variable values, and use the stepping commands to walk line by line through the program to verify its operation. You can also change values and alter the flow of normal program execution. Setting breakpoints helps you debug your program and verify its efficiency.

-

The following topics cover various breakpoint concepts and actions:

+

Breakpoints

+

A breakpoint is a marker set on a specific line of source code and is designed to halt program execution when encountered by the debugger. After you set a breakpoint at a key point in the program, you can halt its execution, examine its current state, and check register and variable values. You can also change values and alter the flow of normal program execution. Setting breakpoints helps you debug your program and verify its efficiency.

+

A project can have multiple breakpoints set in the source code files. All breakpoints in a project are shown in the Breakpoints view. Breakpoints are enabled or disabled on the currently selected line within a source code editor by selecting the Run > Toggle Breakpoint menu option, right-clicking the marker bar in the editor and selecting Toggle Breakpoint, or by pressing CTRL-SHIFT-B.

+

You can set a breakpoint on any executable line of code that the debugger can resolve. Lines containing comments and other non executable code cannot be assigned a breakpoint as they are normally stripped from the compiled binary. The debugger must load the symbols for a module before it can attempt to resolve breakpoints within the module. This is most easily done using the Executables view to import a binary file, especially if the binary is not in the workspace.

+

When the debugger attempts to resolve a breakpoint it will result in:

-

Other references

+

Breakpoints have enabled and disabled types as well as resolved and unresolved states. Table 1 explains the different breakpoint types and states.

+
Table 1 Breakpoint—type and states
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeStateIconExplanation
Enabled
Unresolved
Indicates that the breakpoint is currently enabled but not located in the executable during a debug session. Debugger cannot halt program execution.
Enabled
Resolved
Indicates that the breakpoint is currently enabled and resolved for the source line. The debugger halts program execution at an enabled breakpoint.
Disabled
Unresolved
Indicates that the breakpoint is currently disabled but not located in the executable during a debug session. The debugger does not halt program execution at a disabled breakpoint.
Disabled
Resolved
Indicates that the breakpoint is currently disabled and resolved for the source line. The debugger does not halt program execution at a disabled breakpoint.
+

Other references

+ diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm Tue Jan 26 13:41:56 2010 -0600 @@ -5,20 +5,113 @@ Watchpoints Overview - +

Watchpoints Overview

-

A watchpoint is a marker set on a specific memory location which is designed to suspend program execution when the value at that location changes. Watchpoints are closely related to breakpoints and are shown in the Breakpoints view.

-

When a watchpoint is encountered during program execution, the debugger suspends execution and the Debug perspective appears so you can examine the executable's current state, check register and variable values, and use the stepping commands to walk line by line through the program to verify its operation. You can also change values and alter the flow of normal program execution. Setting watchpoints helps you debug your program and verify its efficiency.

-

The following topics cover various breakpoint concepts and actions:

+

Use watchpoints (sometimes referred to as access breakpoints) to halt program execution when a specific global location is accessed. After you set a watchpoint at a key point in memory, you can halt program execution whenever that point in memory is written to or read from. You can then examine the call chain, check register and variable values, and step through your code. You can also change values and alter the flow of normal program execution.

+

A watchpoint must be both enabled and resolved during a debug session in order to halt program execution. The Breakpoints view indicates the status of any watchpoint using a set of common icons and checkmark status badge. These include:

+
    +
  • An enabled watchpoint has a non-gray icon () indicating that program execution halts when encountered.
    • +
  • A disabled watchpoint displays a gray icon () indicating that program execution will not stop when encountered.
    • +
  • A resolved watchpoint has a small checkmark badge ( ) indicating that the debugger has located it in memory during program launch. When resolved, the debugger can halt program execution if the watchpoint is encountered.
    • +
+

In effect, a watchpoint that is enabled by the user and resolved by the debugger during program launch can halt program execution. The table below shows the various states that cause the debugger to halt program execution:

+
Table 1 Watchpoint—stop execution chart
+ + + + + + + + + + + + + + + + +
Watchpoint
Resolved
Unresolved
Enabled
Stops execution
No
Disabled
No
No
+

 

+

 

+

 

+

In addition, you can use these types of watchpoints:

+

A watchpoint is equivalent to a memory breakpoint.

+

Unlike a breakpoint, a watchpoint can detect when any part of your program affects memory. For example, if a write or write/read watchpoint is set, when the program writes a new value to the address or area of memory that has the watchpoint, the debugger suspends program execution.

+

NOTE You cannot set a watchpoint on a local variable, because the debugger cannot detect watchpoints for variables stored on the stack or in registers.

+
Table 2 Watchpoint—types and states
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeStateIconExplanation
Writeenabled

The watchpoint is activated for write access operations on the specific memory location and if resolved, will halt program execution on a write operation at the watchpoint.

+
disabled

Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation.

+
Readenabled

The watchpoint is activated for read access operations on the specific memory location and if resolved, will halt program execution on a read operation at the watchpoint.

+
disabled

Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation.

+
Write/Readenabled

The watchpoint is activated for both read and write access operations on the specific memory location and if resolved, will halt program execution on any read or write operation at the watchpoint.

+
disabled

Watchpoint is disabled for the source line, debugger does not halt program execution on a read or write operation.

+
+

A project can have a different maximum number of watchpoints, depending on the build target. The IDE generally limits the acceptable range for watchpoints to memory that it can write-protect. This range also depends on the host and on the application.

+

All set watchpoints appear in the Breakpoints view list.

+
Related concepts
+ +
Related tasks
+ +
Related references
+ + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/hints_tips.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/hints_tips.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/hints_tips.htm Tue Jan 26 13:41:56 2010 -0600 @@ -26,23 +26,19 @@

Use the System Search feature in Carbide. Click Search > System..., enter the search data, press Search.

-
How can I quickly open a .h file associated from the source file I am currently editing ?
+
How can I quickly open a .h file associated from the source file I am currently editing?

The CDT editor supports quick opening of associated .h files. To view the .h file, select the name of the .h file in the source you are currently editing and press F3 (Open Declaration). A new editor view will appear and display the .h file.

I can't locate the eclipse.ini file to modify the behavior of Carbide.c++, where can I find it?
-

The eclipse.ini file was renamed the carbide.c++.1.x.ini file to keep the .exe and .ini files in sync.

+

The eclipse.ini file was renamed the carbide.c++.2.x.ini file to keep the .exe and .ini files in sync.

I can't launch Carbide.c++ due to "Error occurred in initialization of VM, could not reserve enough space for object heap?

By default, the heap space set aside for Carbide is 1024MB. You can see this setting in the carbide.c++.1.x.ini file as the line "-Xmx1024m". Some system may have limited VM space available so we suggest you try lowering the default amount to "-Xmx512m" and relaunching Carbide.

-
I want to use CDT for other C/C++ development in Carbide.c++
-
-

Carbide.c++ hides some CDT UI elements using capabilities. We do this to avoid confusion as there are several things labeled C/C++ that don't really apply to Symbian development. To show these items, you need to add the Eclipse SDK to your Carbide.c++ installation (download link: www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/R-3.2.1-200609210945/eclipse-SDK-3.2.1-win32.zip), and then enable it from the preferences (Window > Preferences > General > Capabilities > Nokia Debug).

-
-
When I press F1 in a dialog, the help pane isn't very helpful?
+
When I press F1 in a dialog, the help pane isn't very helpful?

If the Help pane does not display information specific to the page content, it may be because the page in the dialog doesn't have focus. This often occurs in a wizard page when nothing has been selected on the page. The help system has not been told which help content to display in the About section of the help pane.

NOTE The Dynamic help section usually displays the proper helpful links, just not as specific as the About section should display.

@@ -89,22 +85,23 @@
New debug launch configuration fields not filled in correctly upon creation
-

See "Debug icon not visible on executable in C/C++ Projects view" to correct this issue. Once completed, try to create a debug launch configuration again. Click the New button in the Configuration window to create a new configuration with the correct project information.

+

See "Debug icon not visible on executable in Project Explorer view" to correct this issue. Once completed, try to create a debug launch configuration again. Click the New button in the Configuration window to create a new configuration with the correct project information.

-
Debug icon not visible on executable in C/C++ Projects view
-
-

This is commonly caused when the binary parser is not set correctly in the project. To correct, open the project properties window (right-click project name in C/C++ Projects view and select Properties), expand the C/C++ Build section and click the Binary Parser tab in the C/C++ Build page. Now look for the PE Windows Parser option. If it's not checkmarked, checkmark it and click Apply. If it is already set then uncheck it and click Apply, then reapply a checkmark and click Apply. The debug icon should now appear.

-
+
Debug icon not visible on executable in Project Explorer view
+
+

This is commonly caused when the binary parser is not set correctly in the project. To correct, open the project properties window (right-click project name in Project Explorer view and select Properties), expand the C/C++ Build section and click the Binary Parser tab in the C/C++ Build page. Now look for the PE Windows Parser option. If it's not checkmarked, checkmark it and click Apply. If it is already set then uncheck it and click Apply, then reapply a checkmark and click Apply. The debug icon should now appear.

+

Connectivity

Unable to connect to device using Bluetooth and debug it using TRK

When using Bluetooth to connect to a device there are several things that require correction, including:

  • If using built-in Bluetooth under WinXP SP2, ensure the manufacturer’s device drivers are installed and active. The default Microsoft drivers do not work correctly for debugging devices using TRK. For example, if using IBM Integrated Bluetooth on your computer, make sure you have the IBM drivers for the device.
    • -
  • Ensure the COM port used by Bluetooth is not commandeered by another process or device
    • +
  • Ensure the COM port used by Bluetooth is not commandeered by another process or device.
    • +
  • Ensure that you have the latest version of TRK on the target device.
- + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Tue Jan 26 13:41:56 2010 -0600 @@ -21,7 +21,6 @@
  • Symbian OS Attach to Process —used to debug processes running on a target device for which a symbol file is available. This is available only for TRK and stop mode debugging. This launch configuration is not available for emulator debugging. Stop mode and TRK can both attach to a process from the Symbian OS Data view.
  • Symbian OS Crash Debugger —used to launch an interactive command-line session with the Symbian OS crash debugger when the device crashes
  • Symbian OS Emulation —used to run or debug executables on an emulator.
    • -
  • Symbian OS Sophia (only available in OEM Edition)—is an external debugger that the Carbide debugger communicates with, to debug any Symbian OS module on a target using a JTAG connection.
  • Symbian OS System TRK (not available Developer Editions) —used to run or debug applications or ROM code on a target device using the System TRK on-device debug agent. System TRK is an application that runs on reference boards and prototype phones and allows you to debug your executables. The debugger will download files to the phone prior to launching.
  • Symbian OS Trace32 (only available in OEM Edition)—is an external debugger that the Carbide debugger communicates with, to debug any Symbian OS module on a target using a JTAG connection.
    • @@ -32,6 +31,6 @@
  • New Launch Configuration Wizard
  • Debug dialog
    • - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm Tue Jan 26 13:41:56 2010 -0600 @@ -15,7 +15,6 @@
  • Application TRK
  • Attach to Process
  • Emulation
    • -
  • Sophia (STI)
  • System TRK
  • Trace32
    • @@ -23,6 +22,6 @@ - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Tue Jan 26 13:41:56 2010 -0600 @@ -1,155 +1,155 @@ - - - - - - -Carbide Debugger panes - - - -

    Debugger panes

    -

    The options shown in the Debugger page differ based upon the type of launch configuration. Generally, the options fall into these choices:

    - -

    Emulation Debugger page

    -

    The Symbian OS Emulation launch configurations the Debugger page to specify entry point breaks and which logs to output to the Console view.

    -

    -

    Figure 1 - Debugger page showing emulation options

    -
    Table 1. Debugger page — emulation options
    - - - - - - - - - - - - - - - - - - - - - -
    OptionExplanation
    Break at entry point 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.
    View program output

    Enable to direct standard output messages to the Emulation Program Output Console in the Console view.

    -

    NOTE In the epoc.ini file the option LogToFile must also be set to 1.

    View emulator output

    Enable to output emulator messages to the Emulator Output Console in the Console view.

    -

    NOTE In the epoc.ini file the option LogToDebugger must also be set to 1.

    View Windows system messages Enable to output Windows system messages to the Windows System Messages Console in the Console view.
    -

    Run-mode Debugger page

    -

    In a run-mode launch configuration like Application TRK, you can specify an entry break point and how messages are handled as well as define the default instruction set.

    -

    -

    Figure 2 - Debugger page showing run-mode options

    -
    Table 2. Debugger page — run-mode options
    - - - - - - - - - - - - - - - - - - - - - - - - - -
    OptionExplanation

    Break at entry point

    When checked, break at the specified entry point entered into 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.

    View program output

    Enable to direct standard output messages to the TRK Program Output Console in the Console view.

    -

    NOTE In the epoc.ini file the option LogToFile must also be set to 1.

    -
    View messages between Carbide and debug agent

    When checked, show the communications between Carbide and the target device in the TRK Communication Log Console of the Console view.

    -

    NOTE You can pin the TRK Communication Log view so that it does not lose focus.

    Message retry delay (ms) 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.

    Default Instructon Set

    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:

    -
      -
    • Auto (examine code at current PC location)
      • -
    • ARM (32-bit)
      • -
    • THUMB (16-bit)
      • -
    -

    By default the Instruction Set option uses ARM 32-bit.

    -

    Stop-mode Debugger page

    -

    In stop-mode launch configurations like System TRK, Trace32, Sophia, and Attach to Process, use the Startup Options to attach to a target and debug or run from the specified start address. Then use Target Options to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session.

    -

    -

    Figure 3 - Debugger page showing stop-mode options

    -
    Table 3. Debugger page — stop-mode options
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    GroupOptionExplanation
     

    Break at entry point

    When checked, break at the specified entry point entered into 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.

    Startup Options Soft attach Enable the Soft attach 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.
    Debug from start address Enable the Debug from start address option to debug from the target's default start address.
    Run from start address Enable the Run from start address option to run from the target's default start address.
    Start address (hex) Enter in hexidecimal format (0x0) the starting address to use during the debug session.
    Reset target at the start of each debug session 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.
    Target Options Target Processor 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.
     Target initialization file

    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. 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.

     Memory configuration file 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.
    - -

    Other references

    - - - - + + + + + + +Carbide Debugger panes + + + +

    Debugger panes

    +

    The options shown in the Debugger page differ based upon the type of launch configuration. Generally, the options fall into these choices:

    + +

    Emulation Debugger page

    +

    The Symbian OS Emulation launch configurations the Debugger page to specify entry point breaks and which logs to output to the Console view.

    +

    +

    Figure 1 - Debugger page showing emulation options

    +
    Table 1. Debugger page — emulation options
    + + + + + + + + + + + + + + + + + + + + + +
    OptionExplanation
    Break at entry point 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.
    View program output

    Enable to direct standard output messages to the Emulation Program Output Console in the Console view.

    +

    NOTE In the epoc.ini file the option LogToFile must also be set to 1.

    View emulator output

    Enable to output emulator messages to the Emulator Output Console in the Console view.

    +

    NOTE In the epoc.ini file the option LogToDebugger must also be set to 1.

    View Windows system messages Enable to output Windows system messages to the Windows System Messages Console in the Console view.
    +

    Run-mode Debugger page

    +

    In a run-mode launch configuration like Application TRK, you can specify an entry break point and how messages are handled as well as define the default instruction set.

    +

    +

    Figure 2 - Debugger page showing run-mode options

    +
    Table 2. Debugger page — run-mode options
    + + + + + + + + + + + + + + + + + + + + + + + + + +
    OptionExplanation

    Break at entry point

    When checked, break at the specified entry point entered into 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.

    View program output

    Enable to direct standard output messages to the TRK Program Output Console in the Console view.

    +

    NOTE In the epoc.ini file the option LogToFile must also be set to 1.

    +
    View messages between Carbide and debug agent

    When checked, show the communications between Carbide and the target device in the TRK Communication Log Console of the Console view.

    +

    NOTE You can pin the TRK Communication Log view so that it does not lose focus.

    Message retry delay (ms) 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.

    Default Instructon Set

    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:

    +
      +
    • Auto (examine code at current PC location)
      • +
    • ARM (32-bit)
      • +
    • THUMB (16-bit)
      • +
    +

    By default the Instruction Set option uses ARM 32-bit.

    +

    Stop-mode Debugger page

    +

    In stop-mode launch configurations like System TRK, Trace32, and Attach to Process, use the Startup Options to attach to a target and debug or run from the specified start address. Then use Target Options to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session.

    +

    +

    Figure 3 - Debugger page showing stop-mode options

    +
    Table 3. Debugger page — stop-mode options
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    GroupOptionExplanation
     

    Break at entry point

    When checked, break at the specified entry point entered into 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.

    Startup Options Soft attach Enable the Soft attach 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.
    Debug from start address Enable the Debug from start address option to debug from the target's default start address.
    Run from start address Enable the Run from start address option to run from the target's default start address.
    Start address (hex) Enter in hexidecimal format (0x0) the starting address to use during the debug session.
    Reset target at the start of each debug session 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.
    Target Options Target Processor 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.
     Target initialization file

    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. When using T32, most of the initialization is done in the CMM script file. With other debug protocols you can specify the initialization file, which can be run after connecting to the target.

     Memory configuration file 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.
    + +

    Other references

    + + + + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Tue Jan 26 13:41:56 2010 -0600 @@ -13,7 +13,7 @@

    Emulation Main page

    The Symbian OS Emulation launch configuration uses the Main page to define the process to be launched by the emulator.

    @@ -88,7 +88,7 @@

    Stop-mode Main page

    -

    The Symbian OS System TRK, Sophia, and Trace32 launch configurations uses the Main page to defines the project and the executable to launch on the target device.

    +

    The Symbian OS System TRK, and Trace32 launch configurations uses the Main page to defines the project and the executable to launch on the target device.

    Figure 3. Main page (TRACE32 shown)

    Table 3. Stop-mode Main page — items
    diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/projects/launch/sophia.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/sophia.htm Tue Jan 26 11:44:24 2010 -0600 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,32 +0,0 @@ - - - - -Sophia Launch Configuration - - - - -

    Sophia Launch Configuration

    -

    Select the Symbian OS Sophia target interface (STI) launch configuration (only available in OEM Edition) to debug any Symbian OS module on a target using a JTAG connection. The external Sophia debugger communicates with the Carbide debugger and enables stop mode debugging of the target device.

    -

    If the New Launch Configuration Wizard was used to create an Sophia launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Open Debug Dialog... menu option to open the Debug dialog. Select the Sophia configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

    -

    -

    Figure 1. Sophia launch configuration in the Debug dialog

    -

    The Sophia launch configuration panes include:

    -
      -
    • The Main tab defines the project to be launched. Enter the name of the project in the Project field, and the executable name in the Executable field.
      • -
    • The Connection tab defines the Sophia Target Interface, EJ_Debug type, and JTAG TCLK Frequency.
      • -
    • The Debugger tab defines debug configurations, such as entry point to begin debugging, target options, and instruction set.
      • -
    • The ROM Image tab allows you to define startup options and ROM image and ROM log file download information.
      • -
    • The Executables tab allows you to specify which executables that you want to debug that are part of the project.
      • -
    • The Source tab (standard CDT page) defines the location of source files used to display source when debugging an application. By default, these settings are derived from the associated project's build path. You may override these settings here.
      • -
    • The Common tab (standard CDT page) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file.
      • -
    -

    Other references

    - - - - diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm Tue Jan 26 13:41:56 2010 -0600 @@ -9,7 +9,7 @@

    System TRK Launch Configuration (Stop-mode)

    -

    Select the Symbian OS System TRK launch configuration (only available in OEM Edition) provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS Sophia or Trace32 launch configuration is created. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options.

    +

    Select the Symbian OS System TRK launch configuration (only available in OEM Edition) provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS Trace32 launch configuration is created. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options.

    If the New Launch Configuration Wizard was used to create the System TRK launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Open Debug Dialog... menu option to open the Debug dialog. Select the System TRK configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

    Figure 1. System TRK launch configuration in the Debug dialog

    @@ -26,6 +26,6 @@ - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Tue Jan 26 13:41:56 2010 -0600 @@ -50,13 +50,6 @@ - Sophia STI - - - Attach to Process
    • TRK Connection Settings
      • @@ -104,21 +97,16 @@

      This page only appears when creating a Trace32 launch configuration.

      Figure 9 - Trace32 Initialization Settings page

      -

      Sophia STI Initialization Settings

      -

      Use the Sophia STI Initialization Settings page to specify the target interface, initialization file, and target processor of the target device. Enter the Sophia Target Interface and Target Initialization File paths, choose a Target Processor, then click Next.

      -

      This page only appears when creating a Sophia STI launch configuration.

      -

      -

      Figure 10 - Sophia STI Initialization Settings page

      Symbian ROM Image Settings

      Use the Symbian ROM Image Settings page to specify the method of debugging, the start address, and the ROM Image and Log File locations.

      -

      This page appears when creating a Trace32 or Sophia STI launch configuration.

      +

      This page appears when creating a Trace32 launch configuration.

      -

      Figure 11 - Symbian ROM Image Settings page

      +

      Figure 10 - Symbian ROM Image Settings page

      Other references
      - + \ No newline at end of file diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wnd_debug_configuration.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wnd_debug_configuration.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wnd_debug_configuration.htm Tue Jan 26 13:41:56 2010 -0600 @@ -4,18 +4,17 @@ -Carbide Debug dialog - +Debug Window + -

      Debug dialog

      -

      Use the Debug dialog to create, edit, and manage a project's launch configurations. A launch configuration defines the settings used by the Carbide debugger to launch (Run) or debug programs. A project must have at least one launch configuration in order to debug a project and can have many more. Projects that have no launch configuration invoke the New Launch Configuration Wizard when either the Run or Debug command is selected.

      -

      Select the Run > Debug Configuration... menu option to open the Debug dialog.

      -

      The tabs shown in the Debug dialog vary depending upon the type of launch configuration highlighted in the configurations list. See Launch Configuration Overview for more information on the various launch configuration types.

      -

      Click Debug to start a new debug session using the selected launch configuration.

      -

      -

      Figure 1 - Debug dialog (Symbian OS Emulation configuration shown)

      -
      Table 1. Debug dialog — common items
      +

      Debug Window

      +

      The Debug or launch configuration window provides C/C++ debugger options. A launch configuration defines the settings used by the Carbide debugger to launch and debug programs. A project must have at least one debug launch configuration in order to debug a project and can have many more.

      +

      By default, Carbide creates a debug launch configuration the first time you launch the debugger based on current project settings. If additional information is required, like a port ID, the New Launch Configuration Wizard appears asking for the additional information.

      +

      The tabs in the window vary depending upon the currently selected launch configuration.

      +


      +Figure 1 - Debug or launch configuration window (Symbian OS emulation view)

      +
      Table 1. Debug window — common items
      @@ -52,15 +51,30 @@
    • Filter Deleted/Unavailable Projects
    • Filter Configuration Types
    • Apply Window Working Set(s)
      • -
    • Filtering Preferences...
      • +
    • Filtering Preferences...
      • Icon
      -

      Other references

      +
      +

      To open the Debug window

      +
        +
      • Select the Run > Open Debug Dialog... menu item
        • +
      +
        + The Debug window (Figure 1) appears.
      +
        +
      • Select Run > Open Run Dialog... to open a Run window to create a launch configuration for a release build.
        • +
      +
      +
      Other references
      + \ No newline at end of file diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_creating_projs_06.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_creating_projs_06.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_creating_projs_06.htm Tue Jan 26 13:41:56 2010 -0600 @@ -9,7 +9,7 @@

      Creating Qt Projects

      -

      Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into S60. The wizard walks you through the process of defining and creating a Qt project.

      +

      Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

      1. Launch the New Qt Project Wizard
      2. Select type of Qt project
        3. diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_01.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_01.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_01.htm Tue Jan 26 13:41:56 2010 -0600 @@ -9,7 +9,7 @@

        Importing Qt Projects

        -

        Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into S60. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

        +

        Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

        To import a Qt project:

        1. Launch the importer
          2. diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_02.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_02.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_02.htm Tue Jan 26 13:41:56 2010 -0600 @@ -9,7 +9,7 @@

          Importing Qt Projects

          -

          Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into S60. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

          +

          Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

          To import a Qt project:

          1. Launch the importer
            2. diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_03.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_03.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_03.htm Tue Jan 26 13:41:56 2010 -0600 @@ -9,7 +9,7 @@

            Importing Qt Projects

            -

            Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into S60. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

            +

            Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

            To import a Qt project:

            1. Launch the importer
              2. diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_04.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_04.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_importing_projs_04.htm Tue Jan 26 13:41:56 2010 -0600 @@ -9,7 +9,7 @@

              Importing Qt Projects

              -

              Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into S60. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

              +

              Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

              To import a Qt project:

              1. Launch the importer
                2. diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_overview.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_overview.htm Tue Jan 26 13:41:56 2010 -0600 @@ -24,7 +24,7 @@
                • Qt + Eclipse integration — see the Qt Developer User Guide
                • Qt SDK help — look in the qt_sdk_install/doc/html directory of the Qt SDK
                  • -
                • Qt support — visit trolltech.com for more information
                  • +
                • Qt information — visit Forum Nokia Qt wiki topic for more information
                diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_project_setup.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_project_setup.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_project_setup.htm Tue Jan 26 13:41:56 2010 -0600 @@ -10,11 +10,11 @@

                Qt Development Setup

                There are some prerequisites to using Qt projects within the Carbide environment. This includes downloading the correct SDKs, building qmake to use the SDKs, and finally, building the libraries for your target environments.

                -

                You should have the Qt SDK for S60 that works with the S60 SDK in order to develop applications with Carbide. These steps include:

                +

                You should have the Qt SDK for Symbian that works with the S60 SDK in order to develop applications with Carbide. These steps include:

                  -
                1. Download the Qt SDK for S60 package
                  2. -
                2. Install the Qt SDK using the instructions found in the INSTALL file located in the Qt SDK for S60 folder, including: -
                    +
                  1. Download the Qt SDK for Symbian package
                    2. +
                  2. Install the Qt SDK using the instructions found in the INSTALL file located in the Qt SDK for Symbian folder, including: +
                      1. Install needed IDE and SDKs
                      2. Install Qt
                        3. @@ -25,7 +25,7 @@
                    -

                    Once completed, you should be able to import or create new projects using the Qt SDK for S60.

                    +

                    Once completed, you should be able to import or create new projects using the Qt SDK for Symbian.

                    Other references

                    • Qt Project Support
                      • diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm Tue Jan 26 13:41:56 2010 -0600 @@ -19,15 +19,25 @@

                      Remote Connections view

                      -

                      Use the Remote Connections view to monitor, create, edit, or remove common connection settings for remote agents. The columns include:

                      +

                      Use the Remote Connections view to monitor, create, edit, or remove common connection settings for remote agents. Remote agents provide support for debugging, profiling, trace, and more. The connection types currently supported include:

                      +
                        +
                      • Serial — mainly for boards with a serial interface
                        • +
                      • Bluetooth — available for debug support
                        • +
                      • USB — available for both debug and trace support
                        • +
                      • Platform Simulator (PlatSim) — Nokia's device simulator
                        • +
                      +

                      The columns in the Remote Connections view include:

                      • Connection/Services - connection name defined by you and remote agent type
                      • Type - connection type, i.e. Bluetooth, USB, TCP/IP, etc.
                        • -
                      • Status - current connection status, i.e. Available, Not available, In Use, etc.
                        • +
                      • Status - current connection status, i.e. Available, Not accessible, Ready, etc.
                      • Description - provides information on the current connection test status.
                      -

                      +

                      Figure 1 - Remote Connections view

                      +

                      When the view is closed or another perspective opened, a small display item appears in the lower-left corner of the perspective. Click the connection name to open the drop-down menu where you can open the Remote Connections view or switch between connections.

                      +

                      +

                      Figure 2. Remote Connections tab

                      Remote Connections view toolbar icons

                      The following commands appear on the toolbar within the Remote Connections view:

                      @@ -58,10 +68,48 @@

                      Click to edit the selected remote connection.
                      +

                      Remote Connections view Status icons

                      +

                      The following status indicators appear in the Remote Connections view:

                      + + + + + + + + + + + + + + + + + + + + + + + + + + +
                      ItemIconExplanation
                      Connection
                      + +

                      Indicates an inactive remote connection setting.

                      Not Active
                      + +
                      		Indicates an inactive connection type.
                      Ready / Available
                      + +

                      Indicates an active remote connection is ready or that a particular connection type is available.

                      Not Accessible
                      + +
                      +                       		Cannot access the connection type within the connection setup.

                      Remote Connections view context menu options

                      Based on the current selection, one or more of the following commands appear on the context menu when you right-click within the Remote Connections view. For example, if no connections are defined, only the New Connection command is available on the context menu. Right-click on a connection name and the additional Enable Service Testing and Disable Service Testing are available.

                      -

                      Figure 2 - Remote Connections context menu

                      +

                      Figure 3 - Remote Connections context menu

                      @@ -115,9 +163,10 @@
                      Related references
                      - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_edit.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_edit.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_edit.htm Tue Jan 26 13:41:56 2010 -0600 @@ -48,8 +48,8 @@
                    • Verify that you have the latest remote agent installed on a device

                      • -

                      Figure 2 - New Connection wizard Serial Connection Settings page

                      -

                      Table 2. Serial Connection Setting page - Set Connection Settings tab

                      +

                      Figure 2 - New Connection wizard Set Connection Settings tab

                      +

                      Table 2. Bluetooth Setting page - Set Connection Settings tab

                      Item
                      @@ -73,7 +73,7 @@ -
                      Item
                      Test Service Status

                      Click Test Service Status to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check TRK version operation requires more than a few seconds.

                      +

                      Click Initiate service testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check TRK version operation requires more than a few seconds.

                      NOTE The PC must have an internet connection to perform a remote agent version check.

                      Once the comparison is complete the Status text is updated with the result and further instructions as required.

                      @@ -88,8 +88,8 @@

                      Install Remote Agents pane

                      Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

                      -

                      Figure 2 - New Connection wizard Serial Connection Settings page

                      -

                      Table 3. Serial Connection Setting page - Install Remote Agents tab

                      +

                      Figure 2 - New Connection wizard Install remote agents tab

                      +

                      Table 3. Bluetooth Setting page - Install Remote Agents tab

                      @@ -116,7 +116,7 @@
                    • On-Device Setup
                    • Install latest TRK
                      • - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Tue Jan 26 13:41:56 2010 -0600 @@ -52,7 +52,7 @@ - @@ -108,7 +108,7 @@
                    • Setting Symbian OS View Refresh Rate
                      • - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Tue Jan 26 13:41:56 2010 -0600 @@ -9,7 +9,7 @@

                      Carbide supports the use of code styles in projects via the C/C++ Code Style preference panel. Use a code style profile to set specific smart typing features, like indentation, tabs or spaces, and many more options. There are several preset code styles like GNU, while Carbide supplies these profiles:

                      Setting a code style sets it for the entire workspace. When a new file is created the currently selected code style rules are applied as you edit the file. You can apply a set of rules to a previously created source file by opening it in an editor view, then right-clicking and choosing Source > Format (CTRL+SHIFT+F).

                      diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/release_notes.htm Tue Jan 26 13:41:56 2010 -0600 @@ -16,7 +16,7 @@ -

                      Carbide.c++ Release Notes 2.2.0

                      +

                      Carbide.c++ Release Notes 2.5.0

                      The Carbide.c++ is a comprehensive development tool suite for Symbian OS that is based on the Eclipse framework. The C++ Development Toolkit (CDT), provides the foundation for project and build tools management, as well as the primary interface for the debugger to communicate with the IDE.

                      This is a collection of important information concerning last-minute changes and other topics that deserve special attention. Please @@ -35,12 +35,27 @@ Updating the CDT feature in Carbide.c++/Eclipse will wipe out our changes making the tools unusable!

                      See the Tips & tricks page for more helpful information.

                      -

                      What's New in 2.2.0

                      +

                      What's New in 2.5.0

                      The following features for Symbian development are provided within Carbide.c++:

                        -
                      • Eclipse 3.5 — The Eclipse 3.5 project (Galileo) provides the foundation, or integration platform, on which Carbide.c++ is built. See What's New in 3.5 for more information.
                        • +
                      • RVCT 4.0 (ARMv5) supported
                        • +
                      • SmartInstaller for Qt supported
                        • +
                      +

                      2.4.0

                      +
                        +
                      • IMPORTANT WINSCW COMPILER change - the WINSCW compiler 3.2.5 build 487 provides new name mangling to support critical exception handling. Without this change an exception can cause a program or system crash. For more information visit the WINSCW wiki page.
                        • +
                      • Qt Tools 1.6 now supported.
                        • +
                      • The Run builds concurrently option in the Builds preference panel now supports up to 50 concurrent build jobs, up from 4.
                      +

                      2.3.0

                        +
                      • P2 update services now supported. Updating Carbide.c++ should be more flexible and easier than before.
                        • +
                      • The official Qt code style is now included in the Code Style preference panel.
                        • +
                      • Single file compiles on Raptor are now supported.
                        • +
                      +

                      2.2.0

                      +
                        +
                      • Eclipse 3.5 — The Eclipse 3.5 project (Galileo) provides the foundation, or integration platform, on which Carbide.c++ is built. See What's New in 3.5 for more information.
                      • CDT 6.0 — The final version of CDT included as part of the Galileo release. See the CDT 6.0 News and Noteworthy page for more information.
                      • Java 6.0 — Due to the above changes Carbide has also updated to use the Java Runtime Environment (JRE) 6.0. See Java SE 6 Release Notes page for more information.
                      • SBSv2 arguments field - added a text field to the Build > SBSv2 panel to allow parameter passing to Raptor builds.
                        • @@ -48,7 +63,7 @@

                      2.1.0

                        -
                      • Performance inprovements - the following areas of Carbide have been optimized to improve performance: +
                      • Performance improvements - the following areas of Carbide have been optimized to improve performance:
                        • Importing large projects - Importing large projects is one of our primary points of performance improvements. When too many project roots were used the more source and include paths were brought into the project, up to an including entire SDKs. Generally, we found that once a project root contains over 15-20K files Carbide became extremely sluggish. We have improved some edge cases where project roots were calculated incorrectly and now include only what's really needed.
                        • Modifying Project Settings and Build Configuration Data- This is quite a significant improvement as modifying MMP files and switching build configurations are a couple of the most common operations done by end-users and because the time spent processing project and configuration data is done on the main thread, locking the UI. With optimization in one CDT function we were able to bring most project-related and configuration switch changes from 20 seconds to less than 3 seconds. You should also see improvements when saving MMP and INF files (the "Refreshing Configuration Job").
                          • @@ -86,7 +101,7 @@
                        • Executables view improvements — The Executables view now supports the loading of some additional DLL cases to ensure that the DLLs you want to debug are available during a debug session. In addition, a Remove button has been added to the view's toolbar that makes it easier for you to remove any executables from the list.
                        • More indexer improvements — Speed improvements for code completion, syntax coloring, and much more.
                        • Remote Connections view — A visual list of remote connections and their state for managing multiple and diverse device connections.
                          • -
                        • Partial upgrade SIS file support — Carbide now supports the generation of partial upgrade SIS/SISX files. This increases debugger turnaround by only generating new files for changes and uploading these smaller executables to the device.
                          • +
                        • Partial upgrade SIS file support — Carbide now supports the generation of partial upgrade SIS/SISX files. This increases debugger turnaround by only generating new files for changes and uploading these smaller executables to the device.
                        • More Program Counter support — Added a Move to Line command for the debugger that enables you to move the PC to a new line while debugging without executing any intermediate lines or resuming execution.
                        • Multiple TRK improvements including:
                            @@ -172,12 +187,13 @@

                            JVM terminated, Return code = -1

                            or when running from eclipse.exe:

                            Error occurred during initialization of VM Could not reserve enough space for object heap

                            -

                            The solution is to edit your Carbide.c++.1.x.ini (or eclipse.ini if launching Eclipsec.exe) and use a smaller value for the -Xmx parameter to the JVM.

                            +

                            The solution is to edit your Carbide.c++.2.x.ini (or eclipse.ini if launching Eclipsec.exe) and use a smaller value for the -Xmx parameter to the JVM.

                            NOTE In this scenario, Carbide.c++ performance may degrade.

                      - + - - - - @@ -236,11 +248,7 @@ - + - - - - @@ -312,10 +316,6 @@

                      (2) As getting the OS data from crash debugger is time consuming (takes more than one minute in our test), auto-refresh of the data in Symbian OS Data view is disabled for crash debugger. You need to click the "Refresh" button to do a manual refreshing.

                      - - - - @@ -370,13 +370,9 @@
                      Item

                      Debug process or thread

                      Click the Debug button to attach to the process and debug the selected process or thread. Or right-click an item and choose Debug. This applys to both TRK (run mode) and Sophia/Trace32 (stop mode).

                      +

                      Click the Debug button to attach to the process and debug the selected process or thread. Or right-click an item and choose Debug. This applies to both TRK (run mode) and Trace32 (stop mode).
                      [4587] Unable to build GCCE targets on Vista because of makefile error.There are known tooling issues when building for the GCCE platform under Windows Vista that can prevent a GCCE build from occurring. If you want to build for GCCE under S60 and UIQ you will need to manually update some files under \epoc32\tools\. See the article Windows Vista for up-to-date workaround information.

                      There are known tooling issues when building for the GCCE platform under Windows Vista that can prevent a GCCE build from occurring. If you want to build for GCCE under S60 and UIQ you will need to manually update some files under \epoc32\tools\. See the article Windows Vista for up-to-date workaround information.

                      +

                      UPDATE 2010: SDKs still require patching to enable GCCE builds.
                      @@ -196,10 +212,6 @@ When creating new folders, use File > New > Source Folder. This will add a folder and mark it a source folder. If you need to import copies of existing files (File > Import > File System) or link to existing sources (File > New > Folder with "Link to folder in file system"), then a normal folder will be created, not a source folder. If the folder is not underneath an existing source folder in the project, you will need to manually mark it as a source folder using the C/C++ Project Paths > Source tab.
                      [3803] Occasionally a module is not expandable immediately after it's been imported in a project. Workaround: Simply close and reopen the project using the context menu in the Project view.
                      [3010] Bad synchronization in MMP editor for Linker definition file. The templates for Symbian DLL projects do not define a DEFFILE statement, for the case where a DEF file is not needed or imports are not frozen. If you edit the DEF filename through the MMP editor, it is not automatically conditioned for the current target. If you wish to define target-specific DEF file names in the MMP editor, manually insert #ifdef...#endif blocks, or first uncomment the #ifdef...#endif block from the template, so that target-specific filenames will be properly updated.
                      If you are in doubt about the contents select the folder in question, then hit F5 to refresh the directory from the file system.
                      Synergy 6.3 Installations will -always crash Eclipse file navigation dialogs - The solution for this is -to un-register cmexplorer.dll then reboot your machine. Un-registering -this feature will only effect users that use Synergy integration to -Windows Explorer. This issue is known to be fixed with Synergy 6.4.Synergy 6.3 Installations will always crash Eclipse file navigation dialogs - The solution for this is to un-register cmexplorer.dll then reboot your machine. Un-registering this feature will only effect users that use Synergy integration to Windows Explorer. This issue is known to be fixed with Synergy 6.4. The un-register command is:

                      BUILD/IMPORTER
                      [3804] My application fails to start the first time I try to debug it using TRK. Workaround: Launch the debug session again.
                      [3809] IMPORTANT: You cannot import two projects into Carbide that have the same "Root Directory". If a .project file already exists in this location you either need to shorten or lengthen the "Root Directory" or delete the other project in the same location and try to import again.
                      [2616] If you cast a variable to another type the details pane will still show the original typeNo Workaround.
                      [2960] The thread run control icons (step over, step in, run) are sometimes disabled after stepping Click on the top frame of the suspended thread in the Debug view

                      Technical support

                      The following support services are available:

                      -
                      • Visit the Forum Nokia Developer Discussion Board for lively Carbide.c++ discussions
                        • -
                      • Forum Nokia Wiki - visit wiki.forum.nokia.com/index.php/Carbide.c++ for updated information, downloads and tips
                        • -
                      • Customer feedback - send your comments and suggestions to feedback.carbide@nokia.com
                        • -
                      • Read the Carbide.c++ On-device Debugging whitepaper or an introduction to on-device debugging for S60 3rd Edition devices
                        -
                        • + - + \ No newline at end of file diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/sos_references.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/sos_references.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/sos_references.htm Tue Jan 26 13:41:56 2010 -0600 @@ -13,13 +13,14 @@

                        NOTE WINS (Visual Studio) SDKs are not supported. If you want to do emulation debugging you need a WINSCW SDK.

                        - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Tue Jan 26 13:41:56 2010 -0600 @@ -23,13 +23,13 @@

                        Install an SDK

                        -

                        The following SDKs can be downloaded from forum Nokia at: http://forum.nokia.com/.

                        +

                        The following SDKs can be downloaded from forum Nokia at: http://www.forum.nokia.com/.

                        • Install at least one of the following SDKs:
                            • +
                          • Series 60 5.0
                          • Series 60 3.0
                          • Series80
                            • -
                          • UIQ 3.0
                          • Series 60 cust kits
                          • Techview Development kits

                            @@ -37,7 +37,7 @@
                        - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Tue Jan 26 13:41:56 2010 -0600 @@ -8,14 +8,14 @@

                        Stop Mode Debug Example

                        -

                        This example shows how to create and build an application and debug it on a device using JTAG debug software and Lauterbach or Sophia hardware.

                        +

                        This example shows how to create and build an application and debug it on a device using JTAG debug software and Lauterbach hardware.

                        The basic steps include:

                        With stop mode debugging you can use the Carbide.c++ IDE and a JTAG interface to communicate between the debugger and a board to debug any target type within the Symbian OS.

                        @@ -29,9 +29,8 @@ - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_jtag.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_jtag.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_jtag.htm Tue Jan 26 13:41:56 2010 -0600 @@ -38,33 +38,12 @@
                      • Set up the Board

                        • Power up the board. You should now be able to download the image.

                        - -
                        Using Sophia Hardware
                        -
                          -
                        1. If needed, install the following Watchpoint debugger software:
                          -

                          Watchpoint ARM9
                          - Watchpoint ARM11
                          - CodeWarrior - Watchpoint Connection tool
                          - Driver for USB dongle for STI ARM
                          - Watchpoint ARM9 Help Files

                          2. -
                        2. Setup Watchpoint
                          3. -

                          Copy and unzip Watchpoint project and initialization files to any directory on your PC.

                          -
                        3. Establish Target Connection -
                            -
                          1. Plug USB dongle into your PC, and install the drivers if necessary.
                            2. -
                          2. Connect Sophia EJ-Debug JTAG device to the Jtag on the mother board (make sure SW3-7 is off) and to PC via USB cable.
                            3. -
                          3. When Windows prompts you for a driver, navigate to your WATCHPOINT\US_ARM9 or WATCHPOINT\US_ARM11 installation.
                            4. -
                          4. Open the WatchPoint project file. If it launches successfully, you have established a connection.
                            5. -
                          -

                          After successfully opening the project file, make sure that for the H4 target, the Jtag clock is set to 8.33MHz. This can be done from the Resource menu of WatchPoint. Select the ‘ICE Configuration’ option and then select the ‘Clock’ tab. Check the 8.33 MHz radio button and apply the settings.

                          -
                          4. -
                        Related Tasks
                        - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Tue Jan 26 13:41:56 2010 -0600 @@ -1,301 +1,300 @@ - - - - - -Stop Mode On-Device Debugging - - - -

                        Defining a Stop Mode Debug Configuration

                        -

                        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.

                        -
                        -

                        Define a Launch Configuration

                        -
                          -
                        1. Access the Debug window -
                            -
                          1. If necessary, import a project's .mmp or .inf file in Carbide.c++.
                            2. -
                          2. Select the Project in the C/C++ Project view that you want to debug.
                            3. -
                          3. Select the Run > Debug… menu option to display the Debug launch configuration window.
                            4. -
                          4. Define a debug launch configuration to communicate with the on-device debug agent or protocol interface.
                            5. -
                          5. In the Debug window, define the type of debug launch configuration to use when debugging programs on the target device.
                            6. -
                          -
                          2. -

                          -

                          Figure 1 - Debug Configurations

                          -

                          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:

                          -
                            -
                          • Main - defines the project to be launched on the target device
                            • -
                          • Connection - specifies the method used to transfer files to the target device
                            • -
                          • Debugger - provides control over entry points, message handling, and instruction set default settings
                            • -
                          • ROM Image- specifies startup options and ROM log and image files
                            • -
                          • Source - specifies the source lookup paths
                            • -
                          • Common - specifies general launch configuration settings
                            • -
                          -

                          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.

                          -
                        2. Define Main Tab Settings
                          3. -

                          The Main pane shown in Figure 2 defines the project to be launched on the target device. Table 1 defines the fields.

                          -

                          -

                          Figure 2 - Debug Window - Main Tab

                          -

                          Table 1. Main pane

                          - - - - - - - - - - - - - -
                          ItemExplanation
                          Project

                          The project to associate with this debug launch configuration. Click Browse to select a different project.

                          ExecutableThis is the name of the executable that is linked to the project. Click Browse to select a different executable.
                          -

                          -
                        3. Define Connection Tab Settings
                          4. -

                          -

                          Figure 3 - Debug Window - Connection Tab

                          -

                          Table 2 - Connection pane

                          - - - - - - - - - - - - - - - - - - - - - -
                          ItemExplanation
                          -

                          Trace32 Executable

                          Specify the path to the Trace32 executable. The default path assumes that the Trace32 executable is installed in the default location: C:\T32\T32marm.exe.

                          -

                          Trace32 Configuration File

                          		Specify the path to the config.t32 file or other custom configuration file. The default path assumes that the Trace32 configuration file is installed in the default location: C:\T32\config.t32. -

                          For arm11 processors copy the trace32 configuration file for non-ARM11 processor (config_arm11.t32) to your C:\T32 folder and specify it in the edit box.

                          -

                          You can modify the config.t32 file to support UDP (User Datagram Protocol) connections by adding the following lines:
                          - PBI=USB
                          - RCL=NETASSIST
                          - PACKLEN=1024
                          - PORT=20000

                          -

                          - - Trace32 Initialization Script

                          Specify the path to the initialization cmm file. This script will be run in T32 after connecting to T32. You can specify your own scripts for the targets used.

                          -

                          - - View messages between Carbide and Trace32

                          		Enable to log communications with Trace32 to the console window.
                          -

                          -
                        4. Define Debugger Tab Settings
                          5. -

                          -

                          Figure 4 - Debug Window - Debugger tab

                          -

                          Table 3 - Debugger pane

                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          ItemExplanation
                          Break at entry point

                          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.

                          Target Processor 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.
                          -

                          Target Initialization File

                          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.

                          -

                          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.

                          -

                          Memory Configuration File

                          		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.
                          -

                          Reset target at the start of each debug session

                          		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.

                          Default Instructon Set

                          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:

                          -
                            -
                          • Auto (examine code at current PC location)
                            • -
                          • ARM (32-bit)
                            • -
                          • THUMB (16-bit)
                            • -
                          -

                          By default the Instruction Set option uses ARM 32-bit.

                          -

                          -
                        5. Define ROM Image Tab
                          6. -

                          -

                          Figure 5 - Debug Window - ROM Image Tab

                          -

                          Table 4 - ROM Image pane

                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                          ItemExplanation
                          -

                          - - Start Address

                          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.

                          -

                          NOTE 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.

                          -

                          - - Debug from Start address

                          		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.
                          -

                          - - - Run from start address

                          		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.
                          -

                          - - - - Symbian ROM Log file

                          		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.
                          -

                          - - - Symbian OS Kit EPOC32 Directory

                          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.

                          -

                          NOTE Always include the epoc32 folder in this path.

                          -

                          - - - - - Log unresolved modules

                          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.

                          -

                          NOTE You cannot perform source-level debugging on components that do not include symbolic information.

                          -

                          - - - - - Debug non-XIP Executables

                          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.

                          -

                          NOTE 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.

                          -

                          - - - - Symbian ROM Image

                          		Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window.
                          -

                          Download Address (hex)

                          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.

                          -

                          NOTE 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.

                          -

                          Ask for download at the start of each debug session

                          		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.
                          -

                           

                          -
                        -

                        Sophia Target Interface Connection

                        -

                        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.

                        -

                        -

                        Figure 6 - Sophia Connection Window

                        -

                        Table 5 - Sophia Connection Window

                        - - - - - - - - - - - - - - - - - - - - - -
                        ItemExplanation
                        -

                        - - - - - - Sophia Target Interface (WTI.dll) location

                        		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.
                        -

                        - - - - EJ_Debug Type

                        Sophia Systems' EJ-Debug is a compact, USB-powered JTAG emulator. Select the EJ_Debug type. Options include:

                        -
                          -
                        • Auto (automatically detects target CPU)
                          • -
                        • ARM9 (target CPU)
                          • -
                        • ARM11 (target CPU)
                          • -
                        • ARM9_11 (target CPU)
                          • -
                        • ARM7_9_11 (target CPU)
                          • -
                        JTAG TCLK FrequencySelect the JTAG TCLK frequency. Options include: -
                          -
                        • Auto
                          • -
                        • 33 MHz
                          • -
                        • 16 MHz
                          • -
                        • 8 MHz
                          • -
                        • 500 KHz
                          • -
                        View messages between Carbide and STIThe 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.
                        - -
                        -
                        Related Tasks
                        - - - - - - + + + + + +Stop Mode On-Device Debugging + + + + +

                        Defining a Stop Mode Debug Configuration

                        +

                        After installing all necessary software such as Perl, JTAG, compilers, Devkits and SDKs and creating your project, you will need to define a Debug launch configuration for your project. For this example, we'll define a Trace32 launch configuration. For new projects that do not have a launch configuration, a New Launch Configuration Wizard will appear and allow you to define settings. You can also cancel the wizard and define a launch configuration from the following instructions.

                        +
                        +

                        Define a Launch Configuration

                        +
                          +
                        1. Access the Debug window +
                            +
                          1. If necessary, import a project's .mmp or .inf file in Carbide.c++.
                            2. +
                          2. Select the Project in the C/C++ Project view that you want to debug.
                            3. +
                          3. Select the Run > Debug… menu option to display the Debug launch configuration window.
                            4. +
                          4. Define a debug launch configuration to communicate with the on-device debug agent or protocol interface.
                            5. +
                          5. In the Debug window, define the type of debug launch configuration to use when debugging programs on the target device.
                            6. +
                          +
                          2. +

                          +

                          Figure 1 - Debug Configurations

                          +

                          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:

                          +
                            +
                          • Main - defines the project to be launched on the target device
                            • +
                          • Connection - specifies the method used to transfer files to the target device
                            • +
                          • Debugger - provides control over entry points, message handling, and instruction set default settings
                            • +
                          • ROM Image- specifies startup options and ROM log and image files
                            • +
                          • Source - specifies the source lookup paths
                            • +
                          • Common - specifies general launch configuration settings
                            • +
                          +

                          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.

                          +
                        2. Define Main Tab Settings
                          3. +

                          The Main pane shown in Figure 2 defines the project to be launched on the target device. Table 1 defines the fields.

                          +

                          +

                          Figure 2 - Debug Window - Main Tab

                          +

                          Table 1. Main pane

                          + + + + + + + + + + + + + +
                          ItemExplanation
                          Project

                          The project to associate with this debug launch configuration. Click Browse to select a different project.

                          ExecutableThis is the name of the executable that is linked to the project. Click Browse to select a different executable.
                          +

                          +
                        3. Define Connection Tab Settings
                          4. +

                          +

                          Figure 3 - Debug Window - Connection Tab

                          +

                          Table 2 - Connection pane

                          + + + + + + + + + + + + + + + + + + + + + +
                          ItemExplanation
                          + + +

                          Trace32 Executable

                          Specify the path to the Trace32 executable. The default path assumes that the Trace32 executable is installed in the default location: C:\T32\T32marm.exe.

                          + + +

                          Trace32 Configuration File

                          		Specify the path to the config.t32 file or other custom configuration file. The default path assumes that the Trace32 configuration file is installed in the default location: C:\T32\config.t32. +

                          For arm11 processors copy the trace32 configuration file for non-ARM11 processor (config_arm11.t32) to your C:\T32 folder and specify it in the edit box.

                          +

                          You can modify the config.t32 file to support UDP (User Datagram Protocol) connections by adding the following lines:
                          + PBI=USB
                          + RCL=NETASSIST
                          + PACKLEN=1024
                          + PORT=20000

                          + + +

                          + + Trace32 Initialization Script

                          Specify the path to the initialization cmm file. This script will be run in T32 after connecting to T32. You can specify your own scripts for the targets used.

                          + + +

                          + + View messages between Carbide and Trace32

                          		Enable to log communications with Trace32 to the console window.
                          +

                          +
                        4. Define Debugger Tab Settings
                          5. +

                          +

                          Figure 4 - Debug Window - Debugger tab

                          +

                          Table 3 - Debugger pane

                          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                          ItemExplanation
                          Break at entry point

                          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.

                          Target Processor 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.
                          + + + +

                          Target Initialization File

                          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.

                          +

                          When using T32, most of the initialization is done in the CMM script file. With other debug protocols you can specify the initialization file, which can be run after connecting to the target.

                          + + + +

                          Memory Configuration File

                          		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.
                          + + + +

                          Reset target at the start of each debug session

                          		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.

                          Default Instructon Set

                          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:

                          +
                            +
                          • Auto (examine code at current PC location)
                            • +
                          • ARM (32-bit)
                            • +
                          • THUMB (16-bit)
                            • +
                          +

                          By default the Instruction Set option uses ARM 32-bit.

                          +

                          +
                        5. Define ROM Image Tab
                          6. +

                          +

                          Figure 5 - Debug Window - ROM Image Tab

                          +

                          Table 4 - ROM Image pane

                          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                          ItemExplanation
                          + + + +

                          + + Start Address

                          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.

                          +

                          NOTE 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.

                          + + + +

                          + + Debug from Start address

                          		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.
                          + + + +

                          + + + Run from start address

                          		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.
                          + + + +

                          + + + + Symbian ROM Log file

                          		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.
                          + + + +

                          + + + Symbian OS Kit EPOC32 Directory

                          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.

                          +

                          NOTE Always include the epoc32 folder in this path.

                          + + + +

                          + + + + + Log unresolved modules

                          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.

                          +

                          NOTE You cannot perform source-level debugging on components that do not include symbolic information.

                          + + + +

                          + + + + + Debug non-XIP Executables

                          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.

                          +

                          NOTE 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.

                          + + + +

                          + + + + Symbian ROM Image

                          		Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window.
                          + + + +

                          Download Address (hex)

                          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.

                          +

                          NOTE 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.

                          + + + +

                          Ask for download at the start of each debug session

                          		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.
                          +
                        +
                        +
                        Related Tasks
                        + + + + + + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm Tue Jan 26 13:41:56 2010 -0600 @@ -16,7 +16,7 @@
                      • Install the GCCE or RVCT 2.2 or greater compiler (not included with Carbide.c++).
                      • Install the TechView Devkit
                      • Install Board Support Package (BSP) for your target board
                        • -
                      • Install JTAG software and drivers for Trace32 or Sophia I/F tool support
                        • +
                      • Install JTAG software and drivers for Trace32 support
                      • Connect JTAG interface between PC and hardware
                      • Verify that your SDK or customer kit is recognized in the SDK preferences panel.
                      • Build your ROM Image
                        • @@ -25,8 +25,7 @@
                        Related Tasks
                        - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Tue Jan 26 13:41:56 2010 -0600 @@ -18,15 +18,14 @@

                        NOTE You cannot debug ROM DLLs using Application TRK.

                          -
                        • In Sophia or Trace32 you must specify the ROM log file in the ROM Image tab of the Trace32 or Sophia launch configuration
                          • +
                        • In Trace32 you must specify the ROM log file in the ROM Image tab of the Trace32 launch configuration
                        Other references
                        - + \ No newline at end of file diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm Tue Jan 26 13:41:56 2010 -0600 @@ -58,7 +58,7 @@
                      		Other Software

                      A Symbian OS™ SDK and Perl:

                        -
                      • S60 Platform SDKs (forum.nokia.com/main/resources/tools_and_sdks/carbide/) +
                      • S60 Platform SDKs (http://www.forum.nokia.com/Tools_Docs_and_Code/)
                        • S60 5th Edition
                        • S60 3rd Edition, FP1
                          • diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_updating.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_updating.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_updating.htm Tue Jan 26 13:41:56 2010 -0600 @@ -14,29 +14,35 @@

                          Updating Carbide.c++

                          -

                          Updates to Carbide.c++ current features are available using the Software Updates feature.

                          -

                          Carbide is a collection of difference software projects combined into a working environment for Symbian OS C/C++ development. At its base Carbide uses Eclipse and CDT projects from Eclipse.org. We then modify some of these base plug-ins to work with our Carbide plug-ins. This is important for you to know as any updates to those modified base plug-ins may cause Carbide to not work as intended.

                          -

                          IMPORTANT We recommend that you not install any updates for Carbide.c++ features except for those provided by Nokia via Software Update. Replacing any standard Eclipse plugin with an updated version from a non-Nokia update site can result in Carbide.c++ no longer working as intended.

                          +

                          Updates to Carbide.c++ current features are available using the Install New Software feature. This feature now makes use of the P2 provisioning system released in Eclipse 3.4 which provides a more robust updating mechanism for currently installed features as well as the adding of new ones to the Carbide environment.

                          +

                          Carbide is a collection of difference software projects combined into a working environment for Symbian OS C/C++ development. At its base Carbide uses Eclipse and CDT projects from Eclipse.org. We then modify some of these base plug-ins to work with our Carbide plug-ins. This is important to know as any updates to those modified base plug-ins may cause Carbide not to work as intended.

                          +

                          IMPORTANT We recommend that you not install any updates for Carbide.c++ features except for those provided by Nokia via Install New Software. Replacing any standard Eclipse plugin with an updated version from a non-Nokia update site can result in Carbide.c++ no longer working as intended.

                          Installing Carbide Updates

                          +

                          NOTE Always run the Help > Check for Updates wizard and install all updates before attempting to install new software. This can prevent the occurrence of any dependency errors.

                            -
                          1. Select Help > Software Updates > Find and Install... to display the Install/Update dialog. Select "Search for new features to install" and click Next. -

                            -

                            Figure 1 - Install/Update Dialog

                            2. -
                          2. Select the Carbide.c++ Update Site option and click Finish. -

                            -

                            Figure 2 - Update Sites

                            3. -
                          3. Select the Carbide.c++ features to install, then click Next -

                            -

                            Figure 3 - Search results showing Carbide features available

                            -
                            4. -
                          4. Accept with the license - terms and click Next. -

                            -

                            Figure 4 - Update Sites

                            5. -
                          5. Select where the new feature should be installed, then click Finish. -

                            -

                            Figure 5 - Update Sites

                            6. +
                          6. Select Help > Install New Software... to display the Available Software pane of the Install dialog. +

                            +

                            Figure 1 - Install dialog - Available Software pane

                            +
                              +
                            1. Select an update site from the Work with drop down, or click Add... to enter a new site URL.
                              2. +
                            2. Click to select the items to update from the Name column.
                              3. +
                            3. Click Next
                              4. +
                            +
                            7. +
                          7. In the Install Details pane select the specific items to install from those displayed, then click Next. +

                            +

                            Figure 2 - Install dialog - Install Details pane

                            +
                            8. +
                          8. Review the items to install in the second Install Details pane, then click Next. +

                            +

                            Figure 3 - Install dialog - second Install Details pane

                            +
                            9. +
                          9. Accept the license + terms, then click Finish. +

                            +

                            Figure 4 - Install dialog -Review Licenses pane

                            +

                          Carbide downloads the selected features and installs them. You may need to relaunch Carbide.c++ to access the newly installed capabilities.

                          diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm Tue Jan 26 13:41:56 2010 -0600 @@ -15,7 +15,7 @@
                        • Symbian OS System TRK (not available in the Developer Edition) —used to run or debug applications or ROM code on a target device using the System TRK on-device debug agent. System TRK is an application that runs on reference boards and prototype phones and allows you to debug your executables. The debugger will download files to the phone prior to launching.

                        By default, you can click the Debug icon () in the toolbar to launch the New Launch Configuration Wizard. This creates a launch configuration for the project based on project information and any additional input required, like COM port selection. It is the recommended method for creating new launch configurations. Or, use the Debug window to create a customized launch configuration.

                        -

                        +

                        Figure 1. Debug launch configuration for on-device debugging (Application TRK shown)

                        Defining a Customized Launch Configuration

                        diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm Tue Jan 26 13:41:56 2010 -0600 @@ -6,15 +6,11 @@ Installing On-device Debug Agents using Bluetooth -

                        Installing On-device Debug Agents using Bluetooth

                        -

                        Use Bluetooth to install the on-device debug agent, either Application TRK or System TRK, as a SISX file, to enable on-target debugging. The installation location of the on-device debug agent will vary based on the phone. On some phones it will be the Installed folder, on others it may be in My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored.

                        +

                        Use Bluetooth to install the on-device debug agent, either Application TRK or System TRK, as a SISX file, to enable on-target debugging. The installation location of the on-device debug agent will vary based on the phone. Application TRK is usable on both consumer and RnD versions of the device. System TRK is only usable on RnD devices.

                        +

                        On some phones it will be the Installed folder, on others it may be in My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored.

                        NOTE The following example shows how to install the SISX file from a PC running Windows XP SP2 using an internal Bluetooth device. The actions to install the SISX file may be different on your version of Windows. Refer to the OS documentation for information on transferring a file via a Bluetooth connection.

                        Installing an On-device Debug Agent using Bluetooth

                        diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm Tue Jan 26 13:41:56 2010 -0600 @@ -9,7 +9,8 @@

                        Installing On-device Debug Agents using PC Suite

                        -

                        Use the PC Suite software that came with your device (Nokia PC Suite is one example) to install the on-device debug agent, either Application TRK or System TRK, as a SISX file, to enable on-device debugging. The installation location of the on-device debug agent will vary based on the phone. On some phones it will be the Installed folder, on others it may be in My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored.

                        +

                        Use the PC Suite software that came with your device (Nokia PC Suite is one example) to install the on-device debug agent, either Application TRK or System TRK, as a SISX file, to enable on-device debugging. Application TRK is usable on both consumer and RnD versions of the device. System TRK is only usable on RnD devices.

                        +

                        The installation location of the on-device debug agent software varies based on the phone. On some phones it will be the Installed folder, on others it may be in My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored.

                        Using PC Suite you can install any TRK debug agent on the device using a Bluetooth or USB connection.

                        NOTE You can use the connection software that came with your device to install the on-device debug agent SISX file. See your phone's operating manual for assistance on using it's software.

                        @@ -50,7 +51,7 @@
                      • Connecting via Bluetooth
                      • Connecting via USB
                      - + \ No newline at end of file diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm Tue Jan 26 13:41:56 2010 -0600 @@ -22,6 +22,6 @@
                    • On-Device Setup
                    • On-device Debugging
                      • - + \ No newline at end of file diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Tue Jan 26 13:41:56 2010 -0600 @@ -9,21 +9,20 @@

                      Preconditions to On-Device Debugging

                      -

                      Before you can use on-device debugging to debug 3rd edition and UIQ devices, the following preconditions must be met.

                      +

                      Before you can use on-device debugging to debug 3rd and 5th edition devices, the following preconditions must be met.

                      Verifying On-device Debugging Preconditions

                      1. Verify that your system has the following:
                          -
                        • S60 v3.x, UIQ 2.X or UIQ 3.X kit installed
                          • +
                        • S60 v3.x or S60 v5.x kit installed
                        • ActivePerl installed
                        • RVCT or GCCE compiler
                          • -
                        • USB or Bluetooth capable S60 3rd Edition or UIQ 3rd Edition device
                        • USB or Bluetooth support on your PC
                        • Nokia PC Suite (or equivilent software) for connecting and installing applications to the device
                        2. -
                      2. Download and install the current TRK SISX file using the On-Device Setup dialog for debugging S60 5th edition and UIQ devices
                        3. +
                      3. Download and install the current TRK SISX file using the On-Device Setup dialog

                        4. The Application TRK debug agents are stored If not, install it now using the On-Device Connections > New Connection Wizard > Install remote agents pane.

                        NOTE The Application TRK versions included with Carbide is for CE versions of devices only. They are not intended for use with RnD devices.

                      4. Specify the communication method with the on-target device during the debug session
                        5. @@ -45,7 +44,7 @@
                      5. Installing On-device Debug Agents using Bluetooth
                      6. Installing On-device Debug Agents using USB
                        7. - + \ No newline at end of file diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx.htm Tue Jan 26 13:41:56 2010 -0600 @@ -43,7 +43,7 @@ - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx_usb.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx_usb.htm Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx_usb.htm Tue Jan 26 13:41:56 2010 -0600 @@ -15,11 +15,9 @@
                      7. On the device
                        1. Launch Application TRK or System TRK program on the device
                          2. -
                        2. +
                        3. Select PC-Suite from the USB Mode list
                        8. -
                      8. Select PC-Suite from the USB Mode list
                        9. -
                      9. Launch the Application TRK program
                      10. Halt the Bluetooth device search by pressing the Cancel soft key
                      11. Click Options > Settings > Connection
                      12. Change Connection type to USB and set connection options
                        13. @@ -27,7 +25,7 @@

                         

                        Figure 1 - Change connection type to USB and set connection options

                        -
                      13. Select Back and start the TRK again and you should be connected
                        14. +
                      14. Select Back and start TRK again and you should be connected
                      Related concepts
                      @@ -42,7 +40,7 @@ - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/index.xml --- a/core/com.nokia.carbide.cpp.doc.user/index.xml Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/index.xml Tue Jan 26 13:41:56 2010 -0600 @@ -197,8 +197,9 @@ - - + + + @@ -215,11 +216,11 @@ - - - - - + + + + + @@ -231,9 +232,9 @@ - - - + + + @@ -305,7 +306,7 @@ - + @@ -340,10 +341,9 @@ - - - - + + + @@ -409,7 +409,7 @@ - + @@ -510,7 +510,7 @@ - + @@ -592,7 +592,6 @@ - @@ -602,10 +601,6 @@ - - - - @@ -656,7 +651,7 @@ - + @@ -682,8 +677,8 @@ - - + + @@ -708,7 +703,7 @@ - + @@ -727,16 +722,16 @@ - + - + - + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/intro/tutorialsCarbideExtContent.xml --- a/core/com.nokia.carbide.cpp.doc.user/intro/tutorialsCarbideExtContent.xml Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/intro/tutorialsCarbideExtContent.xml Tue Jan 26 13:41:56 2010 -0600 @@ -1,57 +1,57 @@ - - - - - - - - - - Learn how to create, build, and debug a program for the emulator called HelloCarbide using Carbide project templates. - - - - Learn how to create a simple “Test1” DLL project. - - - - Learn how create and build an application and debug it on a device using the App TRK on-device debug agent. - - - - Learn how to create and build an application and debug it on a device using JTAG debug software on Lauterbach or Sophia hardware. - - - - Learn how to use soft attach to debug an image flashed to ROM or on a memory card. - - - - - - + + + + + + + + + + Learn how to create, build, and debug a program for the emulator called HelloCarbide using Carbide project templates. + + + + Learn how to create a simple “Test1” DLL project. + + + + Learn how create and build an application and debug it on a device using the App TRK on-device debug agent. + + + + Learn how to create and build an application and debug it on a device using JTAG debug software on Lauterbach hardware. + + + + Learn how to use soft attach to debug an image flashed to ROM or on a memory card. + + + + + + diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/intro/whatsnew_IntroExt.xml --- a/core/com.nokia.carbide.cpp.doc.user/intro/whatsnew_IntroExt.xml Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/intro/whatsnew_IntroExt.xml Tue Jan 26 13:41:56 2010 -0600 @@ -10,11 +10,11 @@ - Learn about what's new in Carbide.c++ for Symbian OS developers. + Learn about what's new in Carbide.c++ for Symbian OS development. @@ -40,16 +40,6 @@ - Provides updates on the latest Carbide, Symbian, and S60 news. - - - - - + \ No newline at end of file diff -r d0f3375bb257 -r 8121a281245c core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml --- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Jan 26 11:44:24 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Jan 26 13:41:56 2010 -0600 @@ -155,7 +155,6 @@ - @@ -306,15 +305,6 @@ - - - - - - - - -