# HG changeset patch # User fturovic # Date 1245682230 18000 # Node ID 9abb752d5c0a8b122d99b2d1804b114657d87e20 # Parent 96bd14e3e8e22d58f4505c938b17cf82c2b0fe59 Updated New Launch Config and Launch Config Main pages diff -r 96bd14e3e8e2 -r 9abb752d5c0a core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/page_debug_main.png Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/page_debug_main.png has changed diff -r 96bd14e3e8e2 -r 9abb752d5c0a core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/page_main_run_mode.png Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/page_main_run_mode.png has changed diff -r 96bd14e3e8e2 -r 9abb752d5c0a core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/page_main_stop_mode.png Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/page_main_stop_mode.png has changed diff -r 96bd14e3e8e2 -r 9abb752d5c0a core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/wiz_launch_config_build_options.png Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/wiz_launch_config_build_options.png has changed diff -r 96bd14e3e8e2 -r 9abb752d5c0a 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 Jun 22 09:41:33 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Mon Jun 22 09:50:30 2009 -0500 @@ -1,99 +1,117 @@ - - - - - - -Carbide Main page - - - -

Main page

-

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

- -

Emulation Main page

-

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

-

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

-

-

Figure 1. Main page (Emulation shown)

-
Table 1. Emulator Main page —items
- - - - - - - - - - - - - -
ItemExplanation
Project

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

Process to launch The path to the emulator or executable to launch. For Symbian OS 9.1 the emulator path is required. For Symbian OS 9.2 and later the path to the executable should be used. Click Browse to select a different emulator.
- -

Run-mode Main page

-

The Symbian OS Application TRK launch configuration uses the Main page to defines the project and the process to launch on the target device.

-

-

Figure 2 - Main page (Application TRK shown)

-
Table 2. Run-mode Main page —items
- - - - - - - - - - - - - - - - - -
ItemExplanation
Project

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

Remote process to launch

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

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

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

Use connectionChoose the remote connection type to associate with this launch configuration. Click New to add a new connection, or Edit to modify the current one.
-

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.

-

-

Figure 3. Main page

-
Table 3. Stop-mode Main page — items
- - - - - - - - - - - - - - - - - -
ItemExplanation
ProjectThe project to associate with this debug launch configuration. Click Browse to select a different project.
ExecutableThis is the name of the executable that is linked to the project. Click Browse to select a different executable.
Use connectionChoose the remote connection type to associate with this launch configuration. Click New to add a new connection, or Edit to modify the current one.
-

Other references

- - -
 
- + + + + + + +Carbide Main page + + + +

Main page

+

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

+ +

Emulation Main page

+

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

+

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

+

+

Figure 1. Main page (Emulation shown)

+
Table 1. Emulator Main page —items
+ + + + + + + + + + + + + + + + + +
ItemExplanation
Project

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

Process to launch The path to the emulator or executable to launch. For Symbian OS 9.1 the emulator path is required. For Symbian OS 9.2 and later the path to the executable should be used. Click Browse to select a different emulator.
Build (if required) before launching

Controls how auto build is configured for the launch configuration. Changing this setting overrides the global workspace setting and can provide some speed improvements. The options include:

+
    +
  • Disable auto build – Disables auto build for the launch configuration which may improve launch performance.
    • +
  • Enable auto build – Enables auto build for the launch configuration which can slow down launch performance.
    • +
  • Use workspace settings (default) – Uses the global auto build settings.
    • +
  • Configure Workspace Settings... – Opens the Launching preference panel where you can change the workspace settings.
    • +
+ +

Run-mode Main page

+

The Symbian OS Application TRK launch configuration uses the Main page to defines the project and the process to launch on the target device.

+

+

Figure 2 - Main page (Application TRK shown)

+
Table 2. Run-mode Main page —items
+ + + + + + + + + + + + + + + + + + + + + +
ItemExplanation
Project

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

Remote process to launch

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

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

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

Use connectionChoose the remote connection type to associate with this launch configuration. Click New to add a new connection, or Edit to modify the current one.
Build (if required) before launchingSee Emulation Main page above.
+

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.

+

+

Figure 3. Main page

