Carbide Debugger panes

# HG changeset patch # User fturovic # Date 1264528928 21600 # Node ID e90ca175264251506f688d211b3c11f1b31f8b13 # Parent 41b05da1d19fc2e437b092f89e8e1b1cb498abb5# Parent b794e25ca74a8650b757a1df00922e08209bb566 daily head merge diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/.project --- a/core/com.nokia.carbide.cpp.doc.user/.project Mon Jan 25 10:46:04 2010 -0600 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,22 +0,0 @@ - - - com.nokia.carbide.cpp.doc.user - - - - - - org.eclipse.pde.ManifestBuilder - - - - - org.eclipse.pde.SchemaBuilder - - - - - - org.eclipse.pde.PluginNature - - diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Tue Jan 26 12:02:08 2010 -0600 @@ -21,7 +21,6 @@

Symbian OS Attach to Process —used to debug processes running on a target device for which a symbol file is available. This is available only for TRK and stop mode debugging. This launch configuration is not available for emulator debugging. Stop mode and TRK can both attach to a process from the Symbian OS Data view.

Symbian OS Crash Debugger —used to launch an interactive command-line session with the Symbian OS crash debugger when the device crashes

Symbian OS Emulation —used to run or debug executables on an emulator.

Symbian OS Sophia (only available in OEM Edition)—is an external debugger that the Carbide debugger communicates with, to debug any Symbian OS module on a target using a JTAG connection.

Symbian OS System TRK (not available Developer Editions) —used to run or debug applications or ROM code on a target device using the System TRK on-device debug agent. System TRK is an application that runs on reference boards and prototype phones and allows you to debug your executables. The debugger will download files to the phone prior to launching.

Symbian OS Trace32 (only available in OEM Edition)—is an external debugger that the Carbide debugger communicates with, to debug any Symbian OS module on a target using a JTAG connection.

@@ -32,6 +31,6 @@

New Launch Configuration Wizard

Debug dialog

- + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_types.htm Tue Jan 26 12:02:08 2010 -0600 @@ -15,7 +15,6 @@

@@ -23,6 +22,6 @@

Launch Configuration Overview

- + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_debugger.htm Tue Jan 26 12:02:08 2010 -0600 @@ -1,155 +1,154 @@ - - - - - - -Carbide Debugger panes - - - -

Debugger panes

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

Emulation Debugger page (Emulation)
Run-mode Debugger page (Application TRK)
Stop-mode Debugger page (System TRK, Trace32, Sophia, Attach to Process)

Emulation Debugger page

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

Figure 1 - Debugger page showing emulation options

Table 1. Debugger page — emulation options

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

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

Run-mode Debugger page

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

Figure 2 - Debugger page showing run-mode options

Table 2. Debugger page — run-mode options

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

Option	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	Enable to direct standard output messages to the TRK Program Output Console in the Console view. - NOTE In the epoc.ini file the option LogToFile must also be set to 1. -
View messages between Carbide and debug agent	When checked, show the communications between Carbide and the target device in the TRK Communication Log Console of the Console view. - NOTE You can pin the TRK Communication Log view so that it does not lose focus.
Message retry delay (ms)	Enter the delay time in milliseconds (ms) between 100 and 10000 the debugger should wait for a response. The default Message Retry Delay value is 2000.
Default Instructon Set	Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. The options are: - - Auto (examine code at current PC location) - ARM (32-bit) - THUMB (16-bit) - - By default the Instruction Set option uses ARM 32-bit.

Stop-mode Debugger page

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

Figure 3 - Debugger page showing stop-mode options

Table 3. Debugger page — stop-mode options

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

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

- -

Other references

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

Debugger panes

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

Emulation Debugger page (Emulation)
Run-mode Debugger page (Application TRK)
Stop-mode Debugger page (System TRK, Trace32, Attach to Process)

Emulation Debugger page

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

Figure 1 - Debugger page showing emulation options

Table 1. Debugger page — emulation options

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

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

Run-mode Debugger page

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

Figure 2 - Debugger page showing run-mode options

Table 2. Debugger page — run-mode options

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

