In run-mode debugger now supports the auto-targeting of processes that are already running or are created during the execution of the debug session. Previously, the debugger forced users to explicitly attach to a running process. Now, the debugger attempts to target all the EXEs specified in the Executables tab of the launch configuration.

Auto-Targeting of Executables

Common Debugging Actions

This section explains how to perform common debugging actions within the Debug perspective to correct source-code errors, control program execution, and observe memory behavior:

Related concepts

Related references

Common Debugging Actions

This section explains how to perform common debugging actions within the Debug perspective to correct source-code errors, control program execution, and observe memory behavior:

Related concepts

Related references

Concepts

The following concepts provide information on common Carbdie.c++ terminology, technologies, and processes:

This section of the User Guide provides an overview of the main concepts in +Carbide to create and build programs for Symbian OS.

The Symbian OS plug-ins are a set of Eclipse plug-ins that provide project, + SDK and build support for Symbian OS developers. The plug-ins extend the + functionality provided by Eclipse and the C/C++ Development Toolkit (CDT).

The plug-ins simplify Symbian OS development by removing the need to use + command line build tools, and provide a graphical interface to Symbian OS + specific file formats, such as AIF and MBM.

The plug-ins provide a new perspective, called the Carbide.c++ Perspective, on + the Eclipse workbench. This perspective enhances the standard CDT C/C++ + perspective by allowing you to select easily the SDKs and build target types + that you want to use for each project.

diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/contextual_menus.htm Mon Aug 10 15:50:55 2009 -0500 @@ -14,7 +14,7 @@

Editor views - perform editing functions, format, compare, and a host of other file actions
Breakpoints view - enable, disable, remove, or select all breakpoints
Debug view - restart, step into, over, or out of routines, terminate or suspend program execution
Debug view - restart, step into, over, or out of routines, terminate or suspend program execution
Memory view - add or remove memory monitors
Project Explorer view - manage projects, build, delete, freeze, run, debug, and other common project commands
Variables view - enable, disable, find, and change the format or value of variables displayed

About the Carbide Debugger

About the Carbide.c++ Debugger

A debugger controls program execution and shows the internal operation of a computer program. Use the debugger to find problems while the program executes. Also use the debugger to observe how a program uses memory to complete tasks.

The Carbide.c++ debugger provides these levels of control over a computer program:

Execution of one statement at a time
Suspend execution after reaching a specific point in the program
Suspend execution after changing a specified memory value
Suspend any running thread from the stack crawl in the Debug view

After the debugger suspends program execution, use the Debug perspective to perform these tasks:

View the function-call chain
Manipulate variable values
View register values in the computer processor

Related concepts

Working with the Debugger

Related tasks

Related references

About the Carbide Debugger

About the Carbide.c++ Debugger

The Carbide.c++ debugger provides these levels of control over a computer program:

Execution of one statement at a time
Suspend execution after reaching a specific point in the program
Suspend execution after changing a specified memory value
Suspend any running thread from the stack crawl in the Debug view

After the debugger suspends program execution, use the Debug perspective to perform these tasks:

View the function-call chain
Manipulate variable values
View register values in the computer processor

Related concepts

Working with the Debugger

Related tasks

Related references

Concepts in Symbian OS Eclipse Development User Guide

Concepts

- - -

- This section of the User Guide provides an overview of the main concepts in - Eclipse to create and build programs for Symbian OS. -

- The Symbian OS plug-ins are a set of Eclipse plug-ins that provide project, - SDK and build support for Symbian OS developers. The plug-ins extend the - functionality provided by Eclipse and the C/C++ Development Toolkit (CDT). -

- The plug-ins simplify Symbian OS development by removing the need to use - command line build tools, and provide a graphical interface to Symbian OS - specific file formats, such as AIF and MBM. -

- The plug-ins provide a new perspective, called the Carbide.c++ Perspective, on - the Eclipse workbench. This perspective enhances the standard CDT C/C++ - perspective by allowing you to select easily the SDKs and build target types - that you want to use for each project. -

- The following topics discuss these concepts in more detail: -

N-Gage Projects

Carbide.c++ supports the importing of N-Gage projects. However, there are some process issues that effect how you can debug game projects on devices. The following provides a high level overview of the process you should follow to successfully import, build, deploy, and debug an N-Gage game on a device.

Importing N-Gage projects

To start, import your game project into Carbide:

Install the N-Gage SDK on your PC
Place your game project inside the N-Gage SDK
In Carbide.c++, click File > Import
Select Symbian OS Bld.inf importer and navigate to your bld.inf file to import it

Building the N-Gage project

Once the game project has been imported, use these steps to create an N-GAGE game file:

Right-click the project and choose Properties to open the Properties for project_name window
In the Carbide.c++ > Carbide Build Configuration > SIS Builder panel, click Add.
In the SIS Properties window: -
1. Specify the project and metadata PKG files to build
2. Enable the Sign sis file with certificate/key pair for each PKG file
3. Select the certificate/key given to you by the Nokia R&D Certificate Service
4. Click OK
-
If using a batch file to build the N-Gage installation, create a new builder within Carbide by opening the Properties for project_name > Builders panel and click New.

Figure 1 - Builders pane in project Properties dialog

Open the Properties for project_name > Builders panel
Click New
Select Program in the Choose configuration type window, click OK

Figure 2 - Properties for N-Gage Builder dialog

In the Properties for New_Builder window - Main tab: -
- Define the builder name in the Name text box
- Specify the Location of the builder of the installation file
- Specify the Working Directory
-
Click OK

The new builder appears in the Builders panel. The build steps are performed in the order they are displayed. Your builder name should appear under the Carbide CPP Project Builder item. If not, use the Up or Down controls to set the build order. -

Figure 4 - Builder dialog with new N-Gage Builder defined

Click OK to close the Properties for project_name window
Build the project and its SISX file by selecting the Project > Build Project menu item

The Console view shows information as the project and it's SISX file are built and then the build of the installation file (N-GAGE).

For On-device Debugging

Deploying the N-Gage project to a device

Once you have an .N-GAGE game file, you need to deploy it on the target device:

Verify that you have a valid developer certificate on the target device given to you by the Nokia R&D Certificate Service. If not, get and install one.
Verify that you have Application TRK installed on the target device. If not, install it now using On-Device Connections > New Connection Wizard > Install remote agents pane.
Manually install the .N-GAGE file on the device

Debugging the Game project

With your game file installed on the device, create a launch configuration for the project. In Carbide:

OpenWindow > Preferences > Run/Debug > Launching preference panel and disable the Build (if required) before launching option
Right-click the project and choose Debug As > Open Debug Dialog to open the Debug window
Create an Application TRK launch configuration -
- In the Connection tab select the COM port used to connect to the device.
- In the Installation tab, verify that the game SISX file is correct
- In the Debug tab, enable the View messges between PC and debug agent on the phone if you want to monitor communications between TRK and Carbide
-
Click Debug

The Debugger launches the game project in the device and halts when it encounters the breakpoint you set.

For Emulator Debugging

Deploying and debugging the N-Gage project on an emulator

With your game file installed to the emulator, create a launch configuration for the project. In Carbide:

Open Window > Preferences > Run/Debug > Launching and disable the Build (if required) before launching option
Right-click the project and choose Debug As > Open Debug Dialog to open the Debug window
Create an Symbian OS Emulation launch configuration
Click Debug to launch the emulator
In the emulator, select File > Open, locate and select the .N-GAGE installation file and click Open to install the project
Open the Installation folder, launch the N-Gage runtime application
In the N-Gage runtime launch the game
If any breakpoint is hit in the game project, the debugger suspends

From this point you can use all of the debugger features to debug the project.

Always refer to the N-Gage documentation for more information on creating, deploying, and debugging N-Gage projects.

N-Gage Projects

Importing N-Gage projects

To start, import your game project into Carbide:

Install the N-Gage SDK on your PC
Place your game project inside the N-Gage SDK
In Carbide.c++, click File > Import
Select Symbian OS Bld.inf importer and navigate to your bld.inf file to import it

Building the N-Gage project

Once the game project has been imported, use these steps to create an N-GAGE game file:

Right-click the project and choose Properties to open the Properties for project_name window
In the Carbide.c++ > Carbide Build Configuration > SIS Builder panel, click Add.
In the SIS Properties window: +
1. Specify the project and metadata PKG files to build
2. Enable the Sign sis file with certificate/key pair for each PKG file
3. Select the certificate/key given to you by the Nokia R&D Certificate Service
4. Click OK
+
If using a batch file to build the N-Gage installation, create a new builder within Carbide by opening the Properties for project_name > Builders panel and click New.

Figure 1 - Builders pane in project Properties dialog

Open the Properties for project_name > Builders panel
Click New
Select Program in the Choose configuration type window, click OK

Figure 2 - Properties for N-Gage Builder dialog

In the Properties for New_Builder window + Main tab: +
- Define the builder name in the Name text box
- Specify the Location of the builder of the installation file
- Specify the Working Directory
+
Click OK

Figure 4 - Builder dialog with new N-Gage Builder defined

Click OK to close the Properties for project_name window
Build the project and its SISX file by selecting the Project > Build Project menu item

The Console view shows information as the project and it's SISX file are built and then the build of the installation file (N-GAGE).

For On-device Debugging

Deploying the N-Gage project to a device

Once you have an .N-GAGE game file, you need to deploy it on the target device:

Verify that you have a valid developer certificate on the target device given to you by the Nokia R&D Certificate Service. If not, get and install one.
Verify that you have Application TRK installed on the target device. If not, install it now using On-Device Connections > New Connection Wizard > Install remote agents pane.
Manually install the .N-GAGE file on the device

Debugging the Game project

With your game file installed on the device, create a launch configuration for the project. In Carbide:

OpenWindow > Preferences > Run/Debug > Launching preference panel and disable the Build (if required) before launching option
Right-click the project and choose Debug As > Open Debug Dialog to open the Debug window
Create an Application TRK launch configuration +
- In the Connection tab select the COM port used to connect to the device.
- In the Installation tab, verify that the game SISX file is correct
- In the Debug tab, enable the View messges between PC and debug agent on the phone if you want to monitor communications between TRK and Carbide
+
Click Debug

The Debugger launches the game project in the device and halts when it encounters the breakpoint you set.

For Emulator Debugging

Deploying and debugging the N-Gage project on an emulator

With your game file installed to the emulator, create a launch configuration for the project. In Carbide:

Open Window > Preferences > Run/Debug > Launching and disable the Build (if required) before launching option
Right-click the project and choose Debug As > Open Debug Dialog to open the Debug window
Create an Symbian OS Emulation launch configuration
Click Debug to launch the emulator
In the emulator, select File > Open, locate and select the .N-GAGE installation file and click Open to install the project
Open the Installation folder, launch the N-Gage runtime application
In the N-Gage runtime launch the game
If any breakpoint is hit in the game project, the debugger suspends

From this point you can use all of the debugger features to debug the project.

Always refer to the N-Gage documentation for more information on creating, deploying, and debugging N-Gage projects.

Debugger Program Execution

This section explains how to work with the debugger in the Carbide IDE to control program execution. The main component of the debugger is the Debug perspective, which shows these items:

Common debugging controls in the Debug view for: -
- Starting the debugger
- Running the program
- Stepping into, out of, or over routines
- Suspending, resuming, or terminating program execution
- Disconnecting the debugger
- Restarting the debugger
-
Variable information in the Variables view—see the variables in the executing code, their values, and their types
Breakpoint information in the Breakpoints view—see the breakpoints, conditional breakpoints, and breakpoint actions
Source code—see the source code under debugger control

Related concepts

Related references

Debugger Program Execution

This section explains how to work with the debugger in the Carbide IDE to control program execution. The main component of the debugger is the Debug perspective, which shows these items:

Common debugging controls in the Debug view for: +
- Starting the debugger
- Running the program
- Stepping into, out of, or over routines
- Suspending, resuming, or terminating program execution
- Disconnecting the debugger
- Restarting the debugger
+
Variable information in the Variables view—see the variables in the executing code, their values, and their types
Breakpoint information in the Breakpoints view—see the breakpoints, conditional breakpoints, and breakpoint actions
Source code—see the source code under debugger control

Related concepts

Related references

Carbide.c++ User Guide

Version 2.1.0, June, 2009

Version 2.2.0, August, 2009

Suspending and Resuming a Debug Session

Once you've started a debug session, the Debug view provides controls to both suspend and resume program execution under debugger control. The following items describe the commands for:

Suspending a program
Resuming a program

Suspending a program

Use the Suspend command () to stop program execution during a debugging session.

To suspend a running program:

Select the thread in the Debug view to suspend
Click the Suspend () button, or right-click the thread and select Suspend

Resuming a program

Use the Resume command () to continue executing a suspended debugging session. If the debugging session is already active, use this command to switch view from the Thread window to the executing program.

The ways you can resume a program include:

Click the Resume button () in the Debug view

Right-click the thread in the Debug view and select Resume from the context menu

Select Run > Resume from the menu bar

NOTE If the Debug view loses focus, the Resume control will appear disabled. To regain focus, select a thread in the Debug view to update the tool bar and reactivate the Resume control.

Other references

Debugging overview

Suspending and Resuming a Debug Session

Once you've started a debug session, the Debug view provides controls to both suspend and resume program execution under debugger control. The following items describe the commands for:

Suspending a program
Resuming a program

Suspending a program

Use the Suspend command () to stop program execution during a debugging session.

To suspend a running program:

Select the thread in the Debug view to suspend
Click the Suspend () button, or right-click the thread and select Suspend

Resuming a program

The ways you can resume a program include:

Click the Resume button () in the Debug view

Right-click the thread in the Debug view and select Resume from the context menu

Select Run > Resume from the menu bar

NOTE If the Debug view loses focus, the Resume control will appear disabled. To regain focus, select a thread in the Debug view to update the tool bar and reactivate the Resume control.

Other references

Debugging overview

Starting and Terminating a Debug Session

Once you've started a debug session, the Debug view provides controls to both terminate and restart the session. The following items describe the commands for:

Starting a session
Terminating a session
Restarting a session

Starting a session

Use the Debug command () to execute a program under debugger control using the current launch configuration settings.

If the project does not already have a launch configuration, the New Launch Configuration Wizard will automatically create one for emulator targets or ask for additional information to create one. It will generate a default name for the launch configuration and add it to the list of available launch configurations for the project. Once complete and saved the debug session is launched. If a launch configuration is already available, the Debug command launches the last launch configuration used by the project.

To create new launch configurations where none previously existed or launch the last one created:

Click the Debug button () in the Carbide C/C++ perspective
Select Run > Debug from the menu bar

To launch a specific launch configuration:

Right-click the project's EXE file in the C/C++ Projects view and select Debug As > Project_Name from the context menu

Terminating a session

Use the Terminate command () to stop or halt a program based on the type of debugging session underway. Terminate behavior includes:

Emulator - terminates program execution and ends the debug session
Application TRK or System TRK - kills the process on the device and ends the debug session. To terminate without killing the process, use Disconnect instead.
Stop-mode soft attach - suspends the attached process while other processes continue to run on the device. If only a single process is running on the device, the device CPU is suspended. Once the CPU is suspended you must launch a new debug session to resume the device CPU.

This behavior differs from suspending a program, as this temporarily suspends execution.

NOTE If the Debug view loses focus, the Terminate control will appear disabled. To regain focus, select a thread in the Debug view to update the tool bar and reactivate the Terminate control.

Restarting a session

Use the Restart command () after stopping program execution. The debugger goes back to the beginning of the program and begins execution again. This behavior is equivalent to killing execution, then starting a new debugging session.

Other references

Debugging overview

Starting and Terminating a Debug Session

Once you've started a debug session, the Debug view provides controls to both terminate and restart the session. The following items describe the commands for:

Starting a session
Terminating a session
Restarting a session

Starting a session

Use the Debug command () to execute a program under debugger control using the current launch configuration settings.

To create new launch configurations where none previously existed or launch the last one created:

Click the Debug button () in the Carbide C/C++ perspective
Select Run > Debug from the menu bar

To launch a specific launch configuration:

Right-click the project's EXE file in the C/C++ Projects view and select Debug As > Project_Name from the context menu

Terminating a session

Use the Terminate command () to stop or halt a program based on the type of debugging session underway. Terminate behavior includes:

Emulator - terminates program execution and ends the debug session
Application TRK or System TRK - kills the process on the device and ends the debug session. To terminate without killing the process, use Disconnect instead.
Stop-mode soft attach - suspends the attached process while other processes continue to run on the device. If only a single process is running on the device, the device CPU is suspended. Once the CPU is suspended you must launch a new debug session to resume the device CPU.

This behavior differs from suspending a program, as this temporarily suspends execution.

NOTE If the Debug view loses focus, the Terminate control will appear disabled. To regain focus, select a thread in the Debug view to update the tool bar and reactivate the Terminate control.

Restarting a session

Other references

Debugging overview

Stepping Over, Into, and Out of Routines

Once you've suspended a program debug session, the Debug view provides controls to walk through program code, including commands for:

Stepping over a routine
Stepping into a routine
Stepping out of a routine

Stepping over a routine

Use the Step Over command () to execute the current statement and advance to the next statement in the source code. If the current statement is a routine call, program execution continues until reaching one of these points:

the end of the called routine
a breakpoint
a watchpoint
an eventpoint that stops execution

To step over a routine:

Click the Step Over button () in the Debug view
Right-click the thread in the Debug view and select Step Over from the Debug contextual menu
Select Run > Step Over from the menu bar

The current statement or routine executes, then program execution stops.

Stepping into a routine

Use the Step Into command () to execute one source-code statement at a time and follow execution into a routine call.

When stepping through a program in a debug session the IDE attempts to match the program counter (PC) location in the executable with a known project source file. If there is no source file associated with the PC the debugger displays in the Debug view the current PC address of the thread (e.g. 0x6002CC11(EUSER.DLL)()) instead of the function name. At this point you can open the Disassembly view to step through the assembler code. This most commonly happens when trying to step into Symbian OS code. We recommend that you Step Return out of the OS code and back into your project to continue debugging.

Click the Step Into button () in the Debug view
Right-click the thread in the Debug view and select Step Into from the context menu
Select Run > Step Into from the menu bar

After the debugger executes the source-code statement, the current-statement arrow moves to the next statement determined by these rules:

If the executed statement did not call a routine, the current-statement arrow moves to the next statement in the source code.
If the executed statement called a routine, the current-statement arrow moves to the first statement in the called routine.
If the executed statement is the last statement in a called routine, the current-statement arrow moves to the statement that follows the calling routine.

Stepping out of a routine

Use the Step Return command () to execute the rest of the current routine and stop program execution after the routine returns to its caller. This command causes execution to return up the calling chain.

To step out of a routine:

Click the Step Return button () in the Debug view
Right-click the thread in the Debug view, then select Step Return from the context menu
Select Run > Step Return from the menu bar

The current routine executes and returns to its caller, then program execution stops

Other references

Debugging overview

Stepping Over, Into, and Out of Routines

Once you've suspended a program debug session, the Debug view provides controls to walk through program code, including commands for:

Stepping over a routine
Stepping into a routine
Stepping out of a routine

Stepping over a routine

the end of the called routine
a breakpoint
a watchpoint
an eventpoint that stops execution

To step over a routine:

Click the Step Over button () in the Debug view
Right-click the thread in the Debug view and select Step Over from the Debug contextual menu
Select Run > Step Over from the menu bar

The current statement or routine executes, then program execution stops.

Stepping into a routine

Use the Step Into command () to execute one source-code statement at a time and follow execution into a routine call.

Click the Step Into button () in the Debug view
Right-click the thread in the Debug view and select Step Into from the context menu
Select Run > Step Into from the menu bar

After the debugger executes the source-code statement, the current-statement arrow moves to the next statement determined by these rules:

If the executed statement did not call a routine, the current-statement arrow moves to the next statement in the source code.
If the executed statement called a routine, the current-statement arrow moves to the first statement in the called routine.
If the executed statement is the last statement in a called routine, the current-statement arrow moves to the statement that follows the calling routine.

Stepping out of a routine

To step out of a routine:

Click the Step Return button () in the Debug view
Right-click the thread in the Debug view, then select Step Return from the context menu
Select Run > Step Return from the menu bar

The current routine executes and returns to its caller, then program execution stops

Other references

Debugging overview

Debug view

The Debug view provides an overview of the debug session as it relates to the executing program. The target debugging information is shown in a tree hierarchy. The items that appear there include:

Launch instance () - launch configuration name and type
Debugger instance () - debugger name and state
Executable instances () - other executables called by the launch instance
Thread instance () - thread number and state
Stack frame reference () - displays stack frame number, function, filename, and file line number when symbols are available and stack frame number, memory address, and filename when symbols are not available

NOTE The number beside the thread label is a reference counter, not a thread - identification number (TID).

The CDT displays stack frames as child elements. It displays the reason for the suspension beside the thread, (such as end of stepping range, breakpoint hit, and signal received). When a program exits, the exit code is displayed.

In addition to controlling the individual stepping of your programs, you can also control the debug session. You can perform actions such as terminating the session and stopping the program by using the debug launch controls available from Debug view. See Table 1 for details.

Figure 1 shows the Debug view. Table 1 explains the items in the view.

Figure 1 - Debug view

Table 1 Debug view—items

Item	Icon	Explanation
Resume		Click to perform these tasks: - - Continue execution up to the next breakpoint, watchpoint, or eventpoint - Run the program until it exits - Continue execution of a currently stopped program -
Suspend		Click to stop (pause) program execution.
Terminate		Click to terminate program execution. This ends the debugging session.
Disconnect	- - -	Detaches the debugger from the selected process (useful for debugging attached processes). - NOTE After detaching the debugger from an on-device process, closing TRK on the device will also close the process.
Remove All Terminated	- - -	Clears all terminated processes in Debug view.
Restart		Returns the debugger to the beginning of the program and begins execution again. This behavior is equivalent to killing execution, then starting a new debugging session.
Step Over		Click to execute the current line, including any routines, and proceed to the next statement.
Step Into		Click to execute the current line, following execution inside a routine.
Step Return		Click to continue execution to the end of the current routine, then follow execution to the routine’s caller.
Instruction Stepping Mode		Activate to enable instruction stepping mode to examine a program as it steps into disassembled code.

Other references

Debugging overview

Debug view

Launch instance () - launch configuration name and type
Debugger instance () - debugger name and state
Executable instances () - other executables called by the launch instance
Thread instance () - thread number and state
Stack frame reference () - displays stack frame number, function, filename, and file line number when symbols are available and stack frame number, memory address, and filename when symbols are not available

NOTE The number beside the thread label is a reference counter, not a thread + identification number (TID).

Figure 1 shows the Debug view. Table 1 explains the items in the view.

Figure 1 - Debug view

Table 1 Debug view—items

Item	Icon	Explanation
Resume		Click to perform these tasks: + + Continue execution up to the next breakpoint, watchpoint, or eventpoint + Run the program until it exits + Continue execution of a currently stopped program +
Suspend		Click to stop (pause) program execution.
Terminate		Click to terminate program execution. This ends the debugging session.
Disconnect	+ + +	Detaches the debugger from the selected process (useful for debugging attached processes). + NOTE After detaching the debugger from an on-device process, closing TRK on the device will also close the process.
Remove All Terminated	+ + +	Clears all terminated processes in Debug view.
Restart		Returns the debugger to the beginning of the program and begins execution again. This behavior is equivalent to killing execution, then starting a new debugging session.
Step Over		Click to execute the current line, including any routines, and proceed to the next statement.
Step Into		Click to execute the current line, following execution inside a routine.
Step Return		Click to continue execution to the end of the current routine, then follow execution to the routine’s caller.
Instruction Stepping Mode		Activate to enable instruction stepping mode to examine a program as it steps into disassembled code.

Other references

Debugging overview

Attach to Process Launch Configuration

Use the Symbian OS Attach to Process launch configuration to attach the debugger to an already running Symbian OS process or thread on a target device from within any project. This is useful for debugging servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate as one example.

Attaching to a process requires a both target device running the Symbian OS and the presence of a TRK debug agent on the device. You can also use the Symbian OS Data view to attach to a process while debugging. However, you can not attach to a process running on an emulator.

If the New Launch Configuration Wizard created the Attach to Process launch configuration no changes are usually needed. The Attach to Process options match those of System TRK with one additional step, selection of the process to debug in the Attach to Process dialog.

To modify the launch configuration settings, select the Run > Open Debug Dialog... menu option to open the Debug dialog. Select the Attach to Process 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. Attach to Process launch configuration in the Debug dialog

The Attach to Process 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 Debugger tab defines debug configurations, such as entry point to begin debugging, target options, and instruction set.
The ROM Log tab allows you to specify where the ROM log file is stored and the Epoc32 directory.
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

Launch Configuration Overview

Attach to Process Launch Configuration

Figure 1. Attach to Process launch configuration in the Debug dialog

