Installation Pane

# HG changeset patch # User fturovic # Date 1246309943 18000 # Node ID 6cb072f1aa745d6ccefea4f5dbdcb26ee214cd39 # Parent 44ff9ba1e1ccb6635c14b62e12eb3d98a7c782e1 minor edits to fix possessive error diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/app_trk_installation.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/app_trk_installation.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/app_trk_installation.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,71 +1,71 @@ - - - - - - -Installation Pane - - - -

Installation Pane

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

Figure 1 - Debug window's Installation pane

Table 1. Installation pane —items

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

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

- -

To access the Installation Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Installation pane appears (Figure 1).

Common concepts

Common references

- - - - + + + + + + +Installation Pane + + + +

Installation Pane

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

Figure 1 - Debug windows Installation pane

Table 1. Installation pane —items

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

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

+ +

To access the Installation Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Installation pane appears (Figure 1).

Common concepts

Common references

+ + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_debugger.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_debugger.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,73 +1,73 @@ - - - - - - -Debugger Pane - - - -

Debugger Pane

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

Figure 1 - Debug window's Debugger tab

Table 1. Debugger pane —items

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

Item	Explanation
Break at entry point	Select to halt program execution at a specified - function or address. Enter the desired function - name or address in the corresponding field. If you - enter an address, ensure that it is correct and within - your program.
View program output	Enable to direct standard output messages to the Emulation Program Output Console in the Console view. - NOTE In the epoc.ini file the option LogToFile must also be set to 1.
View emulator output	Enable to output emulator messages to the Emulator Output Console in the Console view. - NOTE In the epoc.ini file the option LogToDebugger must also be set to 1.
View Windows system messages	Enable to output Windows system messages to the Windows System Messages Console in the Console view.

- -

To access the Debug window

Select the Run > Debug... menu item

The Debug window appears.

Select a Configuration setting
Click Debugger tab

The Debugger pane appears (Figure 1).

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

Common references

- - - + + + + + + +Debugger Pane + + + +

Debugger Pane

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

Figure 1 - Debug windows Debugger tab

Table 1. Debugger pane —items

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

Item	Explanation
Break at entry point	Select to halt program execution at a specified + function or address. Enter the desired function + name or address in the corresponding field. If you + enter an address, ensure that it is correct and within + your program.
View program output	Enable to direct standard output messages to the Emulation Program Output Console in the Console view. + NOTE In the epoc.ini file the option LogToFile must also be set to 1.
View emulator output	Enable to output emulator messages to the Emulator Output Console in the Console view. + NOTE In the epoc.ini file the option LogToDebugger must also be set to 1.
View Windows system messages	Enable to output Windows system messages to the Windows System Messages Console in the Console view.

+ +

To access the Debug window

Select the Run > Debug... menu item

The Debug window appears.

Select a Configuration setting
Click Debugger tab

The Debugger pane appears (Figure 1).

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

Common references

+ + + \ No newline at end of file diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_exceptions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_exceptions.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_exceptions.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,59 +1,59 @@ - - - - - - -x86 Exceptions Pane - - - -

x86 Exceptions Pane

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

Figure 1 - x86 Exceptions pane

Table 1. x86 Exceptions pane —items

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

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

To access the x86 Exceptions pane

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

The Debug window (Figure 1) appears.

Select a Configuration setting
Click x86 Exceptions tab

The x86 Exceptions pane appears.

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

Common references

- - - - - + + + + + + +x86 Exceptions Pane + + + +

x86 Exceptions Pane

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

Figure 1 - x86 Exceptions pane

Table 1. x86 Exceptions pane —items

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

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

To access the x86 Exceptions pane

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

The Debug window (Figure 1) appears.

Select a Configuration setting
Click x86 Exceptions tab

The x86 Exceptions pane appears.

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Launch Configuration

Common references

+ + + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_main.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_main.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/emulator_main.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,52 +1,52 @@ - - - - - - -Main Pane (Emulator) - - - -

Main Pane (Emulator)

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

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