Option	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	Enable to direct standard output messages to the TRK Program Output Console in the Console view. + NOTE In the epoc.ini file the option LogToFile must also be set to 1. +
View messages between Carbide and debug agent	When checked, show the communications between Carbide and the target device in the TRK Communication Log Console of the Console view. + NOTE You can pin the TRK Communication Log view so that it does not lose focus.
Message retry delay (ms)	Enter the delay time in milliseconds (ms) between 100 and 10000 the debugger should wait for a response. The default Message Retry Delay value is 2000.
Default Instructon Set	Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. The options are: + + Auto (examine code at current PC location) + ARM (32-bit) + THUMB (16-bit) + + By default the Instruction Set option uses ARM 32-bit.

Stop-mode Debugger page

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

Figure 3 - Debugger page showing stop-mode options

Table 3. Debugger page — stop-mode options

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

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

+ +

Other references

+ + + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Tue Jan 26 12:02:08 2010 -0600 @@ -13,7 +13,7 @@

Emulation Main page (Emulation)
Run-mode Main page (Application TRK)
Stop-Mode Main page (System TRK, Sophia, Trace32)
Stop-Mode Main page (System TRK, Trace32)

Emulation Main page

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

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

Stop-mode Main page

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

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

Figure 3. Main page (TRACE32 shown)

Table 3. Stop-mode Main page — items

diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/sophia.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/sophia.htm Mon Jan 25 10:46:04 2010 -0600 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,32 +0,0 @@ - - - - -Sophia Launch Configuration - - - - -

Sophia Launch Configuration

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

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

Figure 1. Sophia launch configuration in the Debug dialog

The Sophia launch configuration panes include:

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

Other references

Launch Configuration Overview

- - - diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/stop_mode.htm Tue Jan 26 12:02:08 2010 -0600 @@ -9,7 +9,7 @@

System TRK Launch Configuration (Stop-mode)

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

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

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

Figure 1. System TRK launch configuration in the Debug dialog

@@ -26,6 +26,6 @@

Launch Configuration Overview

- + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Tue Jan 26 12:02:08 2010 -0600 @@ -32,8 +32,7 @@

Executable Selection

Build Option Selection

New Launch Configuration

- - + Application TRK and System TRK @@ -50,13 +49,6 @@ - Sophia STI -

Sophia Initialization Settings
Symbian ROM Image Settings

- - Attach to Process

TRK Connection Settings

This page only appears when creating a Trace32 launch configuration.

Figure 9 - Trace32 Initialization Settings page

Sophia STI Initialization Settings

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

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

Figure 10 - Sophia STI Initialization Settings page

Symbian ROM Image Settings

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

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

This page appears when creating a Trace32 launch configuration.

Figure 11 - Symbian ROM Image Settings page

Figure 10 - Symbian ROM Image Settings page

Other references

Launch Configuration

Figure 1 - Remote Connections view

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

Figure 2. Remote Connections tab

Remote Connections view toolbar icons

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

@@ -106,7 +109,7 @@

Remote Connections view context menu options

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

Figure 2 - Remote Connections context menu

Figure 3 - Remote Connections context menu

@@ -163,7 +166,7 @@

Install latest TRK

Plug-n-Play TRK Setup

- + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_symbian_kernel.htm Tue Jan 26 12:02:08 2010 -0600 @@ -52,7 +52,7 @@ - @@ -108,7 +108,7 @@

Setting Symbian OS View Refresh Rate

- + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Tue Jan 26 12:02:08 2010 -0600 @@ -8,14 +8,14 @@

Stop Mode Debug Example

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

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

The basic steps include:

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

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

@@ -29,9 +29,8 @@

- + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_jtag.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_jtag.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_jtag.htm Tue Jan 26 12:02:08 2010 -0600 @@ -1,70 +1,49 @@ - - - - - -Stop Mode On-Device Debugging - - - -

Installing JTAG

Install the JTAG Software

Using Lauterbach Hardware

Program Lauterbach with Proper License

You will need a Trace32 (Lauterbach), a USB cable, and a Lauterbach power supply. You will need to program the Lauterbach with licenses for the particular processors you will be targeting.