The Attach to Process 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 Debugger tab defines debug configurations, such as entry point to begin debugging, target options, and instruction set.
The ROM Log tab allows you to specify where the ROM log file is stored and the Epoc32 directory.
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

Launch Configuration Overview

Customizing Launch Configurations

Use the Debug dialog to customize launch configurations previously created in a project, or to create new launch configurations. Ideally, you should create new launch configurations using the New Launch Configuration Wizard. Doing this will ensure that the project's default launch configuration is valid and can successfully launch a debug session. However, not all default launch configurations satisfy all the needs of a project, so being able to modify a launch configuration's options can allow you to customize how the project is launched and debugged based on the needs of that project.

There are two methods for setting up a launch configuration, including:

Default launch configuration (recommended) — the New Launch Configuration Wizard automatically sets up a default launch configuration to run or debug the project on the first Run or Debug execution. This provides a quick and easy method to start running or debugging a project without the inconvenience of setting a lot of options. The default launch configuration can always be edited later as the project launch requirements change.
Custom launch configuration— enables you to create or modify a launch configuration to suit the needs of the project. To modify a launch configuration, create one using the New Launch Configuration Wizard, then enable the Advanced Options option on the New Launch Configuration page before you click Finish. This opens the Debug dialog so you can immediately customize the new launch configuration's options.

NOTE To see if a project already has a launch configuration, open a Run or Debug window using the Run > Open Run Dialog... or Run > Open Debug Dialog... menu items. - -

In the event that the default launch configuration settings need to be changed, it is possible to edit them in the Debug window, or create a new launch configuration for the project that deviates from the default settings.

Creating a Custom Launch Configuration

Open the Run or Debug launch configuration window -
- Select the Run> Open Run Dialog... or Run > Open Debug Dialog... menu item -
  The appropriate Run or Debug launch configuration window appears (Figure 1).
  -
-

-
Figure 1 - Initial blank Debug launch configuration window
-
Select a type of launch configuration (for example, Symbian OS Emulation), then click the New launch configuration icon to create a new - configuration of that type. -
A new configuration appears in the Configuration list under the - appropriate section using the project name and target to create the configuration name.
-
NOTE By default, when you click New, the project information is used to fill in the Project and Process to launch text boxes. You normally should not have to edit these for a run/debug a project. If a bld.inf has multiple MMPS then the first executable named in the list of MMP files is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field.
-
-
Figure 2 - New launch configuration with name and settings filled in (emulator)
-
View the information to define the project and executable -
Modify or fill in the following fields in the Main tab so the IDE - can setup the configuration properly each time. Typically when creating - a new executable from a project that has successfully linked, the - fields will be auto-populated and do not need to be modified. The important fields here are:
-
- Name - This is a unique name to identify this launch configuration. It can be any name.
- Project - The project to associate with this launch configuration. Click Browse to select a different project.
- Process to launch - This is the name of the executable that is linked to the project.
-
Modify settings in the other tabs to customize the launch configuration - for the project -
- Environment (Eclipse)
- Debugger
- Executables
- x86 Exceptions
- Arguments (Eclipse)
- Source (Eclipse)
- Common (Eclipse)
-
To debug something outside of the workspace, be sure to import the binary into the Executables view.
-
Click Debug -
The IDE launches the executable. If the launch configuration is set to change perspective, it switches to the specified perspective.
-

Other references

Customizing Launch Configurations

There are two methods for setting up a launch configuration, including:

Default launch configuration (recommended) — the New Launch Configuration Wizard automatically sets up a default launch configuration to run or debug the project on the first Run or Debug execution. This provides a quick and easy method to start running or debugging a project without the inconvenience of setting a lot of options. The default launch configuration can always be edited later as the project launch requirements change.
Custom launch configuration— enables you to create or modify a launch configuration to suit the needs of the project. To modify a launch configuration, create one using the New Launch Configuration Wizard, then enable the Advanced Options option on the New Launch Configuration page before you click Finish. This opens the Debug dialog so you can immediately customize the new launch configuration's options.

NOTE To see if a project already has a launch configuration, open a Run or Debug window using the Run > Open Run Dialog... or Run > Open Debug Dialog... menu items. + +

Creating a Custom Launch Configuration

Open the Run or Debug launch configuration window +
- Select the Run> Open Run Dialog... or Run > Open Debug Dialog... menu item +
  The appropriate Run or Debug launch configuration window appears (Figure 1).
  +
+

+
Figure 1 - Initial blank Debug launch configuration window
+
Select a type of launch configuration (for example, Symbian OS Emulation), then click the New launch configuration icon to create a new + configuration of that type. +
A new configuration appears in the Configuration list under the + appropriate section using the project name and target to create the configuration name.
+
NOTE By default, when you click New, the project information is used to fill in the Project and Process to launch text boxes. You normally should not have to edit these for a run/debug a project. If a bld.inf has multiple MMPS then the first executable named in the list of MMP files is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field.
+
+
Figure 2 - New launch configuration with name and settings filled in (emulator)
+
View the information to define the project and executable +
Modify or fill in the following fields in the Main tab so the IDE + can setup the configuration properly each time. Typically when creating + a new executable from a project that has successfully linked, the + fields will be auto-populated and do not need to be modified. The important fields here are:
+
- Name - This is a unique name to identify this launch configuration. It can be any name.
- Project - The project to associate with this launch configuration. Click Browse to select a different project.
- Process to launch - This is the name of the executable that is linked to the project.
+
Modify settings in the other tabs to customize the launch configuration + for the project +
- Environment (Eclipse)
- Debugger
- Executables
- x86 Exceptions
- Arguments (Eclipse)
- Source (Eclipse)
- Common (Eclipse)
+
To debug something outside of the workspace, be sure to import the binary into the Executables view.
+
Click Debug +
The IDE launches the executable. If the launch configuration is set to change perspective, it switches to the specified perspective.
+

Emulator Launch Configuration

Select the Symbian OS Emulator launch configuration to run or debug executables using an emulator.

If the New Launch Configuration Wizard was used to create a emulator 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 Symbian OS Emulation launch 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 - Emulator launch configuration in Debug dialog

The Debug window provides C/C++ emulator debug options when a Symbian OS Emulation launch configuration is created. The settings included in the Symbian OS Emulation launch configuration are a combination of Carbide, CDT, and Eclipse options. The tabs in the window include:

The Main tab defines the project to be launched. Enter the name of the project containing the class to launch in the project field, and the executable name in the the Executable field and the emulator or host application in the Emulator or host application field.
The Arguments tab (standard CDT page) defines the arguments to be passed to the application and to the virtual machine (if any). You can also specify the working directory to be used by the launched application.
The Environment tab (standard CDT page) defines the environment variable values to use when running or debugging a program. By default, the environment is inherited from the Eclipse runtime. You may override or append to the inherited environment.
The Debugger tab provides common debugger options for the project.
The Executables tab allows you to specify which executables are debugged by your project.
The x86 Exceptions tab lists all the x86 exceptions that the debugger can catch.
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 and specify which perspectives become active when the launch configuration is launched.

Other references

Launch Configuration Overview

Emulator Launch Configuration

Select the Symbian OS Emulator launch configuration to run or debug executables using an emulator.

Figure 1 - Emulator launch configuration in Debug dialog

The Main tab defines the project to be launched. Enter the name of the project containing the class to launch in the project field, and the executable name in the the Executable field and the emulator or host application in the Emulator or host application field.
The Arguments tab (standard CDT page) defines the arguments to be passed to the application and to the virtual machine (if any). You can also specify the working directory to be used by the launched application.
The Environment tab (standard CDT page) defines the environment variable values to use when running or debugging a program. By default, the environment is inherited from the Eclipse runtime. You may override or append to the inherited environment.
The Debugger tab provides common debugger options for the project.
The Executables tab allows you to specify which executables are debugged by your project.
The x86 Exceptions tab lists all the x86 exceptions that the debugger can catch.
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 and specify which perspectives become active when the launch configuration is launched.

Other references

Launch Configuration Overview

Launch Configuration Overview

A launch configuration defines the operational settings used by the Carbide.c++ tools to launch and debug programs. A project must have at least one launch configuration, and can have as many as necessary. This enables you to develop and debug your project using various compilers (GCCE and RVCT) and different targets (emulator and on-device) as each launch configuration can be tailored to fit the intended target.

Creating a Launch Configuration

To create a default launch configuration for a project use the New Launch Configuration Wizard. Using this method ensures that you have a working launch configuration for the project. You can invoke the New Launch Configuration Wizard for projects lacking a launch configuration by selecting the Run > Debug (F11) or Run > Run (CTRL+F11) menu options, or clicking the Run () or Debug () icons in the toolbar. If a project already has a defined launch configuration, selecting the Run or Debug command calls the previously defined and last used launch configuration, bypassing the wizard entirely.

For emulator projects the wizard simply gathers the data it needs from the project and creates an emulator launch configuration and launches the emulator. For on-device targets, more information is required, so the wizard asks for the missing information it needs, creates the launch configuration, then downloads the executable to the device and launches it. Once the emulator or device is loaded with the executable, the debug session commences.

You can customize any project launch configuration afterward using the Debug dialog as necessary.

Available Launch Configurations

Launch configurations come in several varieties, each designed for a specific purpose. You must choose one at the very start of the New Launch Configuration Wizard, so knowing the differences between them is important. Currently, the types to choose from include:

Symbian OS Application—used to run or debug executables.
Symbian OS Appication TRK —used to run or debug applications on a target device using the Application TRK on-device debug agent. Application TRK is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian OS installation file to the phone and install it prior to launching.
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.

NOTE The specific launch configuration availability is determined by the Carbide.c++ edition you are using.

Other references

Creating Projects Overview
New Launch Configuration Wizard
Debug dialog

Launch Configuration Overview

Creating a Launch Configuration

You can customize any project launch configuration afterward using the Debug dialog as necessary.

Available Launch Configurations

Symbian OS Application—used to run or debug executables.
Symbian OS Appication TRK —used to run or debug applications on a target device using the Application TRK on-device debug agent. Application TRK is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian OS installation file to the phone and install it prior to launching.
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.

NOTE The specific launch configuration availability is determined by the Carbide.c++ edition you are using.

Other references

Creating Projects Overview
New Launch Configuration Wizard
Debug dialog

Emulation Main page

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

The behavior that occurs when launching a debug session varies based upon the SDK. Normally, starting a debug session launches the emulator (epoc.exe) and you must then navigate to your application and open it. However, starting a debug session for an .exe file will, in most cases, launch the .exe directly. This starts the emulator and then opens your application automatically. Note that some SDKs do not support this behavior. In those cases you must still open your application in the emulator manually.

Figure 1. Main page (Emulation shown)

Table 1. Emulator Main page —items

diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/pages_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/pages_overview.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/pages_overview.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,28 +1,28 @@ - - - - - - -Carbide Configuration Pages - - - -

Configuration Pages

The pages in the Debug dialog used to set options for the various launch configurations include:

Arguments (standard CDT page)
Debugger
Executables
File Transfer
Installation
Main
ROM Image
ROM Log
x86 Exceptions
Source (standard CDT page)
Common (standard CDT page)

- - - + + + + + + +Carbide Configuration Pages + + + +

Configuration Pages

The pages in the Debug dialog used to set options for the various launch configurations include:

Arguments (standard CDT page)
Debugger
Executables
File Transfer
Installation
Main
ROM Image
ROM Log
x86 Exceptions
Source (standard CDT page)
Common (standard CDT page)

+ + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/run_mode.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/run_mode.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/run_mode.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,33 +1,33 @@ - - - - -Application TRK Launch Configuration - - - - -

Application TRK Launch Configuration (Run-mode)

Select the Symbian OS Application TRK launch configuration to debug or run applications on a target device using the Application TRK on-device debug agent. Application TRK is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian OS installation file to the phone and install it prior to launching.

If the New Launch Configuration Wizard was used to create the Application 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 Application 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. Application TRK launch configuration in the Debug dialog

The Application TRK 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 Arguments tab (standard CDT page) lets you specify the program arguments that an application uses.
The Debugger tab defines debug configurations, such as entry point to begin debugging and target options.
The File Transfer tab displays an auto-populated list of files that the IDE transfers to the target device at the start of each launch.
The Installation tab specifies the .sis file(s) to install on the target device.
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

Launch Configuration Overview

- - - + + + + +Application TRK Launch Configuration + + + + +

Application TRK Launch Configuration (Run-mode)

Figure 1. Application TRK launch configuration in the Debug dialog

The Application TRK 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 Arguments tab (standard CDT page) lets you specify the program arguments that an application uses.
The Debugger tab defines debug configurations, such as entry point to begin debugging and target options.
The File Transfer tab displays an auto-populated list of files that the IDE transfers to the target device at the start of each launch.
The Installation tab specifies the .sis file(s) to install on the target device.
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

Launch Configuration Overview

+ + + diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/sophia.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,32 +1,32 @@ - - - - -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

Launch Configuration Overview

- - - + + + + +Sophia Launch Configuration + + + + +

Sophia Launch Configuration

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

Launch Configuration Overview

+ + + diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,31 +1,31 @@ - - - - -System TRK Launch Configuration - - - - -

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.

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

The System TRK 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 Debugger tab defines debug configurations, such as entry point to begin debugging and target options.
The ROM Image tab allows you to define startup options and ROM image 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

Launch Configuration Overview

- - - + + + + +System TRK Launch Configuration + + + + +

System TRK Launch Configuration (Stop-mode)

Figure 1. System TRK launch configuration in the Debug dialog

The System TRK 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 Debugger tab defines debug configurations, such as entry point to begin debugging and target options.
The ROM Image tab allows you to define startup options and ROM image 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

Launch Configuration Overview

+ + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/trace32.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/trace32.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/trace32.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,31 +1,31 @@ - - - - -Trace32 Launch Configuration - - - - -

Trace32 Launch Configuration

Select the Symbian OS Trace32 launch configuration (only available in OEM Edition) to debug any Symbian OS module on a target using a JTAG connection. The external Trace32 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 a Trace32 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 Trace32 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. Trace32 launch configuration in the Debug dialog

The Trace32 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 Debugger tab defines debug configurations, such as entry point to begin debugging and target options.
The ROM Image tab allows you to define startup options and ROM image 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

Launch Configuration Overview

- - - + + + + +Trace32 Launch Configuration + + + + +

Trace32 Launch Configuration

Figure 1. Trace32 launch configuration in the Debug dialog

The Trace32 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 Debugger tab defines debug configurations, such as entry point to begin debugging and target options.
The ROM Image tab allows you to define startup options and ROM image 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

Launch Configuration Overview

+ + + diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Mon Aug 10 15:50:55 2009 -0500 @@ -10,7 +10,7 @@

New Launch Configuration Wizard

The New Launch Configuration Wizard launches when no launch configuration exists for a project. Wherever possible the New Launch Configuration wizard gathers the information from the project and asks additional questions based on the type of launch configuration chosen. For example, a launch configuration using Application TRK requires different information than one targeted for System TRK.

@@ -100,17 +100,17 @@

Figure 8 - New Launch Configuration page

Trace32 Initialization Settings

Use the Trace32 Initialization Settings page to specify the initialization script and target processor of the target device.Enter the Trace32 Initialization Script and choose the Target Processor, then click Next.

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.

Figure 11 - Symbian ROM Image Settings page

diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wnd_debug_configuration.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,66 +1,66 @@ - - - - - - -Carbide Debug dialog - - - -

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

Launch Configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Icon	Item	Explanation
	New Launch Configuration	Click the New Launch Configuration icon to add a launch configuration to the configurations list. Default information based upon the project is automatically entered into the various text boxes. - NOTE Normally, you should not have to change any of the default text box entries unless you are creating multiple debug launch configurations for the same project.
	Duplicate	Click the Duplicate icon to duplicate the currently selected launch configuration.
	Delete selected launch configuration(s)	Click the Delete icon to remove the currently selected configuration from the Configurations list.
	Collapse	Click the Collapse icon to collapse expanded lists of launch configurations.
	Filter launch configurations...	Click the Filter icon to select filter options that control which launch configurations appear in the list. Filter options include: - - Filter Closed Projects - Filter Deleted/Unavailable Projects - Filter Configuration Types - Apply Window Working Set(s) - Filtering Preferences... -

Other references

- - + + + + + + +Carbide Debug dialog + + + +

Debug dialog

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

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

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Icon	Item	Explanation
	New Launch Configuration	Click the New Launch Configuration icon to add a launch configuration to the configurations list. Default information based upon the project is automatically entered into the various text boxes. + NOTE Normally, you should not have to change any of the default text box entries unless you are creating multiple debug launch configurations for the same project.
	Duplicate	Click the Duplicate icon to duplicate the currently selected launch configuration.
	Delete selected launch configuration(s)	Click the Delete icon to remove the currently selected configuration from the Configurations list.
	Collapse	Click the Collapse icon to collapse expanded lists of launch configurations.
	Filter launch configurations...	Click the Filter icon to select filter options that control which launch configurations appear in the list. Filter options include: + + Filter Closed Projects + Filter Deleted/Unavailable Projects + Filter Configuration Types + Apply Window Working Set(s) + Filtering Preferences... +

Other references

+ + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/debugger_settings.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/debugger_settings.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/debugger_settings.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,31 +1,31 @@ - - - - - - -Debugger Settings - - - -

Debugger Settings

The Carbide.c++ debugger settings include:

Common concepts

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

- - - - + + + + + + +Debugger Settings + + + +

Debugger Settings

The Carbide.c++ debugger settings include:

Common concepts

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/bld_config_sos_apptrk_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/bld_config_sos_apptrk_01.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/bld_config_sos_apptrk_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/bld_config_sos_apptrk_02.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/build_target_only.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/build_target_only.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_breakpoints_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_breakpoints_view.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_registers_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_registers_view.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_variables_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/context_menu_variables_view.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/debug_context_menu.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/debug_context_menu.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/icon_project_file_link.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/icon_project_file_link.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/new_launch_config_wiz1.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/new_launch_config_wiz1.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_ROM_log.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_ROM_log.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_emulator_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_emulator_debugger.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_run_mode_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_run_mode_debugger.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_stop_mode_rom_image.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/page_stop_mode_rom_image.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_createsis.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_createsis.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_connection.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_connection.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_debugger.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_exe.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_exe.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_image.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_image.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_main.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_main.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_romlog.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_T32_romlog.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_common.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_common.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_debugger.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_main.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_main.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_source.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_source.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_common.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_common.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_connection.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_connection.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_debugger.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_image.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_image.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_main.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_main.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_romlog.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_romlog.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_source.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_debug_sti_source.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_emulator_main.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_emulator_main.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_env.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_env.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_makesis.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_makesis.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_aif_compiler_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_aif_compiler_01.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_mbm_compiler_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_mbm_compiler_01.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_mif_compiler_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_tool_settings_mif_compiler_01.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_common.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_common.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_connection.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_connection.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_debugger.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_debugger.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_exes.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_exes.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_file_transfer.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_file_transfer.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_installation.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_installation.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_source.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/panel_trk_source.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/perspective_prefs.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/perspective_prefs.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/project_updater.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/project_updater.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/select_folder.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/select_folder.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_restart_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_restart_btn.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_resume_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_resume_btn.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_into_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_into_btn.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_over_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_over_btn.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_return_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_step_return_btn.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_suspend_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_suspend_btn.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_terminate_btn.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_debug_terminate_btn.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_mifdef_editor.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_mifdef_editor.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_remote_connections2.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_remote_connections2.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_sos_processes.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_sos_processes.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_variables.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_variables.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_app_trk_launch_config.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_app_trk_launch_config.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_breakpoint_actions_pref.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_breakpoint_actions_pref.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_debug_stop_mode_overview.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_debug_stop_mode_overview.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_edit_mifdef_icon.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_edit_mifdef_icon.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_exe_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_exe_actions.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_log_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_log_actions.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_mifdef_wizard.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_mifdef_wizard.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_on_device_setup_install_trk.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_on_device_setup_install_trk.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_pause_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_pause_actions.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_properties_cpp_build.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_properties_cpp_build.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_skip_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_skip_actions.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_sound_actions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_sound_actions.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_stop_mode_overview.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/wnd_stop_mode_overview.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/app_trk_installation.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/app_trk_installation.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,71 +0,0 @@ - - - - - - -Installation Pane - - - -

Installation Pane

The Debug or launch configuration windows Installation pane specifies the .sis file to install on the target device when using Application TRK. This is required when using the TRK debug agent with 9.x based SDK’s.

Figure 1 - Debug windows Installation pane

Table 1. Installation pane —items

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Installation file -	Enter the complete path to the .sis or .pkg file to install on the target device or click Browse to use the standard file selection dialog. -
Download directory	The directory on the target device to download the file into before installing it. The default directory value is C:\data\.
Install each launch even if installer file has not changed	Enable this option to force an update of the installed file even if no changes have been detected. This ensures a clean program install for each debug session.
Do not show installer UI on the phone	Use this option to specify if the installer UI on the target device is shown when installing the file. Disabling this option may require interaction with the installer UI on the target device, slowing down the install process. The default setting is on.
Install to drive	A list of common drives where files may be installed to. The default drive setting is C.

- -

To access the Installation Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Installer tab

The Installation pane appears (Figure 1).

Common concepts

Common references

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_debugger.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,73 +0,0 @@ - - - - - - -Debugger Pane - - - -

Debugger Pane

The Debug/Run windows Debugger pane provides control entry point breaks and which consoles are active to show logs.

Figure 1 - Debug windows Debugger tab

Table 1. Debugger pane —items

- - - - - - - - - - - - - - - - - - - - - -

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

- -

To access the Debug window

Select the Run > Debug... menu item

The Debug window appears.

Select a Configuration setting
Click Debugger tab

The Debugger pane appears (Figure 1).

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

Common references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_exceptions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_exceptions.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,59 +0,0 @@ - - - - - - -x86 Exceptions Pane - - - -

x86 Exceptions Pane

The Debug/Run windows x86 Exceptions pane lists all the exceptions that the debugger is able to catch. If you want the debugger to catch all the exceptions, enable all of the options in this view. However, if you prefer to handle only certain exceptions, enable only those options that reflect the exceptions you prefer to handle.

Figure 1 - x86 Exceptions pane

Table 1. x86 Exceptions pane —items

- - - - - - - - - - - - - -

Item	Explanation
Check All	Enables catching all exceptions.
Clear All	Disables catching all exceptions.

To access the x86 Exceptions pane

Select the Run > Run... or Run > Debug... menu item

The Debug window (Figure 1) appears.

Select a Configuration setting
Click x86 Exceptions tab

The x86 Exceptions pane appears.

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

Common references

- - - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_main.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_main.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,52 +0,0 @@ - - - - - - -Main Pane (Emulator) - - - -

Main Pane (Emulator)

The emulator Main pane defines the process to be launched by the emulator.

Figure 1 - Debug windows emulator's Main tab

Table 1. Emulator Main pane —items

- - - - - - - - - - - - - -

Item	Explanation
Project	The project to associate with this debug launch configuration. Click Browse to select a different project.
Process to launch	The path to the emulator or executable to launch. For Symbian OS 9.1 the emulator path is required. For Symbian OS 9.2 and later the path to the executable should be used. Click Browse to select a different emulator.

- -

To access the Main Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS System emulator configuration in the Configurations list
Click Main tab

The Main pane appears (Figure 1).

Other references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_overview.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,35 +0,0 @@ - - - - - - -Emulator Overview - - - -

Emulator Overview

The Debug or launch configuration window provides C/C++ emulator debug options when a Symbian OS Emulation launch configuration is created. The settings included in the Symbian OS Emulation launch configuration are a combination of Carbide, CDT, and Eclipse options. The tabs in the window include:

The Main tab defines the project to be launched. Enter the name of the project containing the class to launch in the project field, and the executable name in the the Executable field and the emulator or host application in the Emulator or host application field.
The Arguments tab (standard CDT page) defines the arguments to be passed to the application and to the virtual machine (if any). You can also specify the working directory to be used by the launched application.
The Environment tab (standard CDT page) defines the environment variable values to use when running or debugging a program. By default, the environment is inherited from the Eclipse runtime. You may override or append to the inherited environment.
The Debugger tab provides common debugger options for the project.
The Executables tab allows you to specify which executables are debugged by your project.
The x86 Exceptions tab lists all the x86 exceptions that the debugger can catch.
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 and specify which perspectives become active when the launch configuration is launched.

Figure 1 - Debug or launch configuration window

Other references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_connection.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_connection.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,81 +0,0 @@ - - - - - - -Connection Pane - - - -

Connection Pane

The Connection pane specifies the method used to transfer files to the target device. Once a Serial Port type is chosen, the remaining options contain default values for the specific connection type. Users can change these remaining options to match the target device's communication specifications.

Figure 1 - Debug windows Connection pane

Table 1. Connection pane —items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Serial Port	Select the serial port option to use for this launch or launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. Note that for USB and BT can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device. - If you are using a USB connection, the connected phone's name should appear in the menu to help identify which port is being used.
Baud Rate	Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).
Data Bits	Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.
Parity	Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.
Stop Bits	Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 1.
Flow Control	Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.

