# HG changeset patch # User fturovic # Date 1268177504 21600 # Node ID c4cdf14b6868b6c4c6c03f363369f4b253d5281d # Parent 328f2d956cbea89c25b1771d5c0bdb3515d75300 BUG 10841/10842 revised TOC and Run mode example for PnP diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/cmds_starting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/cmds_starting.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/debug/cmds_starting.htm Tue Mar 09 17:31:44 2010 -0600 @@ -17,7 +17,7 @@

Starting a session

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

-

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

+

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

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

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

+

When the view is closed or another perspective opened, a small display appears in the trim area in the lower-right corner of the workspace showing the current active remote connection. Click the connection name to open the drop-down menu where you can open the Remote Connections view or switch between connections.

+

+

Figure 2. Available remote connection trim indicator

Remote Connections view toolbar icons

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

diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_install_tab.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_install_tab.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_install_tab.htm Tue Mar 09 17:31:44 2010 -0600 @@ -1,46 +1,46 @@ - - - - - - -Install Remote Agents pane - - - - -

Install Remote Agents pane

-

Use the Install remote agents pane to select the latest remote agent version to download and install to the device.

-

-

Figure 2 - New Connection wizard Install remote agents page

-

Table 1. Install Remote Agents pane

-
- - - - - - - - - - - - - - - - -
ItemExplanation
Install remote agents

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

-

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

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

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

-

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

-

-
Related references
- - - - + + + + + + +Install Remote Agents pane + + + + +

Install Remote Agents pane

+

Use the Install remote agents pane to select the latest remote agent version to download and install to the device.

+

+

Figure 2 - New Connection wizard Install remote agents page

+

Table 1. Install Remote Agents pane

+ + + + + + + + + + + + + + + + + +
ItemExplanation
Install remote agents

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

+

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

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

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

+

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

+

+
Related references
+ + + + diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingProjectsToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingProjectsToc.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingProjectsToc.htm Tue Mar 09 17:31:44 2010 -0600 @@ -1,18 +1,18 @@ - -Creating Projects - - - -

Creating Projects

-

The topics include:

- - - - - + +Creating Projects + + + +

Creating Projects

+

The topics include:

+ + + + + \ No newline at end of file diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm Tue Mar 09 17:31:44 2010 -0600 @@ -9,59 +9,26 @@

Run Mode On-Device Debugging

-

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

+

Run mode on-device debugging enables you to download and launch a project on a phone or target device and debug it using the Carbide debugger. Before you can do that, some setup requirements are required. Once the setup is done, Carbide can then use plug-and-play (PnP) with USB to create a remote connection that connects with the TRK agent on the target device to download, launch, and debug the program.

    -
  1. Install device connection software
    2. -
  2. Install Perl
    3. -
  3. Install an SDK
    4. -
  4. Setup environment variables
    5. -
  5. Setup a virtual drive for Techview and Cust Kits
    6. -
  6. Set the default kit in Devices.xml
    7. -
  7. Install the SISX file on the target device
    8. -
  8. Configure TRK connection on the device
    9. -
  9. Create a launch configuration
    10. +
  10. Setup system and development requirements (below)
    11. +
  11. Install Application or System TRK v3.2.6 or later on the target device
    12. +
  12. Connect USB cable to phone or target device for PnP connectivity
    13. +
  13. Create or import a project in the Carbide C/C++ workspace
    14. +
  14. Build the project
    15. +
  15. Debug the project on a phone or target device
-

Install Device Connection Software

-

The two choices for connecting are Bluetooth and PC Suite.