Figure 1 - Debug window's emulator's Main tab

Table 1. Emulator Main pane —items

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

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

- -

To access the Main Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Main pane appears (Figure 1).

Other references

- - - + + + + + + +Main Pane (Emulator) + + + +

Main Pane (Emulator)

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

Figure 1 - Debug windows emulator's Main tab

Table 1. Emulator Main pane —items

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

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

+ +

To access the Main Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Main pane appears (Figure 1).

Other references

+ + + \ No newline at end of file diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_connection.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_connection.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_connection.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,81 +1,81 @@ - - - - - - -Connection Pane - - - -

Connection Pane

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

Figure 1 - Debug window's Connection pane

Table 1. Connection pane —items

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

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

- -

To access the Connection Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Connection pane appears (Figure 1).

Common concepts

Common tasks

Common references

- - - - + + + + + + +Connection Pane + + + +

Connection Pane

Figure 1 - Debug windows Connection pane

Table 1. Connection pane —items

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

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

+ +

To access the Connection Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Connection pane appears (Figure 1).

Common concepts

Common tasks

Common references

+ + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_executables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_executables.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_executables.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,73 +1,73 @@ - - - - - - -Executables Pane - - - -

Executables Pane

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

Figure 1 - Debug window's Executables pane

Table 1. Executable pane —items

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

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

To access the Executables Pane

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

The Debug window appears.

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

The Executables pane appears (Figure 1).

Common concepts

Common references

- - - + + + + + + +Executables Pane + + + +

Executables Pane

Figure 1 - Debug windows Executables pane

Table 1. Executable pane —items

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

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

To access the Executables Pane

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

The Debug window appears.

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

The Executables pane appears (Figure 1).

Common concepts

Common references

+ + + \ No newline at end of file diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_file_transfer.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_file_transfer.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_file_transfer.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,85 +1,85 @@ - - - - - - -TRK File Transfer Pane - - - -

File Transfer Pane

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

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

Figure 1 - Debug window's File Transfer pane

Table 1. File Transfer pane —items

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

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

- -

To access the File Tansfer Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The File Transfer pane appears (Figure 1).

Common concepts

Common tasks

Common references

- - - + + + + + + +TRK File Transfer Pane + + + +

File Transfer Pane

Figure 1 - Debug windows File Transfer pane

Table 1. File Transfer pane —items

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

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

+ +

To access the File Tansfer Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The File Transfer pane appears (Figure 1).

Common concepts

Common tasks

Common references

+ + + \ No newline at end of file diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_debugger.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_debugger.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,133 +1,133 @@ - - - - - - -Debugger panes for TRK - - - -

Debugger panes for TRK

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

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

Run mode debugging
Stop mode debugging

Run-mode Debugger pane

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

Figure 1 - Debug window's Debugger pane for run mode debugging

Table 1. Debugger pane — run-mode options

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

Item	Explanation
Break at entry point -	When checked, break at the specified entry point entered into the text field. For .EXE targets, the default entry point is set to E32Main. By default, the Break at entry point option is unchecked for all other target types.
View program output	When checked, show the contents of any program output in the TRK Progam Output Console in a Console view.
View messages between Carbide and debug agent	When checked, show the communications between Carbide and the target device in the TRK Communication Log Console of the Console view. - NOTE You can pin the TRK Communication Log view so that it does not lose focus.
Message retry delay (ms)	Enter the delay time in milliseconds (ms) between 100 and 10000 the debugger should wait for a response. The default Message Retry Delay value is 2000.
Default Instructon Set -	Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. The options are: - - Auto (examine code at current PC location) - ARM (32-bit) - THUMB (16-bit) - - By default the Instruction Set option uses ARM 32-bit.

Stop-mode Debugger pane

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

Figure 2 - Debug window's Debugger pane for stop mode debugging

Table 2. Debugger pane — stop-mode options

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