- -

To access the Connection Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Connection tab

The Connection pane appears (Figure 1).

Common concepts

Common tasks

Common references

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_executables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_executables.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,73 +0,0 @@ - - - - - - -Executables Pane - - - -

Executables Pane

The Executables pane specifies which executables to debug with your project based on the chosen rule. The Executables pane gives you project level control over the executables associated with it. The pane shows all the executables in the workspace or those imported into the Executables view from outside the workspace that can be debugged by this project. See the Executables view for information on controlling executables from the workspace.

Figure 1 - Debug windows Executables pane

Table 1. Executable pane —items

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which govern the executable support used by this project for debugging purposes. The options include: - - Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. - Executables built by this project — shows only the executables built by this project using the specified SDK - Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. - All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. - -
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

To access the Executables Pane

Select the Run > Open Debug Dialog... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Executables tab

The Executables pane appears (Figure 1).

Common concepts

Common references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_file_transfer.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_file_transfer.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,85 +0,0 @@ - - - - - - -TRK File Transfer Pane - - - -

File Transfer Pane

The File Transfer pane displays an auto-populated list of files for System TRK that the IDE transfers to the target device at the start of each launch. Users can add, edit, or delete files in the list. By default, any file added is automatically checked for downloading to the device. Users can uncheck a file to remove it from the download list without removing the file itself. Any missing files are marked with a warning icon and a message appears describing the issue making it easy to see potential file problems prior to attempting a download.

System TRK users can use this panel to download any type of file, like bitmaps, HTML, sounds, and more, to the phone and applicable to Application TRK for transfering any files outside of the installation file.

Figure 1 - Debug windows File Transfer pane

Table 1. File Transfer pane —items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
File transfer list	The File transfer list displays the project files that are moved to the target device for launch and debugging purposes. It contains these columns: - - Enabled—a checkmark indicates that the IDE should transfer the specified file to the target directory. If unchecked, do not transfer the file. - File to transfer—the path and filename to a file on the host machine to be transfered - Target path—the path to the target directory where transfered files are placed on the device -
Add	Click to add a file to the file transfer list.
Edit...	Click to edit the selected file in the file transfer list.
Remove	Click to remove the selected file from the file transfer list.
Select All	Click to select all the files in the file transfer list.
Deselect All	Click to unselect all the files in the file transfer list.

- -

To access the File Tansfer Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click File Transfer tab

The File Transfer pane appears (Figure 1).

Common concepts

Common tasks

Common references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_debugger.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,133 +0,0 @@ - - - - - - -Debugger panes for TRK - - - -

Debugger panes for TRK

The Debug/Run windows Debugger panes for TRK provides control over entry points, message handling, and instruction set default settings.

Different options are available in the Debugger pane based on the type of TRK launch configuration, including:

Run mode debugging
Stop mode debugging

Run-mode Debugger pane

In run-mode you can control message handling and instruction sets.

Figure 1 - Debug windows Debugger pane for run mode debugging

Table 1. Debugger pane — run-mode options

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
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	When checked, show the contents of any program output in the TRK Progam Output Console in a Console view.
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 pane

In stop-mode 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 2 - Debug windows Debugger pane for stop mode debugging

Table 2. Debugger pane — stop-mode options

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

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

- -

To access the Debugger Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Debugger tab

The Debugger pane appears (Figure 1).

Common concepts

Common references

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_main.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_main.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,62 +0,0 @@ - - - - - - -Main Pane - - -

Main Pane

The Main pane defines the project and the process to launch on the target device.

Figure 1 - Debug windows Main pane

Table 1. Main pane —items

- - - - - - - - - - - - - -

Item	Explanation
Project	The project to associate with this launch configuration. Click Browse to select a different project.
Remote process to launch	The absolute path of the remote executable to launch on the target device. The binary to debug may be stored on one of several memory locations, the most common are: - - RAM (default) — programs running in RAM are launched from c:\sys\bin\ - ROM — programs running in ROM are launched from z:\sys\bin\ - Memory cards — programs running on a memory card are launched from e:\sys\bin\ - - In the event a program is not launching, verify that the path is correct for the memory location where the binary resides. -

Item

Explanation

Project

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

Remote process to launch

The absolute path of the remote executable to launch on the target device. The binary to debug may be stored on one of several memory locations, the most common are:

RAM (default) — programs running in RAM are launched from c:\sys\bin\
ROM — programs running in ROM are launched from z:\sys\bin\
Memory cards — programs running on a memory card are launched from e:\sys\bin\

In the event a program is not launching, verify that the path is correct for the memory location where the binary resides.

- -

To access the Main Pane

Select the Run > Debug... menu item

The Debug window appears.

Select a Symbian OS Application TRK configuration in the Configurations list
Click Main tab

The Main pane appears (Figure 1).

Common concepts

Common references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/run_mode_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/run_mode_overview.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,42 +0,0 @@ - - - - - - -Run-mode Overview - - - -

Run-mode Overview

The Debug or launch configuration window provides C/C++ debugger options for on-device debugging. On-device debugging uses a program called Terminal Resident Kernel (TRK) to communicate between Carbide and the device. On-device debugging is supported by creating one of the following debug launch configurations:

Symbian OS Application TRK—supports application debugging only
Symbian OS System TRK—supports both application and limited ROM debugging (not available in the Developer Edition)

The settings included in the TRK launch configurations are a combination of Carbide, CDT, and Eclipse options. Once a suitable Symbian OS debug launch configuration is defined the tabs in the window include:

The Main tab defines the project to be launched. Enter the name of the project containing the class to launch in the project field, and the executable name in the Executable field and the remote process to launch on the device.
The Arguments tab (standard Eclipse page) defines any arguments to be passed to the process to launch.
The Debugger tab provides common debugger options for the project.
The Connection tab specifies the method used to transfer files to the target device. This is where you specify the COM port if the connection is via Bluetooth or USB.
The File Transfer tab displays a list of files to transfer to the target device at the start of each launch. This is used primarily by System TRK to transfer files to a phone for debugging.
The Installation tab (shown in Application TRK only) defines where programs are installed on the target device. This is where you specify the SIS file to be uploaded for Application TRK.
The Executables tab allows you to specify which executables within your project to debug.
The ROM Log tab (shown in System TRK only) specifies where the ROM log file is stored and the Epoc32 directory.
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 and specify which perspectives become active when the launch configuration is launched.

Figure 1 - Debug/Run window for on-device debugging (Application TRK version)

Other references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/stop_mode_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/stop_mode_overview.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,33 +0,0 @@ - - - - - - -Stop-mode Overview - - - -

Stop-mode Overview

The Debug or launch configuration window 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. The tabs in the window include:

The Main tab defines the project to be launched. Enter the name of the project containing the class to launch in the project field, and the executable name in the Executable field to launch on the device.
The Connection tab specifies the method used to transfer files to the target device.
The Debugger tab provides control over common Carbide.c++ debugger capabilities.
The ROM Image tab allows you to define startup options and ROM image download information.
The Executables tab allows you to specify which executables within your project to debug.
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 and specify which perspectives become active when the launch configuration is launched.

Figure 1 - Debug or launch configuration window for stop mode debugging

Other references

- - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/stop_mode_rom_image.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/stop_mode_rom_image.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,73 +0,0 @@ - - - - - - -ROM Image pane - - - -

ROM Image pane

Use the ROM Image tab to define startup options and ROM image download information.

Figure 1 - ROM Image pane in launch configuration

Table 4. Launch configuration window—ROM Image tab items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
Symbian Epoc32 Directory	Enter or browse to the epoc32 directory for the Symbian OS kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

Other references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/sys_trk_rom_log.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/sys_trk_rom_log.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,47 +0,0 @@ - - - - - -ROM Log page - - - -

ROM Log page

Use the ROM Log page to specify where the ROM log file is stored and the Epoc32 directory.

Figure 1. ROM Log page

Table 1. ROM Log page—items

- - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Parse Rom Log File	Activate 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.
Symbian Rom Log File	In the Symbian Rom Log File 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 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	Activate the Log unresolved modules option 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.

Related tasks

Stop Mode On-Device Debugging Preconditions

- - - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm Mon Aug 10 15:50:55 2009 -0500 @@ -50,7 +50,7 @@

diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/perspective_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/perspective_debug.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/perspective_debug.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,52 +1,52 @@ - - - - - - -Debug perspective - - - - -

Debug perspective

The Carbide.c++ -Debug perspective is where you debug programs running on an emulator or a target device. The default views include:

Debug view - displays information about a suspended process during a debug session
Variables view - allows manipulation of variables used in source code
Breakpoints view - allows manipulation of breakpoints and watchpoints
Symbian OS Data view - shows kernel data in the Symbian OS running on the device being debugged
Executables view - provides a dynamic list of executables and their related source files
Editor view - one or more source code editor windows
Outline view - displays an outline of a structured C/C++ file that is currently open in the - editor view
Console view - displays the output of a process, like the execution of your program, or other outputs
Tasks view - displays tasks that you manually add

And can include:

Memory view - allows you to monitor and modify process memory
Disassembly view - displays the assembly code of the source code currently being debugged
Expressions view - used to monitor and manipulate global and local variables, structure members, and array elements
Modules view - uses the Symbolics Loading option to show modules loaded during a debug session
Registers view - shows general, FPU, or host-specific registers of the host computer or target device

Figure 1. Debug perspective used by Carbide.c++

NOTE Click the icon to show additional options that may not be visible in the perspective view.

For more information on perspectives see Workbench User Guide > Concepts > Perspectives, and for views see C/C++ Development User Guide > Reference -> C/C++ Views and Editors.

Related references

- - - + + + + + + +Debug perspective + + + + +

Debug perspective

The Carbide.c++ +Debug perspective is where you debug programs running on an emulator or a target device. The default views include:

Debug view - displays information about a suspended process during a debug session
Variables view - allows manipulation of variables used in source code
Breakpoints view - allows manipulation of breakpoints and watchpoints
Symbian OS Data view - shows kernel data in the Symbian OS running on the device being debugged
Executables view - provides a dynamic list of executables and their related source files
Editor view - one or more source code editor windows
Outline view - displays an outline of a structured C/C++ file that is currently open in the + editor view
Console view - displays the output of a process, like the execution of your program, or other outputs
Tasks view - displays tasks that you manually add

And can include:

Memory view - allows you to monitor and modify process memory
Disassembly view - displays the assembly code of the source code currently being debugged
Expressions view - used to monitor and manipulate global and local variables, structure members, and array elements
Modules view - uses the Symbolics Loading option to show modules loaded during a debug session
Registers view - shows general, FPU, or host-specific registers of the host computer or target device

Figure 1. Debug perspective used by Carbide.c++

NOTE Click the icon to show additional options that may not be visible in the perspective view.

For more information on perspectives see Workbench User Guide > Concepts > Perspectives, and for views see C/C++ Development User Guide > Reference +> C/C++ Views and Editors.

Related references

+ + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,58 +1,58 @@ - - - - - - -Filter Preferences - - - -

Launch Configuration Filters

The Launch Configuration Filters Preference window provides additional options for filtering out the launch configurations that appear in the list of configurations.

To access the Launch Configurations Filter Window

Select the Run > Open Debug Dialog... menu item

The Debug window appears.

Select the Filter icon in the toolbar above the list of configuration types and defined configurations.

The Preferences (Filtered) window appears (Figure 1).

Figure 1 - Launch Configurations Filter Window

The Launch Configuration Filters panel is used to filter out launch configurations from the list of launch configuration types that appear in the Run or Debug window used to define launch configurations. For example, select the Filter checked launch configuration types option and check the configuration types that you do not want to appear in the Run > Run... or Run > Debug... window, as shown in Figure 2. Then select Run > Debug... and notice that the types you have checked do not appear in the list.

To open the Launch Configurations Filter from Preferences

Select Window > Preferences...
Expand the Run/Debug group
Expand Launching and select Launch Configurations

Figure 2 - Launch Configurations Filter

Related concepts

Related references

Related tasks

- - - + + + + + + +Filter Preferences + + + +

Launch Configuration Filters

The Launch Configuration Filters Preference window provides additional options for filtering out the launch configurations that appear in the list of configurations.

To access the Launch Configurations Filter Window

Select the Run > Open Debug Dialog... menu item

The Debug window appears.

Select the Filter icon in the toolbar above the list of configuration types and defined configurations.

The Preferences (Filtered) window appears (Figure 1).

Figure 1 - Launch Configurations Filter Window

To open the Launch Configurations Filter from Preferences

Select Window > Preferences...
Expand the Run/Debug group
Expand Launching and select Launch Configurations

Figure 2 - Launch Configurations Filter

Related concepts

Related references

Related tasks

+ + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_trk_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_trk_overview.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_trk_overview.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,26 +1,26 @@ - - - - - - -TRK Panel Overview - - - -

TRK Pane Overview

When debugging a remote device using TRK, the following panes appear in the launch configuration window:

Main Pane
Debugger Pane
File Transfer Pane
Executables Pane
Installation Pane
ROM Log (System TRK only)
Source—specifies the location of source files used when debugging a C or C++ application
Common—specifies the location to store your run configuration, how to access it and what perspective to open when running an application

- - - + + + + + + +TRK Panel Overview + + + +

TRK Pane Overview

When debugging a remote device using TRK, the following panes appear in the launch configuration window:

Main Pane
Debugger Pane
File Transfer Pane
Executables Pane
Installation Pane
ROM Log (System TRK only)
Source—specifies the location of source files used when debugging a C or C++ application
Common—specifies the location to store your run configuration, how to access it and what perspective to open when running an application

+ + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_add.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_add.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_add.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,122 +1,122 @@ - - - - - - -Adding, Editing, and Deleting Connections - - - - -

Adding, Editing, and Deleting Connections

Use the Remote Connections view to monitor, create, edit, or remove common remote connection settings.

Edit connection name and type

Use the Edit connection name and type page to assign a name and connection type to the new connection setup.

Figure 1 - New Connection wizard Edit connection name and type page

Table 1. Edit connection name and type page - options

- - - - - - - - - - - - - - - - - -

Item	Explanation
Connetion Name	Enter a name for the connection.
Conection Type	Select the type of connection this setup will use.
Supported Services	Shows a list of services supported by the connection type chosen.

Set Connection Settings pane

Use the Set Connection Settings pane to compare the version of remote agent installed on the device with the latest version available for Carbide. In this pane you can:

Set the device OS used by the device and supported by the selected remote agent
Allow easy serial port selection when connecting to a device
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

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Serial Port	A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
Baud Rate	a dropdown list of baud rates common to serial connections.
Device OS	A dropdown list of device OSes that are supported by the remote agent software. Select the OS used by the device before running a check.
Select a service to test	Click to select a listed service for testing.
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. - 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. - - If a connection fails, the errors normally fall into these two categories: - - connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response. - TRK not responding - this indicates that the COM port is open but TRK is not responding. First, verify that TRK is up and running on the device. Second, TRK may be listening on a different COM port, so choose another named COM port and try again. - -

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

- - - - - - - - - - - - - - - - - -

Item	Explanation
Install remote agents	A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 2.8.7. - Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.
Save	Click Save to store a local copy of the currently selected TRK to disk. You can then manually install the file to your devices using the method of your choice.
Install	Click Install to download and install the TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete. - NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Item

Explanation

Install remote agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 2.8.7.

Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.

Save

Click Save to store a local copy of the currently selected TRK to disk. You can then manually install the file to your devices using the method of your choice.

Install

Click Install to download and install the TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete.

NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Related references

On-Device Setup
Install latest TRK

- - - - + + + + + + +Adding, Editing, and Deleting Connections + + + + +

Adding, Editing, and Deleting Connections

Use the Remote Connections view to monitor, create, edit, or remove common remote connection settings.

Edit connection name and type
Set Connection Settings pane
Install Remote Agents pane

Edit connection name and type

Use the Edit connection name and type page to assign a name and connection type to the new connection setup.

Figure 1 - New Connection wizard Edit connection name and type page

Table 1. Edit connection name and type page - options

+ + + + + + + + + + + + + + + + + +

Item	Explanation
Connetion Name	Enter a name for the connection.
Conection Type	Select the type of connection this setup will use.
Supported Services	Shows a list of services supported by the connection type chosen.

Set Connection Settings pane

Use the Set Connection Settings pane to compare the version of remote agent installed on the device with the latest version available for Carbide. In this pane you can:

Set the device OS used by the device and supported by the selected remote agent
Allow easy serial port selection when connecting to a device
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

+ + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Serial Port	A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
Baud Rate	a dropdown list of baud rates common to serial connections.
Device OS	A dropdown list of device OSes that are supported by the remote agent software. Select the OS used by the device before running a check.
Select a service to test	Click to select a listed service for testing.
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. + 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. + + If a connection fails, the errors normally fall into these two categories: + + connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response. + TRK not responding - this indicates that the COM port is open but TRK is not responding. First, verify that TRK is up and running on the device. Second, TRK may be listening on a different COM port, so choose another named COM port and try again. + +

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

+ + + + + + + + + + + + + + + + + +

Item	Explanation
Install remote agents	A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 2.8.7. + Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.
Save	Click Save to store a local copy of the currently selected TRK to disk. You can then manually install the file to your devices using the method of your choice.
Install	Click Install to download and install the TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete. + NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Item

Explanation

Install remote agents

Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.

Save

Click Save to store a local copy of the currently selected TRK to disk. You can then manually install the file to your devices using the method of your choice.

Install

Click Install to download and install the TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete.

Related references

On-Device Setup
Install latest TRK

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_edit.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,122 +1,122 @@ - - - - - - -Editing connections - - - - -

Editing connections

Use the Remote Connections view to monitor, create, edit, or remove common remote connection settings.

Edit connection name and type

Use the Edit connection name and type page to assign a name and connection type to the new connection setup.

Figure 1 - New Connection wizard Edit connection name and type page

Table 1. Edit connection name and type page - options

- - - - - - - - - - - - - - - - - -

Item	Explanation
Connetion Name	Enter a name for the connection.
Conection Type	Select the type of connection this setup will use.
Supported Services	Shows a list of services supported by the connection type chosen.

Set Connection Settings pane

Use the Set Connection Settings pane to compare the version of remote agent installed on the device with the latest version available for Carbide. In this pane you can:

Set the device OS used by the device and supported by the selected remote agent
Allow easy serial port selection when connecting to a device
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

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Serial Port	A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
Baud Rate	a dropdown list of baud rates common to serial connections.
Device OS	A dropdown list of device OSes that are supported by the remote agent software. Select the OS used by the device before running a check.
Select a service to test	Click to select a listed service for testing.
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. - 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. - - If a connection fails, the errors normally fall into these two categories: - - connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response. - TRK not responding - this indicates that the COM port is open but TRK is not responding. First, verify that TRK is up and running on the device. Second, TRK may be listening on a different COM port, so choose another named COM port and try again. - -

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

- - - - - - - - - - - - - - - - - -

Item	Explanation
Install remote agents	A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 2.8.7. - Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.
Save	Click Save to store a local copy of the currently selected TRK to disk. You can then manually install the file to your devices using the method of your choice.
Install	Click Install to download and install the TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete. - NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Item

Explanation

Install remote agents

Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.

Save

Click Save to store a local copy of the currently selected TRK to disk. You can then manually install the file to your devices using the method of your choice.

Install

Click Install to download and install the TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete.

Related references

On-Device Setup
Install latest TRK

- - - - + + + + + + +Editing connections + + + + +

Editing connections

Use the Remote Connections view to monitor, create, edit, or remove common remote connection settings.

Edit connection name and type
Set Connection Settings pane
Install Remote Agents pane

Edit connection name and type

Use the Edit connection name and type page to assign a name and connection type to the new connection setup.

Figure 1 - New Connection wizard Edit connection name and type page

Table 1. Edit connection name and type page - options

+ + + + + + + + + + + + + + + + + +

Item	Explanation
Connetion Name	Enter a name for the connection.
Conection Type	Select the type of connection this setup will use.
Supported Services	Shows a list of services supported by the connection type chosen.

Set Connection Settings pane

Use the Set Connection Settings pane to compare the version of remote agent installed on the device with the latest version available for Carbide. In this pane you can:

Set the device OS used by the device and supported by the selected remote agent
Allow easy serial port selection when connecting to a device
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

+ + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Serial Port	A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
Baud Rate	a dropdown list of baud rates common to serial connections.
Device OS	A dropdown list of device OSes that are supported by the remote agent software. Select the OS used by the device before running a check.
Select a service to test	Click to select a listed service for testing.
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. + 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. + + If a connection fails, the errors normally fall into these two categories: + + connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response. + TRK not responding - this indicates that the COM port is open but TRK is not responding. First, verify that TRK is up and running on the device. Second, TRK may be listening on a different COM port, so choose another named COM port and try again. + +

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

+ + + + + + + + + + + + + + + + + +

Item	Explanation
Install remote agents	A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 2.8.7. + Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.
Save	Click Save to store a local copy of the currently selected TRK to disk. You can then manually install the file to your devices using the method of your choice.
Install	Click Install to download and install the TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete. + NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Item

Explanation

Install remote agents

Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.

Save

Click Save to store a local copy of the currently selected TRK to disk. You can then manually install the file to your devices using the method of your choice.

Install

Click Install to download and install the TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete.

Related references

On-Device Setup
Install latest TRK

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/view_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_debug.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,111 +0,0 @@ - - - - - - -Debug View - - - -

Debug View

The Debug view shows the target debugging information in a tree hierarchy. The items that appear there include:

Launch instance () - launch configuration name and type
Debugger instance () - debugger name and state
Executable instances () - other executables called by the launch instance
Thread instance () - thread number and state
Stack frame reference () - displays stack frame number, function, filename, and file line number when symbols are available and stack frame number, memory address, and filename when symbols are not available

NOTE The number beside the thread label is a reference counter, not a thread -identification number (TID).

Figure 1 shows the Debug view. Table 1 explains the items in the view.

Figure 1 - Debug view

Table 1 Debug view—items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Icon	Explanation
Resume		Click to perform these tasks: - - Continue execution up to the next breakpoint, watchpoint, or eventpoint - Run the program until it exits - Continue execution of a currently stopped program -
Suspend		Click to stop (pause) program execution.
Terminate		Click to terminate program execution.
Disconnect		Detaches the debugger from the selected process (useful for debugging attached processes). - NOTE After detaching the debugger from an on-device process, closing TRK on the device will also close the process.
Remove All Terminated		Clears all terminated processes in Debug view.
Restart		Returns the debugger to the beginning of the program and begins execution again. This behavior is equivalent to killing execution, then starting a new debugging session.
Step Over		Click to execute the current line, including any routines, and proceed to the next statement.
Step Into		Click to execute the current line, following execution inside a routine.
Step Return		Click to continue execution to the end of the current routine, then follow execution to the routine’s caller.
Instruction Stepping Mode		Activate to enable instruction stepping mode to examine a program as it steps into disassembled code.

Related concepts

Breakpoints

Related tasks

Related references

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/view_disassembly.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_disassembly.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_disassembly.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,101 +1,101 @@ - - - - - - -Disassembly Window - - - - -

Disassembly View

When debugging your application, the Disassembly view shows the loaded program as assembler instructions. When you use the Disassembly view, you can do the following tasks:

Step through the disassembly instructions of your program using the Instruction Stepping Mode () icon in the Debug view (Figure 1).
Reposition the PC using the various move commands (Figure 1) by first selecting the line to move to, then select the command from the context menu.
Set breakpoints at the start of any assembler instruction by right-clicking the left hand column to view the context menu options (Figure 2)

Figure 1 shows the Dissassembly view and the PC context menu that appears when you right-click in the data pane. Right-clicking the left border opens the breakpoint context menu.

Figure 1 - Repositioning the PC in the Disassembly view

Figure 2 - Setting Breakpoints in the Disassembly view

Table 1. Disassembly view —context menu

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Icon	Explanation
Run to Line	- -	Select Run to Line to execute the program from the currently executed line (the green line) to the selected line (the blue line).
Move to Line	- - -	Select Move to Line to move the program counter to the selected line (the blue line) skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program. - WARNING Using this command can leave a program in an unstable state. Use at your own risk.
Resume at Line	- -	Select Resume at Line to begin program execution at the selected line (the blue line), skipping all lines between it and the currently executed line (the green line). - WARNING Using this command can leave a program in an unstable state. Use at your own risk.
Toggle Breakpoint	-	Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between setting and removing the breakpoint.
Disable/Enable Breakpoint	-	Right-click in left-hand column of the Disassembly view and select the breakpoint option shown as determined by the current state of the breakpoint.
Breakpoint Properties	-	Select this option to open the Breakpoint Properties dialog.

Opening the Disassembly view

Select Window > Show View > Disassembly

-
OR
-

Click the Instruction Stepping Mode () icon in the Debug view -
A Disassembly view appears in the current perspective.
-

Related reference

- - - + + + + + + +Disassembly Window + + + + +