Older Lauterbachs have Xscale for Lubbock and ARM9 for H2/Renesas licenses installed on them already. Newer Lauterbachs should have ARM9 for H2/Renesas and ARM11 for H4 licenses installed on them already. If you don’t have the proper license installed on the Lauterbach for the processor you want to work with, you will receive an error when launching a debug session.

Run the Trace32 Installer -
- Run the Setup.bat file. During installation select the following options:
  
  - Product Type: In-Circuit Debugger
  - ICD interface Type: USB Interface
  - Selection of license for new software: License key not necessary
  - CPU selection: ICD ARM7 ARM9 ARM10 ARM11 ICD XSCALE
-
Install the USB Drivers

Place a Trace32 CD into the host machine.
Plug in the USB connector from the Lauterbach into the host machine.
Once the host machine detects the connection, install the drivers from the CD.

Copy Trace32 License File to T32 Folder

The newer Lauterbachs require a license file in the T32 folder. Copy the trace32 license file called license.t32 to your C:\T32 folder.

Copy Trace32 Configuration File

For H4 board: Copy the trace32 configuration file for the non-ARM11 processor, called config_arm11.t32, to your C:\T32 folder. You can also modify the default config_arm11.t32 file. This file needs to be modified to specify the port number and also enable T32 to support debugger commands outside T32. Carbide.c++ provides specific T32 config files in the support folder. The default config file will be called carbideconfig.t32.

Set up the Board

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

- -

Using Sophia Hardware

If needed, install the following Watchpoint debugger software:
-
Watchpoint ARM9
- Watchpoint ARM11
- CodeWarrior - Watchpoint Connection tool
- Driver for USB dongle for STI ARM
- Watchpoint ARM9 Help Files
Setup Watchpoint

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

Establish Target Connection -
1. Plug USB dongle into your PC, and install the drivers if necessary.
2. Connect Sophia EJ-Debug JTAG device to the Jtag on the mother board (make sure SW3-7 is off) and to PC via USB cable.
3. When Windows prompts you for a driver, navigate to your WATCHPOINT\US_ARM9 or WATCHPOINT\US_ARM11 installation.
4. Open the WatchPoint project file. If it launches successfully, you have established a connection.
-
After successfully opening the project file, make sure that for the H4 target, the Jtag clock is set to 8.33MHz. This can be done from the Resource menu of WatchPoint. Select the ‘ICE Configuration’ option and then select the ‘Clock’ tab. Check the 8.33 MHz radio button and apply the settings.
-

Related Tasks

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

Installing JTAG

Install the JTAG Software

Using Lauterbach Hardware

Program Lauterbach with Proper License

You will need a Trace32 (Lauterbach), a USB cable, and a Lauterbach power supply. You will need to program the Lauterbach with licenses for the particular processors you will be targeting.

Run the Trace32 Installer +
- Run the Setup.bat file. During installation select the following options:
  
  + Product Type: In-Circuit Debugger
  + ICD interface Type: USB Interface
  + Selection of license for new software: License key not necessary
  + CPU selection: ICD ARM7 ARM9 ARM10 ARM11 ICD XSCALE
+
Install the USB Drivers

Place a Trace32 CD into the host machine.
Plug in the USB connector from the Lauterbach into the host machine.
Once the host machine detects the connection, install the drivers from the CD.

Copy Trace32 License File to T32 Folder

The newer Lauterbachs require a license file in the T32 folder. Copy the trace32 license file called license.t32 to your C:\T32 folder.

Copy Trace32 Configuration File

Set up the Board

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

Related Tasks

+ + + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_launchcfg.htm Tue Jan 26 12:02:08 2010 -0600 @@ -1,301 +1,280 @@ - - - - - -Stop Mode On-Device Debugging - - - -

Defining a Stop Mode Debug Configuration

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

Define a Launch Configuration

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

Figure 1 - Debug Configurations

Select either a Symbian OS Sophia or Symbian OS Trace32 configuration type for stop mode on-device debugging and click the New launch configuration icon. The following pages require review and possible option settings:

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

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

Define Main Tab Settings

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

Figure 2 - Debug Window - Main Tab

Table 1. Main pane

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

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

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

Define Connection Tab Settings

Figure 3 - Debug Window - Connection Tab