-
BlueTooth
-
    -
  1. System requirements:
    2. +

    Setup system and development requirements

    +

    All of the following requirements are required to build, communicate, and control programs on a phone or target device.

      -
    • Administration rights on your computer
      • -
    • BT dongle attached to your computer
      • -
    • Bluetooth installer to install the drivers
      • +
    • Install PC Suite or Ovi Suite on your PC to ensure the correct drivers are installed for connecting to the phone or target device.
      • +
    • Install the correct version of Perl on your PC to support Symbian OS builds
      • +
    • Install a supported SDK and make sure its the default
      • +
    • Configure the environmental variables
      • +
    • (Optional) Setup a virtual drive to use Techview and Cust Kits
    -
  2. Install the Bluetooth dongle to a USB port
    3. -
  3. Install the drivers from the Bluetooth CD
    4. -
  4. Click on the Bluetooth icon in your system tray and run the Bluetooth setup
    5. -
  5. Right click on the Bluetooth icon in the System tray and select Advanced Configuration
    6. -
  6. Click the Accessibility tab -
      -
    1. Check the option “Let other Bluetooth devices discover this computer”
      2. -
    2. Set the option under “Allow” to “All Devices”
      3. -
    -
    7. -
-

NOTE The Nokia PC image includes the Microsoft Bluetooth drivers which do not support serial emulation over Bluetooth. You need to download and install the drivers provided by the Bluetooth manufacturer to connect to a device.

-
Nokia PC Suite
-
    -
  1. Install PC Suite (or later version) -

    Launch the PC Suite installer and follow the onscreen instructions to install the software. When finished, a Get Connected wizard should appear

    -
    2. -
  2. Press Next
    3. -
  3. In the "Select your connection type" window select "Cable Connection" and press Next
    4. -
  4. You will be prompted to connect the phone via the USB cable
    5. -
  5. Connect the phone and continue with onscreen instructions
    6. -
  6. After installation your phone should be listed
    7. -
  7. Click Finish
    8. -
  8. Select PC suite on your phone
    9. -

    The Nokia PC Suite window should appear

    -
  9. Select the Manage Connections icon
    10. -
  10. Uncheck all the connections available
    11. -
  11. Click Ok
    12. -

    PC Suite is now ready to use.

    -
+

Once you've setup your environment, its time to verify that the TRK agent is on the phone or target device.

diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm Tue Mar 09 17:31:44 2010 -0600 @@ -1,37 +1,30 @@ - - - - - - -Debugger Settings - - - -

Run Mode On-Device Debugging

-

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

-
    -
  1. Install device connection software
    2. -
  2. Install Perl
    3. -
  3. Install an SDK
    4. -
  4. Setup environment variables
    5. -
  5. Setup a virtual drive for Techview and Cust Kits
    6. -
  6. Set the default kit in Devices.xml
    7. -
  7. Install the SISX file on the target device
    8. -
  8. Configure TRK connection on the device
    9. -
  9. Create a launch configuration
    10. -
-
-

Install PERL

- -
-

Software can be downloaded from: http://www.activestate.com/Products/ActivePerl/.

-

NOTE Later releases of Perl are not yet supported by the Symbian utilities and can cause unknown compiling errors.

-
-
- - - - + + + + + + +Installing PERL + + + +

Installing PERL

+

PERL is required for many Symbian OS utilities and commands.

+
+

Installing PERL

+ +
+

Software can be downloaded from: http://www.activestate.com/Products/ActivePerl/.

+

NOTE Later releases of Perl are not yet supported by the Symbian utilities and can cause unknown compiling errors.

+
+
+
Other references
+ + + + + diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Tue Mar 09 17:31:44 2010 -0600 @@ -4,41 +4,58 @@ -Debugger Settings +Installing an SDK -

Run Mode On-Device Debugging

-

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

-
    -
  1. Install device connection software
    2. -
  2. Install Perl
    3. -
  3. Install an SDK
    4. -
  4. Setup environment variables
    5. -
  5. Setup a virtual drive for Techview and Cust Kits
    6. -
  6. Set the default kit in Devices.xml
    7. -
  7. Install the SISX file on the target device
    8. -
  8. Configure TRK connection on the device
    9. -
  9. Create a launch configuration
    10. -
+

Installing an SDK

+

To create projects an SDK must be installed. If more than one SDK is installed one must be specified as the default.