Disassembly View

When debugging your application, the Disassembly view shows the loaded program as assembler instructions. When you use the Disassembly view, you can do the following tasks:

Step through the disassembly instructions of your program using the Instruction Stepping Mode () icon in the Debug view (Figure 1).
Reposition the PC using the various move commands (Figure 1) by first selecting the line to move to, then select the command from the context menu.
Set breakpoints at the start of any assembler instruction by right-clicking the left hand column to view the context menu options (Figure 2)

Figure 1 shows the Dissassembly view and the PC context menu that appears when you right-click in the data pane. Right-clicking the left border opens the breakpoint context menu.

Figure 1 - Repositioning the PC in the Disassembly view

Figure 2 - Setting Breakpoints in the Disassembly view

Table 1. Disassembly view —context menu

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Icon	Explanation
Run to Line	+ +	Select Run to Line to execute the program from the currently executed line (the green line) to the selected line (the blue line).
Move to Line	+ + +	Select Move to Line to move the program counter to the selected line (the blue line) skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program. + WARNING Using this command can leave a program in an unstable state. Use at your own risk.
Resume at Line	+ +	Select Resume at Line to begin program execution at the selected line (the blue line), skipping all lines between it and the currently executed line (the green line). + WARNING Using this command can leave a program in an unstable state. Use at your own risk.
Toggle Breakpoint	+	Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between setting and removing the breakpoint.
Disable/Enable Breakpoint	+	Right-click in left-hand column of the Disassembly view and select the breakpoint option shown as determined by the current state of the breakpoint.
Breakpoint Properties	+	Select this option to open the Breakpoint Properties dialog.

Opening the Disassembly view

Select Window > Show View > Disassembly

+
OR
+

Click the Instruction Stepping Mode () icon in the Debug view +
A Disassembly view appears in the current perspective.
+

Related reference

+ + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,103 +1,103 @@ - - - - - - -Executables view - - - -

Executables view

The Executables view provides a dynamic list of executables and their related source files. The Executables view makes it easy to:

target all binaries for debugging because the symbolics are automatically loaded when a bld.inf is imported or a project is created from a template
debug a binary that is not part of a project in the workspace by importing it into the Executables view to load the symbolics
debug a process running on a device by attaching to the process and importing the binaries associated with the process into the Executables view to load the symbolics. For example, you to debug a library loaded by the process, you would need to import the libary and the process executable.
remove binaries when a project is closed or deleted from the workspace
remove binaries imported from outside the workspace by clicking the Remove the selected executables icon () or deleting the binary from the Executables project in the Project Explorer view
locate and manage which source and resource files are associated with each executable. Paths shown in black text have been resolved, those in gray text cannot be found.
identify and correct any path issues with missing source files (shown in gray text). Double-click the missing source file to open a Locate File editor view which enables you to find the missing file.
view routines and header files used by the source file. Click the tree control to expand or collapse a list of included header files and routine names for fast navigation.
find and set breakpoints, watchpoints, and eventpoints in source files. Double-click a source file to open it in an editor view and to review the status of its breakpoints.

In addition, an Executables project is created in the Project Explorer view. The binaries shown in the Executables project can be deleted which also removes them from the Executables view. For binaries outside the workspace you must import them into the Executables view so their symbolics can be used during the debug session. You can also drag and drop executables into the view.

NOTE To debug ROM DLLs with System TRK or in stop mode, always specify the ROM Log file in the project's launch configuration.

Figure 1 - Executables view

The Executables view consists of the Executable Name and Source File Name panes describled in the table below. Use the Columns button in the toolbar to show or hide specific columns in each pane. Columns can be sorted and rearranged in the order desired.

Table 1. Executables view information

- - - - - - - - - - - - - -

Pane	Explanation
Executable Name	Displays a list of executables in the workspace as well as other files added by the user. Select an executable to update the Source File Name pane with related files. The executable information shown can include: - - Executable Name - (default) Name of the exectable file. - Executable Project - (default) The project associated with the executable. - Executable Location - (default) The current location of the executable. - Executable Size - The executable size shown in bytes. - Executable Date - The source file′s modification date. - Executable Type - The executable type (.exe, etc.) - - Click the Columns icon () to set which columns to show in this pane.
Source File Name	Displays a list of source files for the selected executable as extracted from the symbol table. The source file information shown can include: - - Source File Name - (default) Name of the source file used by the executable. If no binary files are in the project the message No source files found in <project_name> is shown. - Source File Location - (default) The current location of the source file. If the path is shown in gray text the source file was not located. To locate it, double-click to open a new editor, then click Locate File... to locate the missing file. The new path is compared to the old one and all files located in the same directory are automatically updated to use the new path. - Source File Original Location - (default) The original location of the source file which may be different than the current location. - Source File Size - The executable size shown in bytes. - Source File Date - The source file′s modification date. - Source File Type - The source type (.h, .inc, etc.) - - Expand a file′s tree control to view the functions and header files used by the file. Double-click to open the source file for editing or to set breakpoints. - Click the Columns icon () to set which columns to show in this pane.

Pane

Explanation

Executable Name

Displays a list of executables in the workspace as well as other files added by the user. Select an executable to update the Source File Name pane with related files. The executable information shown can include:

Executable Name - (default) Name of the exectable file.
Executable Project - (default) The project associated with the executable.
Executable Location - (default) The current location of the executable.
Executable Size - The executable size shown in bytes.
Executable Date - The source file′s modification date.
Executable Type - The executable type (.exe, etc.)

Click the Columns icon () to set which columns to show in this pane.

Source File Name

Displays a list of source files for the selected executable as extracted from the symbol table. The source file information shown can include:

Source File Name - (default) Name of the source file used by the executable. If no binary files are in the project the message No source files found in <project_name> is shown.
Source File Location - (default) The current location of the source file. If the path is shown in gray text the source file was not located. To locate it, double-click to open a new editor, then click Locate File... to locate the missing file. The new path is compared to the old one and all files located in the same directory are automatically updated to use the new path.
Source File Original Location - (default) The original location of the source file which may be different than the current location.
Source File Size - The executable size shown in bytes.
Source File Date - The source file′s modification date.
Source File Type - The source type (.h, .inc, etc.)

Expand a file′s tree control to view the functions and header files used by the file. Double-click to open the source file for editing or to set breakpoints.

Click the Columns icon () to set which columns to show in this pane.

Executables view toolbar icons

The table below lists the unique icons displayed in the Executables view toolbar.

Table 2. Executables view toolbar options

- - - - - - - - - - - - - - - - - - - - - - - - - - -

Command	Name	Description
	Refresh the list of executables	Click to refresh the executables list.
	Import an executable file	Click to import an executable not in the workspace into the executables list.
- - -	Remove the selected executables	Click to remove one or more selected executables from the executables list. You will see a alert if the executable cannot be removed.
	Columns	Opens the Configure Columns dialog for configuring which columns appear in the Executable and Source File panes.

Other references

Debug perspective

- - - - + + + + + + +Executables view + + + +

Executables view

The Executables view provides a dynamic list of executables and their related source files. The Executables view makes it easy to:

target all binaries for debugging because the symbolics are automatically loaded when a bld.inf is imported or a project is created from a template
debug a binary that is not part of a project in the workspace by importing it into the Executables view to load the symbolics
debug a process running on a device by attaching to the process and importing the binaries associated with the process into the Executables view to load the symbolics. For example, you to debug a library loaded by the process, you would need to import the libary and the process executable.
remove binaries when a project is closed or deleted from the workspace
remove binaries imported from outside the workspace by clicking the Remove the selected executables icon () or deleting the binary from the Executables project in the Project Explorer view
locate and manage which source and resource files are associated with each executable. Paths shown in black text have been resolved, those in gray text cannot be found.
identify and correct any path issues with missing source files (shown in gray text). Double-click the missing source file to open a Locate File editor view which enables you to find the missing file.
view routines and header files used by the source file. Click the tree control to expand or collapse a list of included header files and routine names for fast navigation.
find and set breakpoints, watchpoints, and eventpoints in source files. Double-click a source file to open it in an editor view and to review the status of its breakpoints.

NOTE To debug ROM DLLs with System TRK or in stop mode, always specify the ROM Log file in the project's launch configuration.

Figure 1 - Executables view

Table 1. Executables view information

+ + + + + + + + + + + + + +

Pane	Explanation
Executable Name	Displays a list of executables in the workspace as well as other files added by the user. Select an executable to update the Source File Name pane with related files. The executable information shown can include: + + Executable Name - (default) Name of the exectable file. + Executable Project - (default) The project associated with the executable. + Executable Location - (default) The current location of the executable. + Executable Size - The executable size shown in bytes. + Executable Date - The source file′s modification date. + Executable Type - The executable type (.exe, etc.) + + Click the Columns icon () to set which columns to show in this pane.
Source File Name	Displays a list of source files for the selected executable as extracted from the symbol table. The source file information shown can include: + + Source File Name - (default) Name of the source file used by the executable. If no binary files are in the project the message No source files found in <project_name> is shown. + Source File Location - (default) The current location of the source file. If the path is shown in gray text the source file was not located. To locate it, double-click to open a new editor, then click Locate File... to locate the missing file. The new path is compared to the old one and all files located in the same directory are automatically updated to use the new path. + Source File Original Location - (default) The original location of the source file which may be different than the current location. + Source File Size - The executable size shown in bytes. + Source File Date - The source file′s modification date. + Source File Type - The source type (.h, .inc, etc.) + + Expand a file′s tree control to view the functions and header files used by the file. Double-click to open the source file for editing or to set breakpoints. + Click the Columns icon () to set which columns to show in this pane.

Pane

Explanation

Executable Name

Executable Name - (default) Name of the exectable file.
Executable Project - (default) The project associated with the executable.
Executable Location - (default) The current location of the executable.
Executable Size - The executable size shown in bytes.
Executable Date - The source file′s modification date.
Executable Type - The executable type (.exe, etc.)

Click the Columns icon () to set which columns to show in this pane.

Source File Name

Displays a list of source files for the selected executable as extracted from the symbol table. The source file information shown can include:

Source File Name - (default) Name of the source file used by the executable. If no binary files are in the project the message No source files found in <project_name> is shown.
Source File Location - (default) The current location of the source file. If the path is shown in gray text the source file was not located. To locate it, double-click to open a new editor, then click Locate File... to locate the missing file. The new path is compared to the old one and all files located in the same directory are automatically updated to use the new path.
Source File Original Location - (default) The original location of the source file which may be different than the current location.
Source File Size - The executable size shown in bytes.
Source File Date - The source file′s modification date.
Source File Type - The source type (.h, .inc, etc.)

Expand a file′s tree control to view the functions and header files used by the file. Double-click to open the source file for editing or to set breakpoints.

Click the Columns icon () to set which columns to show in this pane.

Executables view toolbar icons

The table below lists the unique icons displayed in the Executables view toolbar.

Table 2. Executables view toolbar options

+ + + + + + + + + + + + + + + + + + + + + + + + + + +

Command	Name	Description
	Refresh the list of executables	Click to refresh the executables list.
	Import an executable file	Click to import an executable not in the workspace into the executables list.
+ + +	Remove the selected executables	Click to remove one or more selected executables from the executables list. You will see a alert if the executable cannot be removed.
	Columns	Opens the Configure Columns dialog for configuring which columns appear in the Executable and Source File panes.

Other references

Debug perspective

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/view_log.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_log.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_log.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,72 +1,72 @@ - - - - - - -Console View - - - -

Console View

The Console view displays the output of a process and allows you to provide keyboard input to a process. There are numerous consoles available, see the Open Console dropdown list for those available to you. Most are enabled from various project panels in Carbide.

Figure 1 - Console view showing build console information

To view RDebug::Printf output in the Console view when targeting devices, ensure that the following Debugger options are matched with settings in the epoc.ini file.

Set LogToDebugger 1 to use the View program output option
Set LogToFile 1 to enable the View emulator output option

Table 1 Console view—items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Icon	Explanation
Scroll Lock		Toggles the scrolling of the console view contents.
Clear Console		Clears all content in the Console view.
Pin Console		Toggles the behavior of the console. When enabled the current console content is fixed all the time instead of scrolling out of sight. When disabled, the console changes according to the action. -
Display Selected Console		Changes the contents of the current console view to show the selected console output.
Open Console		Opens a new console to display the log for: - - Platform Security Diagnostics - New Windows System Messages Console - New Emulation Program Output Console - New TRK Program Output Console - New TRK Communications Log Console - New Trace32 Communications Log Console - New Symbian Rom Log Console - New Emulator Output Console - CVS - New Console View - - Remember that program output is console output from the running binary and communications log is the messages sent between TRK and the on-device debug agent. - NOTE You can pin any message log view so that it does not lose focus.

- - - - + + + + + + +Console View + + + +

Console View

Figure 1 - Console view showing build console information

To view RDebug::Printf output in the Console view when targeting devices, ensure that the following Debugger options are matched with settings in the epoc.ini file.

Set LogToDebugger 1 to use the View program output option
Set LogToFile 1 to enable the View emulator output option

Table 1 Console view—items

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Icon	Explanation
Scroll Lock		Toggles the scrolling of the console view contents.
Clear Console		Clears all content in the Console view.
Pin Console		Toggles the behavior of the console. When enabled the current console content is fixed all the time instead of scrolling out of sight. When disabled, the console changes according to the action. +
Display Selected Console		Changes the contents of the current console view to show the selected console output.
Open Console		Opens a new console to display the log for: + + Platform Security Diagnostics + New Windows System Messages Console + New Emulation Program Output Console + New TRK Program Output Console + New TRK Communications Log Console + New Trace32 Communications Log Console + New Symbian Rom Log Console + New Emulator Output Console + CVS + New Console View + + Remember that program output is console output from the running binary and communications log is the messages sent between TRK and the on-device debug agent. + NOTE You can pin any message log view so that it does not lose focus.

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/view_module_wnd.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_module_wnd.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_module_wnd.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,24 +1,24 @@ - - - - - - -Modules View - - - -

Modules View

The Modules view displays a list of modules loaded while debugging your program. The listed modules can be selected to show related information. You can open the Modules view in the Carbide C/C++ perspective by selecting Window > Show view > Other..., then expand the Debug folder and select Modules. In the Debug perspective select Window > Show view > Modules.

The Modules view is only loaded during a debug session and closes when the debug session ends. Select the running man icon to list the Type, Symbols, and Symbols file for the executable. Select the stack of books icon to list the Type, Symbols, Symbols file, and Base address for the shared library.

Figure 1 shows the Modules view.

Figure 1 - Modules view

Related reference

Debug view

- - - - + + + + + + +Modules View + + + +

Modules View

Figure 1 shows the Modules view.

Figure 1 - Modules view

Related reference

Debug view

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/view_signals_wnd.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_signals_wnd.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_signals_wnd.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,49 +1,49 @@ - - - - - - -Signals View - - - -

Signals View

The Signals view of the Debug perspective lets you view the signals defined on the selected debug target and how the debugger handles each one.

NOTE Currently Carbide.c++ does not support this CDT feature.

Figure 1 shows the Signals view.

Figure 1 - Signals view

Table 1 Signals view—items

- - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Name	Displays the name of the signal.
Pass	Where "yes" is displayed, the debugger lets your program see the signal. Your program can handle the signal, or else it may terminate if the signal is fatal and not handled.
Suspend	Where "yes" is displayed, the debugger suspends your program when this signal is handled.
Description	Displays a description of the signal.

Related reference

Debug view

- - - - + + + + + + +Signals View + + + +

Signals View

The Signals view of the Debug perspective lets you view the signals defined on the selected debug target and how the debugger handles each one.

NOTE Currently Carbide.c++ does not support this CDT feature.

Figure 1 shows the Signals view.

Figure 1 - Signals view

Table 1 Signals view—items

+ + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Name	Displays the name of the signal.
Pass	Where "yes" is displayed, the debugger lets your program see the signal. Your program can handle the signal, or else it may terminate if the signal is fatal and not handled.
Suspend	Where "yes" is displayed, the debugger suspends your program when this signal is handled.
Description	Displays a description of the signal.

Related reference

Debug view

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,52 +1,52 @@ - - - - - - -Symbian Project Navigator view - - - - -

Symbian Project Navigator view

The Symbian Project Navigator view shows all files that belong to the -current build configuration. This view lists the Symbian projects in your current workspace and their corresponding *.inf file (typically bld.inf). The *.inf file contains the related MMP project files, which are also listed in a tree structure. You can collapse or expand the list for each MMP to see which sources belong to each MMP.

To open this view select Window > Show View > Symbian Project Navigator, or select Window > Show View > Other ... and expand the Carbide.c++ folder then choose Symbian Project Navigator.

Figure 1 shows the Symbian Project Navigator view.

Figure 1 - Symbian Project Navigator view

Table 1. Symbian Project Navigator view —shortcut menu

- - - - - - - - - - - - - - - - - - - - - -

Item	Icon	Explanation
Toggle SOURCEPATH		Toggles the display between showing the SOURCEPATH folders contained in the MMP file and showing the Bld.inf structure.
Toggle MMPs		Toggle the display to show all MMP files or the MMP files associated with the current build configuration.
Toggle MMP Order	- - -	Toggle to show the MMPs list in alphabetical or build order. The default setting is build order.

Related references

Symbian OS View
Debug View

- - - - + + + + + + +Symbian Project Navigator view + + + + +

Symbian Project Navigator view

The Symbian Project Navigator view shows all files that belong to the +current build configuration. This view lists the Symbian projects in your current workspace and their corresponding *.inf file (typically bld.inf). The *.inf file contains the related MMP project files, which are also listed in a tree structure. You can collapse or expand the list for each MMP to see which sources belong to each MMP.

To open this view select Window > Show View > Symbian Project Navigator, or select Window > Show View > Other ... and expand the Carbide.c++ folder then choose Symbian Project Navigator.

Figure 1 shows the Symbian Project Navigator view.

Figure 1 - Symbian Project Navigator view

Table 1. Symbian Project Navigator view —shortcut menu

+ + + + + + + + + + + + + + + + + + + + + +

Item	Icon	Explanation
Toggle SOURCEPATH		Toggles the display between showing the SOURCEPATH folders contained in the MMP file and showing the Bld.inf structure.
Toggle MMPs		Toggle the display to show all MMP files or the MMP files associated with the current build configuration.
Toggle MMP Order	+ + +	Toggle to show the MMPs list in alphabetical or build order. The default setting is build order.

Related references

Symbian OS View
Debug View

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,114 +1,114 @@ - - - - - - -Symbian OS Data - - - - -

Symbian OS Data view

The Symbian OS Data view displays the processes and threads for the suspended debug session based on the selection in the Debug view. Read-only data is displayed for ARM build configurations. To open the Symbian OS Data view select Window > Show View > Symbian OS Data when the Debug perspective is visible or select Window > Show View > Other..., then expand the Carbide.c++ folder and select Symbian OS Data when the Carbide C/C++ perspective is visible. Click Ok to display the Symbian OS Data window (Figure 1).

NOTE The Symbian OS Data view works with the debugger and will only display data during a live debug session. The Symbian OS Data view is not supported for emulator debugging, and will not show anything during emulator debug.

The Symbian OS Data view reveals kernel data in the Symbian OS running on the device being debugged. The kernel data displayed is always that of the device with the currently selected thread or process in Debug view. If you are debugging two devices at the same time, the content of the view will change when focus is switched from a thread on one device to a thread on another device. The kernel data includes more than just processes and threads.

For the stop mode debugger and the crash debugger, all the data listed above is supported. For the Application and System TRK debuggers, the chunks and libraries views are not supported. The Symbian OS Data view is not supported for the emulator debugger and will show nothing during an emulator debug session. During a stop mode debug session or a TRK debug session, you are able to select a process or a thread in the Symbian OS Data view and attach the debugger to it for source level debugging if the binary is listed in the Executables view. Binaries listed in the Executable view can be source level debugged. Binaries not listed in the Executables view can only be assembly code debugged in the Disassembly view.

NOTE Any executable must be included in the Executables view before it can be debugged.

When the Time interval for auto-refreshing OS View option is enabled (which is on by default except for crash debugger), the data in the Symbian OS Data view will be auto-refreshed. Note that "auto-refresh" has a different meaning in different debuggers. During a stop mode debug session, the view will refresh data whenever the debugged program on the device is stopped and shows data as stale (greyed out) when the program is running. During a TRK debug session, the View will refresh data at a time interval regardless of whether the debugged program is stopped or not. The time interval is specified by an option in the Carbide.c++ global preference panel, which is five seconds by default.

When auto-refresh is turned off, the debugger will not automatically refresh data in the View and will show the data as stale (greyed out). However you can manually refresh the data by clicking on the "Refresh" button in the View. Usually you may want to turn off the auto-refresh if you think it is slowing down your debug operations such as stepping.

Symbian OS Data pages -

The Symbian OS Data view consists of five tabs. Each tabbed pane is described below. In all panes, the Name Filter field is a standard Eclipse UI control that allows you to find an item by filtering out items by name using wildcards (*, ?) and camel case naming conventions. Camel case refers to using mixed case multiple names merged together in coding like SecInvInit and DosServer. In all panes, you can select an item and view its properties (attributes). In panes with columns you can click a column title to toggle between ascending and descending sorting.

Data to be viewed includes:

Overview
Processes
Threads
Chunks
Libraries

NOTE Information for the Chunks and Libraries tabs is not available when debugging with the TRK debug agent.

Figure 1. Symbian OS Data view

Table 1 - Symbian OS Data view toolbar buttons

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Button	Icon	Function
Refresh data		Click this button to force a refresh of data in the view. Use the Carbide.c++ Debugger preference panel Time interval for auto-refreshing OS View option to control the automatic refreshing of data.
Enable/disable auto-refresh		Click this button to turn on/off auto refresh of data.
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). -
Properties		Click this button to show properties of currently selected item in the Properties view. Or right-click an item and choose Properties.
Timer		Click this button to define the time interval for auto-refreshing data. This applies to run mode debugging only.
Collapse All		Click the Collaps All command to collapse all of the currently elements in the view.

Overview Tab

This tab (shown in Figure 1) provides a tree view of ownership of all processes, threads, and chunks in the OS. -In contrast, the other tabs provide a flat list of corresponding kernel objects such as process, thread, chunk, library, etc.

Processes

The Processes tab (Figure 2) provides a flat list of corresponding kernel objects. -Click a column title to sort the list by the title attribute in alternating ascending and descending order. For example, you may choose to sort the process list by Name, ID, or by Priority.

Figure 2. Processes Pane of Symbian OS View

The process(es) being debugged will be shown in bold font. You can debug (attach debugger to) any process in the Processes tab by selecting it and clicking the "Debug" button or just by double clicking on it. In that case a new process item will show up in the Debug View if the process is not being debugged. Otherwise, you will get a message saying it's already under debug.

Threads

The Threads tab (Figure 3) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header. The thread(s) being debugged will be shown in bold font.

NOTE You can debug (attach debugger to) any thread in the Thread tab by double clicking on it or selecting it and clicking the Debug button. In that case, a new thread item will show up in Debug view if the thread is not being debugged.

Figure 3. Threads Pane of Symbian OS View

Chunks

Chunks are an area of contiguous linear memory. It is the unit of memory allocation where a region of RAM is mapped into contiguous logical addresses. Chunks are allocated during boot for such things as the Kernel's data and stack.

The Chunks tab (Figure 4) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header.

NOTE Chunks data is not available during TRK debugging.

Figure 4. Chunks Pane of Symbian OS View

Libraries Tab

The Libraries pane (Figure 5) in the Symbian OS view provides information on libraries in the Symbian OS residing on the target.

NOTE Library data is not available during TRK debugging.

Figure 5. Libraries Pane of Symbian OS View

Attaching to a Process

If you double click on a thread item in the Thread tab, or right-click and choose Debug, the owning process of the thread will be attached. The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian OS Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian OS Data toolbar or right-click the thread and choose Properties.

NOTE If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the Breakpoints view to verify that the executable breakpoints have been resolved.

IMPORTANT In stop mode debugging when debugging multiple processes at the same time, selecting a process in the Debug pane and clicking Terminate disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click Terminate the CPU is suspended until the next debug session.

WARNING Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device.

Other references

Debug view
Setting Symbian OS View Refresh Rate
-

- - - - + + + + + + +Symbian OS Data + + + + +

Symbian OS Data view

NOTE Any executable must be included in the Executables view before it can be debugged.

Symbian OS Data pages +

Data to be viewed includes:

Overview
Processes
Threads
Chunks
Libraries

NOTE Information for the Chunks and Libraries tabs is not available when debugging with the TRK debug agent.

Figure 1. Symbian OS Data view

