If you see a dialog box with the message "TRACE32 device already in use" then one of the following has happened:
1. You've started TRACE32, while another TRACE32 GUI is still exclusively connected to the same PowerDebug box.
2. TRACE32 PowerView was previously not properly closed (e.g. killed or crashed).
3. You have started a second TRACE32 for an AMP multicore scenario, but the second GUI wasn't configured with CORE=2 or the first GUI wasn't configured for CORE=1.
If you want TRACE32 to automatically to force connection to the PowerDebug box by resetting it, use the statement CONNECTIONMODE=AUTOCONNECT in the PBI= section of your TRACE32 configuration file (usually "config.t32").
Example for a USB connection:
PBI=
USB
CONNECTIONMODE=AUTOCONNECTIf you want TRACE32 to automatically close the new TRACE32 session, use the statement CONNECTIONMODE=AUTOABORT in the PBI= section of your TRACE32 configuration file.
PBI=
USB
CONNECTIONMODE=AUTOABORT
TRACE32 additionally supports the connection modes AUTORETRY and QUERYCONNECT. Below is a description of all connection modes:
Connection mode | Description | |
|---|---|---|
AUTOABORT | If PowerDebug device is already in use, the TRACE32 executable will be closed automatically without any user interaction. | |
AUTOCONNECT | The TRACE32 executable will automatically take over control over the PowerDebug. | |
AUTORETRY | If PowerDebug device is already in use, the TRACE32 executable will wait until the current TRACE32 session ends. | |
NORMAL | Default. If PowerDebug device is already in use, warn user and close application after confirmation. | |
QUERYCONNECT | If PowerDebug device is already in use, ask user if connection shall be forced.  | |
Please refer to the TRACE32 Installation Guide for mode information.
In case you are using t32start.exe to start the TRACE32 PowerView user interface, then you can set up the connection mode under USB Settings or Ethernet Settings then Connection Mode. Refer to T32Start for more information.
Comment (1)