Item	Explanation
Break at entry point	When checked, break at the specified entry point entered into the text field. For .EXE targets, the default entry point is set to E32Main. By default, the Break at entry point option is unchecked for all other target types.
Soft attach	Enable the Soft attach option to attach a debug session to a target and debug from the specified start address instead of the target's default start address. When enabled the downloaded image option is ignored.
Debug from start address	Enable the Debug from start address option to debug from the target's default start address.
Run from start address	Enable the Run from start address option to run from the target's default start address.
Start address (hex)	Enter in hexidecimal format (0x0) the starting address to use during the debug session.
Reset target at the start of each debug session	Forces the Carbide IDE to reset the target at the start of each debug session. This ensures that the debugging session uses the most up-to-date program code.
Target Processor	A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.
Target initialization file	Check this box to have the debugger run an initialization script when the debug session starts. For example, if a target device requires initialization for the debugger to be able to read and write memory or registers, you can specify an initialization script here. - Click Browse to select a script file using a standard file selection dialog box. When using T32, most of the initialization is done in the CMM script file. With other debug protocols like Sophia, you can specify the initialization file, which can be run after connecting to the target.
Memory configuration file	Controls whether the debugger uses a memory configuration file when a debug session starts. The Carbide debugger uses this configuration file to know which memory is accessible, readable, and writable on the target.

- -

To access the Debugger Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Debugger pane appears (Figure 1).

Common concepts

Common references

- - - - + + + + + + +Debugger panes for TRK + + + +

Debugger panes for TRK

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

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

Run mode debugging
Stop mode debugging

Run-mode Debugger pane

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

Figure 1 - Debug windows Debugger pane for run mode debugging

Table 1. Debugger pane — run-mode options

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

Item	Explanation
Break at entry point +	When checked, break at the specified entry point entered into the text field. For .EXE targets, the default entry point is set to E32Main. By default, the Break at entry point option is unchecked for all other target types.
View program output	When checked, show the contents of any program output in the TRK Progam Output Console in a Console view.
View messages between Carbide and debug agent	When checked, show the communications between Carbide and the target device in the TRK Communication Log Console of the Console view. + NOTE You can pin the TRK Communication Log view so that it does not lose focus.
Message retry delay (ms)	Enter the delay time in milliseconds (ms) between 100 and 10000 the debugger should wait for a response. The default Message Retry Delay value is 2000.
Default Instructon Set +	Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. The options are: + + Auto (examine code at current PC location) + ARM (32-bit) + THUMB (16-bit) + + By default the Instruction Set option uses ARM 32-bit.

Stop-mode Debugger pane

Figure 2 - Debug windows Debugger pane for stop mode debugging

Table 2. Debugger pane — stop-mode options

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

Item	Explanation
Break at entry point	When checked, break at the specified entry point entered into the text field. For .EXE targets, the default entry point is set to E32Main. By default, the Break at entry point option is unchecked for all other target types.
Soft attach	Enable the Soft attach option to attach a debug session to a target and debug from the specified start address instead of the target's default start address. When enabled the downloaded image option is ignored.
Debug from start address	Enable the Debug from start address option to debug from the target's default start address.
Run from start address	Enable the Run from start address option to run from the target's default start address.
Start address (hex)	Enter in hexidecimal format (0x0) the starting address to use during the debug session.
Reset target at the start of each debug session	Forces the Carbide IDE to reset the target at the start of each debug session. This ensures that the debugging session uses the most up-to-date program code.
Target Processor	A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.
Target initialization file	Check this box to have the debugger run an initialization script when the debug session starts. For example, if a target device requires initialization for the debugger to be able to read and write memory or registers, you can specify an initialization script here. + Click Browse to select a script file using a standard file selection dialog box. When using T32, most of the initialization is done in the CMM script file. With other debug protocols like Sophia, you can specify the initialization file, which can be run after connecting to the target.
Memory configuration file	Controls whether the debugger uses a memory configuration file when a debug session starts. The Carbide debugger uses this configuration file to know which memory is accessible, readable, and writable on the target.

+ +

To access the Debugger Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Debugger pane appears (Figure 1).

