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.
Open Window > Preferences > Run/Debug > Launching preference panel and disable the Build (if required) before launching option under the General Options group
Right-click the project and choose Debug As > Debug Configuration to open the Debug Cinfigurations window
-
Create an Symbian OS Application TRK launch configuration
+
Create an Symbian OS Application CODA 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
+
In the Debug tab, enable the View messages between PC and debug agent on the phone if you want to monitor communications between CODA and Carbide
Registers are the register contents of the central processing unit (CPU) of the host computer or the targeted device. When debugging projects using the emulator, only the host computer x86 registers are visible in the Registers view. When debugging projects on a device, only the target device registers are visible.
-
In most cases, the contents of all the registers can be modified. However, when debugging applications on a target device with Application TRK, you cannot change the LR and SP registers.
+
In most cases, the contents of all the registers can be modified. However, when debugging applications on a target device with Application CODA, you cannot change the LR and SP registers.
Figure 1. Registers view with possible register types
The types of registers can include:
@@ -36,7 +36,7 @@
R14 is the link register (it is used for storing return addresses in the construction of sub routines)
R15 is the program counter (PC)
-
In most cases, the contents of all the registers can be modified. However, when debugging applications on a target device with Application TRK, you cannot change the LR, SP, and CPSR registers.
+
In most cases, the contents of all the registers can be modified. However, when debugging applications on a target device with Application CODA, you cannot change the LR, SP, and CPSR registers.
TCF (Target Communication Framework) is a vendor-neutral, lightweight, extensible network protocol used mainly for communicating with embedded systems (targets). Its most distinguishing feature is that TCF is designed to transparently plug in value-adding servers between the tool and the target. TCF is protocol agnostic in that it does not depend on a specific transport like TCP/IP, serial, SSH tunnel, or other. It also supports auto-discovery of targets and services, so any tool can determine which services are available from the target.
-
Carbide.c++ uses TCF to communicate with TRK, Trace, and other services on a target device. For example, the Carbide debugger uses TCF to communicate with the TRK remote agent to control debuggable programs running on the target. Other Carbide plug-ins can also use TCF to communicate with their specific services.
+
Carbide.c++ uses TCF to communicate with CODA, Trace, and other services on a target device. For example, the Carbide debugger uses TCF to communicate with the CODA remote agent to control debuggable programs running on the target. Other Carbide plug-ins can also use TCF to communicate with their specific services.
The on-device TRK remote agent (Application TRK or System TRK) is a program that enables on-device debugging of phone prototypes, reference boards, and retail phones. An on-device debug agent is a program that is installed on a phone or reference board. It communicates with the debugger using a serial-over-Bluetooth or serial-over-USB connection. Through this serial communication, the on-device debug agent acts as the interface between the Carbide.c++ debugger and the target device. An on-device debug agent provides:
+
Carbide On-device Debug Agent
+
The Carbide On-device Debug Agent (CODA) is a program that enables on-device debugging of phone prototypes, reference boards, and retail phones. An on-device debug agent is a program that is installed on a phone or reference board. It communicates with the debugger using a serial-over-Bluetooth or serial-over-USB connection. Through this serial communication, the on-device debug agent acts as the interface between the Carbide.c++ debugger and the target device. The CODA provides:
Debug agent running on Symbian OS
Provides a stable & integrated interface to Symbian OS
@@ -17,7 +17,7 @@
Can be built-in to the OS image or installed as a .sis file
Using the on-device remote agent, one can use the Carbide.c++ IDE to debug programs running on phone hardware, making the debugging process much easier. The on-device debug agent works on all Nokia Qt SDK, Symbian^3, and Symbian TechView devkits.
Some of the key benefits to using an on-device debug agent include:
Easy debugging via serial interface (Bluetooth, USB, IrDA, etc)
@@ -26,8 +26,8 @@
There are two variations of the on-device debug agent, they are:
-
Application TRK—supports application debugging only and available to developers creating applications for devices. Developers do not have access to system level routines, system ROM, other user application code, cannot modify the LR and SR registers, and must use a SIS file to debug an application.
-
System TRK—
+
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, other user application code, 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 (includes application executables and limited ROM based components (i.e. no device drivers) and available to original equipment manufacturers (OEM) for device creation and customization
The Debug view has a few other commands that are useful under some debugging situations:
Disconnecting from a process
-
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.
+
Use the Disconnect command () when debugging with Application CODA or System CODA 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.
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.
+
Application CODA or System CODA - 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.
This is commonly caused when the binary parser is not set correctly in the project. To correct, open the project properties window (right-click project name in Project Explorer view and select Properties), expand the C/C++ Build section and click the Binary Parser tab in the C/C++ Build page. Now look for the PE Windows Parser option. If it's not checkmarked, checkmark it and click Apply. If it is already set then uncheck it and click Apply, then reapply a checkmark and click Apply. The debug icon should now appear.
Connectivity
-
Unable to connect to device using Bluetooth and debug it using TRK
+
Unable to connect to device using Bluetooth and debug it using CODA
When using Bluetooth to connect to a device there are several things that require correction, including:
-
If using built-in Bluetooth under WinXP SP2, ensure the manufacturer’s device drivers are installed and active. The default Microsoft drivers do not work correctly for debugging devices using TRK. For example, if using IBM Integrated Bluetooth on your computer, make sure you have the IBM drivers for the device.
+
If using built-in Bluetooth under WinXP SP2, ensure the manufacturer’s device drivers are installed and active. The default Microsoft drivers do not work correctly for debugging devices using CODA. For example, if using IBM Integrated Bluetooth on your computer, make sure you have the IBM drivers for the device.
Ensure the COM port used by Bluetooth is not commandeered by another process or device.
-
Ensure that you have the latest version of TRK on the target device.
+
Ensure that you have the latest version of CODA on the target device.
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.
+
Attaching to a process requires a both target device running the Symbian OS and the presence of CODA 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 CODA 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 > Debug As 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
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 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 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 System TRK — 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 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.
The Symbian OS Emulation launch configurations the Debugger page to specify entry point breaks and which logs to output to the Console view.
@@ -48,7 +48,7 @@
Run-mode Debugger page
-
In a run-mode launch configuration like Application TRK, you can specify an entry break point and how messages are handled as well as define the default instruction set.
+
In a run-mode launch configuration like Application CODA, you can specify an entry break point and how messages are handled as well as define the default instruction set.
Figure 2 - Debugger page showing run-mode options
Table 2. Debugger page — run-mode options
@@ -63,12 +63,12 @@
View program output
-
Enable to direct standard output messages to the TRK Program Output Console in the Console view.
+
Enable to direct standard output messages to the CODA Program Output Console in the Console view.
NOTE In the epoc.ini file the option LogToFile must also be set to 1.
Stop-mode Debugger page
-
In stop-mode launch configurations like System TRK,and Attach to Process, use the Startup Options to attach to a target and debug or run from the specified start address. Then use Target Options to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session.
+
In stop-mode launch configurations like System CODA,and Attach to Process, use the Startup Options to attach to a target and debug or run from the specified start address. Then use Target Options to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session.
The Executables page specifies the executables available to debug with your project based on the chosen rule. The Executables page gives you project level control over the executables associated with it. The page 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.
The File Transfer page displays an auto-populated list of files for System TRK that the IDE transfers to the target device at the start of each launch. For RnD device images, the target location for files is normally c:\sys\bin or another protected area. For production device images Application TRK does not support the transfer of files to c:\sys\bin or other protected areas.
-
Users can add, edit, or delete files in the list and sort by clicking on a column header. 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. 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.
+
The File Transfer page displays an auto-populated list of files for System CODA that the IDE transfers to the target device at the start of each launch. For RnD device images, the target location for files is normally c:\sys\bin or another protected area. For production device images Application CODA does not support the transfer of files to c:\sys\bin or other protected areas.
+
Users can add, edit, or delete files in the list and sort by clicking on a column header. 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. System CODA users can use this panel to download any type of file, like bitmaps, HTML, sounds, and more, to the phone and applicable to Application CODA for transfering any files outside of the installation file.
Figure 1. File Transfer page
Table 1. File Transfer page —items
@@ -28,10 +28,10 @@
Target directory—the path to the target directory where transfered files are placed on the device.
-
The target directories where files can be installed depends upon the type of device image you have on the device and which version of TRK you are using.
+
The target directories where files can be installed depends upon the type of device image you have on the device and which version of CODA you are using.
-
Application TRK - public folders only on production device images
-
System TRK - public and protected folders, like c:\sys\bin, on RnD device images
+
Application CODA - public folders only on production device images
+
System CODA - public and protected folders, like c:\sys\bin, on RnD device images
The Installation page 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.
+
The Installation page specifies the .sis file to install on the target device when using Application CODA. This is required when using the CODA debug agent with 9.x based SDK’s.
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 > Debug As 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.
+
Application CODA Launch Configuration (Run-mode)
+
Select the Symbian OS Application CODA launch configuration to debug or run 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.
+
If the New Launch Configuration Wizard was used to create the Application CODA 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 Application CODA 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:
+
Figure 1. Application CODA launch configuration in the Debug dialog
+
The Application CODA 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.
Select the Symbian OS System TRK launch configuration provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS 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 > Debug As 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.
+
System CODA Launch Configuration (Stop-mode)
+
Select the Symbian OS System CODA launch configuration provides C/C++ stop-mode debug options that use a JTAG interface when a Symbian OS 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 CODA 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 System CODA 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:
+
Figure 1. System CODA launch configuration in the Debug dialog
+
The System CODA 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 New Launch Configuration Wizard launches when no launch configuration exists for a build configuration in 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.
+
The New Launch Configuration Wizard launches when no launch configuration exists for a build configuration in 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 CODA requires different information than one targeted for System CODA.
Every project consists of one or more build configurations as listed under the Build project icon () of the toolbar or in the Add/Remove Carbide Build Configuration dialog. Every build configuration needs a launch configuration to enable debugging. Launch configurations can be shared between build configurations. The New Launch Configuration Wizard detects when a build configuration doesn't have an associated launch configuration and guides you through the setup process.
Figure 1. Build configurations for the chosen project appear under the Build icon
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.
+
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 CODA) to the least likely type (Attach to Process). Select a type and click Next.
Figure 2 - Launch Type page
Build Options Selection
@@ -80,15 +80,15 @@
Select the Executable to launch, verify it is the correct binary, then click Next.
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.
+
CODA Connection Settings
+
Use the CODA 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 5 - TRK Connection Settings page
+
Figure 5 - CODA 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.
+
CODA SIS Selection
+
Use the CODA 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 6 - TRK SIS Selection page
+
Figure 6 - CODA 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.
In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
+
In this example we demonstrate how to debug applications on a remote device using the Application CODA remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
+
In this example we demonstrate how to debug applications on a remote device using the Application CODA remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
Connect target device to PC
-
Install TRK remote agent (v3.2.7) or later on the target device
+
Install CODA remote agent (v3.2.7) or later on the target device
Connect the USB cable between the remote device and PC running Carbide.
Use the Remote Connections view to verify a successful connection or by looking at the remote connection trim display shown at the bottom of the workplace window.
-
The Status column indicates whether the service you need for debugging, TRK, is Available. If it's status is Not Accessible you are probably missing the TRK remote agent on the remote device.
+
The Status column indicates whether the service you need for debugging, CODA, is Available. If it's status is Not Accessible you are probably missing the CODA remote agent on the remote device.
Click OK on the remote device when it asks to use PC Suite mode with USB.
NOTE Debugging requires the use of PC Suite mode. If you are in another mode, like Mass storage mode, an alert appears asking you to change.
In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
+
Install CODA remote agent
+
In this example we demonstrate how to debug applications on a remote device using the Application CODA remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
To debug on a remote device you need a program to communicate between the Carbide debugger and your executable running on the device. That program is the TRK (Terminal Resident Kernel) remote agent, also known as Application TRK.
+
To debug on a remote device you need a program to communicate between the Carbide debugger and your executable running on the device. That program is the CODA (Carbide On-device Debug Agent) remote agent, also known as Application CODA.
In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
+
In this example we demonstrate how to debug applications on a remote device using the Application CODA remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
In this example we demonstrate how to debug applications on a remote device using the Application TRK remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
+
In this example we demonstrate how to debug applications on a remote device using the Application CODA remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:
You debug on a remote device using the exact same methods used for the emulator. Once the project is built and downloaded to the target device, the TRK remote agent then takes control. Then, using the Carbide debugger you can use all the debugger features to exercise the program on the device while monitoring its vitals in the Debug perspective.
+
You debug on a remote device using the exact same methods used for the emulator. Once the project is built and downloaded to the target device, the CODA remote agent then takes control. Then, using the Carbide debugger you can use all the debugger features to exercise the program on the device while monitoring its vitals in the Debug perspective.
The SIS Builder supports the generation of partial upgrade .SIS files. A dialog appears when a SIS file exceeds 250k in size that describes the partial upgrade feature with a link to the SIS Builder page. Partial upgrade files enable Carbide to generate and download to the device only those portions of the application that have changed, enabling faster debug cycles. It does this using the SIS partial upgrade (PU) flag to mark the SIS file as a replacement or addition to the original SIS file. Debugging of large applications using Application TRK is enhanced as the entire application no longer needs to be installed on the device each time a change is made.
+
The SIS Builder supports the generation of partial upgrade .SIS files. A dialog appears when a SIS file exceeds 250k in size that describes the partial upgrade feature with a link to the SIS Builder page. Partial upgrade files enable Carbide to generate and download to the device only those portions of the application that have changed, enabling faster debug cycles. It does this using the SIS partial upgrade (PU) flag to mark the SIS file as a replacement or addition to the original SIS file. Debugging of large applications using Application CODA is enhanced as the entire application no longer needs to be installed on the device each time a change is made.
When the Partial update option is checked for a SIS file, both a complete and partial SIS files are generated. This ensures that the full SIS file is kept in sync with the partial upgrade SIS file. The partial upgrade SIS files are placed in the same folder as the full SIS file when stored in a project directory, or in the root of the project directory when the SIS file exists outside of the project. You can see where a partial upgrade file is created by examining the Partial upgrade sis/sisx path in the Installation tab of the launch configuration. Links to the partial upgrade files are added to the project within the Project Explorer view.
NOTE Internally, the .PKG file format of a partial upgrade file is identical to a complete .PKG file with two exceptions, 1) the file list only includes the names of files changed, and 2) the PU flag is set.
Partial upgrade files are deleted and only full SIS/SISX files are generated when:
The Set PKG File for Build Configuration dialog appears when an Application TRK build configuration does not include a PKG file. Use it to assign a PKG file to the project's current build configuration that will be used to create a project's SIS installation file. If you define a launch configuration used for on-device debugging with the TRK debug agent, you will need to specify a PKG file for the project. A PKG file primarily provides a list of program and resource files to install on the device.
+
The Set PKG File for Build Configuration dialog appears when an Application CODA build configuration does not include a PKG file. Use it to assign a PKG file to the project's current build configuration that will be used to create a project's SIS installation file. If you define a launch configuration used for on-device debugging with the CODA debug agent, you will need to specify a PKG file for the project. A PKG file primarily provides a list of program and resource files to install on the device.
NOTE On Symbian OS 9.x builds, if the key/cert pair are not defined, makekeys will be called and temporary ones will be generated for you to "self-sign" the application. Self-signed applications should be in the
0xE0000000-0xEFFFFFFF range.
-
NOTE All Application TRK build configuration require a PKG file. If none is found in the active project then you will be asked to choose one.
+
NOTE All Application CODA build configuration require a PKG file. If none is found in the active project then you will be asked to choose one.
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 5.0 needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 3.2.6.
-
Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.
+
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 5.0 needs a version of the CODA software compiled for that SDK.
+
Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA 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.
+
Click Save to store a local copy of the currently selected CODA 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 remote agents list. A progress bar is shown if the install operation requires more than a few seconds to complete.
+
Click Install to download and install the CODA selected in the Install remote agents list. A progress bar is shown if the install operation requires more than a few seconds to complete.
NOTE Drivers installed by PC Suite or Ovi Suite are required in order for Install to download a remote agent onto the target device.
NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite or Ovi 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.
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.
+
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 CODA software compiled for that SDK.
+
Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA 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.
+
Click Save to store a local copy of the currently selected CODA 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.
+
Click Install to download and install the CODA selected in the Install latest CODA 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.
Click Initiate Service Testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check TRK version operation requires more than a few seconds.
+
Click Initiate Service Testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check CODA 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.
+
CODA not responding - this indicates that the COM port is open but CODA is not responding. First, verify that CODA is up and running on the device. Second, CODA may be listening on a different COM port, so choose another named COM port and try again.
@@ -89,16 +89,16 @@
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 5.x needs a version of the TRK software compiled for that SDK, which in the image above is Application TRK 3.2.6.
-
Additional information about the selected entry is displayed to the right to help you choose the correct version of TRK for the target device.
+
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 5.x needs a version of the CODA software compiled for that SDK.
+
Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA 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.
+
Click Save to store a local copy of the currently selected CODA 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.
+
Click Install to download and install the CODA selected in the Install latest CODA 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.
Click Initiate service testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check TRK version operation requires more than a few seconds.
+
Click Initiate service testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check CODA 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.
+
CODA not responding - this indicates that the COM port is open but CODA is not responding. First, verify that CODA is up and running on the device. Second, CODA may be listening on a different COM port, so choose another named COM port and try again.
@@ -97,16 +97,16 @@
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.
+
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 CODA software compiled for that SDK.
+
Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA 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.
+
Click Save to store a local copy of the currently selected CODA 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.
+
Click Install to download and install the CODA selected in the Install latest CODA 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.
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 TRK, 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, 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
@@ -27,7 +27,7 @@
Device OS
-
A dropdown list of device OSes that are supported by the TRK debug agent software. Select the OS used by the device before running a check.
+
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.
Use the New Connection wizard to verify and update Carbide software services on a device. Click the Help > On-Device Connections... menu option to open. Current services available include TRK, Tracing, and others. The following tabs are present:
+
Use the New Connection wizard to verify and update Carbide software services on a device. Click the Help > On-Device Connections... menu option to open. Current services available include CODA, Tracing, and others. The following tabs are present:
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.
+
Remember that program output is console output from the running binary and communications log is the messages sent between CODA and the on-device debug agent.
NOTE You can pin any message log view so that it does not lose focus.
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.
+
NOTE To debug ROM DLLs with System CODA 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.
NOTE Information for the Chunks and Libraries tabs is not available when debugging with the TRK debug agent.
+
NOTE Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.
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.
+
NOTE Chunks data is not available during CODA debugging.
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.
+
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.
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 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 Information for the Chunks and Libraries tabs is not available when debugging with the TRK debug agent.
+
NOTE Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.
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.
@@ -55,7 +55,7 @@
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 applies to both TRK (run mode) and TCF (stop mode).
+
Click the Debug button to attach to the process and debug the selected process or thread. Or right-click an item and choose Debug. This applies to both CODA (run mode) and TCF (stop mode).
@@ -88,12 +88,12 @@
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.
+
NOTE Chunks data is not available during CODA 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.
+
NOTE Library data is not available during CODA debugging.
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.
+
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.
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 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 Information for the Chunks and Libraries tabs is not available when debugging with the TRK debug agent.
+
NOTE Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.
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.
@@ -55,7 +55,7 @@
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 applies to both TRK (run mode) and TCF (stop mode).
+
Click the Debug button to attach to the process and debug the selected process or thread. Or right-click an item and choose Debug. This applies to both CODA (run mode) and TCF (stop mode).
@@ -88,12 +88,12 @@
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.
+
NOTE Chunks data is not available during CODA 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.
+
NOTE Library data is not available during CODA debugging.
The following features for Symbian development are provided within Carbide.c++:
+
+
CODA replaces TRK as the debug agent on remote devices. CODA (Carbide On-device Debug Agent) uses the TCF interface to provice improved communication support between the Carbide debugger and the remote device.
+
Milestone 2
A new Carbide.c++ Portal view provides easier access to Carbide information, an extensions marketplace, and support.
Run mode on-device debugging enables you to download and launch a project on a phone or target device and debug it using the Carbide debugger. Before you can do that, some setup requirements are required. Once the setup is done, Carbide can then use plug-and-play (PnP) with USB to create a remote connection that connects with the TRK agent on the target device to download, launch, and debug the program.
+
Run mode on-device debugging enables you to download and launch a project on a phone or target device and debug it using the Carbide debugger. Before you can do that, some setup requirements are required. Once the setup is done, Carbide can then use plug-and-play (PnP) with USB to create a remote connection that connects with the CODA agent on the target device to download, launch, and debug the program.
Setup system and development requirements (below)
Install Application or System TRK v3.2.6 or later on the target device
The on-device debug agent is delivered to the target device as a SISX file. There are two versions of TRK: Application TRK and System TRK.
+
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.
-
Application TRK— 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 TRK— 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.
+
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.
The following SISX file is officially signed by Nokia:
s60_3_0_app_trk_2_6_nokia_signed.sisx
@@ -41,12 +41,12 @@
On the device you will be prompted to enter the same PIN code. Enter PIN code.
The device will then ask you to accept the connection request from the PC. Press OK.
The OBEX folder on the PC should now be available.
-
Drop the TRK SISX file into the folder
+
Drop the CODA SISX file into the folder
The device will prompt you to accept the connection request from the PC. Press OK.
The SISX file should then transfer from the PC to the device
Navigate to where the SISX file was placed
If you dropped it into the OBEX folder it will be in Applications > Messages > Inbox. If you dropped it into the C folder it will be in Applications > Utilities >FileBrowse > C.
-
Select the TRK SISX file on the device to install the TRK debug agent.
+
Select the CODA SISX file on the device to install the CODA debug agent.
On the device make sure the Bluetooth port is turned on
-
On the phone launch TRK.
-
The location of the TRK on-device debug agent will vary based on the phone. On some phones it will be in the Installed folder, on others it may be in the My Own folder.
-
TRK will ask which host you want to pair with. When requested, select your computer from the available Bluetooth devices list.
-
After the host and phone are paired, TRK should be connected. Verify that TRK is running.
+
On the phone launch CODA.
+
The location of the CODA on-device debug agent will vary based on the phone. On some phones it will be in the Installed folder, on others it may be in the My Own folder.
+
CODA will ask which host you want to pair with. When requested, select your computer from the available Bluetooth devices list.
+
After the host and phone are paired, CODA should be connected. Verify that CODA is running.
On the PC:
Right click on the Bluetooth icon in the System tray and select Advanced Configuration
Click the Local Services tab
Write down the Bluetooth COM Port number from the Local Services tab (Figure 1).
-
The Port number will be used when configuring the TRK launch configuration. The Bluetooth COM Port number in the Local Services tab should match the COM port used in the Connections tab of the TRK launch configuration.
+
The Port number will be used when configuring the CODA launch configuration. The Bluetooth COM Port number in the Local Services tab should match the COM port used in the Connections tab of the CODA launch configuration.
Click OK to close the Bluetooth Configuration window
Figure 1. Bluetooth Configuration windows Local Services panel
@@ -47,12 +47,12 @@
Connect the USB cable to the PC and then to the target device
On the device select PC suite from the USB mode list
-
Launch the TRK agent
-
The location of the TRK on-device debug agent will vary based on the phone. On some phones it will be in the Installed folder, on others it may be in My Own folder.
+
Launch the CODA agent
+
The location of the CODA on-device debug agent will vary based on the phone. On some phones it will be in the Installed folder, on others it may be in My Own folder.
Halt the Bluetooth device search by pressing Cancel
Click Options > Settings > Connection
Change Connection type to USB and set connection options (Figure 2)
-
Select Back and start the TRK again and you should be connected
+
Select Back and start the CODA again and you should be connected
Figure 2. USB Connection Settings
On the PC
@@ -65,7 +65,7 @@
Figure 3. Device Manager - Ports
Write down the port ID and Communication Port Properties.
-
The COM Port number in the Device Manager window should match the COM port used in the Connections tab of the TRK launch configuration.
+
The COM Port number in the Device Manager window should match the COM port used in the Connections tab of the CODA launch configuration.
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 TRK or Symbian OS System TRK configuration type for on-device debugging and click New
-
For debug launch configurations using the TRK debug agent, the following pages require review and possible option settings:
+
Select either a Symbian OS Application CODA or Symbian OS System CODA 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
Arguments (Eclipse) - defines the arguments to be passed to the application and to the virtual machine
@@ -86,8 +86,8 @@
View messages between Carbide and debug agent
-
When checked, show the communications between the PC and the target device in a Console view when the TRK Communciation message log is visible.
-
NOTE You can pin the TRK Communication message log view so that it does not lose focus.
+
When checked, show the communications between the PC and the target device in a Console view when the CODA Communciation message log is visible.
+
NOTE You can pin the CODA Communication message log view so that it does not lose focus.
Message retry delay (ms)
@@ -105,7 +105,7 @@
Connection Tab
-
Select the Connection tab that is available for TRK. Specify the Serial port for your configuration. The Connection pane specifies the method used to transfer files to the target device. Once the Current Connection to Target type is selected, the remaining options contain default values for the specific connection type. You can change these options to match the target device's communication specifications.
+
Select the Connection tab that is available for CODA. Specify the Serial port for your configuration. The Connection pane specifies the method used to transfer files to the target device. Once the Current Connection to Target type is selected, the remaining options contain default values for the specific connection type. You can change these options to match the target device's communication specifications.
Figure 7. Debug windows Connection pane using PC Suite
Table 3. Connection pane
@@ -145,7 +145,7 @@
Installation Tab
-
For Application TRK select the Installation tab. The Installation pane specifies the .sis file to install on the target device. This is used by Application TRK because Application TRK downloads all files via a SIS file. This is required when using the TRK debug agent with 9.x based SDK’s.
+
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.
Figure 8. Debug windows Installation pane
Table 4. Installation pane
@@ -176,8 +176,8 @@
File Transfer Tab
-
For System TRK select the File Transfer pane. The File Transfer pane displays a list of files the Carbide IDE transfers to the target device at the start of each launch. By default, any file added is automatically checked for downloading to the device.
-
NOTE If debugging a DLL from an application and using System TRK, ensure that the DLL is included so that it is deployed to the device with the application. It is not added by default.
+
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.
Use a 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 DLLs where the main process is unknown or for servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate.
One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view.
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.
+
NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian OS and the CODA debug agent.
When attempting to find a process the debugger uses the UID3 to locate the process.
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.
+
In addition, any PKG file added here is picked up by the Installation tab in Application CODA 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.
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.
+
You will see symbolic information for other components when you are debugging in ROM using System CODA 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
+
In System CODA you must specify the ROM log file in the ROM Log tab of the CODA or Attach to Process launch configurations
-
NOTE You cannot debug ROM DLLs using Application TRK.
+
NOTE You cannot debug ROM DLLs using Application CODA.
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.
+
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 CODA. 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:
diff -r 2da3246ba2e6 -r 445b096b330f 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 Wed Sep 15 14:44:31 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Wed Sep 15 14:45:18 2010 -0500
@@ -9,10 +9,10 @@
-
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.
+
Run Mode Debug Example (Application CODA)
+
This example shows how to create and build an application and debug it on a device using the Application CODA 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
+
Debugging a Run-mode Project using Application CODA
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.
@@ -24,21 +24,21 @@
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).
This example shows how to create and build an application and debug it on a device using the Application TRK on-device debug agent. Click this link to the HelloCarbide cheatsheet that provides links to detailed steps. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.
+
This example shows how to create and build an application and debug it on a device using the Application CODA on-device debug agent. Click this link to the HelloCarbide cheatsheet that provides links to detailed steps. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.
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:
+
To communicate between the Carbide.c++ debugger and the on-device debug agent, using either Application CODA or System CODA, 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.
+
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 System CODA (not available in the Developer Edition) —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.
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.
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.
+
Choose the Symbian OS Application CODA or System CODA 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:
+
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
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
+
Installation (Application CODA 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
+
ROM Log (System CODA 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.
The on-device debug agent software supports the use of Bluetooth to debug programs running on a target device. To enable communication with a Bluetooth device, a connection must be established between the PC and the device. The on-device debug agent requires a dedicated COM port in order to talk with the device. In some cases, other programs that use the same COM port number will interfere with the TRK debug agent, essentially "fighting" over control of the COM port. Follow the steps below to setup a Bluetooth connection with the Bluetooth enabled device.
+
The on-device debug agent software supports the use of Bluetooth to debug programs running on a target device. To enable communication with a Bluetooth device, a connection must be established between the PC and the device. The on-device debug agent requires a dedicated COM port in order to talk with the device. In some cases, other programs that use the same COM port number will interfere with the CODA debug agent, essentially "fighting" over control of the COM port. Follow the steps below to setup a Bluetooth connection with the Bluetooth enabled device.
NOTE Ensure that no other program has commandeered the Bluetooth connection. For example, some phone connectivity programs will not release a COM port unless specifically told to do so.
NOTE Most problems with on-target debugging setup occur here, so be careful when performing each of these steps.
@@ -27,12 +27,12 @@
Figure 1. Bluetooth Configuration windows Accessibility panel
Write down the Bluetooth COM Port number from the Local Services tab (Figure 2) for later use
Use Bluetooth to install the on-device debug agent, either Application TRK or System TRK, as a SISX file, to enable on-target debugging. The installation location of the on-device debug agent will vary based on the phone. Application TRK is usable on both consumer and RnD versions of the device. System TRK is only usable on RnD devices.
+
Use Bluetooth to install the on-device debug agent, either Application CODA or System CODA, as a SISX file, to enable on-target debugging. The installation location of the on-device debug agent will vary based on the phone. Application CODA is usable on both consumer and RnD versions of the device. System CODA is only usable on RnD devices.
On some phones it will be the Installed folder, on others it may be in My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored.
NOTE The following example shows how to install the SISX file from a PC running Windows XP SP2 using an internal Bluetooth device. The actions to install the SISX file may be different on your version of Windows. Refer to the OS documentation for information on transferring a file via a Bluetooth connection.
@@ -27,8 +27,8 @@
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
+
Click OK when prompted to install CODA
+
Follow the instructions on the screen to finish installing the CODA debug agent
Use the PC Suite software that came with your device (Nokia PC Suite is one example) to install the on-device debug agent, either Application TRK or System TRK, as a SISX file, to enable on-device debugging. Application TRK is usable on both consumer and RnD versions of the device. System TRK is only usable on RnD devices.
+
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 CODA or System CODA, as a SISX file, to enable on-device debugging. Application CODA is usable on both consumer and RnD versions of the device. System TRK is only usable on RnD devices.
The installation location of the on-device debug agent software varies based on the phone. On some phones it will be the Installed folder, on others it may be in My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored.
Using PC Suite you can install any TRK debug agent on the device using a Bluetooth or USB connection.
NOTE You can use the connection software that came with your device to install the on-device debug agent SISX file. See your phone's operating manual for assistance on using it's software.
Launching preference panel and disable the Build (if required) before launching option under the General Options group
) in the Debug view
diff -r 2da3246ba2e6 -r 445b096b330f core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/cmds_starting.htm
--- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/cmds_starting.htm Wed Sep 15 14:44:31 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/cmds_starting.htm Wed Sep 15 14:45:18 2010 -0500
@@ -31,7 +31,7 @@
) to stop or halt a program based on the type of debugging session underway. Terminate behavior includes: 
) of the toolbar or in the Add/Remove Carbide Build Configuration dialog. Every build configuration needs a launch configuration to enable debugging. Launch configurations can be shared between build configurations. The New Launch Configuration Wizard detects when a build configuration doesn't have an associated launch configuration and guides you through the setup process.
) to launch the 
