# HG changeset patch # User fturovic # Date 1285872835 18000 # Node ID bbb6c7da6e3fdd990bf98766cb24ddd50f240afc # Parent 593dde21e8745c44f164412eb53258e1dfa3f4df BUG 12110 - more TRK references removed in text and images diff -r 593dde21e874 -r bbb6c7da6e3f core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_remote_connections.png Binary file core/com.nokia.carbide.cpp.doc.user/html/reference/images/view_remote_connections.png has changed diff -r 593dde21e874 -r bbb6c7da6e3f core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm Thu Sep 30 11:33:17 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm Thu Sep 30 13:53:55 2010 -0500 @@ -30,7 +30,7 @@
Related references
diff -r 593dde21e874 -r bbb6c7da6e3f core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm Thu Sep 30 11:33:17 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm Thu Sep 30 13:53:55 2010 -0500 @@ -32,7 +32,7 @@
  • Status - current connection status, i.e. Available, Not Accessible, Ready, etc.
  • Description - provides information on the current connection test status.
  • -

    +

    Figure 1 - Remote Connections view

    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.

    diff -r 593dde21e874 -r bbb6c7da6e3f 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 Thu Sep 30 11:33:17 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_install_tab.htm Thu Sep 30 13:53:55 2010 -0500 @@ -11,7 +11,7 @@

    Install Remote Agents

    -

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

    +

    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

    diff -r 593dde21e874 -r bbb6c7da6e3f 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 Thu Sep 30 11:33:17 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_07.htm Thu Sep 30 13:53:55 2010 -0500 @@ -18,58 +18,29 @@
  • 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
  • +
  • Configure CODA connection on the device
  • Create a launch configuration
  • Configure CODA Connection on the Device

    -
    Connecting with Bluetooth
    -
      -
    1. On the device make sure the Bluetooth port is turned on
    2. -
    3. On the phone launch CODA.
    4. -

      The location of CODA (Carbide 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.

      -
    5. CODA will ask which host you want to pair with. When requested, select your computer from the available Bluetooth devices list.
    6. -
    7. After the host and phone are paired, CODA should be connected. Verify that CODA is running.
    8. -
    9. On the PC: -
        -
      1. Right click on the Bluetooth icon in the System tray and select Advanced Configuration
      2. -
      3. Click the Local Services tab
      4. -
      5. Write down the Bluetooth COM Port number from the Local Services tab (Figure 1).
      6. -

        The Port number will be used when configuring the CODA launch configuration. The Bluetooth COM Port number in the Local Services tab should match the COM port used in the Connections tab of the CODA launch configuration.

        -
      7. Click OK to close the Bluetooth Configuration window
      8. -

        -

        Figure 1. Bluetooth Configuration windows Local Services panel

        -
      -
    10. -
    -
    Connecting with PC Suite
    +
    Connecting with Nokia Ovi/PC Suite
      +
    1. Verify Nokia Ovi/PC Suite are installed on the PC (drivers are required by Carbide)
    2. Connect the USB cable to the PC and then to the target device
    3. -
    4. On the device select PC suite from the USB mode list
    5. -
    6. Launch the CODA agent
    7. -

      The location of the CODA on-device debug agent will vary based on the phone. On some phones it will be in the Installed folder, on others it may be in My Own folder.

      -
    8. Halt the Bluetooth device search by pressing Cancel
    9. +
    10. On the device select PC Suite from the USB mode list
    11. +
    12. On the device launch the CODA agent
    13. +

      The location of the CODA on-device debug agent will vary based on the phone. On some phones it will be in the Installed, Applications, or My Own folder.

    14. Click Options > Settings > Connection
    15. -
    16. Change Connection type to USB and set connection options (Figure 2)
    17. +
    18. Change Connection type to USB and set connection options
    19. +

      CODA options

    20. Select Back and start the CODA software again and you should be connected
    21. -

      -

      Figure 2. USB Connection Settings

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

        -

        Figure 3. Device Manager - Ports

        - -
      7. Write down the port ID and Communication Port Properties.
      8. -

        The COM Port number in the Device Manager window should match the COM port used in the Connections tab of the CODA launch configuration.

        -
      9. Close the Device Manager window
      10. +
      11. On the PC verify connection in Remote Connections view
        +

        Remote Connections view

        +
      -
    -
    +

    With the remote device connected you are ready to start debugging.

    + diff -r 593dde21e874 -r bbb6c7da6e3f 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 Thu Sep 30 11:33:17 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_08.htm Thu Sep 30 13:53:55 2010 -0500 @@ -18,7 +18,7 @@
  • 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
  • +
  • Configure CODA connection on the device
  • Create a launch configuration
  • @@ -30,8 +30,8 @@
  • 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 Device (Install SIS) or Symbian OS Device configuration type for on-device debugging and click New
  • +

    Figure 4. Debug window

    +
  • Select either a Symbian Device (Install SIS) or Symbian Device configuration type for on-device debugging and click New
  • For debug launch configurations using the CODA debug agent, the following pages require review and possible option settings:

    diff -r 593dde21e874 -r bbb6c7da6e3f core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Thu Sep 30 11:33:17 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Thu Sep 30 13:53:55 2010 -0500 @@ -9,23 +9,23 @@

    Preconditions to On-Device Debugging

    -

    Before you can use on-device debugging to debug 3rd and 5th edition devices, the following preconditions must be met.

    +

    Before you can use on-device debugging to debug 5th edition devices, the following preconditions must be met.

    Verifying On-device Debugging Preconditions

    1. Verify that your system has the following:
      • A current Symbian OS SDK is installed
      • -
      • Perl installed
      • +
      • Perl is installed
      • RVCT or GCCE compiler
      • -
      • USB or Bluetooth support on your PC
      • +
      • USB support on your PC
      • Nokia Ovi/PC Suite (or equivilent software) for connecting and installing applications to the device
    2. Download and install the current CODA SISX file using the On-Device Connections dialog
    3. If CODA is not install, use the On-Device Connections > New Connection Wizard > Install remote agents pane.

    4. Specify the communication method with the on-target device during the debug session
    5. -

      Start CODA on the device. During startup of CODA on the device you must specify the communication method the on-device agent uses to debug the device. Currently, those methods include Bluetooth and USB or a null serial cable. For Bluetooth, you must pair the device with the PC and a valid serial port assigned. For USB, A USB cable must connect the PC to the device and a valid serial port assigned. Use On-Device Connections dialog to make the identification and connection setup quick and easy.

      +

      Start CODA on the device. During startup of CODA on the device you must specify the communication method the on-device agent uses to debug the device. Currently, those methods include USB or a null serial cable. For USB, A USB cable must connect the PC to the device and a valid serial port assigned. Use On-Device Connections dialog to make the identification and connection setup quick and easy.

    Related concepts
    @@ -36,12 +36,10 @@
    Related reference
    Related tasks
    -