Common concepts

Common references

+ + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_main.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_main.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/launch_configs/page_trk_main.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,62 +1,62 @@ - - - - - - -Main Pane - - -

Main Pane

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

Figure 1 - Debug window's Main pane

Table 1. Main pane —items

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

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

Item

Explanation

Project

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

Remote process to launch

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

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

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

- -

To access the Main Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Main pane appears (Figure 1).

Common concepts

Common references

- - - + + + + + + +Main Pane + + +

Main Pane

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

Figure 1 - Debug windows Main pane

Table 1. Main pane —items

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

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

Item

Explanation

Project

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

Remote process to launch

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

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

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

+ +

To access the Main Pane

Select the Run > Debug... menu item

The Debug window appears.

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

The Main pane appears (Figure 1).

Common concepts

Common references

+ + + \ No newline at end of file diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/menus/open_cmd_window.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/open_cmd_window.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/open_cmd_window.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,20 +1,20 @@ - - - - - - -Open Command Window - - - -

Open Command Window

Launches a Microsoft Window's Command Prompt set to the workspace directory.

Other references

Carbide Menus

- - - - + + + + + + +Open Command Window + + + +

Open Command Window

Launches a Microsoft Windows Command Prompt set to the workspace directory.

Other references

Carbide Menus

+ + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/menus/open_explorer_window.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/open_explorer_window.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/open_explorer_window.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,20 +1,20 @@ - - - - - - -Show in Explorer - - - -

Show in Explorer

Launches a Microsoft Window's Explorer window set to the workspace directory.

Other references

Carbide Menus

- - - - + + + + + + +Show in Explorer + + + +

Show in Explorer

Launches a Microsoft Windows Explorer window set to the workspace directory.

Other references

Carbide Menus

+ + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/panel_debug_exceptions.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,59 +1,59 @@ - - - - - - -x86 Exceptions Pane - - - -

x86 Exceptions Pane

The Debug or launch configuration window's x86 Exceptions pane lists all the exceptions that the debugger is able to catch. If you want the debugger to catch all the exceptions, enable all of the options in this view. However, if you prefer to handle only certain exceptions, enable only those options that reflect the exceptions you prefer to handle.

Figure 1 - x86 Exceptions pane

Table 1. x86 Exceptions pane —items

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

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

To access the x86 Exceptions pane

Select the Run > Debug... menu item

The Debug window (Figure 1) appears.

Select a Configuration setting
Click x86 Exceptions tab

The x86 Exceptions pane appears.

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Debug Configuration

Common references

- - - - - + + + + + + +x86 Exceptions Pane + + + +

x86 Exceptions Pane

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

Figure 1 - x86 Exceptions pane

Table 1. x86 Exceptions pane —items

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

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

To access the x86 Exceptions pane

Select the Run > Debug... menu item

The Debug window (Figure 1) appears.

Select a Configuration setting
Click x86 Exceptions tab

The x86 Exceptions pane appears.

Common concepts

About the Debugger

Common tasks

Debugging a Program (Example)
Creating a Debug Configuration

Common references

+ + + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_07.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_07.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_07.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,76 +1,76 @@ - - - - - - -Debugger Settings - - - -

Run Mode On-Device Debugging

To implement run mode on-device debugging the following tasks need to be completed.

Install device connection software
Install Perl
Install an SDK
Setup environment variables
Setup a virtual drive for Techview and Cust Kits
Set the default kit in Devices.xml
Install the SISX file on the target device
Configure TRK connection on the device
Create a launch configuration

Configure TRK Connection on the Device

Connecting with Bluetooth

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 PC: -
1. Right click on the Bluetooth icon in the System tray and select Advanced Configuration
2. Click the Local Services tab
3. Write down the Bluetooth COM Port number from the Local Services tab (Figure 1).
4. Click OK to close the Bluetooth Configuration window
-

Connecting with PC Suite

- -

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.

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

Figure 2. USB Connection Settings

On the PC

