## New Launch Configuration Wizard

The New Launch Configuration Wizard launches when no launch configuration exists for a project. Wherever possible the New Launch Configuration wizard gathers the information from the project and asks additional questions based on the type of launch configuration chosen. For example, a launch configuration using Application TRK requires different information than one targeted for System TRK.

For Application TRK and System TRK the following pages appear:

- Launch Type
- Executable Selection
- TRK Connection Settings
- TRK SIS Selection (Application TRK only)
- New Launch Configuration

For Trace32 launch configurations the following wizard pages appear:

- Launch Type
- Executable Selection
- Trace32 Initialization Settings
- Symbian ROM Image Settings
- New Launch Configuration

For Sophia STI launch configurations the following wizard pages appear:

- Launch Type
- Executable Selection
- Sophia Initialization Settings
- Symbian ROM Image Settings
- New Launch Configuration

For Attach to Process launch configurations the following wizard pages appear:

- TRK Connection Settings
- New Launch Configuration

To access the New Launch Configurtion Wizard, set the Build Target to a Phone Debug target (Figure 1), then click the Debug icon (). If no launch configuration exists for the build target the wizard is launched. If a launch configuration already exists, then that launch configuration is launched and not the wizard.

For emulator targets, the New Launch Configuration Wizard can gather all the information it needs from the project, so clicking Debug just launches the debug session.

Figure 1 - Build Target selection list

### Launch Types

Use the Launch Types page to select the type of launch configuration for the build 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 2 - Launch Type 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 Executable to launch option is disabled. Use the Specify device or emulator path of executable 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\) .

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.

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

Figure 3 - Executable Selection page

### TRK Connection Settings

Use the TRK Connection Settings page to specify the COM port 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 Setup 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 4 - 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 page to add, edit, or review the SIS files to build. Once the correct SIS File to Install is selected, click Next.

Figure 5 - 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 6 - 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 7 - 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 8 - 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 9 - Symbian ROM Image Settings page

##### Other references

- Launch Configuration