-

Install an SDK

-

The following SDKs can be downloaded from forum Nokia at: http://www.forum.nokia.com/.

-
+ +
Other references
- - - - + diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_03.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_03.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_03.htm Tue Mar 09 17:31:44 2010 -0600 @@ -1,56 +1,49 @@ - - - - - - -Debugger Settings - - - -

Run Mode On-Device Debugging

-

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

-
    -
  1. Install device connection software
    2. -
  2. Install Perl
    3. -
  3. Install an SDK
    4. -
  4. Setup environment variables
    5. -
  5. Setup a virtual drive for Techview and Cust Kits
    6. -
  6. Set the default kit in Devices.xml
    7. -
  7. Install the SISX file on the target device
    8. -
  8. Configure TRK connection on the device
    9. -
  9. Create a launch configuration
    10. -
-
-

Setup Environment Variables

-
    -
  1. Set EPOCROOT variable -
      -
    1. Right click on My Computer and select Properties
      2. -
    2. Select the Advanced tab
      3. -
    3. Select the Environmental Variables button
      4. -
    4. Setup a new System variable called EPOCROOT. The value will depend on the path of the epoc32 folder in the kit, for example:
      5. -

      Variable name: EPOCROOT
      - Variable value: \bin\techview\

      -
    -
    2. -

    NOTE Take note of the location of the epoc32 folder when using multiple kits. Some kits place the epoc32 folder at \bin\techview\ and some kits will place it at the root. If you have multiple installations and switch to a new kit, you will need to change the EPOCROOT path; otherwise build problems may occur. When building the ROM image, scripts may complain about the EPOCROOT path or that it can’t find bldmake.bat if an incorrect EPOCROOT path is set.

    -
  2. Set Path to Tools Directory -
      -
    1. If using an installer the tools path is set up automatically and points to:
      2. - Variable: PATH
      - Value: C:\Program Files\Common Files\Symbian\Tools -
    2. If installing from zip files you will need to setup the tools path manually. Add the path to the beginning of the PATH variable:
      3. - Variable: PATH
      - Variable Value: \epoc32\tools;\epoc32\gcc\bin; -
    3. If using multiple kits that use a mix of installer and zip files then you can set up your PATH variable like this:
      4. - Variable: PATH
      - Value: \epoc32\tools;\epoc32\gcc\bin;C:\Program Files\Common Files\Symbian\Tools -
    -
    3. -
-
- - - - + + + + + + +Configuring Environment Variables + + + +

Configuring Environment Variables

+

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

+
+

Configuring Environment Variables

+
    +
  1. Set EPOCROOT variable +
      +
    1. Right click on My Computer and select Properties
      2. +
    2. Select the Advanced tab
      3. +
    3. Select the Environmental Variables button
      4. +
    4. Setup a new System variable called EPOCROOT. The value will depend on the path of the epoc32 folder in the kit, for example:
      5. +

      Variable name: EPOCROOT
      + Variable value: \bin\techview\

      +
    +
    2. +

    NOTE Take note of the location of the epoc32 folder when using multiple kits. Some kits place the epoc32 folder at \bin\techview\ and some kits will place it at the root. If you have multiple installations and switch to a new kit, you will need to change the EPOCROOT path; otherwise build problems may occur. When building the ROM image, scripts may complain about the EPOCROOT path or that it can’t find bldmake.bat if an incorrect EPOCROOT path is set.

    +
  2. Set Path to Tools Directory +
      +
    1. If using an installer the tools path is set up automatically and points to:
      2. + Variable: PATH
      + Value: C:\Program Files\Common Files\Symbian\Tools +
    2. If installing from zip files you will need to setup the tools path manually. Add the path to the beginning of the PATH variable:
      3. + Variable: PATH
      + Variable Value: \epoc32\tools;\epoc32\gcc\bin; +
    3. If using multiple kits that use a mix of installer and zip files then you can set up your PATH variable like this:
      4. + Variable: PATH
      + Value: \epoc32\tools;\epoc32\gcc\bin;C:\Program Files\Common Files\Symbian\Tools +
    +
    3. +