Open Window's Computer Management by right-clicking My Computer and select Manage from the context menu to open the Computer Management window.
Select System Tools > Device Manager > Ports (COM & LPT) to display all active ports
Locate the S60 Phone USB (COMxx) item in the list

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.

Close the Device Manager window

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

Run Mode On-Device Debugging

To implement run mode on-device debugging the following tasks need to be completed.

Install device connection software
Install Perl
Install an SDK
Setup environment variables
Setup a virtual drive for Techview and Cust Kits
Set the default kit in Devices.xml
Install the SISX file on the target device
Configure TRK connection on the device
Create a launch configuration

Configure TRK Connection on the Device

Connecting with Bluetooth

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 PC: +
1. Right click on the Bluetooth icon in the System tray and select Advanced Configuration
2. Click the Local Services tab
3. Write down the Bluetooth COM Port number from the Local Services tab (Figure 1).
4. Click OK to close the Bluetooth Configuration window
+

Connecting with PC Suite

+ +

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.

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

Figure 2. USB Connection Settings

On the PC

Open Windows Computer Management by right-clicking My Computer and select Manage from the context menu to open the Computer Management window.
Select System Tools > Device Manager > Ports (COM & LPT) to display all active ports
Locate the S60 Phone USB (COMxx) item in the list

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.

Close the Device Manager window

+ + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,187 +1,187 @@ - - - - - - -Debugger Settings - - - -

Run Mode On-Device Debugging

To implement run mode on-device debugging the following tasks need to be completed.

Install device connection software
Install Perl
Install an SDK
Setup environment variables
Setup a virtual drive for Techview and Cust Kits
Set the default kit in Devices.xml
Install the SISX file on the target device
Configure TRK connection on the device
Create a launch configuration

Creating a Launch Configuration setup

Import the MMP or INF file
Select the Project in the C/C++ Project pane you want to debug
From the IDE select Run > Debug…
The New Launch Configuration Wizard appears

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

Figure 4. Debug Window

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:

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
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 - files transfered to the target device at the start of each launch
Installation - specifies the .sis or .pkg file to install on the target device
Executables - specifies which executables are debugged by your project
Source (Eclipse) - defines the location of source files used to display source when debugging
Common (Eclipse) - defines general information about the launch configuration

Click Debug after all the preference panels have been set. The Debug window closes and the Carbide.c++ debugger begins a debugging session using the new configuration. The next time you click the Debug icon, this debug launch configuration is used to start a debug session.

Main Tab

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

Figure 5. Debug window - Main Tab

Table 1. Main pane

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

Item	Explanation
Project	The project to associate with this debug launch configuration. Click Browse to select a different project.
Remote process to launch	The absolute path of the remote process to launch on the target device.

- -

Debugger Tab

The Debug or launch configuration window's Debugger pane provides control over entry points, message handling, and instruction set default settings.

Figure 6. Debug window's Debugger Pane

Table 2. Debugger pane

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

Item	Explanation
Break at entry point	When checked, break at the specified entry point entered in the text field. For .EXE targets, the default entry point is set to E32Main. By default, the Break at entry point option is unchecked for all other target types.
View program output	When checked, show the contents of any unframed messages from the communications port in a Console view.
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.
Message retry delay (ms)	Enter the delay time in milliseconds (ms) between 100 and 10000 that the debugger should wait for a response. The default Message retry delay value is 2000.
Default Instructon Set	Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. The options are: - Auto (examine code at current PC location) - ARM (32-bit) - THUMB (16-bit) - - By default the Instruction Set option uses ARM 32-bit.

- -

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.

Figure 7. Debug window's Connection pane using PC Suite

Table 3. Connection pane

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

Item	Explanation
Current Connection to Target	Choose the connection type to use when communicating with a device.
Serial Port	Select the serial port option to use for the launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. - NOTE USB and Bluetooth can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device.
Baud Rate	Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).
Data Bits	Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.
Parity	Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.
Stop Bits	Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 2.
Flow Control	Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.

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.