Table 2 - Connection pane

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

Item	Explanation
- Trace32 Executable	Specify the path to the Trace32 executable. The default path assumes that the Trace32 executable is installed in the default location: C:\T32\T32marm.exe.
- Trace32 Configuration File	Specify the path to the config.t32 file or other custom configuration file. The default path assumes that the Trace32 configuration file is installed in the default location: C:\T32\config.t32. - For arm11 processors copy the trace32 configuration file for non-ARM11 processor (config_arm11.t32) to your C:\T32 folder and specify it in the edit box. - You can modify the config.t32 file to support UDP (User Datagram Protocol) connections by adding the following lines: - PBI=USB - RCL=NETASSIST - PACKLEN=1024 - PORT=20000
- - - Trace32 Initialization Script	Specify the path to the initialization cmm file. This script will be run in T32 after connecting to T32. You can specify your own scripts for the targets used.
- - - View messages between Carbide and Trace32	Enable to log communications with Trace32 to the console window.

Define Debugger Tab Settings

Figure 4 - Debug Window - Debugger tab

Table 3 - 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.
Target Processor	A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.
- Target Initialization File	Check this box to have the debugger run an initialization script when the debug session starts. For example, if a target device requires initialization for the debugger to be able to read and write memory or registers, you can specify an initialization script here. Click Browse to select a script file using a standard file selection dialog box. - When using T32, most of the initialization is done in the CMM script file. With other debug protocols like Sophia, you can specify the initialization file, which can be run after connecting to the target.
- Memory Configuration File	Controls whether the debugger uses a memory configuration file when a debug session starts. The Carbide debugger uses this configuration file to know which memory is accessible, readable, and writable on the target.
- Reset target at the start of each debug session	Forces the Carbide IDE to reset the target at the start of each debug session. This ensures that the debugging session uses the most up-to-date program code.
Default Instructon Set	Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. This can happen at addresses for which we have no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code. The options are: - - Auto (examine code at current PC location) - ARM (32-bit) - THUMB (16-bit) - - By default the Instruction Set option uses ARM 32-bit.

Define ROM Image Tab

Figure 5 - Debug Window - ROM Image Tab

Table 4 - ROM Image pane

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

Item	Explanation
- - - Start Address	Enter the physical address in memory where the Symbian OS start code begins execution. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x8000000 is a valid entry. - NOTE The address entered in this field must match the start address specified in the source code used to build the Symbian OS ROM image to be debugged. The Start address must match the Download address.
- - - Debug from Start address	Select this option to have the debugger halt the program at the address specified in Start Address once the target initialization is done and the OS is downloaded; if the user has chosen to download the OS. You can then step through start-up code or run the target in bare-board mode.
- - - - Run from start address	Select this option to have the debugger start the code at the address specified in Start Address once the target initialization is done. If you have breakpoints set, the debugger stops at the first breakpoint encountered. You can click the Break button to halt the device.
- - - - - Symbian ROM Log file	Check the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images. In the first text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.
- - - - Symbian OS Kit EPOC32 Directory	Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory. - NOTE Always include the epoc32 folder in this path.
- - - - - - Log unresolved modules	Check this box to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session. - NOTE You cannot perform source-level debugging on components that do not include symbolic information.
- - - - - - Debug non-XIP Executables	Check this box to debug a project, or a dynamically loaded module, that is loaded from NAND-Flash or other removable media (MMC, memory stick, etc.) at run time and executed in RAM. Use this option to debug modules that work fine when executed in place as part of the ROM image, but sometimes fail when placed in NAND-Flash or other removable media. - NOTE Selecting this option will affect debugging performance. When the debugger needs to load a module (DLL, EXE, etc.) it will stop the target, read information from it, then restart it.
- - - - - Symbian ROM Image	Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window.
- Download Address (hex)	Enter the physical address in memory at which the debugger should place the ROM image. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x000FFF00 is a valid entry. - NOTE The address entered in this field must match the download address specified in the source code used to build the Symbian OS ROM image to be debugged. If you leave this field blank, the debugger does not download the ROM image to the device at the beginning of the debug session. The Download address must match the Start address.
- Ask for download at the start of each debug session	Check this box to have the debugger display a dialog box at the beginning of every debug session that lets you choose whether or not you want the debugger to download the ROM image to the device.