+
+
Other references
+ + + + + diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_04.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_04.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_04.htm Tue Mar 09 17:31:44 2010 -0600 @@ -1,43 +1,35 @@ - - - - - - -Debugger Settings - - - -

Run Mode On-Device Debugging

-

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

-
    -
  1. Install device connection software
    2. -
  2. Install Perl
    3. -
  3. Install an SDK
    4. -
  4. Setup environment variables
    5. -
  5. Setup a virtual drive for Techview and Cust Kits
    6. -
  6. Set the default kit in Devices.xml
    7. -
  7. Install the SISX file on the target device
    8. -
  8. Configure TRK connection on the device
    9. -
  9. Create a launch configuration
    10. -
-
-

Setup a Virtual Drive for Techview and Cust Kits

-

Techvew Kits and cust kits have kernel components, kernel extensions and device drivers that are typically built on a virtual drive. So if you want to debug them the debugger will need to load files from the virtual drive that the binaries were built on. If you do not know the virtual drive the kit was built on you should first pick a drive letter randomly.

-
    -
  1. To subst a drive, type on a command line:
    - > subst drive_letter: path_to_kit
    -     For example:
    -> subst M: C:\Symbian\S60_3_0_200626
    2. -
  2. On the command line type:
    ->subst
    -

    You should see the new virtual drive pointing to your kit. If the debugger tries to load a file it can’t find, it will look for it on the virtual drive. You can see this in the stack crawl. The stack crawl should give the full path of the file on the virtual drive the file was built on. The debugger will not be able to load the file until the correct virtual drive is specified.

    -

    If this happens you can redo the virtual drive to use the drive specified in the stack crawl or navigate to the file using the existing virtual drive. From that point the IDE will add that path and recursively check folders for files it needs.

    -
    3. -
  3. Make sure when you set up your default SDK in the Carbide IDE that you use the virtual drive.
    4. -
-
- - - - + + + + + + +Setup a Virtual Drive for Techview and Cust Kits + + + +

Setup a Virtual Drive for Techview and Cust Kits (optional)

+

Techview Kits and cust kits have kernel components, kernel extensions and device drivers that are typically built on a virtual drive. So if you want to debug them the debugger will need to load files from the virtual drive that the binaries were built on. If you do not know the virtual drive the kit was built on you should first pick a drive letter randomly.

+
+

Setup a Virtual Drive for Techview and Cust Kits

+
    +
  1. To subst a drive, type on a command line:
    + > subst drive_letter: path_to_kit
    +     For example:
    +> subst M: C:\Symbian\S60_3_0_200626
    2. +
  2. On the command line type:
    +>subst
    +

    You should see the new virtual drive pointing to your kit. If the debugger tries to load a file it can’t find, it will look for it on the virtual drive. You can see this in the stack crawl. The stack crawl should give the full path of the file on the virtual drive the file was built on. The debugger will not be able to load the file until the correct virtual drive is specified.

    +

    If this happens you can redo the virtual drive to use the drive specified in the stack crawl or navigate to the file using the existing virtual drive. From that point the IDE will add that path and recursively check folders for files it needs.

    +
    3. +
  3. Make sure when you set up your default SDK in the Carbide IDE that you use the virtual drive.
    4. +
+
+
Other references
+ + + + + diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_05.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_05.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_05.htm Tue Mar 09 17:31:44 2010 -0600 @@ -1,43 +1,43 @@ - - - - - - -Debugger Settings - - - -

Run Mode On-Device Debugging

-

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

-
    -
  1. Install device connection software
    2. -
  2. Install Perl
    3. -
  3. Install an SDK
    4. -
  4. Setup environment variables
    5. -
  5. Setup a virtual drive for Techview and Cust Kits
    6. -
  6. Set the default kit in Devices.xml
    7. -
  7. Install the SISX file on the target device
    8. -
  8. Configure TRK connection on the device
    9. -
  9. Create a launch configuration
    10. -