Figure 8. Debug window's Installation pane

Table 4. Installation pane

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

Item	Explanation
Installation file	Browse to and select the file to be installed.
Download directory	Specify directory to receive download.
Install each launch even if installer file has not changed	Check this option to always install the .sis file.
Do not show installer UI on the phone	Check this option to hide the installer interface on the phone.
Install to drive:	Select drive on phone to install the .sis file.

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.

Figure 9. Debug window's File Transfer pane

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

Run Mode On-Device Debugging

To implement run mode on-device debugging the following tasks need to be completed.

Install device connection software
Install Perl
Install an SDK
Setup environment variables
Setup a virtual drive for Techview and Cust Kits
Set the default kit in Devices.xml
Install the SISX file on the target device
Configure TRK connection on the device
Create a launch configuration

Creating a Launch Configuration setup

Import the MMP or INF file
Select the Project in the C/C++ Project pane you want to debug
From the IDE select Run > Debug…
The New Launch Configuration Wizard appears

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:

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
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 - files transfered to the target device at the start of each launch
Installation - specifies the .sis or .pkg file to install on the target device
Executables - specifies which executables are debugged by your project
Source (Eclipse) - defines the location of source files used to display source when debugging
Common (Eclipse) - defines general information about the launch configuration

Main Tab

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

Figure 5. Debug window - Main Tab

Table 1. Main pane

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

Item	Explanation
Project	The project to associate with this debug launch configuration. Click Browse to select a different project.
Remote process to launch	The absolute path of the remote process to launch on the target device.

+ +

Debugger Tab

The Debug or launch configuration windows Debugger pane provides control over entry points, message handling, and instruction set default settings.

Figure 6. Debug windows Debugger Pane

Table 2. Debugger pane

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

Item	Explanation
Break at entry point	When checked, break at the specified entry point entered in the text field. For .EXE targets, the default entry point is set to E32Main. By default, the Break at entry point option is unchecked for all other target types.
View program output	When checked, show the contents of any unframed messages from the communications port in a Console view.
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.
Message retry delay (ms)	Enter the delay time in milliseconds (ms) between 100 and 10000 that the debugger should wait for a response. The default Message retry delay value is 2000.
Default Instructon Set	Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. The options are: + Auto (examine code at current PC location) + ARM (32-bit) + THUMB (16-bit) + + By default the Instruction Set option uses ARM 32-bit.

+ +

Connection Tab

Figure 7. Debug windows Connection pane using PC Suite

Table 3. Connection pane

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

Item	Explanation
Current Connection to Target	Choose the connection type to use when communicating with a device.
Serial Port	Select the serial port option to use for the launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. + NOTE USB and Bluetooth can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device.
Baud Rate	Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).
Data Bits	Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.
Parity	Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.
Stop Bits	Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 2.
Flow Control	Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.

Installation Tab

Figure 8. Debug windows Installation pane

Table 4. Installation pane

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

Item	Explanation
Installation file	Browse to and select the file to be installed.
Download directory	Specify directory to receive download.
Install each launch even if installer file has not changed	Check this option to always install the .sis file.
Do not show installer UI on the phone	Check this option to hide the installer interface on the phone.
Install to drive:	Select drive on phone to install the .sis file.

File Transfer Tab

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.

Figure 9. Debug windows File Transfer pane

+ + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,53 +1,53 @@ - - - - - - -Bluetooth Connectivity Setup - - - -

Bluetooth Connection Setup

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.

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.

Setting up a Bluetooth Connection for On-device Debugging

NOTE This example shows how to setup a Bluetooth connection on a PC running Windows XP SP2 with an internal Bluetooth device. The actions to setup Bluetooth connections may be different on your version of Windows. Refer to the OS documentation for information on configuring Bluetooth connections. Ensure that the correct Bluetooth drivers are installed.

Open the Bluetooth Configuration window (Start > Settings > Control Panel > Bluetooth Configuration)
Verify the following settings in the Accessibility tab (Figure 1): -
- The option "Let other Bluetooth devices discover this computer" is checkmarked
- The option "Allow" is set to "All Devices"
-