- -

Sophia Target Interface Connection

The following Connection pane is specific to the Sophia Target Interface and is shown in a Sophia Launch Configuration only. Other panes are same as Trace32 panes.

Figure 6 - Sophia Connection Window

Table 5 - Sophia Connection Window

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

Item	Explanation
- - - - - - - Sophia Target Interface (WTI.dll) location	Specifies the location of a Sophia dll that the debugger will load and interface with in order to communicate with the Sophia JTAG interface. The preference panel will try to determine this value from the registry or some other means and auto fill it when possible.
- - - - - EJ_Debug Type	Sophia Systems' EJ-Debug is a compact, USB-powered JTAG emulator. Select the EJ_Debug type. Options include: - - Auto (automatically detects target CPU) - ARM9 (target CPU) - ARM11 (target CPU) - ARM9_11 (target CPU) - ARM7_9_11 (target CPU) -
JTAG TCLK Frequency	Select the JTAG TCLK frequency. Options include: - - Auto - 33 MHz - 16 MHz - 8 MHz - 500 KHz -
View messages between Carbide and STI	The View Messages between Carbide and STI check box allows you to specify if the debug protocol messages between Carbide and STI should be logged in a Communication Log console window.

- - -

Related Tasks

Stop Mode On-Device Debugging Preconditions

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

Defining a Stop Mode Debug Configuration

Define a Launch Configuration

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

Figure 1 - Debug Configurations

Select either a Symbian OS Trace32 configuration type for stop mode on-device debugging and click the New launch configuration icon. The following pages require review and possible option settings:

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

Define Main Tab Settings

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

Figure 2 - Debug Window - Main Tab

Table 1. Main pane

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

Define Connection Tab Settings

Figure 3 - Debug Window - Connection Tab

Table 2 - Connection pane

Item	Explanation
+ Trace32 Executable	Specify the path to the Trace32 executable. The default path assumes that the Trace32 executable is installed in the default location: C:\T32\T32marm.exe.
+ Trace32 Configuration File	Specify the path to the config.t32 file or other custom configuration file. The default path assumes that the Trace32 configuration file is installed in the default location: C:\T32\config.t32. + For arm11 processors copy the trace32 configuration file for non-ARM11 processor (config_arm11.t32) to your C:\T32 folder and specify it in the edit box. + You can modify the config.t32 file to support UDP (User Datagram Protocol) connections by adding the following lines: + PBI=USB + RCL=NETASSIST + PACKLEN=1024 + PORT=20000
+ + + Trace32 Initialization Script	Specify the path to the initialization cmm file. This script will be run in T32 after connecting to T32. You can specify your own scripts for the targets used.
+ + + View messages between Carbide and Trace32	Enable to log communications with Trace32 to the console window.

Define Debugger Tab Settings

Figure 4 - Debug Window - Debugger tab

Table 3 - 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.
Target Processor	A drop down with a list of all supported processors. The process selection should help in determining the memory model. This will in turn help determine the base address and the offsets for the Symbian OS kernel aware information.
+ + + + Target Initialization File	Check this box to have the debugger run an initialization script when the debug session starts. For example, if a target device requires initialization for the debugger to be able to read and write memory or registers, you can specify an initialization script here. Click Browse to select a script file using a standard file selection dialog box. + When using T32, most of the initialization is done in the CMM script file. With other debug protocols you specify the initialization file, which can be run after connecting to the target.
+ + + + Memory Configuration File	Controls whether the debugger uses a memory configuration file when a debug session starts. The Carbide debugger uses this configuration file to know which memory is accessible, readable, and writable on the target.
+ + + + Reset target at the start of each debug session	Forces the Carbide IDE to reset the target at the start of each debug session. This ensures that the debugging session uses the most up-to-date program code.
Default Instructon Set	Specifies the default instruction set to use if the debugger cannot determine the processor mode in order to set breakpoints and to disassemble code. This can happen at addresses for which we have no symbolic information. The debugger uses the mode when setting breakpoints and disassembling code. The options are: + + Auto (examine code at current PC location) + ARM (32-bit) + THUMB (16-bit) + + By default the Instruction Set option uses ARM 32-bit.