-
-

Set the Default Kit in Devices.xml

-

The Symbian environment needs to know the kit you are using. This is needed since you may have multiple kits installed. You can specify the development kit by setting a default in the file called devices.xml located in the C:\Program Files\Common Files\Symbian folder.

-
From the command line
-
    -
  1. Set the default device devkit by typing on the command line:
    -> devices –setdefault @device id: name
    2. - -

    The device id and name can be found in the devices.xml file. For example, for a Techview 9.2 kit you might type
    - > devices –setdefault @ SymbianOS_92_2006_wk40:com.symbian.techview

    - -
  2. Now ensure the default device is set by entering:
    -> devices
    3. -
  3. Make sure the correct default is set.
    4. -
-
- - - - + + + + + + +Run Mode On-Device Debugging + + + +

Run Mode On-Device Debugging

+

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

+
    +
  1. Install device connection software
    2. +
  2. Install Perl
    3. +
  3. Install an SDK
    4. +
  4. Setup environment variables
    5. +
  5. Setup a virtual drive for Techview and Cust Kits
    6. +
  6. Set the default kit in Devices.xml
    7. +
  7. Install the SISX file on the target device
    8. +
  8. Configure TRK connection on the device
    9. +
  9. Create a launch configuration
    10. +
+
+

Set the Default Kit in Devices.xml

+

The Symbian environment needs to know the kit you are using. This is needed since you may have multiple kits installed. You can specify the development kit by setting a default in the file called devices.xml located in the C:\Program Files\Common Files\Symbian folder.

+
From the command line
+
    +
  1. Set the default device devkit by typing on the command line:
    +> devices –setdefault @device id: name
    2. + +

    The device id and name can be found in the devices.xml file. For example, for a Techview 9.2 kit you might type
    + > devices –setdefault @ SymbianOS_92_2006_wk40:com.symbian.techview

    + +
  2. Now ensure the default device is set by entering:
    +> devices
    3. +
  3. Make sure the correct default is set.
    4. +
+
+ + + + diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_06.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_06.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_06.htm Tue Mar 09 17:31:44 2010 -0600 @@ -1,70 +1,70 @@ - - - - - - -Debugger Settings - - - -

Run Mode On-Device Debugging

-

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

-
    -
  1. Install device connection software
    2. -
  2. Install Perl
    3. -
  3. Install an SDK
    4. -
  4. Setup environment variables
    5. -
  5. Setup a virtual drive for Techview and Cust Kits
    6. -
  6. Set the default kit in Devices.xml
    7. -
  7. Install the SISX file on the target device
    8. -
  8. Configure TRK connection on the device
    9. -
  9. Create a launch configuration
    10. -
-
-

Install the SISX File on the Target Device

-

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

- -

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

-
Installing using Bluetooth
-
    -
  1. Right click on the Bluetooth item on the system tray and select Quick Connect > File Transfer > Find Devices
    2. -
  2. Refresh the File Transfer window to allow the device to detect all the Bluetooth devices
    3. -
  3. From the list select your device and click Open
    4. -
  4. You should enable the My Bluetooth Places window popup option that creates a connection shortcut “MyDeviceOBEX File Transfer” in the My Bluetooth Places folder.
    5. -
  5. The Obex File Transfer window for your devices should open from within the My Bluetooth Folder
    6. -
  6. You will be prompted to enter a Bluetooth PIN code. Enter any number.
    7. -
  7. On the device you will be prompted to enter the same PIN code. Enter PIN code.
    8. -
  8. The device will then ask you to accept the connection request from the PC. Press OK.
    9. -

    The OBEX folder on the PC should now be available.

    -
  9. Drop the TRK SISX file into the folder
    10. -
  10. The device will prompt you to accept the connection request from the PC. Press OK.
    11. -
  11. The SISX file should then transfer from the PC to the device
    12. -
  12. Navigate to where the SISX file was placed
    13. -

    If you dropped it into the OBEX folder it will be in Applications > Messages > Inbox. If you dropped it into the C folder it will be in Applications > Utilities >FileBrowse > C.

    -
  13. Select the TRK SISX file on the device to install the TRK debug agent.
    14. -