Table 1 - Symbian OS Data view toolbar buttons

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Button	Icon	Function
Refresh data		Click this button to force a refresh of data in the view. Use the Carbide.c++ Debugger preference panel Time interval for auto-refreshing OS View option to control the automatic refreshing of data.
Enable/disable auto-refresh		Click this button to turn on/off auto refresh of data.
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). +
Properties		Click this button to show properties of currently selected item in the Properties view. Or right-click an item and choose Properties.
Timer		Click this button to define the time interval for auto-refreshing data. This applies to run mode debugging only.
Collapse All		Click the Collaps All command to collapse all of the currently elements in the view.

Overview Tab

This tab (shown in Figure 1) provides a tree view of ownership of all processes, threads, and chunks in the OS. +In contrast, the other tabs provide a flat list of corresponding kernel objects such as process, thread, chunk, library, etc.

Processes

The Processes tab (Figure 2) provides a flat list of corresponding kernel objects. +Click a column title to sort the list by the title attribute in alternating ascending and descending order. For example, you may choose to sort the process list by Name, ID, or by Priority.

Figure 2. Processes Pane of Symbian OS View

Threads

Figure 3. Threads Pane of Symbian OS View

Chunks

NOTE Chunks data is not available during TRK debugging.

Figure 4. Chunks Pane of Symbian OS View

Libraries Tab

The Libraries pane (Figure 5) in the Symbian OS view provides information on libraries in the Symbian OS residing on the target.

NOTE Library data is not available during TRK debugging.

Figure 5. Libraries Pane of Symbian OS View

Attaching to a Process

WARNING Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device.

Other references

Debug view
Setting Symbian OS View Refresh Rate
+

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_Trace32_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_Trace32_config.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,297 +0,0 @@ - - - - - - -Trace32 Support - - - -

Symbian OS Trace32 Support

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.

Launch configurations define a collection of settings used to tell the debugger how to start a debug session. The launch configuration panes for creating a Trace32 stop mode debug launch configuration are described below. Figure 1 is an example of the Trace32 Debug launch configuration window and the related panes accessible in a tabbed format. 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.

To open the Debug window

Select the Project in the C/C++ Project view that you want to debug
Select the Run > Debug... menu item to display the Debug launch configuration window (figure 1)
Define a debug launch configuration to communicate with the protocol interface

The panes include:

The Main tab (Figure 1) 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 (Figure 2) defines the Trace32 executable, configuration file and initialization script.
The Debugger tab (Figure3) defines debug configurations, such as entry point to begin debugging and target options.
The ROM Image tab (Figure 4) allows you to define startup options and ROM image download information.
The Executables tab (Figure 5) allows you to specify which executables that you want to debug that are part of the project.
The Source tab (Figure 6) (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 (Figure 7) (standard CDT page) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file.

Main

Figure 1 - Trace32 Launch Configuration Settings - Main Tab

Table 1. Debug Launch configuration window—Main tab items

- - - - - - - - - - - - - -

Item	Explanation
Project	The project to associate with this debug launch configuration. Click Browse to select a different project.
Executable	This is the name of the executable that is linked to the project. Click Browse to select a different executable.

Connection

Figure 2 - Trace32 Launch Configuration Settings - Connection Tab

Table 2. Launch configuration window—Connection tab items

- - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Trace32 Executable	Enter or browse to the Trace32 executable to be launched for debugging. By default, it will be set to c:\t32\t32marm.exe. The default installation path is c:\t32.
Trace32 Configuration File	Enter or browse to the Trace32 Configuration File. The default configuration file is a Carbide specific T32 config file (config_carbide.t32). Default location is - C:\Program Files\Nokia\Carbide.c++ v2.0.x\plugins\com.nokia.carbide.cpp.support_ - <version>\Symbian_Support\Trace32\ - You can modify the config_carbide.t32 file to support UDP (User Datagram Protocol) connections by adding the following lines: - -RCL=NETASSIST -PACKLEN=1024 -PORT=20000
Trace32 Initialization Script	Enter or browse to the Trace32 initialization cmm script file. This script will be run in Trace32 after connecting to Trace32. Users are expected to have their own scripts for the targets they are using. The cmm files are provided here for H2 and H4 boards: - C:\Program Files\Nokia\Carbide.c++ v2.0.x\plugins\com.nokia.carbide.cpp.support_ - <version>>\Symbian_Support\Trace32\cmm_scripts\H2 & H4
View Messages between Carbide and Trace32	The View Messages between Carbide and Trace32 check box allows you to specify whether or not the debug protocol messages between Carbide and T32 should be logged in a T32 Communication Log console window.

Debugger

Figure 3 - Trace32 Launch Configuration Settings - Debugger Tab

Table 3. Launch configuration window—Debugger tab items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Break at entry point	Select the check box and specify an entry point in the text box if you want the debugger to break at an entry point in the program being debugged. The default is set to E32Main since most applications entry point is E32Main. But you can specify a function name in the program being debugged.
Soft attach	Select to attach to a target without restarting the target device. This is very handy when the device uses flash, memory cards, or other external media for booting purposes and when it's not possible to configure the device to restart by the debugger. With soft attach, the debugger doesn't change the state of the target device. The debugger halts the target after attaching to the target to show the current PC location. User can preform normal debugging operations from then onwards.
Debug from start address	Select this option to stop the target at the start address once the target initialization is done and the OS is downloaded; if you have chosen to download the OS.
Run from start address	Select this option to run the target from the start address once the target initialization is done.
Start Address (hex)	Specify the memory address that the Carbide debugger will use to set the program counter to start the target. This is typically the start address of the Symbian OS.
Reset target at the start of each debug session	Select this check box to reset the target at the start of each debug session. For Trace32, the reset is typically done as part of the CMM script file. - Consult board specifications to determine if resetting is necessary.
Target Processor	Select a target processor from the drop down list of all supported processors. By default the field is set to Generic. When you select a processor, Carbide determines whether the debugger provides ARMV5 or ARMV6 support.
Target Initialization File	Select the check box and enter or browse to the target initialization file. Typically, this initialization file is used to initialize the target after connecting. When using Trace32, the initialization is done in the CMM script file.
Memory Configuration File	Select the check box and enter or browse to the memory configuration file. The Carbide debugger uses this configuration file to determine which memory is accessible, readable, and writable on the target.
Default Instruction set	The following options are available: - - Auto (examine code at current PC location) - Arm (32 bit) - Thumb (16 bit) - - Arm is the default. It is used by the debugger to determine the processor mode when it cannot be determined otherwise. This can happen at addresses for which there is no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code.

ROM Image

Figure 4 - Trace32 Launch Configuration Settings - ROM Image Tab

Table 4. Launch configuration window—ROM Image tab items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
Symbian Epoc32 Directory	Enter or browse to the epoc32 directory for the Symbian OS kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

Executables

Figure 5 - Trace32 Launch Configuration Settings - Executables Tab

Table 5. Executable pane —items

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which govern the executable support used by this project for debugging purposes. The options include: - - Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. - Executables built by this project — shows only the executables built by this project using the specified SDK - Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. - All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. -
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

Source

Figure 6 - Trace32 Launch Configuration Settings - Source Tab

Table 6. Launch configuration window—Source tab items

- - - - - - - - - - - - - -

Item	Explanation
Source Lookup Path	Allows you to add locations to search for source files. You can arrange the list by selecting the type of source path and clicking Up and Down buttons. Select a type of source and click Remove button to delete the item from the list.
Search for duplicate source files on the path	Enable this option to search for duplicate source files on source paths listed.

Common

Figure 7 - Trace32 Launch Configuration Settings - Common Tab

Table 7. Launch configuration window—Common tab items

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Save As	Allows you to save the launch configuration as a file local to the project or as shared file. For a shared file you can enter or browse to a folder within an existing project directory.
Display in favorites menu	Select menu for launch configuration to appear.
Console Encoding	Select the character set to use to display information in the console window.
Standard Input and Output	Allocate input and output to console and/or specified file. If a file is selected, you can select Append option to append data to selected file.
Launch in background	Enable this option to launch debug operation in a background process.

Related concepts

Launch Configurations
About the Debugger

Related tasks

Creating a Launch Configuration

Related references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,80 +1,80 @@ - - - - - - -Debug Window - - - -

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Icon	Item	Explanation
	New Launch Configuration	Click the New Launch Configuration icon to add a launch configuration to the Configurations list. Default information based upon the project is automatically entered into the various text boxes. - NOTE Normally, you should not have to change any of the default text box entries unless you are creating multiple debug launch configurations for the same project.
	Duplicate	Click the Duplicate icon to duplicate the currently selected launch configuration.
	Delete selected launch configuration(s)	Click the Delete icon to remove the currently selected configuration from the Configurations list.
	Collapse	Click the Collapse icon to collapse expanded lists of launch configurations.
	Filter launch configurations...	Click the Filter icon to select filter options that control which launch configurations appear in the list. Filter options include: - - Filter Closed Projects - Filter Deleted/Unavailable Projects - Filter Configuration Types - Apply Window Working Set(s) - Filtering Preferences... -

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

- - - + + + + + + +Debug Window + + + +

Debug Window

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

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Icon	Item	Explanation
	New Launch Configuration	Click the New Launch Configuration icon to add a launch configuration to the Configurations list. Default information based upon the project is automatically entered into the various text boxes. + NOTE Normally, you should not have to change any of the default text box entries unless you are creating multiple debug launch configurations for the same project.
	Duplicate	Click the Duplicate icon to duplicate the currently selected launch configuration.
	Delete selected launch configuration(s)	Click the Delete icon to remove the currently selected configuration from the Configurations list.
	Collapse	Click the Collapse icon to collapse expanded lists of launch configurations.
	Filter launch configurations...	Click the Filter icon to select filter options that control which launch configurations appear in the list. Filter options include: + + Filter Closed Projects + Filter Deleted/Unavailable Projects + Filter Configuration Types + Apply Window Working Set(s) + Filtering Preferences... +

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 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_sophia_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_sophia_config.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,301 +0,0 @@ - - - - - - -Sophia Support - - - -

Symbian OS Sophia Target Interface Support

Launch configurations define a collection of settings used to tell the debugger how to start a debug session. The launch configuration panes for creating a Sophia (STI) stop mode debug launch configuration are described below. Figure 1 is an example of the STI Debug launch configuration window and the related panes accessible in a tabbed format.

To open the Debug window

Select the Run > Debug... menu item

The Debug window (Figure 1) appears.

The panes include:

The Main tab (Figure 1) 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 (Figure 2) defines the Sophia Target Interface, EJ_Debug type, and JTAG TCLK Frequency.
The Debugger tab (Figure3) defines debug configurations, such as entry point to begin debugging, target options, and instruction set.
The ROM Image tab (Figure 4) allows you to define startup options and ROM image and ROM log file download information.
The Executables tab (Figure 5) allows you to specify which executables that you want to debug that are part of the project.
The Source tab (Figure 6) (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 (Figure 7) (standard CDT page) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file.

Main

Figure 1 - Sophia (STI) Launch Configuration Settings - Main Tab

Table 1. Debug Launch configuration window—Main tab items

- - - - - - - - - - - - - -

Item	Explanation
Project	The project to associate with this debug launch configuration. Click Browse to select a different project.
Executable	This is the name of the executable that is linked to the project. Click Browse to select a different executable.

Connection

Figure 2 - Sophia Launch Configuration Settings - Connection Tab

Table 2. Launch configuration window—Connection tab items

- - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Sophia Target Interface Location	Enter or browse to the Sophia interface (WTI.dll) to be launched for debugging. By default, it will be set to C:\CarbideIF_ARM\WTI.dll. If default file does not exist then an error message will appear.
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 Frequency	Select the JTAG TCLK frequency. Options include: - - Auto - 33 MHz - 16 MHz - 8 MHz - 500 KHz -
View Messages between Carbide and STI	The View Messages between Carbide and STI check box allows you to specify if the debug protocol messages between Carbide and STI should be logged in a Communication Log console window.

Debugger

Figure 3 - Sophia Launch Configuration Settings - Debugger Tab

Table 3. Launch configuration window—Debugger tab items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Break at entry point	Select the check box and specify an entry point in the text box if you want the debugger to break at an entry point in the program being debugged. The default is set to E32Main since most applications entry point is E32Main. But you can specify a function name in the program being debugged.
Soft attach	Select to attach to a target without restarting the target device. This is very handy when the device uses flash, memory cards, or other external media for booting purposes and when it's not possible to configure the device to restart by the debugger. With soft attach, the debugger doesn't change the state of the target device. The debugger halts the target after attaching to the target to show the current PC location. User can preform normal debugging operations from then onwards.
Debug from start address	Select this option to stop the target at the start address once the target initialization is done and the OS is downloaded; if you have chosen to download the OS.
Run from start address	Select this option to run the target from the start address once the target initialization is done.
Start Address (hex)	Specify the memory address that the Carbide debugger will use to set the program counter to start the target. This is typically the start address of the Symbian OS.
Reset target at the start of each debug session	Select this check box to reset the target at the start of each debug session. For Trace32, the reset is typically done as part of the CMM script file. - Consult board specifications to determine if resetting is necessary.
Target Processor	Select a target processor from the drop down list of all supported processors. By default the field is set to Generic. When you select a processor, Carbide determines whether the debugger provides ARMV5 or ARMV6 support.
Target Initialization File	Select the check box and enter or browse to the target initialization file. Typically, this initialization file is used to initialize the target after connecting. When using Trace32, the initialization is done in the CMM script file.
Memory Configuration File	Select the check box and enter or browse to the memory configuration file. The Carbide debugger uses this configuration file to determine which memory is accessible, readable, and writable on the target.
Default Instruction set	The following options are available: - - Auto (examine code at current PC location) - Arm (32 bit) - Thumb (16 bit) - - Arm is the default. It is used by the debugger to determine the processor mode when it cannot be determined otherwise. This can happen at addresses for which there is no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code.

ROM Image

Figure 4 - Sophia Launch Configuration Settings - ROM Image Tab

Table 4. Launch configuration window—ROM Image tab items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
Symbian Epoc32 Directory	Enter or browse to the epoc32 directory for the Symbian OS kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

Executables

Figure 5 - Sophia Launch Configuration Settings - Executables Tab

Table 5. Executable pane —items

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which govern the executable support used by this project for debugging purposes. The options include: - - Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. - Executables built by this project — shows only the executables built by this project using the specified SDK - Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. - All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. -
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

Source

Figure 6 - Sophia Launch Configuration Settings - Source Tab

Table 6. Launch configuration window—Source tab items

- - - - - - - - - - - - - -

Item	Explanation
Source Lookup Path	Allows you to add locations to search for source files. You can arrange the list by selecting the type of source path and clicking Up and Down buttons. Select a type of source and click Remove button to delete the item from the list.
Search for duplicate source files on the path	Enable this option to search for duplicate source files on source paths listed.

Common

Figure 7 - Sophia Launch Configuration Settings - Common Tab

Table 7. Launch configuration window—Common tab items

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Save As	Allows you to save the launch configuration as a file local to the project or as shared file. For a shared file you can enter or browse to a folder within an existing project directory.
Display in favorites menu	Select menu for launch configuration to appear.
Console Encoding	Select the character set to use to display information in the console window.
Standard Input and Output	Allocate input and output to console and/or specified file. If a file is selected, you can select Append option to append data to selected file.
Launch in background	Enable this option to launch debug operation in a background process.

Related concepts

Launch Configurations
About the Debugger

Related tasks

Creating a Launch Configuration

Related references

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/AddingClasses.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddingClasses.html Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddingClasses.html Mon Aug 10 15:50:55 2009 -0500 @@ -1,84 +1,80 @@ - -Adding Classes in Tasks - - - -

Adding Classes

- -

Use the New Class wizard to add a new C++ class to a project.

- -

To add a new C++ class

- -

-
- Click File > New > Class from the menu bar, - or select New > Class from the project′s pop-up - menu where you want the new class to reside.
-
- The New C++ Class wizard then appears. -
-
-
- Specify the folder when the class should be created by typing the Source Folder name or by clicking Browse and - selecting the source folder.
- -
-
-
- Select the Namespace checkbox, if you want to add - the class to a namespace. Click Browse to select an existing - namespace, or type the name of the new namespace.
-
-
- In the Class Name field, type the name of the class.
-
-
- Click Add to choose the Base Classes from which the class has to be derived
- -
-
To select a base type you are looking for, do the following:
-
1. Type the search string to locate the class, struct and other low-level types you are looking for
2. Select a Visible Type to narrow your search.
  -
  For example, if you are for looking for only classes then select the Class checkbox, etc. The Matching Types lists all the types matching the visible type and search string. The Qualifier lists the header file which contain the type - declaration of all the type listed.
  -
3. Click Add to add the selected type to the Base Classes list.
  -
  By default, the types are added with Public access and without Virtual inheritance, although these settings can be changed.
  -
4. Click OK when you have completed adding base classes, or click Cancel to cancel the action.
-
Once the Base Classes are added, you can click Remove to remove a selected class from the list. You can also click Up and Down after selecting a class from the list to change the order in which the base classes are inherited.
-
Select the Method Stubs you want the wizard to generate by selecting the appropriate checkbox. By default, both Constructor and Destructor are selected. By - default, the constructor is added with public access, and as non-virtual and non-inline, and the destructor is added as public, virtual, and not inline.
-
- Select the Use Default checkbox to create the C++ - class in new header and source files with default names. Otherwise, deselect - the Use Default checkbox, and enter the Header and Source file names. Click Browse to select the Header and Source files, if you want to - add the class declaration and definition to existing files.
- -
- Click Finish to create a C++ class according to the - specification, or click Cancel to cancel the task.

Related concepts

SDK Support

Related tasks

New C++ Classs Wizard

- - - - + +Adding Classes in Tasks + + + +

Adding Classes

+ +

Use the New Class wizard to add a new C++ class to a project.

+ +

To add a new C++ class

+ +

+
+ Click File > New > Class from the menu bar, + or select New > Class from the project′s pop-up + menu where you want the new class to reside.
+
+ The New C++ Class wizard then appears. +
+
+
+ Specify the folder when the class should be created by typing the Source Folder name or by clicking Browse and + selecting the source folder.
+ +
+
+
+ Select the Namespace checkbox, if you want to add + the class to a namespace. Click Browse to select an existing + namespace, or type the name of the new namespace.
+
+
+ In the Class Name field, type the name of the class.
+
+
+ Click Add to choose the Base Classes from which the class has to be derived
+ +
+
To select a base type you are looking for, do the following:
+
1. Type the search string to locate the class, struct and other low-level types you are looking for
2. Select a Visible Type to narrow your search.
  +
  For example, if you are for looking for only classes then select the Class checkbox, etc. The Matching Types lists all the types matching the visible type and search string. The Qualifier lists the header file which contain the type + declaration of all the type listed.
  +
3. Click Add to add the selected type to the Base Classes list.
  +
  By default, the types are added with Public access and without Virtual inheritance, although these settings can be changed.
  +
4. Click OK when you have completed adding base classes, or click Cancel to cancel the action.
+
Once the Base Classes are added, you can click Remove to remove a selected class from the list. You can also click Up and Down after selecting a class from the list to change the order in which the base classes are inherited.
+
Select the Method Stubs you want the wizard to generate by selecting the appropriate checkbox. By default, both Constructor and Destructor are selected. By + default, the constructor is added with public access, and as non-virtual and non-inline, and the destructor is added as public, virtual, and not inline.
+
+ Select the Use Default checkbox to create the C++ + class in new header and source files with default names. Otherwise, deselect + the Use Default checkbox, and enter the Header and Source file names. Click Browse to select the Header and Source files, if you want to + add the class declaration and definition to existing files.
+ +
+ Click Finish to create a C++ class according to the + specification, or click Cancel to cancel the task.

Related tasks

New C++ Classs Wizard

+ + + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Mon Aug 10 15:50:55 2009 -0500 @@ -27,7 +27,7 @@

Import the MMP or INF file

Select the Project in the C/C++ Project pane you want to debug

From the IDE select Run > Debug…

The New Launch Configuration Wizard appears

To communicate between the Carbide.c++ debugger and the on-device debug agent or protocol interface you must define a debug launch configuration. The Debug window is where you define the type of debug launch configuration to use when debugging programs on the target device (Figure 4).

Figure 4. Debug Window

diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,117 +1,117 @@ - - - - - - -Using Soft Attach for On-Device Debugging - - - -

Using Soft Attach for On-Device Debugging

You can debug hardware via Trace32 using the soft attach option. This enables you to debug an image flashed to ROM or on a memory card. Soft attach includes all the capabilities fo Stop-mode debugging but can't debug any code loaded before the OS is booted.

There are several components that must be provided to the debugger so that it can communicate with the attached hardware device. They are:

Config_carbide.t32 - a required configuration file used to configure Carbide for soft attach debugging
.cmm file - you must select the correct .cmm script file for the hardware otherwise it will not initialize properly and the debugger will be unable to communicate. The .cmm script files are located in the <Carbide>\plugins\com.nokia.carbide.cpp.support_2.0.x.xxx\Symbian_Support\Trace32\cmm_scripts directory.
-
- Also, if there is a specific .cmm file for the device, like H2 or H4, especially if it includes _attach in the name, choose that version over the others to do soft attach on the hardware.
.log file - you must have a valid .log file for the ROM image in order to debug the image

If the New Launch Configuration Wizard is used, you will be asked to identify the above files. If you used the New or Debug dialog to create a launch configuration, make sure that the above files are supplied.

The major steps to perform a soft attach are:

Import and build your project and the ROM image
Startup the device using the ROM image
Setup the debugger and begin debugging

1. Importing and building the project and ROM image

Import the project
Build the project
Create a ROM image -
Enter the desired command-line arguments for the ROM image in the ROM Build Command Line text box in the Carbide ROM Build Settings panel of the Properties for <project> dialog.
-

2. Starting up the device with the ROM image

Transfer the ROM image to the hardware via memory card or flash

NOTE Ensure that the hardware includes a boot loader program so that it can boot the ROM image from the memory card.

Power up the device -
Once the operating system has booted up, it is ready for the debugger to attach
-

3. Setting up the debugger to debug

On the hardware, launch the program to debug
Click Run > Debug to launch the New Launch Configuration Wizard
In the Launch Types page -
1. Select the Trace32 Launch Configuration
2. Click Next
-
In the Symbian ROM Image Settings page -
1. Enter the path to the Trace32 Initialization Script .cmm file
2. Select the Target Processor
3. Click Next
- In the Symbian ROM Image Settings page -
1. Enable Soft attach
2. Enter the Symbian ROM Log File
3. Click Next
-
In the New Launch Configuration page -
1. Enable the "Open launch configuration for additional customization of launch settings" option
2. Click Finish
-
In the Debug > Symbian OS Trace 32 > New_Configuration > Connection tab -
1. Enable the "View messages between Carbide and Trace32"
2. Click Debug
-

If the View messages between Carbide and Trace32 option is enabled, the Console view will show the communications between the debugger and the hardware (Figure 1). If you do not see the messages, verify that the Trace32 Communications Log is the active log view.

Figure 1. Debugger log showing .cmm file being used to initialize hardware

Once the debugger connects to the hardware it will halt the hardware at a random memory address (Figure 2). Press Resume in the Debug view to begin debugging.

Figure 2. Debugger stopping at a random address using soft attach

Debug the program in the Carbide debugger

Once the debugger is connected to the hardware you can:

Set breakpoints in the editor view

-
If breakpoints were already set in the project then an Editor view should display them as resolved. If no breakpoints have been set, now is the time to add them.
-
NOTE The number of breakpoints you can set is controlled by the hardware.
-

Click Suspend to halt the processor on the hardware
Use Disconnect (preferred) to stop debugging the program. This does not halt the processor.
Use Terminate to end the debug session

Related references

Debug perspective
Executables view
Symbian OS Data view
Registers view
Breakpoint view

- - - - + + + + + + +Using Soft Attach for On-Device Debugging + + + +

Using Soft Attach for On-Device Debugging

There are several components that must be provided to the debugger so that it can communicate with the attached hardware device. They are:

Config_carbide.t32 - a required configuration file used to configure Carbide for soft attach debugging
.cmm file - you must select the correct .cmm script file for the hardware otherwise it will not initialize properly and the debugger will be unable to communicate. The .cmm script files are located in the <Carbide>\plugins\com.nokia.carbide.cpp.support_2.0.x.xxx\Symbian_Support\Trace32\cmm_scripts directory.
+
+ Also, if there is a specific .cmm file for the device, like H2 or H4, especially if it includes _attach in the name, choose that version over the others to do soft attach on the hardware.
.log file - you must have a valid .log file for the ROM image in order to debug the image

The major steps to perform a soft attach are:

Import and build your project and the ROM image
Startup the device using the ROM image
Setup the debugger and begin debugging

1. Importing and building the project and ROM image

Import the project
Build the project
Create a ROM image +
Enter the desired command-line arguments for the ROM image in the ROM Build Command Line text box in the Carbide ROM Build Settings panel of the Properties for <project> dialog.
+

2. Starting up the device with the ROM image

Transfer the ROM image to the hardware via memory card or flash

NOTE Ensure that the hardware includes a boot loader program so that it can boot the ROM image from the memory card.

Power up the device +
Once the operating system has booted up, it is ready for the debugger to attach
+

3. Setting up the debugger to debug

On the hardware, launch the program to debug
Click Run > Debug to launch the New Launch Configuration Wizard
In the Launch Types page +
1. Select the Trace32 Launch Configuration
2. Click Next
+
In the Symbian ROM Image Settings page +
1. Enter the path to the Trace32 Initialization Script .cmm file
2. Select the Target Processor
3. Click Next
+ In the Symbian ROM Image Settings page +
1. Enable Soft attach
2. Enter the Symbian ROM Log File
3. Click Next
+
In the New Launch Configuration page +
1. Enable the "Open launch configuration for additional customization of launch settings" option
2. Click Finish
+
In the Debug > Symbian OS Trace 32 > New_Configuration > Connection tab +
1. Enable the "View messages between Carbide and Trace32"
2. Click Debug
+

Figure 1. Debugger log showing .cmm file being used to initialize hardware

Once the debugger connects to the hardware it will halt the hardware at a random memory address (Figure 2). Press Resume in the Debug view to begin debugging.

Figure 2. Debugger stopping at a random address using soft attach

Debug the program in the Carbide debugger

Once the debugger is connected to the hardware you can:

Set breakpoints in the editor view

+
If breakpoints were already set in the project then an Editor view should display them as resolved. If no breakpoints have been set, now is the time to add them.
+
NOTE The number of breakpoints you can set is controlled by the hardware.
+

Click Suspend to halt the processor on the hardware
Use Disconnect (preferred) to stop debugging the program. This does not halt the processor.
Use Terminate to end the debug session

Related references

Debug perspective
Executables view
Symbian OS Data view
Registers view
Breakpoint view

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,37 +1,37 @@ - - - - - -Stop Mode On-Device Debugging - - - -

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.

The basic steps include:

Verify that your SDK or customer kit is recognized in the SDK preferences panel.
Create project or Import the project's bld.inf file into Carbide.c++
Specify your ROM build settings for the selected project
Build your Project with the ARMV5 Debug Build Configuration
Create a launch configuration for Trace32 or Sophia
Launch the debugger

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.

Attach to Process

Use Attach to Process to debug any binaries outside the workspace. The methods to do this include:

Select a process in the Symbian OS Data View, then click Debug to launch the debugger which then attaches to the selected process. Ensure that the binary to debug is included in the Executables view in order to set and hit any breakpoints.
Create an Attach to Process Launch Configuration using the New Launch Configuration Wizard for the project

Related Tasks

- - - - + + + + + +Stop Mode On-Device Debugging + + + +

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.

The basic steps include:

Verify that your SDK or customer kit is recognized in the SDK preferences panel.
Create project or Import the project's bld.inf file into Carbide.c++
Specify your ROM build settings for the selected project
Build your Project with the ARMV5 Debug Build Configuration
Create a launch configuration for Trace32 or Sophia
Launch the debugger

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.

Attach to Process

Use Attach to Process to debug any binaries outside the workspace. The methods to do this include:

Select a process in the Symbian OS Data View, then click Debug to launch the debugger which then attaches to the selected process. Ensure that the binary to debug is included in the Executables view in order to set and hit any breakpoints.
Create an Attach to Process Launch Configuration using the New Launch Configuration Wizard for the project

Related Tasks

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,32 +1,32 @@ - - - - - -Stop Mode On-Device Debugging - - - -

Stop Mode On-Device Debugging Preconditions

Before conducting a Stop Mode On-Device debug session the following preconditions should be met.

Verifying On-device Debugging Preconditions

Install ActiveState PERL. You can download a copy of Perl at www.ActiveState.com.
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
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

Related Tasks

- - - + + + + + +Stop Mode On-Device Debugging + + + +

Stop Mode On-Device Debugging Preconditions

Before conducting a Stop Mode On-Device debug session the following preconditions should be met.

Verifying On-device Debugging Preconditions

Install ActiveState PERL. You can download a copy of Perl at www.ActiveState.com.
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
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

Related Tasks

+ + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/view_symbian_kernel_set.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/view_symbian_kernel_set.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/view_symbian_kernel_set.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,37 +1,37 @@ - - - - - - -Stopping Program Execution - - - -

Setting Symbian OS Data View Refresh Rate

A global preference option in the Preferences window of Carbide.c++ allows a user to change the time interval for auto-refreshing kernel data in the Symbian OS View.

To set the refresh rate

Select Window > Preferences to display Preferences window
Expand C/C++ and Debug from list
Select Carbide.c++ to display the Carbide.c++ Global settings panel (figure 1)
Enter a time interval from 3 to 600 seconds for kernel data to be refreshed. 20 seconds is the default.

Figure 1. Symbian OS Kernel Data Refresh Rate

Related concepts

Related references

Debug View
Symbian OS View Window

- - - - + + + + + + +Stopping Program Execution + + + +

Setting Symbian OS Data View Refresh Rate

A global preference option in the Preferences window of Carbide.c++ allows a user to change the time interval for auto-refreshing kernel data in the Symbian OS View.

To set the refresh rate

Select Window > Preferences to display Preferences window
Expand C/C++ and Debug from list
Select Carbide.c++ to display the Carbide.c++ Global settings panel (figure 1)
Enter a time interval from 3 to 600 seconds for kernel data to be refreshed. 20 seconds is the default.

Figure 1. Symbian OS Kernel Data Refresh Rate

Related concepts

Related references

Debug View
Symbian OS View Window

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,36 +1,36 @@ - - - - - - -Debugging a Program - - - -

Debugging a Program

Use the Debug command () to execute a program under debugger control using the current launch configuration settings.

If this is the first time the program is launched for debugging, a new debug launch configuration is automatically created for you based on current project settings and assigned a name. If a debug launch configuration is already available, the Debug command launches using the last debug launch configuration used with the project.

Launching a Program for Debugging

Click the Debug button () in the C/C++ perspective

Select Run > Debug from the menu bar

Both of these methods create a new debug launch configuration if none previously existed in the project or uses the last one launched for debugging.

To launch using a specific debug launch configuration, right-click the project's EXE file in the C/C++ Projects view and select Debug As > Project_Name from the C/C++ Projects context menu

The debugger assumes control of the program execution as the program runs.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - + + + + + + +Debugging a Program + + + +

Debugging a Program

Use the Debug command () to execute a program under debugger control using the current launch configuration settings.

Launching a Program for Debugging

Click the Debug button () in the C/C++ perspective

Select Run > Debug from the menu bar

Both of these methods create a new debug launch configuration if none previously existed in the project or uses the last one launched for debugging.

To launch using a specific debug launch configuration, right-click the project's EXE file in the C/C++ Projects view and select Debug As > Project_Name from the C/C++ Projects context menu

The debugger assumes control of the program execution as the program runs.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

+ + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_disconnect.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_disconnect.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,34 +0,0 @@ - - - - - - -Disconnecting the Debugger - - - -

Disconnecting the Debugger

Use the Disconnect command () when debugging with Application TRK or System TRK to detach the debugger from a process on the device while leaving the device running.

When debugging in stop-mode it will detach the debugger and leave the CPU running on the device.

Disconnecting the Debugger

Click the Disconnect button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Disconnect from the Debug context menu

Related references

Working with the Debugger
Debug View

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_kill.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_kill.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,45 +0,0 @@ - - - - - - -Killing Program Execution - - - -

Terminate Program Execution

Use the Terminate command () to stop or halt a program based on the type of debugging session underway. Terminate behavior includes:

Emulator - terminates program execution and ends the debug session
Application TRK or System TRK - kills the process on the device and ends the debug session. To terminate without killing the process, use Disconnect instead.
Stop-mode soft attach - suspends the attached process while other processes continue to run on the device. If only a single process is running on the device, the device CPU is suspended. Once the CPU is suspended you must launch a new debug session to resume the device CPU.

This behavior differs from suspending a program, as this temporarily suspends execution.

NOTE If the Debug view loses focus, the Terminate control will appear disabled. To regain focus, select a thread in the Debug view to update the tool bar and reactivate the Terminate control.

Terminating Program Execution

Click the Terminate button () in the Debug view

-
or
-

Right-click and select Terminate from the Debug context menu

Select Run > Terminate from the menu bar

The debugger kills program execution and ends the debugging session.

NOTE If using an emulator, exiting it will also end the debugging session.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_restart.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_restart.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,36 +0,0 @@ - - - - - - -Common Debugging Actions - - - -

Restarting the Debugger

Click the Restart button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Restart from the Debug contextual menu

Select Run > Restart from the menu bar

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_resume.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_resume.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,41 +0,0 @@ - - - - - - -Resuming Program Execution - - - -

Resuming Program Execution

NOTE If the Debug view loses focus, the Resume control will appear disabled. To regain focus, select a thread in the Debug view to update the tool bar and reactivate the Resume control.

Resuming Program Execution

Click the Resume button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Resume from the Debug contextual menu

Select Run > Resume from the menu bar

The suspended session resumes, or the view changes to the running program.

NOTE The Resume command appears only for those platforms that support it. If your platform does not support this command, you must stop the current debugging session and start a new session.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_run.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_run.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,42 +0,0 @@ - - - - - - -Running a Program - - - -

Running a Program

Use the Run command () to execute a program normally, without debugger control. If the target is an emulator, the emulator is launched and the program installed. Use the emulator controls to run the program within the emulator environment. If the target is not an emulator, the program is installed and can be run on the device like any other program.

When starting the program for the first time, there are two types of launch configurations that you can choose between:

Run As > Symbian OS Application — select this option to create a new run launch configuration for the project or run the the first launch configuration it finds in the run launch configuration list (starting at the top of the list). Basically, this is a shortcut to help you start debugging immediately.
Open Run Dialog... — enables you to define one or more launch configurations for this project.

Running a Program

Click the Run () control in the tool bar

-
or
-

Right-click the project's EXE file in the C/C++ Projects view and select Run As > Project_Name from the C/C++ Projects context menu

The debugger does not control program execution as the program runs.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_start.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_start.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,45 +0,0 @@ - - - - - - -Starting the Debugger - - - -

Starting the Debugger

Use the Debug command () to begin debugging a compiled program. The debugger takes control of program execution, starting at the main entry point of the program. When starting the debugger for the first time, there are two types of debug launch configurations that you can choose between:

Debug As > Symbian OS Application — select this option to create a new debug launch configuration for the project or run the the first debug launch configuration it finds in the debug launch configuration list (starting at the top of the list). Basically, this is a shortcut to help you start debugging immediately.
Open Debug Dialog... — enables you to define one or more launch configurations for this project.

In the following steps, Config_Name refers to both debug launch configuration types.

Starting the Debugger

NOTE You can only debug compiled programs. Use the Build Project command to compile project sources into a binary file.

Right-click the project's EXE file in the C/C++ Projects view and select Debug As > Config_Name from the C/C++ Projects contextual menu

Select the project to debug and click the Debug button () in the C/C++ perspective

-
NOTE If you don't see the Debug button on your EXE file you'll need to define a Configuration for the program.
-
or
-

Select the project to debug and then select Run > Debug As > Config_Name from the menu bar

The current routine executes and returns to its caller, then program execution stops

NOTE Some projects require additional configuration before the debugging session can begin. The IDE might prompt you for permission to perform this configuration automatically.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepinto.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepinto.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,44 +0,0 @@ - - - - - - -Stepping Into a Routine - - - -

Stepping Into a Routine

Use the Step Into command () to execute one source-code statement at a time and follow execution into a routine call.

Stepping Into a Routine

Click the Step Into button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Step Into from the Debug contextual menu

Select Run > Step Into from the menu bar

After the debugger executes the source-code statement, the current-statement arrow moves to the next statement determined by these rules:

If the executed statement did not call a routine, the current-statement arrow moves to the next statement in the source code.
If the executed statement called a routine, the current-statement arrow moves to the first statement in the called routine.
If the executed statement is the last statement in a called routine, the current-statement arrow moves to the statement that follows the calling routine.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepout.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepout.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,38 +0,0 @@ - - - - - - -Step Return Out of a Routine - - - -

Step Return Out of a Routine

-Use the Step Return command (

) to execute the rest of the current routine and stop program execution after the routine returns to its caller. -

This command causes execution to return up the calling chain.

Step Returning from a Routine

Click the Step Return button () in the Debug view

-
or
-

Right-click the thread in the Debug view, then select Step Return from the Debug context menu

Select Run > Step Return from the menu bar

The current routine executes and returns to its caller, then program execution stops

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepover.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stepover.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,43 +0,0 @@ - - - - - - -Stepping Over a Statement - - - -

Stepping Over a Statement

the end of the called routine
a breakpoint
a watchpoint
an eventpoint that stops execution

Stepping Over a Routine

Click the Step Over button () in the Debug view

-
or
-

Right-click the thread in the Debug view and select Step Over from the Debug contextual menu

Select Run > Step Over from the menu bar

The current statement or routine executes, then program execution stops.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stop.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_stop.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,30 +0,0 @@ - - - - - - -Suspending Program Execution - - - -

Suspending Program Execution

Use the Suspend command () to stop program execution during a debugging session.

Stopping a Debug Session

Select the thread in the Debug view to suspend
Click the Suspend () button, or right-click the thread and select Suspend

The operating system surrenders control to the debugger, which suspends program execution.

For more information on debugging, see C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.

Related references

Working with the Debugger
Debug View

- - - - diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_debugger_to_process.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_debugger_to_process.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_debugger_to_process.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,46 +1,46 @@ - - - - - - -Attaching to a Symbian OS Process - - - -

Attaching to a Symbian OS Process

Use the Symbian OS Attach to Process launch configuration to attach the debugger to an already running Symbian OS process or thread on a target device. This is useful for debugging servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate as one example.

You can also attach to a process in the Symbian OS Data view when debugging.

NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian OS and the TRK debug agent.

When attempting to find a process the debugger uses the UID3 to locate the process.

Attaching to a Symbian OS Process

Import an executable to import it into the Executables view
Select any project in the workspace or the binary to attach to in the Executables view

In this example, we select the Executables project created when the binary was imported from the Project Explorer view (Figure 1).

Figure 1 - Executables project created when importing an executable

Click Debug () to launch the New Configuration Launch Wizard
Select the Attach to Process Launch Configuration option and fill in the requested information
Click Debug

The Attach to Process window appears. Click a column title to sort the processes in ascending or descending order to help you locate a specific process or use the filter text box to show specific processes.

Figure 2 - Attach to Process window

Select a process, click OK

The Attach to Process window closes. Open a Symbian OS view to show the process and thread information.

NOTE Terminating an Attach to Process session actually kills the process on the device. This means you must restart the process on the device in order to attach to it again.

Related references

- - - - + + + + + + +Attaching to a Symbian OS Process + + + +

Attaching to a Symbian OS Process

You can also attach to a process in the Symbian OS Data view when debugging.

NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian OS and the TRK debug agent.

When attempting to find a process the debugger uses the UID3 to locate the process.

Attaching to a Symbian OS Process

Import an executable to import it into the Executables view
Select any project in the workspace or the binary to attach to in the Executables view

In this example, we select the Executables project created when the binary was imported from the Project Explorer view (Figure 1).

Figure 1 - Executables project created when importing an executable

Click Debug () to launch the New Configuration Launch Wizard
Select the Attach to Process Launch Configuration option and fill in the requested information
Click Debug

Figure 2 - Attach to Process window

Select a process, click OK

The Attach to Process window closes. Open a Symbian OS view to show the process and thread information.

NOTE Terminating an Attach to Process session actually kills the process on the device. This means you must restart the process on the device in order to attach to it again.

Related references

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/launch_config_toolbar.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/launch_config_toolbar.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/new_config.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/new_config.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/sos_processes_attach.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/images/sos_processes_attach.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/add_build_config_create_wnd.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/add_build_config_create_wnd.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/icon_add_item_to_list.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/icon_add_item_to_list.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_build_config_select_tgt_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_build_config_select_tgt_02.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_prj_debugas_debug.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_prj_debugas_debug.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_prj_debugas_sos_menu.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/menu_prj_debugas_sos_menu.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/new_launch_config_wiz.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/new_launch_config_wiz.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_app.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_app.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_02.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_bld_tgt.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_bld_tgt.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_cpp_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/page_debug_dlls_cpp_view.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/pref_launching.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/pref_launching.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/proj_prop_builders.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/proj_prop_builders.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/run_config_device.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/run_config_device.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/symprojnav_mmp.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/symprojnav_mmp.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_01.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_02.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_03.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_03.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_04.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_cpp_prj_mutli_build_04.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_hellocarbide_cpp_view.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/view_hellocarbide_cpp_view.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wiz_add_sos_class_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wiz_add_sos_class_01.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wiz_add_sos_class_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wiz_add_sos_class_02.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_debug_configuration.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_debug_configuration.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_03.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_03.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_04.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_04.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_07.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_07.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_08.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_import_executable_08.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_prj_freeze_def_files.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_prj_freeze_def_files.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_prj_props_createsis.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_prj_props_createsis.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,63 +1,63 @@ - - - - - - -Working with PKG and SIS Files - - - -

Creating a .SIS File

Carbide.c++ attempts to build SIS files for all phone targets when a PKG file exists in a given build project. More than one SIS/PKG file can be included and built by a project, but only one can be downloaded to the device for debugging purposes.

There are three main tools involved in generating SIS files from PKG files.

Makekeys - We invoke this tool when you don't specify a key/cert pair for OS - 9.x SIS file creation.
Makesis — This tool takes a single PKG file as input and generates an unsigned SIS file. This is generally sufficient to run an application on a pre platform security device (EKA1). This tool is also used to generate SIS files for Platform Security, but in that case signsis must be used.
Signsis — This tool is used to sign a SIS file generated by makesis. This tool is not available on all SDKs. This tool requires an existing certificate/key pair and does not randomly generate the pair for self-signing.

When a phone target build detects a PKG file at the end of a build, a post-link stage will be executed to create a SIS file, that is:

For non-Platform Security SDKs (pre-OS 9.x), makesis is called

Depending upon which tool is used, you will need to complete some entries in the SIS Builder pane of the Carbide Build Configurations window of the project Properties dialog box. You can access this pane by selecting a project in the C/C++ Projects view and select Project > Properties > Carbide Build Configurations. Fill in the necessary information to add PKG files to the project for downloading.

- - - - - - - - - - - - - -

Tool

Explanation

SIS Builder

Use the Add control to add one or more SIS or PKG files to the project up to the maximum number Carbide supports. Note that the SIS Builder pane operates on a build configuration level. You will need to add files in this pane for every build configuration in the project.

In addition, any PKG file added here is picked up by the Installation tab in Application TRK configurations. However, as only one SIS file can be debugged at a time you must specify which SIS/PKG file to install for debugging purposes. This is handy if you have both a developer SIS file and a certified SIS file that you want to remain in sync during development. Both are always built but you only need to debug one.

Figure 1 - SIS Builder tab

SIS Properties

Complete the PKG File, and Signing Options settings in the SIS Properties dialog. By default, SIS files are output in the directory of the original SIS file.

Figure 2 - SIS Properties dialog

For phones that utilize OS 9.x, all SIS files must be signed before being installed on a device. You can specify your certificate and key pair file in the SIS Builder pane. By default, if no certificate/key pair is defined, temporary ones will be created in the build directory. This is a process called self-signing. However, not all devices allow self-signed applications to be installed. For information on obtaining certificate and key pairs for your development please visit https://www.symbiansigned.com.

Self-signing Tips

The MMP file must have certain keywords specified correctly including:

The keyword uid3 must be specified in the correct range. See https://www.symbiansigned.com/app/page/uidfaq for more info.
VendorID requires a value, even if its zero (VENDORID 0)
Capability requires a value, in this case none (CAPABILITY none)

Failure to include the above keywords can cause a self-signed APP/DLL process to fail to launch.

After you have a valid .sis file, it will need to be uploaded to the target device. The sis file is uploaded and installed automatically once you run a Debug launch configuration.

Related tasks

Manually Deploying Programs to Devices

- - - + + + + + + +Working with PKG and SIS Files + + + +

Creating a .SIS File

There are three main tools involved in generating SIS files from PKG files.

Makekeys - We invoke this tool when you don't specify a key/cert pair for OS + 9.x SIS file creation.
Makesis — This tool takes a single PKG file as input and generates an unsigned SIS file. This is generally sufficient to run an application on a pre platform security device (EKA1). This tool is also used to generate SIS files for Platform Security, but in that case signsis must be used.
Signsis — This tool is used to sign a SIS file generated by makesis. This tool is not available on all SDKs. This tool requires an existing certificate/key pair and does not randomly generate the pair for self-signing.

When a phone target build detects a PKG file at the end of a build, a post-link stage will be executed to create a SIS file, that is:

For non-Platform Security SDKs (pre-OS 9.x), makesis is called

+ + + + + + + + + + + + + +

Tool

Explanation

SIS Builder

Figure 1 - SIS Builder tab

SIS Properties

Complete the PKG File, and Signing Options settings in the SIS Properties dialog. By default, SIS files are output in the directory of the original SIS file.

Figure 2 - SIS Properties dialog

Self-signing Tips

The MMP file must have certain keywords specified correctly including:

The keyword uid3 must be specified in the correct range. See https://www.symbiansigned.com/app/page/uidfaq for more info.
VendorID requires a value, even if its zero (VENDORID 0)
Capability requires a value, in this case none (CAPABILITY none)

Failure to include the above keywords can cause a self-signed APP/DLL process to fail to launch.

After you have a valid .sis file, it will need to be uploaded to the target device. The sis file is uploaded and installed automatically once you run a Debug launch configuration.

Related tasks

Manually Deploying Programs to Devices

+ + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,101 +1,100 @@ - - - - - - - Creating a Launch Configuration - - - -

Creating a Launch Configuration

To run or debug a project you need a launch configuration. A project must have at least one launch configuration, and can have as many as necessary. When run on an emulator project the wizard simply creates an emulator launch configuration and launches the emulator. When running a device project for the first time the New Launch Configuration Wizard seeks additional information required to create the launch configuration, then downloads the executable to the device and launches it. Once the emulator or device are loaded with the executable, the debug session can commence.

There are two methods for setting up a launch configuration, including:

Default launch configuration— automatically sets up a default launch configuration to run or debug the project on the first Run or Debug execution. This provides a quick and easy method to start running or debugging a new project without the hassle of setting a lot of options. The default launch configuration can always be edited later as the project launch requirements change.
Custom launch configuration— enables you to setup a custom launch configuration to debug the project

Creating a Default Launch Configuration

NOTE Carbide.c++ only creates a new default launch configuration when it cannot find one in the project. If the project already contains a launch configuration, Carbide.c++ launches that instead.

Click the Run () or Debug () icon in the tool bar -
or
-
Choose Select Run > Run menu option to launch the project or Run > Debug menu option to debug the project

Carbide.c++ creates a default launch configuration for the project and begins running or debugging the project. If the project already has a defined launch configuration, clicking Run or Debug uses it instead of creating a new one. There are two possible scenarios when creating a default launch configuration:

for emulator targets - an emulator launch configuration is created based on the project settings
for target devices - the New Launch Configuration Wizard appears asking for additional information

NOTE To see if a project already has a launch configuration, open a Run or Debug window using the Run > Open Run Dialog... or Run > Open Debug Dialog... menu items. - -

Creating a Custom Launch Configuration

Open the Run or Debug launch configuration window -
- Select the Run> Open Run Dialog... or Run > Open Debug Dialog... menu item -
  The appropriate Run or Debug launch configuration window appears (Figure 1).
  -
-

-
Figure 1 - Initial blank Debug launch configuration window
-
Select a type of launch configuration (for example, Symbian OS Emulation), then click the New launch configuration icon to create a new - configuration of that type. -
A new configuration appears in the Configuration list under the - appropriate section using the project name and target to create the configuration name.
-
NOTE By default, when you click New, the project information is used to fill in the Project and Process to launch text boxes. You normally should not have to edit these for a run/debug a project. If a bld.inf has multiple MMPS then the first executable named in the list of MMP files is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field.
-

New launch configuration

Figure 2 - New launch configuration with name and settings filled in (emulator)

View the information to define the project and executable -
Modify or fill in the following fields in the Main tab so the IDE - can setup the configuration properly each time. Typically when creating - a new executable from a project that has successfully linked, the - fields will be auto-populated and do not need to be modified. The important fields here are:
-
- Name - This is a unique name to identify this debug launch configuration. It can be any name.
- Project - The project to associate with this debug launch configuration. Click Browse to select a different project.
- Process to launch - This is the name of the executable that is linked to the project.
-
Modify settings in the other Carbide tabs to customize the launch configuration - for the project -
- Environment (Eclipse)
- Debugger
- Executables
- x86 Exceptions
- Arguments (Eclipse)
- Source (Eclipse)
- Common (Eclipse)
-
To debug something outside of the workspace, be sure to import the binary into the Executables view.
-
Click Debug -
The IDE launches the executable. If the launch configuration is set to change perspective, it switches to the specified perspective.
-

Other references

- - - + + + + + + + Creating a Launch Configuration + + + +

Creating a Launch Configuration

There are two methods for setting up a launch configuration, including:

Default launch configuration— automatically sets up a default launch configuration to run or debug the project on the first Run or Debug execution. This provides a quick and easy method to start running or debugging a new project without the hassle of setting a lot of options. The default launch configuration can always be edited later as the project launch requirements change.
Custom launch configuration— enables you to setup a custom launch configuration to debug the project

Creating a Default Launch Configuration

NOTE Carbide.c++ only creates a new default launch configuration when it cannot find one in the project. If the project already contains a launch configuration, Carbide.c++ launches that instead.

Click the Run () or Debug () icon in the tool bar +
or
+
Choose Select Run > Run menu option to launch the project or Run > Debug menu option to debug the project

for emulator targets - an emulator launch configuration is created based on the project settings
for target devices - the New Launch Configuration Wizard appears asking for additional information

NOTE To see if a project already has a launch configuration, open a Run or Debug window using the Run > Open Run Dialog... or Run > Open Debug Dialog... menu items. + +

Creating a Custom Launch Configuration

Open the Run or Debug launch configuration window +
- Select the Run> Open Run Dialog... or Run > Open Debug Dialog... menu item +
  The appropriate Run or Debug launch configuration window appears (Figure 1).
  +
+

+
Figure 1 - Initial blank Debug launch configuration window
+
Select a type of launch configuration (for example, Symbian OS Emulation), then click the New launch configuration icon to create a new + configuration of that type. +
A new configuration appears in the Configuration list under the + appropriate section using the project name and target to create the configuration name.
+
NOTE By default, when you click New, the project information is used to fill in the Project and Process to launch text boxes. You normally should not have to edit these for a run/debug a project. If a bld.inf has multiple MMPS then the first executable named in the list of MMP files is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field.
+

New launch configuration

Figure 2 - New launch configuration with name and settings filled in (emulator)

View the information to define the project and executable +
Modify or fill in the following fields in the Main tab so the IDE + can setup the configuration properly each time. Typically when creating + a new executable from a project that has successfully linked, the + fields will be auto-populated and do not need to be modified. The important fields here are:
+
- Name - This is a unique name to identify this debug launch configuration. It can be any name.
- Project - The project to associate with this debug launch configuration. Click Browse to select a different project.
- Process to launch - This is the name of the executable that is linked to the project.
+
Modify settings in the other Carbide tabs to customize the launch configuration + for the project +
- Environment (Eclipse)
- Debugger
- Executables
- x86 Exceptions
- Arguments (Eclipse)
- Source (Eclipse)
- Common (Eclipse)
+
To debug something outside of the workspace, be sure to import the binary into the Executables view.
+
Click Debug +
The IDE launches the executable. If the launch configuration is set to change perspective, it switches to the specified perspective.
+

Other references

+ + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,32 +1,32 @@ - - - - - - -Debugging in ROM - - - -

Debugging in ROM

You will see symbolic information for other components when you are debugging in ROM using System TRK if those components were built with symbolic information and the ROM Log file is specified. If a function in the stack crawl is in a ROM module and the IDE is able to find a file containing symbolic information for that module, the IDE will load it automatically and display function names. The IDE will also allow source level debugging and let you set breakpoints in this module.

Some issues to pay attention to when debugging include:

In System TRK you must specify the ROM log file in the ROM Log tab of the TRK or Attach to Process launch configurations

-
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

Other references

- - - + + + + + + +Debugging in ROM + + + +

Debugging in ROM

Some issues to pay attention to when debugging include:

In System TRK you must specify the ROM log file in the ROM Log tab of the TRK or Attach to Process launch configurations

+
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

Other references

+ + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/wiz_new_launch_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/wiz_new_launch_config.htm Mon Aug 10 14:45:48 2009 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,95 +0,0 @@ - - - - - - - New Launch Configuration Wizard - - - -

New Launch Configuration Wizard

For Application TRK and System TRK the following pages appear:

Launch Type
Executable Selection
TRK Connection Settings
TRK SIS Selection (Application TRK only)
New Launch Configuration

For Trace32 launch configurations the following wizard pages appear:

Launch Type
Executable Selection
Trace32 Initialization Settings
Symbian ROM Image Settings
New Launch Configuration

For Sophia STI launch configurations the following wizard pages appear:

Launch Type
Executable Selection
Sophia Initialization Settings
Symbian ROM Image Settings
New Launch Configuration

For Attach to Process launch configurations the following wizard pages appear:

TRK Connection Settings
New Launch Configuration

To access the New Launch Configurtion Wizard, set the Build Target to a Phone Debug target (Figure 1), then click the Debug icon (). If no launch configuration exists for the build target the wizard is launched. If a launch configuration already exists, then that launch configuration is launched and not the wizard.

For emulator targets, the New Launch Configuration Wizard can gather all the information it needs from the project, so clicking Debug just launches the debug session.

Figure 1 - Build Target selection list

Launch Types

Use the Launch Types page to select the type of launch configuration for the build target. This page does not appear when using an Emulator target. Available types are listed from the most frequently chosen (Application TRK) to the least likely type (Attach to Process). Select a type and click Next.

Figure 2 - Launch Type page

Executable Selection

Use the Application Selection page to choose a binary created by the project to launch and debug and verify its location. If only a single binary is available the Process to launch option is disabled.

EMULATOR ONLY Use the Location field for emulator targets to verify that the correct executable on the host is selected. This field is not used with on-device launch configurations.

Use the Specify device path of remote process to launch option to specify alternate paths for launching the executable from RAM (c:\sys\bin\), ROM (z:\sys\bin\) or memory cards (e:\sys\bin\) .

Select the Executable to launch, verify it is the correct binary, then click Next.

Figure 3 - Executable Selection page (when project has multiple EXEs)

TRK Connection Settings

Use the TRK Connection Settings page to specify the connection used to communicate with the target device. If the device is already connected, the drop down list will include both the COM port and the name of the device using that port. Use the On-Device Conection dialog to verify and update all Carbide software services on the device. Choose the serial port used to communicate with the target device and click Next.

Figure 4 - TRK Connection Settings page

TRK SIS Selection

Use the TRK SIS Selection page to select the SIS file to install on the target device. Click the Modify SIS builder settings for build configuration link to open the SIS Builder properties pane to add, edit, or review the SIS files to build. Once the correct SIS File to Install is selected, click Next.

Figure 5 - TRK SIS Selection page

New Launch Configuration

Use the New Launch Configuration page to note the name of the configuration, confirm the launch configuration settings, and then launch the debug session. If something doesn't look right, click Back to return to a page and change its setting. If all the settings are correct, click Finish to start the debug session using this launch configuration.

If you checkmark Advanced settings, the Debug dialog appears instead of launching the project. This enables you to make additional changes to the new launch configuration before starting the debug session. By design and intent, this should seldom be required for the initial launch.

Figure 6 - New Launch Configuration page

Trace32 Initialization Settings

This page only appears when creating a Trace32 launch configuration.

Figure 7 - Trace32 Initialization Settings page

Sophia STI Initialization Settings

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

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

Figure 9 - Symbian ROM Image Settings page

Other references

Launch Configuration

- - - - \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/working_with_sis_pkg_files.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/working_with_sis_pkg_files.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/working_with_sis_pkg_files.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,54 +1,53 @@ - - - - - - -Working with PKG and SIS Files - - - -

Creating a PKG File

After creating a project for the application you are developing for a device, you will need to create a .pkg file if you are using Application TRK. A .pkg file contains all the files that will need to be downloaded to the device. Once a .pkg file is available, you can add it to a project, and the IDE will use it and additional information entered in the SIS Builder pane to create an application's .sis installation file. By default, when creating a project, the .pkg file is located in the project's sis folder.

A minimal .pkg file consists of the following lines:

Header — provides the following information on a single line: -
- application name — name of the application displayed on the target device
- UID — (0x10004299) unique application ID value
- major and minor version numbers — values that represent the application's major and minor version numbers
- current build number — value that represents the current .sis build number
-
Filenames and install location — the name of the file to include in the .sis file and its install location within the target device. Each line describes a single file.
Comments — .pkg file comment lines are preceeded by a semi-colon

PKG File Symbols

Carbide.c++ attempts to build SIS files for the current build configuration when a PKG file exists in a given build project. However, there can be one or more SIS file per project but only one can be selected in the Installation pane for downloading and debugging. We have introduced symbols you can use within your PKG file for Carbide so that you can use one PKG file in a project to produce several different SIS files, if required.

The following symbols are available for PKG files in order to make reuse of PKG files more efficient across build targets. These symbols are only supported within Carbide.c++. They are:

$(EPOCROOT) — the location of the epoc32 folder but not including the epoc32 folder
$(PLATFORM) — platform designator, for example: ARMI, WINSC (Emulator) , GCCE, THUMB, etc.
$(TARGET) — target designator UDEB (Debug) or UREL (Release)

These symbols are used to specify the input location of file resources on your host PC to be packaged in the SIS file.

Sample PKG file

A sample .pkg file might look like this:

;Header
- #{"HelloWorld"},(0xA0004299),1,0,0
-
-"$(EPOCROOT)epoc32\release\$(PLATFORM)\$(TARGET)\HelloWorld.exe" -"!:\sys\bin\HelloWorld.exe"
-"$(EPOCROOT)epoc32\data\z\resource\apps\HelloWorld.rsc" -"!:\resource\apps\HelloWorld.rsc"
-"$(EPOCROOT)epoc32\data\z\private\10003af\import\apps\HelloWorld_reg.rsc" - "!:\private\10003a3f\import\apps\HelloWorld_reg.rsc"
-"$(EPOCROOT)epoc32\data\z\resource\apps\HelloWorld.mbm" -"!:\resource\apps\HelloWorld.mbm"

In addition you will need to add the PKG file to the project before building the final application. Add the pkg file in the SIS builder tab of the Carbide Build Configurations in the project properties window.

Related references

- - - + + + + + + +Working with PKG and SIS Files + + + +

Creating a PKG File

A minimal .pkg file consists of the following lines:

Header — provides the following information on a single line: +
- application name — name of the application displayed on the target device
- UID — (0x10004299) unique application ID value
- major and minor version numbers — values that represent the application's major and minor version numbers
- current build number — value that represents the current .sis build number
+
Filenames and install location — the name of the file to include in the .sis file and its install location within the target device. Each line describes a single file.
Comments — .pkg file comment lines are preceeded by a semi-colon

PKG File Symbols

The following symbols are available for PKG files in order to make reuse of PKG files more efficient across build targets. These symbols are only supported within Carbide.c++. They are:

$(EPOCROOT) — the location of the epoc32 folder but not including the epoc32 folder
$(PLATFORM) — platform designator, for example: ARMI, WINSC (Emulator) , GCCE, THUMB, etc.
$(TARGET) — target designator UDEB (Debug) or UREL (Release)

These symbols are used to specify the input location of file resources on your host PC to be packaged in the SIS file.

Sample PKG file

A sample .pkg file might look like this:

;Header
+ #{"HelloWorld"},(0xA0004299),1,0,0
+
+"$(EPOCROOT)epoc32\release\$(PLATFORM)\$(TARGET)\HelloWorld.exe" -"!:\sys\bin\HelloWorld.exe"
+"$(EPOCROOT)epoc32\data\z\resource\apps\HelloWorld.rsc" -"!:\resource\apps\HelloWorld.rsc"
+"$(EPOCROOT)epoc32\data\z\private\10003af\import\apps\HelloWorld_reg.rsc" - "!:\private\10003a3f\import\apps\HelloWorld_reg.rsc"
+"$(EPOCROOT)epoc32\data\z\resource\apps\HelloWorld.mbm" -"!:\resource\apps\HelloWorld.mbm"

Related references

SIS Builder pane
SIS Properties

+ + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,61 +1,61 @@ - - - - - - -Debugging a Symbian OS Program on the S60 Emulator - - - -

Debugging a Symbian OS Program

Use the Carbide.c++ debugger to debug a compiled Symbian OS program in an emulator or on-device. The same process works for other emulators and target devices as well.

NOTE This example uses an emulator. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.

Debugging a Symbian OS program

NOTE You can only debug compiled programs. Use the Build Project command to compile project sources into a binary file if you do not already have an executable in the project. You will also need a symbolics ( .sym) file for debugging on a target device. Ensure that a .sym file has been created. If you are importing an existing application, you may have to rebuild the application and create a related .sym file. Make sure a .sym file has been created in the output directory.

Set a breakpoint in the HelloCarbide program

Open the \src\CHelloCarbideAppUI.cpp file and set a breakpoint in the HandleCommandL routine.

Figure 1 - Breakpoint set in CHelloCarbideAppUI::HandleCommandL routine.

Launch the Carbide.c++ debugger and S60 EPOC Emulator

Start the Carbide debugger which launches the S60 EPOC Emulator and installs the HelloCarbide application. For on-device debugging, your application will be installed on your target device.

Figure 2 - S60 Emulator launches

Open the Installed directory within the S60 Emulator or your target device

Figure 3 - Open the Installed directory

Launch the HelloCarbide application

Use the S60 Emulator or target device controls to launch the HelloCarbide application (Figure 4). -

Figure 4 - Launch the HelloCarbide application

The HelloCarbide application launches (Figure 5).

Figure 5 - HelloCarbide application running on S60 Emulator

Click the Options soft-key on the S60 Emulator to display the Select menu.
Choose the Message menu item and press the Select soft-key to send a message (Figure 6).

Figure 6 - Send Message to HelloCarbide application

The HandleCommandL breakpoint is hit in the program and control returns to the Carbide.c++ debugger (Figure 7). You can now set additional breakpoints, examine variables, or use the Debug view buttons to control the program.

Figure 7 - Back in the CHelloCarbideAppUI::HandleCommandL routine

That's it for this basic introduction to debugging with Carbide.c++.

Concepts

Projects

Tasks

- - - + + + + + + +Debugging a Symbian OS Program on the S60 Emulator + + + +

Debugging a Symbian OS Program

Use the Carbide.c++ debugger to debug a compiled Symbian OS program in an emulator or on-device. The same process works for other emulators and target devices as well.

NOTE This example uses an emulator. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.

Debugging a Symbian OS program

Set a breakpoint in the HelloCarbide program

Open the \src\CHelloCarbideAppUI.cpp file and set a breakpoint in the HandleCommandL routine.

Figure 1 - Breakpoint set in CHelloCarbideAppUI::HandleCommandL routine.

Launch the Carbide.c++ debugger and S60 EPOC Emulator

Start the Carbide debugger which launches the S60 EPOC Emulator and installs the HelloCarbide application. For on-device debugging, your application will be installed on your target device.

Figure 2 - S60 Emulator launches

Open the Installed directory within the S60 Emulator or your target device

Figure 3 - Open the Installed directory

Launch the HelloCarbide application

Use the S60 Emulator or target device controls to launch the HelloCarbide application (Figure 4). +

Figure 4 - Launch the HelloCarbide application

The HelloCarbide application launches (Figure 5).

Figure 5 - HelloCarbide application running on S60 Emulator

Click the Options soft-key on the S60 Emulator to display the Select menu.
Choose the Message menu item and press the Select soft-key to send a message (Figure 6).

Figure 6 - Send Message to HelloCarbide application

Figure 7 - Back in the CHelloCarbideAppUI::HandleCommandL routine

That's it for this basic introduction to debugging with Carbide.c++.

Concepts

Projects

Tasks

+ + + \ No newline at end of file diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,72 +1,72 @@ - - - - - - -Run Mode Debug Example - - - - -

Run Mode Debug Example (Application TRK)

This example shows how to create and build an application and debug it on a device using the Application TRK on-device debug agent. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.

Debugging a Run-mode Project using Application TRK

Import the Bld.inf to create a project using the Import wizard

In this example we are importing a project called Music, a complex project that includes several EXEs (MusicPlayer, MusicShop, MusicVisualizer). When we import, we select an ARM target.

Go to the project Properties page and in the Carbide Build Configuration panel specify the PKG file in the SIS Builder tab
Build the project (Ctrl+B)
Verify that all the binaries built by the project appear in the Executables view.

NOTE The symbolics are automatically loaded for the binaries that appear in the Executables view.

Set breakpoints in the project source files

In this example we will set one breakpoint in two different EXEs. The first is set in the file called MCEngine.cpp (MCServer.exe) and the second is set in MPlayerAppUI.cpp (MusicPlayer.exe).

Click the Debug icon () to launch the New Launch Configuration wizard -
1. Select the Application TRK Launch Configuration from the Launch Types page, then click Next
2. If you have more than one executable, select the Main Executable in the Executable Selection page of the wizard, then click Next
3. Select the remote connection to use in the TRK Connection Settings page, then click Next
4. Select the SIS file to install in the TRK SIS Selection page if not already populated
-
-
-
Figure 4 - TRK Connection Settings page showing selection
-
-
1. Click Finish
-
Once the debug session launches, control returns to the Debugger when one of the breakpoints set earlier is hit.

At this point you can debug the program in the Debug perspective. Look at the Breakpoints view to verify that the breakpoints set earlier are resolved. In this case, the breakpoint in the MCServer.exe.

Figure 5 - Debug perspective showing the resolved breakpoint

Click Resume in the Debug view to hit the breakpoint set in the second EXE

Figure 6 - Debug perspective showing the resolved EXE breakpoint

In the Debug view -
1. Click Disconnect to leave the application running on the device, OR
2. Click Terminate to stop the application running on the device
-

In addition, you can click the Symbian OS Data View to examine the processes running on the devise during the debug session.

Related references

- - - - + + + + + + +Run Mode Debug Example + + + + +

Run Mode Debug Example (Application TRK)

Debugging a Run-mode Project using Application TRK

Import the Bld.inf to create a project using the Import wizard

In this example we are importing a project called Music, a complex project that includes several EXEs (MusicPlayer, MusicShop, MusicVisualizer). When we import, we select an ARM target.

Go to the project Properties page and in the Carbide Build Configuration panel specify the PKG file in the SIS Builder tab
Build the project (Ctrl+B)
Verify that all the binaries built by the project appear in the Executables view.

NOTE The symbolics are automatically loaded for the binaries that appear in the Executables view.

Set breakpoints in the project source files

In this example we will set one breakpoint in two different EXEs. The first is set in the file called MCEngine.cpp (MCServer.exe) and the second is set in MPlayerAppUI.cpp (MusicPlayer.exe).

Click the Debug icon () to launch the New Launch Configuration wizard +
1. Select the Application TRK Launch Configuration from the Launch Types page, then click Next
2. If you have more than one executable, select the Main Executable in the Executable Selection page of the wizard, then click Next
3. Select the remote connection to use in the TRK Connection Settings page, then click Next
4. Select the SIS file to install in the TRK SIS Selection page if not already populated
+
+
+
Figure 4 - TRK Connection Settings page showing selection
+
+
1. Click Finish
+
Once the debug session launches, control returns to the Debugger when one of the breakpoints set earlier is hit.

Figure 5 - Debug perspective showing the resolved breakpoint

Click Resume in the Debug view to hit the breakpoint set in the second EXE

Figure 6 - Debug perspective showing the resolved EXE breakpoint

In the Debug view +
1. Click Disconnect to leave the application running on the device, OR
2. Click Terminate to stop the application running on the device
+

In addition, you can click the Symbian OS Data View to examine the processes running on the devise during the debug session.

Related references

+ + + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/window_updater.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/window_updater.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_copy_to_memory_card.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_copy_to_memory_card.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_select_device.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_select_device.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_stop_usb_device.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/trk_stop_usb_device.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_file_transfer.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_file_transfer.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_mass_storage.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_mass_storage.png has changed diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_remove_hardware.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/images/wnd_usb_remove_hardware.png has changed diff -r 23528f18d3fd -r ad8d147e8273 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 Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm Mon Aug 10 15:50:55 2009 -0500 @@ -1,52 +1,52 @@ - - - - - - -Launch Configuration Setup - - - -

Launch Configuration Setup

To communicate between the Carbide.c++ debugger and the on-device debug agent, using either Application TRK or System TRK, you must define a debug launch configuration that matches the installed debug agent. The two configurations available include:

Symbian OS Appication TRK— used to run or debug applications on a target device using the Application TRK on-device debug agent. Application TRK is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian OS installation file to the phone and install it prior to launching.
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

Choose the Run > Open Debug Dialog... menu item

The Debug window appears.

Select a Configuration type for on-device debugging and click New

Choose the Symbian OS Application TRK or System TRK configuration based on which debug agent is installed on the device, then click New. A new debug launch configuration appears in the Configuration list and the Main tab appears.

Enter the required information

For debug launch configurations using the TRK debug agent, the following pages require review and possible option settings:

Main— defines the project to be launched on the target device
Arguments — enter command line build system arguments
Debugger— provides control over entry points, message handling, and instruction set default settings
Connection— specifies the method used to transfer files to the target device
File Transfer — the files transfered to the target device at the start of each launch
Installation (Application TRK only)— specifies the .sis or .pkg file to install on the target device
Executables — specifies the executables to be debugged
ROM Log (System TRK only) — specifies the executables to be debugged

Click Debug

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.

Related references

- - - + + + + + + +Launch Configuration Setup + + + +

Launch Configuration Setup

Symbian OS Appication TRK— used to run or debug applications on a target device using the Application TRK on-device debug agent. Application TRK is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian OS installation file to the phone and install it prior to launching.
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.

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

Defining a Customized Launch Configuration

Choose the Run > Open Debug Dialog... menu item

The Debug window appears.

Select a Configuration type for on-device debugging and click New

Enter the required information

For debug launch configurations using the TRK debug agent, the following pages require review and possible option settings:

Main— defines the project to be launched on the target device
Arguments — enter command line build system arguments
Debugger— provides control over entry points, message handling, and instruction set default settings
Connection— specifies the method used to transfer files to the target device
File Transfer — the files transfered to the target device at the start of each launch
Installation (Application TRK only)— specifies the .sis or .pkg file to install on the target device
Executables — specifies the executables to be debugged
ROM Log (System TRK only) — specifies the executables to be debugged

Click Debug

Related references

+ + + diff -r 23528f18d3fd -r ad8d147e8273 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Mon Aug 10 14:45:48 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Mon Aug 10 15:50:55 2009 -0500 @@ -27,7 +27,7 @@

Figure 1. Bluetooth Configuration windows Accessibility panel

Write down the Bluetooth COM Port number from the Local Services tab (Figure 2) for later use

The Bluetooth COM Port number in the Local Services tab - should match the COM port used in the Connections tab of the TRK launch
+ should match the COM port used in the Connections tab of the TRK launch
configuration.

Figure 2. Bluetooth Configuration windows Local Services panel

@@ -41,7 +41,7 @@

Related references

Related tasks

Locate the S60 Phone USB (COMx) item in the list (Figure 2)

Figure 2. Device Manager showing Ports (COM & LPT) section

The USB COM Port number should match the COM port used in the Connections tab of the TRK launch +
The USB COM Port number should match the COM port used in the Connections tab of the TRK launch configuration.
Close the Device Manager window

Related references

Related tasks

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.

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

On the device ensure that the Bluetooth communications is turned on
On the PC ensure that the Bluetooth device is turned on
From your PC, search for available Bluetooth devices and make sure your device is listed
On the PC, right-click the SISX file, then choose the Send To > Bluetooth > device menu item (Figure 1)

Figure 1. Right-click SISX file

Follow the on-screen instructions to transfer the SISX file to the target device

The SISX file is transfered to the target device as a message. On the target device you may need to set a PIN code for the file transfer, accept the message, then wait for the "You have 1 new message" alert to appear.

Locate the new message on the target device

Start the Messaging application on the target device and locate the new message.

Select the SISx file and open the file to install it
Click OK when prompted to install TRK
Follow the instructions on the screen to finish installing the TRK debug agent

Related concepts

On-device Debugging

Related references

Related tasks

Installing On-device Debug Agents using Bluetooth

Installing an On-device Debug Agent using Bluetooth

On the device ensure that the Bluetooth communications is turned on
On the PC ensure that the Bluetooth device is turned on
From your PC, search for available Bluetooth devices and make sure your device is listed
On the PC, right-click the SISX file, then choose the Send To > Bluetooth > device menu item (Figure 1)

Figure 1. Right-click SISX file

Follow the on-screen instructions to transfer the SISX file to the target device

Locate the new message on the target device

Start the Messaging application on the target device and locate the new message.

Select the SISx file and open the file to install it
Click OK when prompted to install TRK
Follow the instructions on the screen to finish installing the TRK debug agent

Related concepts

On-device Debugging

Related references

Related tasks

Installing On-device Debug Agents using USB

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.

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.

Installing an On-device Debug Agent using PC Suite (USB example)

Store the TRK SISX file on the PC connected to the device

The Application TRK debug agents are stored online and can be downloaded and installed using the On-Device Connections > New Connection Wizard > Install remote agents pane.

Connect the USB cable to the PC, then to the device

A status indicator should appear on the device indicating a serial connection has been established.

Connect to the device using the latest PC Suite software -
1. Install PC Suite if not available
2. Launch the PC Suite software
3. Click the "Click here to connect to a phone" and follow the Get Connected wizard instructions
-
Double-click the TRK SISX file to install it on the device

-
The PC Suite application installer launches and asks where to install the SISX file. Select the recommended destination for installed applications on the device and click Yes. The SISX file is installed.
- Then exit out of PC Suite.

Related concepts

On-device Debugging

Related reference

Related tasks

Installing On-device Debug Agents using USB

Installing On-device Debug Agents using PC Suite

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.

Installing an On-device Debug Agent using PC Suite (USB example)

Store the TRK SISX file on the PC connected to the device

The Application TRK debug agents are stored online and can be downloaded and installed using the On-Device Connections > New Connection Wizard > Install remote agents pane.

Connect the USB cable to the PC, then to the device

A status indicator should appear on the device indicating a serial connection has been established.

Connect to the device using the latest PC Suite software +
1. Install PC Suite if not available
2. Launch the PC Suite software
3. Click the "Click here to connect to a phone" and follow the Get Connected wizard instructions
+
Double-click the TRK SISX file to install it on the device

+
The PC Suite application installer launches and asks where to install the SISX file. Select the recommended destination for installed applications on the device and click Yes. The SISX file is installed.
+ Then exit out of PC Suite.

Related concepts

On-device Debugging

Related reference

Related tasks

Installing On-device Debug Agents using USB

An USB connection can be used to install the on-device debug agent, either Application TRK or System TRK, (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.

NOTE You can use the connection software that came with your device to install the on-device debug agent SISX file. For example, all Nokia phones ship with the PC Suite software for installing programs. See your phone's operating manual for assistance on using it's software.

Installing an On-device Debug Agent using USB

Connect the PC and the target device using a USB connectivity cable

Physically connect the USB cable to the PC, then to the target device.

Setup the target device to accept file transfers from the PC

The target device recognizes the USB cable connection.

Select USB Mode > File Transfer, then press OK soft key

A notification message appears warning you the phone will be offline.

Press OK soft key to accept notification

The message "USB file transfer connection active" appears on the phone. On the PC, a folder appears showing the memory cards folders and files.

Copy the SISX file to phone memory or MMC card

Locate the SISX file on the PC, then select and copy it into the target device's memory card.

Install the SISX file

The final step is to install the SISX program on the target device.

Locate and launch the SISX file to install
Follow the instructions on the screen to finish installing the TRK debug agent

Related concepts

On-device Debugging

Related reference

Related tasks

Installing On-device Debug Agents using USB

Installing an On-device Debug Agent using USB

Connect the PC and the target device using a USB connectivity cable

Physically connect the USB cable to the PC, then to the target device.

Setup the target device to accept file transfers from the PC

The target device recognizes the USB cable connection.

Select USB Mode > File Transfer, then press OK soft key

A notification message appears warning you the phone will be offline.

Press OK soft key to accept notification

The message "USB file transfer connection active" appears on the phone. On the PC, a folder appears showing the memory cards folders and files.

Copy the SISX file to phone memory or MMC card

Locate the SISX file on the PC, then select and copy it into the target device's memory card.

Install the SISX file

The final step is to install the SISX program on the target device.

Locate and launch the SISX file to install
Follow the instructions on the screen to finish installing the TRK debug agent

Related concepts

On-device Debugging

Related reference

Related tasks

Installing an On-device Debug Agent

To use any version of the on-device debug agent on a target device it must be installed. We highly recommend using the On-Device Connections dialog to help connect and verify that the latest version of TRK is installed on the device. Or, to manage this manually, follow the instructions to install the TRK debug agent software using Bluetooth or USB.

Related references

Installing an On-device Debug Agent

Related references

TRK Overview

This section describes how to setup and use the on-device debug agent software to debug programs on S60 v3.x and UIQ 3rd edition devices. Topics include:

Preconditions for Using On-device Debugging
Installing the On-device Debug Agent on a Device
Connecting a PC to a Device using PC Suite, Bluetooth or USB
Setting up Carbide.c++ Connectivity

Related references

TRK Overview

This section describes how to setup and use the on-device debug agent software to debug programs on S60 v3.x and UIQ 3rd edition devices. Topics include:

Preconditions for Using On-device Debugging
Installing the On-device Debug Agent on a Device
Connecting a PC to a Device using PC Suite, Bluetooth or USB
Setting up Carbide.c++ Connectivity

Related references

ODD Preconditions

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.

Verifying On-device Debugging Preconditions

Verify that your system has the following: -
- S60 v3.x, UIQ 2.X or UIQ 3.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
-
Download and install the current TRK SISX file using the On-Device Setup dialog for debugging S60 5th edition and UIQ devices

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.

Specify the communication method with the on-target device during the debug session

Start the Application TRK or System TRK on the device. During startup of TRK on the device you must specify the communication method the on-device agent uses to debug the device. Currently, those methods include Bluetooth and USB or a null serial cable. For Bluetooth, you must pair the device with the PC and a valid serial port assigned. For USB, A USB cable must connect the PC to the device and a valid serial port assigned. Use On-Device Setup dialog to make the identification and connection setup quick and easy.

Related concepts

Related reference

Starting the On-Device TRK Debug Agent

Related tasks

ODD Preconditions

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.

Verifying On-device Debugging Preconditions

Verify that your system has the following: +
- S60 v3.x, UIQ 2.X or UIQ 3.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
+
Download and install the current TRK SISX file using the On-Device Setup dialog for debugging S60 5th edition and UIQ devices

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.

Specify the communication method with the on-target device during the debug session

Related concepts

Related reference

Starting the On-Device TRK Debug Agent

Related tasks

Bluetooth Connectivity Setup

Starting the On-Device TRK Debug Agent

The location of the TRK 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.

Launch the Application TRK or System TRK program on the device
When requested, select your computer from the available Bluetooth devices list

Figure 1. Example device list on a S60 3rd Edition or UIQ device

Verify the Bluetooth connection is working -(Figure 2) -
-
Figure 2. COM port verification in TRK on a device
-
If Application TRK reports "Not Connected" -
1. Click Options > Settings soft key
2. If Connection is not set to BlueTooth, choose BlueTooth
3. Click Ok soft key
4. Restart Application TRK
-

Bluetooth Connectivity Setup

Starting the On-Device TRK Debug Agent

Launch the Application TRK or System TRK program on the device
When requested, select your computer from the available Bluetooth devices list

Figure 1. Example device list on a S60 3rd Edition or UIQ device

Verify the Bluetooth connection is working +(Figure 2) +
+
Figure 2. COM port verification in TRK on a device
+
If Application TRK reports "Not Connected" +
1. Click Options > Settings soft key
2. If Connection is not set to BlueTooth, choose BlueTooth
3. Click Ok soft key
4. Restart Application TRK
+

Related concepts

On-device Debugging

Related references

Debug Window (On-device Debugging) Overview

Related tasks

Installing On-device Debug Agents using Bluetooth

Bluetooth Connectivity Setup

Starting the On-Device Debug Agent Using USB

On the device -
1. Launch Application TRK or System TRK program on the device
-
Select PC-Suite from the USB Mode list
Launch the Application TRK program
Halt the Bluetooth device search by pressing the Cancel soft key
Click Options > Settings > Connection
Change Connection type to USB and set connection options

-

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

Select Back and start the TRK again and you should be connected

Related concepts

On-device Debugging

Related references

Debug Window (On-device Debugging) Overview

Related tasks

Installing On-device Debug Agents using Bluetooth

Bluetooth Connectivity Setup

Starting the On-Device Debug Agent Using USB

On the device +
1. Launch Application TRK or System TRK program on the device
+
Select PC-Suite from the USB Mode list
Launch the Application TRK program
Halt the Bluetooth device search by pressing the Cancel soft key
Click Options > Settings > Connection
Change Connection type to USB and set connection options

+

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

Select Back and start the TRK again and you should be connected

Related concepts

On-device Debugging

Related references

Debug Window (On-device Debugging) Overview

Related tasks

Installing On-device Debug Agents using Bluetooth

On-device Debugging Troubleshooting

If you are having problems with on-device debugging, see if the following solutions can solve the problem.

Deploying SIS Files using Carbide (Application TRK)

Am unable to create my SIS file, what can cause this ?

-
Ensure that you are using symbols in your PKG file to generate the SIS file. See Working with PKG and SIS Files for more details.
-

How do I know my SIS file got installed correctly?

-
If you did not receive an error message that Carbide.c++ could not install the SIS file, then go to the Application Manager on the phone and look for the SIS file. If the SIS file is there it tells you that Carbide.c++ successfully deployed the application to the device.
-
Next, check the target directory on the device for the executable. If the executable is present, attempt to launch the executable. If the executable launches this lets you know the binaries were built correctly for the device. If the executable does not launch, try to build the application again using the command-line version of the tool.
-
To verify the install process, go to the Installation tab of your launch configuration and disable the Do not show installer UI on the phone option. The next time Carbide.c++ attempts to deploy the application, prompts will appear on the phone verifying that it is okay to install the application. You can then watch the SIS file being installed on the phone.
-

How do I force the install of a SIS file to a device?

-
In Carbide.c++, go to the Installation tab of your launch configuration and enable the Install each launch even if installer file has not changed option. Once set, just click the Debug control again to deploy the new application binaries to the device.
-

Am getting the an error when attempting to install my SIS file, what can I do?

-
To get better error messages about possible install failures, go to the Installation tab of your launch configuration and disable the Do not show installer UI on the phone option. The next time Carbide.c++ attempts to deploy the application, prompts will appear on the phone verifying that it is okay to install the application. You can then watch the SIS file being installed on the phone. When the SIS file fails to install again, TRK will provide more specific errors on why the installation failed.
-

Am getting the error "process fails to launch", what can I do to correct this?

-
There are several things that can cause this error including:
-

Verify deployment of the SIS file, see How do I know my SIS file got installed correctly? above.
Verify that the MMP or PKG files does not contain any errors.
If the application uses a self-signed SIS, a UID3 is required that is set within the proper address range. See https://www.symbiansigned.com/app/page/uidfaq for more info.
Verify that the UID3 address matches between the MMP and PKG file if using Application TRK. If using Sys TRK, verify the File Transfer tab on the System TRK launch configuration is correct.
Verify that your binaries are built correctly by attempting to launch the executable on the phone from the target directory. If this fails, rebuild the application using the command-line tools, then see How do I force the install of a SIS file to a device? above to redeploys and debug again.
If debugging a DLL from an application and using System TRK, ensure that the DLL is included in the File Transfer tab of the launch configuration so that it is deployed to the device with the application. It is not added by default.

Am getting an exception when trying to debug with Application TRK

-
The main reason for this is that you have entered ROM code or another prohibited address space. You can confirm this by checking the Disassembler view. When in a prohibited memory address the view may be blank. To correct, click Step Over or Resume to move to the next breakpoint in your code.
-

I'm running out of memory on the device, what can I do?

-
On platforms that include Platform Security there are several directories like c:\sys\bin where you cannot easily delete files that are no longer required. Over time the device's memory becomes full, making it difficult or impossible to install and debug additional programs.
-
If using Application TRK to install and debug programs, use the Application Manager on the device to remove all the files specified in the program's PKG file, but not the SIS file itself.
-
If you are using System TRK to install and debug programs and additional files, you will need to create a SIS that includes the files listed in the File Transfer pane, deploy it manually to the device, then run the Application Manager on the device to remove the files.
-

Connectivity

How can I use USB instead of Bluetooth to debug my application?

-
For USB support in TRK 2.5 or greater, while the TRK application is running on the phone, choose Options > Settings, then set Connection to USB.
-
For USB support in TRK v2.1, include the metrotrk_usb.ini file instead of the metrotrk_bt.ini file in your ROM image. You do this by modifying the metrotrk.iby file like this:
-
Replace the line:
-
data=ZSYSTEM\..\metrotrk\metrotrk_bt.ini \metrotrk.ini
-
With:
-
data=ZSYSTEM\..\metrotrk\metrotrk_usb.ini \metrotrk.ini
-
Then rebuild the ROM image.
-
NOTE With the S60 wk46 release onwards, the port number needs to be set to 1 instead of 0.
-
Installing Latest USB Drivers
-
On the host PC, you need to update the USB drivers to work with the latest S60 - devices. The latest drivers create a virtual com port on the host which you can - specify in Carbide. Download and install the latest Nokia Connectivity Cable - Drivers from PC Suite Vivaldi web site.
-
When you first connect the USB cable to the phone you'll get a prompt to choose - the "PC Suite" or "File Transfer" mode. Choose "PC Suite" mode to use TRK with - USB. Also you will get several “New Hardware found” wizards. You need to go - through the installation each time to successfully use the USB connection to - access the device.
-
Connecting to Device using USB
-
If the current Connection setting on the phone is Bluetooth, when you start - the TRK application on the phone you should see a list of Bluetooth devices. - Press Cancel. In the TRK Welcome Screen press Options, then - the Settings control. You should see the connection set to Bluetooth. Select - the Options > Change option and change the - connection option to USB. Your connection should now show as USB. Press - Back to go to the TRK Welcome screen. In the TRK Welcome screen press Select > - Connect. The status in the TRK welcome screen should show as connected.
-
The next time you connect the USB cable to the phone you’ll get a prompt to - choose the "PC Suite" or "File Transfer" mode. Choose "PC Suite" mode to use - TRK with USB. Then start the TRK application.
-

What is the virtual COM port number for my S60 phone on the host PC if I am using USB?

-
Normally, you can determine the COM port ID using the Device Manager if TRK is already connected via USB. -
-
To check, choose Start > Settings > Control panel > System > Hardware > Device Manager. In the Device Manager, choose "Ports" to view the active ports (Figure 1).
-
-
Figure 1. Ports displayed in Ports section of Device Manager.
-
In some situations all USB virtual COM ports are installed under "Modems" in the Device Manager. In the Device Manager dialog, choose "Modems" and see if there are two COM ports listed. One of them will work for debugging. Most of the time, the higher port number works for debugging with TRK.
-

I am having difficulty getting a Bluetooth connection to work with AppTRK, any suggestions?

-
The following are known issues when trying to use Bluetooth serial port on the host:
-

XP Microsoft Bluetooth stack does not work correctly with bt serial port emulation (on the PC side). For using TRK, you need BT serial port emulation. Some of the BT dongle manufacturers recommend changing to their own drivers to enable Bt stack serial port emulation. -
- Resolution at the moment: Change the XP drivers to bt dongle manufacturers (IBM, TDK, MSI) own drivers by uninstalling the XP drivers and installing the dongle drivers. After the installation the Microsoft Bluetooth Enumerator and Microsoft Bluetooth Services must be shut down.
- From Computer Management -> Device Manager uninstall the Microsoft BT Enumerator
- From Computer Management -> Services and Applications -> Services shutdown the Microsoft Bluetooth Services
- On the desktops, the Belkin Bluetooth dongle is known to properly provide BT Serial port emulation. Other Bluetooth dongles should work as long as the serial port service is provided by the Bluetooth driver
-

TRK is launched on the device, but I am getting “Can’t connect to TRK” error message in the Carbide.c++ tools, any suggestions?

-
Check that Carbide.c++ and your USB Virtual COM port or BT Serial Port agree on the port settings.
-

Use the On-Device Setup dialog to quickly determine if you can communicate with the device in the Check TRK version pane
Open your Bluetooth or USB cable's connection settings: Start -> Settings -> Control panel -> System -> Hardware -> Device Manager. In the Device Manager dialog, click open the Ports directory, then you will see all the com ports available on the machine. Here you will be able to see the COM port for Bluetooth or USB. Sometimes you will have two COM ports for Bluetooth, so you might have to try specifying either of them.
In the Carbide tools, open the launch configuration associated with the target device and verify that you have specified the correct launch configuration for TRK. For example, the launch configuration should be either Symbian OS Application TRK or Symbian OS System TRK configuration.
In the Carbide tools, open the launch configuration associated with the target device. In the Connections tab make sure you specify the same COM port number as in the device manager. For Bluetooth, if two ports are listed in the device manager, then you need to try to both, to see which one works. For USB, don't select the COM port assigned to the serial port. Always select the COM port assigned to the virtual COM port ID for the phone that is specified in the Device Manager.
Make sure the settings in these two dialogs are the same and that the launch configuration settings refer to the right COM port. You shouldn't have to touch the other settings, but they're Data Bits: 8; Parity: None; Stop Bits: 1; Flow Control: None.

On-device Debugging Troubleshooting

If you are having problems with on-device debugging, see if the following solutions can solve the problem.

Deploying SIS Files using Carbide (Application TRK)

Am unable to create my SIS file, what can cause this ?

+
Ensure that you are using symbols in your PKG file to generate the SIS file. See Working with PKG and SIS Files for more details.
+

How do I know my SIS file got installed correctly?

+
If you did not receive an error message that Carbide.c++ could not install the SIS file, then go to the Application Manager on the phone and look for the SIS file. If the SIS file is there it tells you that Carbide.c++ successfully deployed the application to the device.
+
Next, check the target directory on the device for the executable. If the executable is present, attempt to launch the executable. If the executable launches this lets you know the binaries were built correctly for the device. If the executable does not launch, try to build the application again using the command-line version of the tool.
+
To verify the install process, go to the Installation tab of your launch configuration and disable the Do not show installer UI on the phone option. The next time Carbide.c++ attempts to deploy the application, prompts will appear on the phone verifying that it is okay to install the application. You can then watch the SIS file being installed on the phone.
+

How do I force the install of a SIS file to a device?

+
In Carbide.c++, go to the Installation tab of your launch configuration and enable the Install each launch even if installer file has not changed option. Once set, just click the Debug control again to deploy the new application binaries to the device.
+

Am getting the an error when attempting to install my SIS file, what can I do?

+
To get better error messages about possible install failures, go to the Installation tab of your launch configuration and disable the Do not show installer UI on the phone option. The next time Carbide.c++ attempts to deploy the application, prompts will appear on the phone verifying that it is okay to install the application. You can then watch the SIS file being installed on the phone. When the SIS file fails to install again, TRK will provide more specific errors on why the installation failed.
+

Am getting the error "process fails to launch", what can I do to correct this?

+
There are several things that can cause this error including:
+

Verify deployment of the SIS file, see How do I know my SIS file got installed correctly? above.
Verify that the MMP or PKG files does not contain any errors.
If the application uses a self-signed SIS, a UID3 is required that is set within the proper address range. See https://www.symbiansigned.com/app/page/uidfaq for more info.
Verify that the UID3 address matches between the MMP and PKG file if using Application TRK. If using Sys TRK, verify the File Transfer tab on the System TRK launch configuration is correct.
Verify that your binaries are built correctly by attempting to launch the executable on the phone from the target directory. If this fails, rebuild the application using the command-line tools, then see How do I force the install of a SIS file to a device? above to redeploys and debug again.
If debugging a DLL from an application and using System TRK, ensure that the DLL is included in the File Transfer tab of the launch configuration so that it is deployed to the device with the application. It is not added by default.

Am getting an exception when trying to debug with Application TRK

+
The main reason for this is that you have entered ROM code or another prohibited address space. You can confirm this by checking the Disassembler view. When in a prohibited memory address the view may be blank. To correct, click Step Over or Resume to move to the next breakpoint in your code.
+

I'm running out of memory on the device, what can I do?

+
On platforms that include Platform Security there are several directories like c:\sys\bin where you cannot easily delete files that are no longer required. Over time the device's memory becomes full, making it difficult or impossible to install and debug additional programs.
+
If using Application TRK to install and debug programs, use the Application Manager on the device to remove all the files specified in the program's PKG file, but not the SIS file itself.
+
If you are using System TRK to install and debug programs and additional files, you will need to create a SIS that includes the files listed in the File Transfer pane, deploy it manually to the device, then run the Application Manager on the device to remove the files.
+

Connectivity

How can I use USB instead of Bluetooth to debug my application?

+
For USB support in TRK 2.5 or greater, while the TRK application is running on the phone, choose Options > Settings, then set Connection to USB.
+
For USB support in TRK v2.1, include the metrotrk_usb.ini file instead of the metrotrk_bt.ini file in your ROM image. You do this by modifying the metrotrk.iby file like this:
+
Replace the line:
+
data=ZSYSTEM\..\metrotrk\metrotrk_bt.ini \metrotrk.ini
+
With:
+
data=ZSYSTEM\..\metrotrk\metrotrk_usb.ini \metrotrk.ini
+
Then rebuild the ROM image.
+
NOTE With the S60 wk46 release onwards, the port number needs to be set to 1 instead of 0.
+
Installing Latest USB Drivers
+
On the host PC, you need to update the USB drivers to work with the latest S60 + devices. The latest drivers create a virtual com port on the host which you can + specify in Carbide. Download and install the latest Nokia Connectivity Cable + Drivers from PC Suite Vivaldi web site.
+
When you first connect the USB cable to the phone you'll get a prompt to choose + the "PC Suite" or "File Transfer" mode. Choose "PC Suite" mode to use TRK with + USB. Also you will get several “New Hardware found” wizards. You need to go + through the installation each time to successfully use the USB connection to + access the device.
+
Connecting to Device using USB
+
If the current Connection setting on the phone is Bluetooth, when you start + the TRK application on the phone you should see a list of Bluetooth devices. + Press Cancel. In the TRK Welcome Screen press Options, then + the Settings control. You should see the connection set to Bluetooth. Select + the Options > Change option and change the + connection option to USB. Your connection should now show as USB. Press + Back to go to the TRK Welcome screen. In the TRK Welcome screen press Select > + Connect. The status in the TRK welcome screen should show as connected.
+
The next time you connect the USB cable to the phone you’ll get a prompt to + choose the "PC Suite" or "File Transfer" mode. Choose "PC Suite" mode to use + TRK with USB. Then start the TRK application.
+

What is the virtual COM port number for my S60 phone on the host PC if I am using USB?

+
Normally, you can determine the COM port ID using the Device Manager if TRK is already connected via USB. +
+
To check, choose Start > Settings > Control panel > System > Hardware > Device Manager. In the Device Manager, choose "Ports" to view the active ports (Figure 1).
+
+
Figure 1. Ports displayed in Ports section of Device Manager.
+
In some situations all USB virtual COM ports are installed under "Modems" in the Device Manager. In the Device Manager dialog, choose "Modems" and see if there are two COM ports listed. One of them will work for debugging. Most of the time, the higher port number works for debugging with TRK.
+

I am having difficulty getting a Bluetooth connection to work with AppTRK, any suggestions?

+
The following are known issues when trying to use Bluetooth serial port on the host:
+

XP Microsoft Bluetooth stack does not work correctly with bt serial port emulation (on the PC side). For using TRK, you need BT serial port emulation. Some of the BT dongle manufacturers recommend changing to their own drivers to enable Bt stack serial port emulation. +
- Resolution at the moment: Change the XP drivers to bt dongle manufacturers (IBM, TDK, MSI) own drivers by uninstalling the XP drivers and installing the dongle drivers. After the installation the Microsoft Bluetooth Enumerator and Microsoft Bluetooth Services must be shut down.
- From Computer Management -> Device Manager uninstall the Microsoft BT Enumerator
- From Computer Management -> Services and Applications -> Services shutdown the Microsoft Bluetooth Services
- On the desktops, the Belkin Bluetooth dongle is known to properly provide BT Serial port emulation. Other Bluetooth dongles should work as long as the serial port service is provided by the Bluetooth driver
+

TRK is launched on the device, but I am getting “Can’t connect to TRK” error message in the Carbide.c++ tools, any suggestions?

+
Check that Carbide.c++ and your USB Virtual COM port or BT Serial Port agree on the port settings.
+

Use the On-Device Setup dialog to quickly determine if you can communicate with the device in the Check TRK version pane
Open your Bluetooth or USB cable's connection settings: Start -> Settings -> Control panel -> System -> Hardware -> Device Manager. In the Device Manager dialog, click open the Ports directory, then you will see all the com ports available on the machine. Here you will be able to see the COM port for Bluetooth or USB. Sometimes you will have two COM ports for Bluetooth, so you might have to try specifying either of them.
In the Carbide tools, open the launch configuration associated with the target device and verify that you have specified the correct launch configuration for TRK. For example, the launch configuration should be either Symbian OS Application TRK or Symbian OS System TRK configuration.
In the Carbide tools, open the launch configuration associated with the target device. In the Connections tab make sure you specify the same COM port number as in the device manager. For Bluetooth, if two ports are listed in the device manager, then you need to try to both, to see which one works. For USB, don't select the COM port assigned to the serial port. Always select the COM port assigned to the virtual COM port ID for the phone that is specified in the Device Manager.
Make sure the settings in these two dialogs are the same and that the launch configuration settings refer to the right COM port. You shouldn't have to touch the other settings, but they're Data Bits: 8; Parity: None; Stop Bits: 1; Flow Control: None.