Define ROM Image Tab

Figure 5 - Debug Window - ROM Image Tab

Table 4 - ROM Image pane

Item	Explanation
+ + + + + Start Address	Enter the physical address in memory where the Symbian OS start code begins execution. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x8000000 is a valid entry. + NOTE The address entered in this field must match the start address specified in the source code used to build the Symbian OS ROM image to be debugged. The Start address must match the Download address.
+ + + + + Debug from Start address	Select this option to have the debugger halt the program at the address specified in Start Address once the target initialization is done and the OS is downloaded; if the user has chosen to download the OS. You can then step through start-up code or run the target in bare-board mode.
+ + + + + + Run from start address	Select this option to have the debugger start the code at the address specified in Start Address once the target initialization is done. If you have breakpoints set, the debugger stops at the first breakpoint encountered. You can click the Break button to halt the device.
+ + + + + + + Symbian ROM Log file	Check the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images. In the first text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.
+ + + + + + Symbian OS Kit EPOC32 Directory	Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory. + NOTE Always include the epoc32 folder in this path.
+ + + + + + + + Log unresolved modules	Check this box to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session. + NOTE You cannot perform source-level debugging on components that do not include symbolic information.
+ + + + + + + + Debug non-XIP Executables	Check this box to debug a project, or a dynamically loaded module, that is loaded from NAND-Flash or other removable media (MMC, memory stick, etc.) at run time and executed in RAM. Use this option to debug modules that work fine when executed in place as part of the ROM image, but sometimes fail when placed in NAND-Flash or other removable media. + NOTE Selecting this option will affect debugging performance. When the debugger needs to load a module (DLL, EXE, etc.) it will stop the target, read information from it, then restart it.
+ + + + + + + Symbian ROM Image	Controls the logging of communication with Trace32. Enable to log communications with Trace32 to the console window.
+ + + Download Address (hex)	Enter the physical address in memory at which the debugger should place the ROM image. This address is target-specific. The address should be in hexadecimal format with the 0x prefix. For example, 0x000FFF00 is a valid entry. + NOTE The address entered in this field must match the download address specified in the source code used to build the Symbian OS ROM image to be debugged. If you leave this field blank, the debugger does not download the ROM image to the device at the beginning of the debug session. The Download address must match the Start address.
+ + + Ask for download at the start of each debug session	Check this box to have the debugger display a dialog box at the beginning of every debug session that lets you choose whether or not you want the debugger to download the ROM image to the device.

Related Tasks

Stop Mode On-Device Debugging Preconditions

+ + + + + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm Tue Jan 26 12:02:08 2010 -0600 @@ -16,7 +16,7 @@

Install the GCCE or RVCT 2.2 or greater compiler (not included with Carbide.c++).

Install the TechView Devkit

Install Board Support Package (BSP) for your target board

Install JTAG software and drivers for Trace32 or Sophia I/F tool support

Install JTAG software and drivers for Trace32 support

Connect JTAG interface between PC and hardware

Verify that your SDK or customer kit is recognized in the SDK preferences panel.

Build your ROM Image

@@ -25,8 +25,7 @@

Related Tasks

- + diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Tue Jan 26 12:02:08 2010 -0600 @@ -18,15 +18,14 @@

NOTE You cannot debug ROM DLLs using Application TRK.

In Sophia or Trace32 you must specify the ROM log file in the ROM Image tab of the Trace32 or Sophia launch configuration
In Trace32 you must specify the ROM log file in the ROM Image tab of the Trace32 launch configuration

Other references

- + \ No newline at end of file diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/index.xml --- a/core/com.nokia.carbide.cpp.doc.user/index.xml Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/index.xml Tue Jan 26 12:02:08 2010 -0600 @@ -601,10 +601,6 @@ - - - - diff -r b794e25ca74a -r e90ca1752642 core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml --- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Mon Jan 25 10:46:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Jan 26 12:02:08 2010 -0600 @@ -155,7 +155,6 @@ - @@ -306,15 +305,6 @@ - - - - - - - - -