Symbian OS Phone Launch

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

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:

Creating a Launch Configuration for a Reference Board

Select the Run > Debug menu item, or click the Debug () icon, or press F11
-
SHORTCUT Select the Run > Debug As > Debug Symbian OS Application on Reference Board menu item to skip Step 2.
-
Select the Symbian OS Reference Board Launch item, then click OK
Select the Symbian OS Device item, then click OK
Select a Launch Type, then click Next
Complete each page in the New Launch Configuration Wizard for the chosen Launch Type.
Review the settings in the New Launch Configuration page

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 CODA — used to run or debug applications on a target device using the Application CODA on-device debug agent. Application CODA 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 CODA and stop mode debugging. This launch configuration is not available for emulator debugging. Stop mode and CODA 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 System CODA — used to run or debug applications or ROM code on a target device using the System CODA on-device debug agent. System CODA 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 Device — used to run or debug applications or ROM code on a target device using CODA (Carbide On-device Debug Agent). CODA is an application that runs on reference boards and prototype phones and allows you to debug executables. The debugger will download files to the phone prior to launching.
Symbian OS Device (Attach to Process) — used to debug processes running on a target device for which a symbol file is available. This is available only for CODA and stop mode debugging. This launch configuration is not available for emulator debugging. Stop mode and CODA can both attach to a process from the Symbian OS Data view.
Symbian OS Device (Install SIS) — used to run or debug applications on a target device using CODA. CODA 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 Emulator — used to run or debug executables on an emulator.
Symbian OS Simulator — used to run or debug executables on a simulator.

Other references

Launch Configuration Filtering

Use the Launch Configurations preference panel to filter the launch configurations that appear in the configurations list in the Run or Debug dialog. This allows you to manage which configuration types are shown. For example, enable the Filter checked launch configuration types option and check the configuration types that you do not want to appear in the Run and Debug dialogs.

Figure 1 - Launch Configurations preference panel

Related references

Symbian OS Phone Launch — uses the Eclipse Debugger for C/C++ as the debugger engine which includes snapshots, improved variables view, and other features not available in the Classic debugger.
Classic Symbian OS Reference Board Launch — uses the classic debugger engine.

Figure 1. Debug As dialog

Creating a Launch Configuration for Emulators

Select the Run > Debug menu item, or click the Debug () icon, or press F11
-
SHORTCUT Select the Run > Debug As > Debug Symbian OS Application on Emulator menu item to skip Step 2.
Select the Symbian OS Emulator Launch item, then click OK
Select the Symbian OS Emulator item, then click OK
Complete each page in the New Launch Configuration Wizard , then click Next
Review the settings in the New Launch Configuration page
Click Debug to download and debug the project on the emulator

Symbian OS Phone Launch

Symbian OS Device Launch

Symbian OS Phone Launch

Symbian OS Device Launch

Use the Debug As dialog to select the New Launch Configuration Wizard that will create a launch configuration for the project. Currently there are two choices of debugger:

Symbian OS Phone Launch — uses the Eclipse Debugger for C/C++ as the debugger engine which includes snapshots, improved variables view, and other features not available in the Classic debugger.
Device — uses the Eclipse Debugger for C/C++ as the debugger engine which includes snapshots, improved variables view, and other features not available in the Classic debugger.
Classic Symbian OS Reference Board Launch — uses the classic debugger engine.

Figure 1. Debug As dialog

Creating a Launch Configuration for a Phone