Figure 1. Bluetooth Configuration window's Accessibility panel

Write down the Bluetooth COM Port number from the Local Services tab (Figure 2) for later use

The Bluetooth COM Port number in the Local Services tab - should match the COM port used in the Connections tab of the TRK launch
- configuration.

Figure 2. Bluetooth Configuration window's Local Services panel

Click OK to close the Bluetooth Configuration window
Download the Application TRK or System TRK SISX file to the device

- - - - + + + + + + +Bluetooth Connectivity Setup + + + +

Bluetooth Connection Setup

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.

Setting up a Bluetooth Connection for On-device Debugging

Open the Bluetooth Configuration window (Start > Settings > Control Panel > Bluetooth Configuration)
Verify the following settings in the Accessibility tab (Figure 1): +
- The option "Let other Bluetooth devices discover this computer" is checkmarked
- The option "Allow" is set to "All Devices"
+

Figure 1. Bluetooth Configuration windows Accessibility panel

Write down the Bluetooth COM Port number from the Local Services tab (Figure 2) for later use

The Bluetooth COM Port number in the Local Services tab + should match the COM port used in the Connections tab of the TRK launch
+ configuration.

Figure 2. Bluetooth Configuration windows Local Services panel

Click OK to close the Bluetooth Configuration window
Download the Application TRK or System TRK SISX file to the device

Related concepts

On-device Debugging

Related references

Debug Window (On-device Debugging) Overview

Related tasks

Installing On-device Debug Agents using Bluetooth

+ + + + diff -r 44ff9ba1e1cc -r 6cb072f1aa74 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm Mon Jun 29 16:00:45 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm Mon Jun 29 16:12:23 2009 -0500 @@ -1,55 +1,55 @@ - - - - - - -USB Connectivity Setup - - - -

USB Connection Setup

On-device debugging supports the use of USB to debug programs running on a target device. To enable communication with a USB device, a connection must be established between the PC and the device. Doing that requires one of the following USB connectivity cables to physically connect the PC to the device:

DKU-2
CA-53

Setting up a USB Connection for On-device Debugging

Install the latest USB connectivity software, for example, S60 devices use Nokia PC Suite
Connect the USB connectivity cable to your PC and then the target device
For S60 devices, select PC-Suite from the USB Mode list when the target device is connected
Download the Application TRK or System TRK SISX file to the device
On the PC - (optional)

Open the Window's Computer Management (Windows XP)

Right-click My Computer and select Manage from the context menu to open the Computer Management window. Select System Tools > Device Manager > Ports (COM & LPT) to display all active ports.

Locate the S60 Phone USB (COMx) item in the list (Figure 2)

Figure 2. Device Manager showing Ports (COM & LPT) section

The USB COM Port number should match the COM port used in the Connections tab of the TRK launch - configuration.
Close the Device Manager window

Related concepts

On-device Debugging

Related references

Debug Window (On-device Debugging) Overview

Related tasks

Installing On-device Debug Agents using USB

- - - - + + + + + + +USB Connectivity Setup + + + +

USB Connection Setup

DKU-2
CA-53

Setting up a USB Connection for On-device Debugging

Install the latest USB connectivity software, for example, S60 devices use Nokia PC Suite
Connect the USB connectivity cable to your PC and then the target device
For S60 devices, select PC-Suite from the USB Mode list when the target device is connected
Download the Application TRK or System TRK SISX file to the device
On the PC + (optional)

Open the Windows Computer Management (Windows XP)

Locate the S60 Phone USB (COMx) item in the list (Figure 2)

Figure 2. Device Manager showing Ports (COM & LPT) section

The USB COM Port number should match the COM port used in the Connections tab of the TRK launch + configuration.
Close the Device Manager window

Related concepts

On-device Debugging

Related references

Debug Window (On-device Debugging) Overview

Related tasks

Installing On-device Debug Agents using USB

+ + + +