+
Table 3. Stop-mode Main page — items
+ + + + + + + + + + + + + + + + + + + + + +
ItemExplanation
ProjectThe project to associate with this debug launch configuration. Click Browse to select a different project.
ExecutableThis is the name of the executable that is linked to the project. Click Browse to select a different executable.
Use connectionSee Run-mode Main page above.
Build (if required) before launchingSee Emulation Main page above.
+

Other references

+ + +
 
+ \ No newline at end of file diff -r 96bd14e3e8e2 -r 9abb752d5c0a 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 Jun 22 09:41:33 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Mon Jun 22 09:50:30 2009 -0500 @@ -21,6 +21,7 @@ @@ -59,49 +60,53 @@

Figure 1 - Build Target selection list

Category Types

-

Use the Category Types page to select the the launch category. The choices include Phone, Board, and possibly others. The choice made here filters the Launch Types page to show valid launch configurations. Once a category is selected, click Next.

+

Use the Category Types page to select the the launch category. The choices include Phone, Board, and possibly others. The choice made here filters the Launch Types page to only show valid launch configurations. Once a category is selected, click Next.

Figure 2 - Category Types page

Launch Types

Use the Launch Types page to select the type of launch configuration for the build target. This page does not appear when using an Emulator target. Available types are listed from the most frequently chosen (Application TRK) to the least likely type (Attach to Process). Select a type and click Next.

Figure 3 - Launch Type page

+

Build Options Selection

+

Use the Build Options Selection page to define if the launch configuration uses auto build or not. Choices include using the global auto built setting (default), enable or disable auto build for the launch configuration. You can also set the global option using the Configure Workspace Settings... to open the Launching preference panel.

+

+

Figure 4 - Build Options Selection page

Executable Selection

Use the Application Selection page to choose a binary created by the project to launch and debug and verify its location. If only a single binary is available the Process to launch option is disabled.

EMULATOR ONLY Use the Location field for emulator targets to verify that the correct executable on the host is selected. This field is not used with on-device launch configurations.

Use the Specify device path of remote process to launch option to specify alternate paths for launching the executable from RAM (c:\sys\bin\), ROM (z:\sys\bin\) or memory cards (e:\sys\bin\) .

Select the Executable to launch, verify it is the correct binary, then click Next.

-

Figure 4 - Executable Selection page (when project has multiple EXEs)

+

Figure 5 - Executable Selection page (when project has multiple EXEs)

TRK Connection Settings

Use the TRK Connection Settings page to specify the connection used to communicate with the target device. If the device is already connected, the drop down list will include both the COM port and the name of the device using that port. Use the On-Device Conection dialog to verify and update all Carbide software services on the device. Choose the serial port used to communicate with the target device and click Next.

-

-

Figure 5 - TRK Connection Settings page

+

+

Figure 6 - TRK Connection Settings page

 

TRK SIS Selection

Use the TRK SIS Selection page to select the SIS file to install on the target device. Click the Modify SIS builder settings for build configuration link to open the SIS Builder properties pane to add, edit, or review the SIS files to build. Once the correct SIS File to Install is selected, click Next.

-

Figure 6 - TRK SIS Selection page

+

Figure 7 - TRK SIS Selection page

New Launch Configuration

Use the New Launch Configuration page to note the name of the configuration, confirm the launch configuration settings, and then launch the debug session. If something doesn't look right, click Back to return to a page and change its setting. If all the settings are correct, click Finish to start the debug session using this launch configuration.

If you checkmark Advanced settings, the Debug dialog appears instead of launching the project. This enables you to make additional changes to the new launch configuration before starting the debug session. By design and intent, this should seldom be required for the initial launch.

-

Figure 7 - New Launch Configuration page

+

Figure 8 - New Launch Configuration page

Trace32 Initialization Settings

Use the Trace32 Initialization Settings page to specify the initialization script and target processor of the target device.Enter the Trace32 Initialization Script and choose the Target Processor, then click Next.

This page only appears when creating a Trace32 launch configuration.

-

Figure 8 - Trace32 Initialization Settings page

+

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 9 - Sophia STI Initialization Settings page

+

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.

-

Figure 10 - Symbian ROM Image Settings page

+

Figure 11 - Symbian ROM Image Settings page

Other references