-
Installing using PC Suite
-
    -
  1. Place the SISX file on your PC
    2. -
  2. Connect the USB cable to the phone
    3. -
  3. On the device it will display USB mode:
    - PC Suite
    - File transfer
    4. -
  4. Select PC Suite and the device will connect to the PC
    5. -
  5. Open PC suite. In the bottom left a status display should indicate “Series 60 Device connected via USB”.
    6. -
  6. Double click “Install applications”. The Nokia Application Installer wizard will appear.
    7. -
  7. On the left you should see My Computer and on the right My Phone
    8. -
  8. From My Computer select the SISX file on your PC
    9. -
  9. From My Phone select the “Phone memory” drop down list an select where you want to install the file.
    10. -
  10. Select the green arrow pointing from My Computer to My Device. The SISX file should then be transferred to the device and installed.
    11. -
-
- - - - + + + + + + +Run Mode On-Device Debugging + + + +

Run Mode On-Device Debugging

+

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

+
    +
  1. Install device connection software
    2. +
  2. Install Perl
    3. +
  3. Install an SDK
    4. +
  4. Setup environment variables
    5. +
  5. Setup a virtual drive for Techview and Cust Kits
    6. +
  6. Set the default kit in Devices.xml
    7. +
  7. Install the SISX file on the target device
    8. +
  8. Configure TRK connection on the device
    9. +
  9. Create a launch configuration
    10. +
+
+

Install the SISX File on the Target Device

+

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

+ +

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

+
Installing using Bluetooth
+
    +
  1. Right click on the Bluetooth item on the system tray and select Quick Connect > File Transfer > Find Devices
    2. +
  2. Refresh the File Transfer window to allow the device to detect all the Bluetooth devices
    3. +
  3. From the list select your device and click Open
    4. +
  4. You should enable the My Bluetooth Places window popup option that creates a connection shortcut “MyDeviceOBEX File Transfer” in the My Bluetooth Places folder.
    5. +
  5. The Obex File Transfer window for your devices should open from within the My Bluetooth Folder
    6. +
  6. You will be prompted to enter a Bluetooth PIN code. Enter any number.
    7. +
  7. On the device you will be prompted to enter the same PIN code. Enter PIN code.
    8. +
  8. The device will then ask you to accept the connection request from the PC. Press OK.
    9. +

    The OBEX folder on the PC should now be available.

    +
  9. Drop the TRK SISX file into the folder
    10. +
  10. The device will prompt you to accept the connection request from the PC. Press OK.
    11. +
  11. The SISX file should then transfer from the PC to the device
    12. +
  12. Navigate to where the SISX file was placed
    13. +

    If you dropped it into the OBEX folder it will be in Applications > Messages > Inbox. If you dropped it into the C folder it will be in Applications > Utilities >FileBrowse > C.

    +
  13. Select the TRK SISX file on the device to install the TRK debug agent.
    14. +
+
Installing using PC Suite
+
    +
  1. Place the SISX file on your PC
    2. +
  2. Connect the USB cable to the phone
    3. +
  3. On the device it will display USB mode:
    + PC Suite
    + File transfer
    4. +
  4. Select PC Suite and the device will connect to the PC
    5. +
  5. Open PC suite. In the bottom left a status display should indicate “Series 60 Device connected via USB”.
    6. +
  6. Double click “Install applications”. The Nokia Application Installer wizard will appear.
    7. +
  7. On the left you should see My Computer and on the right My Phone
    8. +
  8. From My Computer select the SISX file on your PC
    9. +
  9. From My Phone select the “Phone memory” drop down list an select where you want to install the file.
    10. +
  10. Select the green arrow pointing from My Computer to My Device. The SISX file should then be transferred to the device and installed.
    11. +