Select the Run > Debug menu item, or click the Debug () icon, or press F11
-
SHORTCUT Select the Run > Debug As > Debug Symbian OS Application on Phone menu item to skip Step 2.
Select the Symbian OS Phone Launch item, then click OK
Select the Device item, then click OK
(Optional) Modify the launch configuration settings
1. Modify the Remote connection setting options
-
+

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.
+
The Launch Configurations preference panel filters the list of launch configuration types that appear in the Run or Debug window as options. 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. 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
1. Select Window > Preferences...
2. Expand the Run/Debug group
3. Expand Launching and select Launch Configurations
4. Click Run/Debug > Launching > Launch Configurations to open the preference panel
-
-
Figure 2 - Launch Configurations Filter
Related concepts
- Adding/Removing Build Configurations
- Setting a Build Configuration
-

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 218e49ed806f -r 617a89f9dffc 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 Tue Sep 21 10:33:50 2010 -0700 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_trk_overview.htm Tue Sep 21 15:50:51 2010 -0500 @@ -16,7 +16,7 @@
File Transfer Pane
Executables Pane
Installation Pane
ROM Log (System CODA only)
ROM Log (Symbian OS Device 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

Item	Explanation	Item	Explanation
Serial Port

Install Remote Agents

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 Install remote agents page

Table 1. Install Remote Agents pane

Setup Connection

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

Figure 1 - New Connection wizard Setup Connection tab

Table 1. Setup Connection page - options

Bluetooth - serial port connection through Bluetooth
Serial - serial port connection through a COM serial port
USB - serial port connection through USB that supports TRK 3.x
USB - serial port connection through USB that supports CODA 4.x

And the supported services may include:

Bluetooth - serial port connection through Bluetooth
Serial - serial port connection through a COM serial port
USB - serial port connection through USB that supports TRK 3.x
USB - serial port connection through USB that supports CODA 4.x

Test Connection

Use the Set Connection Settings pane to compare the version of remote service installed on the device with the latest version available for Carbide. A remote service is any software on the device that can communicate with Carbide. This includes CODA, Trace, Performance Investigator, and other services. In this pane you can:

Use the Set Connection Settings pane to compare the version of remote service installed on the device with the latest version available for Carbide. A remote service is any software on the device that can communicate with Carbide. This includes CODA (Carbide On-device Debug Agent), Trace, Performance Investigator, and other services. In this pane you can:

Set the device OS used by the device and supported by the remote service
Verify that Carbide can communicate with the remote service via the chosen connection setting
Verify that you have the latest version of the remote service installed on the device

Options presented may differ based on the type of connection setting chosen.

Figure 1 - Test Connection pane in the New Connection dialog

Table 1 Test Connection pane — items

Test Connection - verify connection operates as intended
Install Remote Agents - download and install remote agents

Figure 1 - New Connection dialog

Related references

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 CODA or in stop mode, always specify the ROM Log file in the project's launch configuration.

NOTE To debug ROM DLLs with Symbian OS Device 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.

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

For the stop mode debugger and the crash debugger, all the data listed above is supported. For the Application and Symbian OS Device 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 CODA 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 CODA 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.

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

Run Mode Projects

The topics include:

Install the SISX File on the Target Device

The on-device debug agent is delivered to the target device as a SISX file. There are two versions of CODA: Application CODA and System CODA.

The on-device debug agent is delivered to the target device as a SISX file. There are two versions of CODA: Symbian OS Device (Install SIS) and Symbian OS Device.

Application CODA— supports application debugging only and available to developers creating applications for devices. Developers do not have access to system level routines, system ROM, and other user application code. User cannot modify the LR and SR registers, and must use a SIS file to debug an application.
System CODA— supports both application and limited ROM debugging; including application executables and limited ROM based components (no device drivers). Also available to original equipment manufacturers (OEMs) for device creation and customization.
Symbian OS Device (Install SIS)— supports application debugging only and available to developers creating applications for devices. Developers do not have access to system level routines, system ROM, and other user application code. User cannot modify the LR and SR registers, and must use a SIS file to debug an application.
Symbian OS Device— supports both application and limited ROM debugging; including application executables and limited ROM based components (no device drivers). Also available to original equipment manufacturers (OEMs) for device creation and customization.

The following SISX file is officially signed by Nokia: s60_3_0_app_trk_2_6_nokia_signed.sisx

diff -r 218e49ed806f -r 617a89f9dffc 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 Tue Sep 21 10:33:50 2010 -0700 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Tue Sep 21 15:50:51 2010 -0500 @@ -29,9 +29,9 @@

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

Select either a Symbian OS Application CODA or Symbian OS System CODA configuration type for on-device debugging and click New

Select either a Symbian OS Device (Install SIS) or Symbian OS Device configuration type for on-device debugging and click New

For debug launch configurations using the CODA debug agent, the following pages require review and possible option settings:

Main - defines the project to be launched on the target device

Explanation
Device OS	A dropdown list of device OSes that are supported by the CODA debug agent software. Select the OS used by the device before running a check.	Device OS (used to determine installer version)	A dropdown list of device OSes that are supported by CODA. Select the OS used by the device before running a check.
Select a service to test

Installation Tab

For Application CODA select the Installation tab. The Installation pane specifies the .sis file to install on the target device. This is used by Application CODA because Application CODA downloads all files via a SIS file. This is required when using the CODA debug agent with 9.x based SDK’s.

For CODA select the Installation tab. The Installation pane specifies the .sis file to install on the target device. This is because CODA downloads all files via a SIS file. This is required when using CODA with 9.x based SDK’s.

Figure 8. Debug windows Installation pane

Table 4. Installation pane

File Transfer Tab

For System CODA select the File Transfer pane. The File Transfer pane displays a list of files the Carbide IDE transfers to the target device at the start of each launch. By default, any file added is automatically checked for downloading to the device.

NOTE If debugging a DLL from an application and using System CODA, ensure that the DLL is included so that it is deployed to the device with the application. It is not added by default.

For CODA select the File Transfer pane. The File Transfer pane displays a list of files the Carbide IDE transfers to the target device at the start of each launch. By default, any file added is automatically checked for downloading to the device.

NOTE If debugging a DLL from an application and using CODA, ensure that the DLL is included so that it is deployed to the device with the application. It is not added by default.

Figure 9. Debug windows File Transfer pane

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

This example shows how to create and build an application and debug it on a device using stop-mode.

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.

With stop mode debugging you can use the Carbide.c++ IDE 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:

Debugging a Run-mode Project using Application CODA

Debugging a Run-mode Project using Symbian OS Device (Install SIS)

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). For the import, we select an ARM target.

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 CODA Launch Configuration from the Launch Types page, then click Next
2. Select the Symbian OS Device (Install SIS) Launch Configuration from the Launch Types page, then click Next
3. If you have more than one executable, select the Main Executable in the Executable Selection page of the wizard, then click Next

