2.3.29. CONNECT

Connects the debugger to a specified target.

Syntax

CONNECT [{,reset|,noreset}] [{,halt|,nohalt}] [=] "@connection-id"

CONNECT [,gui] [=] "@connection-id"

where:

reset

Reset the target before connecting to it.

noreset

Do not reset the target on connecting to it.

halt

Stop the target on connecting to it.

nohalt

Do not stop the target on connecting to it.

"connection-id"

Specifies the required connection name (see Connecting to a target).

The quotes are optional for connections to targets with names that contain alphanumeric characters, underscores, or hyphens. For example:

@ARM926EJ-S_0@RealView-ICE

If you have a SoC Designer target, the target and model names are usually separated by a period, and multiprocessor models include the processor number in square brackets. Therefore, you must include the quotes. For example:

"@ARM926EJ-S_x2.arm926ej-s[0]@SoC"

gui

Enables you to choose the connect mode from a dialog or prompt:

  • If you use this option when running in GUI mode, it displays a dialog.

  • If you use this option when running in command line mode, it displays a prompt.

The connect specifies what state you want the debugger to leave the target in after the connection. See Connect modes for more details.

Description

The CONNECT command creates a new target connection. The details of the connection are specified using the board file. To connect to a target you indicate which target in the board file you want to connect to, using the identifier string.

Using the CONNECT command means that you do not use the Connect to Target window. However, it is helpful to think of that window when considering the operation of the CONNECT command. An example Connect to Target window is shown in Figure 2.2.

Figure 2.2. Connect to Target window (Configuration grouping)

Connect to Target window (Configuration grouping)

Note

If you set the connect mode in the board (.BRD) file of the target the target connects using that mode. If you specify prompt for the connect mode, then the CONNECT command acts as though you specified the ,gui qualifier. The reset, noreset, halt, and nohalt qualifiers override the connect mode setting in the board file.

Restrictions on the use of CONNECT

The CONNECT command is not allowed in a macro.

Connect modes

When you connect to a target, the connect mode determines what happens to the target:

No Reset and Stop (,noreset,halt)

Connect to the target, but do not reset it. If the target is running, stop it. This is the default.

No Reset and No Stop (,noreset,nohalt)

Connect to the target, but do not reset it. The running state of the target is unchanged.

Reset and Stop (,reset,halt)

Connect to the target, and reset it. If the target is running after the reset, stop it.

Reset and No Stop (,reset,nohalt)

Connect to the target, and reset it. The running state of the target is unchanged.

Note

The connect modes available depend on the Debug Interface you are using.

Connecting to a target

You can connect to a target where the Debug Configuration is not currently expanded using a single command:

connect "@target@DebugConfiguration"

Depending on the Debug Interface, target might include a numerical suffix. If there is more than one target configured for a Debug Configuration, then the number reflects the order on the JTAG scan chain for hardware targets.

If you have created more than one Debug Configuration, and both provide access to targets with the same name (for example, ARM940T_0), then the debugger connects to the target of the first Debug Configuration that you accessed.

For example:

connect @ARM940T_0@RealView-ICE

This command connects to the ARM940T_0 target, expecting this to be available in the RealView-ICE Debug Configuration.

If the Debug Configuration, in this case RealView-ICE, has not been configured with an ARM940T_0, the connection fails with the message Error P1001E (Parser): Specified target not in list of available targets. You must correctly configure the Debug Configuration before you connect to the target.

If you specify a target that has not been configured, you are prompted to configure the target before you can connect.

See also

Copyright © 2002-2011 ARM. All rights reserved.ARM DUI 0175N
Non-ConfidentialID052111