+
+ + + + diff -r 328f2d956cbe -r c4cdf14b6868 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 Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_07.htm Tue Mar 09 17:31:44 2010 -0600 @@ -4,7 +4,7 @@ -Debugger Settings +Run Mode On-Device Debugging @@ -70,7 +70,7 @@ - + diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Tue Mar 09 17:31:44 2010 -0600 @@ -4,7 +4,7 @@ -Debugger Settings +Run Mode On-Device Debugging @@ -181,7 +181,7 @@

Figure 9. Debug windows File Transfer pane

- + diff -r 328f2d956cbe -r c4cdf14b6868 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 Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Tue Mar 09 17:31:44 2010 -0600 @@ -43,11 +43,7 @@ -
Related tasks
- - + diff -r 328f2d956cbe -r c4cdf14b6868 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 Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm Tue Mar 09 17:31:44 2010 -0600 @@ -14,42 +14,28 @@
  • DKU-2
  • CA-53
    • +

    Carbide uses plug-and-play (PnP) to create a remote connection for the phone or target device once it's plugged in. Once a remote connection is created the Remote Connections view appears in Carbide. In addition, the current available connection is shown in the workspace's lower-right trim area.

    +

    +

    Figure 1. Current available connection shown in workspace trim area

    +

    NOTE PC Suite or Ovi Suite must be installed on your PC for the following steps to work.

    Setting up a USB Connection for On-device Debugging

      -
    1. Install the latest USB connectivity software, for example, S60 devices use Nokia PC Suite
      2. -
    2. Connect the USB connectivity cable to your PC and then the target device
      3. -
    3. For S60 devices, select PC-Suite from the USB Mode list when the target device is connected
      4. -
    4. Download the Application TRK or System TRK SISX file to the device
      5. -
    5. On the PC - (optional)
      6. -
    -
      -
        -
      1. Open the Windows Computer Management (Windows XP)
        2. -

        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.

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

        -

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

        -
      3. The USB COM Port number should match the COM port used in the Connections tab of the TRK launch - configuration.
        4. -
      4. Close the Device Manager window
        5. -
      +
    1. Connect the USB connectivity cable to your PC and then the phone or target device
      2. +
    2. On the phone or target device, select PC-Suite from the USB Mode options when asked
      3. +
    3. In Carbide.c++, verify the current available connection is shown in the Remote Connections view or the indicator in the trim area
    Related concepts
    Related references
    -
    Related tasks
    - - + diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm Tue Mar 09 17:31:44 2010 -0600 @@ -9,13 +9,14 @@

    Installing an On-device Debug Agent

    -

    To use any version of the on-device debug agent on a target device it must be installed. We highly recommend using the On-Device Connections dialog to help connect and verify that the latest version of TRK is installed on the device. Or, to manage this manually, follow the instructions to install the TRK debug agent software using Bluetooth or USB.

    +

    To use any version of the on-device debug agent on a target device it must be installed. We highly recommend using the On-Device Connections dialog to help connect and verify that the latest version of TRK (3.2.6+) is installed on the device, especially to support plug-and-play (PnP) connections.

    +

    Refer to the Bluetooth Connection Setup page for more information on using Bluetooth or the USB Connection Setup page if using USB.

    Related references
    - + diff -r 328f2d956cbe -r c4cdf14b6868 core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml --- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Mar 09 10:34:04 2010 -0600 +++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Mar 09 17:31:44 2010 -0600 @@ -9,13 +9,12 @@ - - - - - - - + + + + + + @@ -224,7 +223,6 @@ - @@ -234,13 +232,19 @@ - - + + + + + + + + @@ -248,7 +252,8 @@ - + + @@ -256,7 +261,8 @@ - + + @@ -265,17 +271,19 @@ + + - + - + - - + + @@ -287,7 +295,7 @@ - + @@ -337,7 +345,6 @@ -