Debugging the Game project

General registers

Other references

Related tasks

Other Useful Commands

Disconnecting from a process

Applications Launch Configuration

Other references

Attach to Process Launch Configuration

Emulator Launch Configuration

Creating a Launch Configuration for a Reference Board

Available Launch Configurations

Other references

Launch Configuration Filtering

Related references

Creating a Launch Configuration for Emulators

Symbian OS Phone Launch

Symbian OS Device Launch

Creating a Launch Configuration for a Phone

Launch Types

Other references

Table 1. Connection page —items

Debugger panes

Emulation Debugger page

Table 1. Debugger page — emulation options

Run-mode Debugger page

Table 2. Debugger page — run-mode options

Stop-mode Debugger page

Table 3. Debugger page — stop-mode options

Other references

Executables page

Table 1. Executable page —items

File Transfer page

Table 1. File Transfer page —items

Installation page

Table 1. Installation page —items

Main page

Emulation Main page

Run-mode Main page

Table 2. Run-mode Main page —items

Stop-mode Main page

Table 3. Stop-mode Main page — items

ROM Image page

Table 4. Launch configuration window—ROM Image tab items

ROM Log page

Table 1. ROM Log page—items

x86 Exceptions page

Table 1. x86 Exceptions page —items

Application CODA Launch Configuration (Run-mode)

Symbian OS Device (Install SIS) Launch Configuration (Run-mode)

System CODA Launch Configuration (Stop-mode)

Symbian OS Device Launch Configuration (Stop-mode)

New Launch Configuration Wizard

Launch Types

Build Options Selection

Executable Selection

CODA Connection Settings

Table 1. Debug Configuration window — common items

Remote Target Debugging (Run-mode) Tutorial

Connect target device to PC

Other references

Install CODA remote agent

Installing or updating the TRK remote agent

Installing or updating CODA

Configure project for debugging

Debug project on target device

Partial Upgrade Files

Set PKG File for Build Configuration

Table 1 Items

Related reference

Launch Configuration Filters

To access the Launch Configurations Filter Window

To open the Launch Configurations Filter from Preferences

Related concepts

Install Remote Agents

Setup Connection

Test Connection

Table 1 Test Connection pane — items

Related references

Run Mode Projects