# TRACE32 Pod Configuration

## Overview

The TRACE32 hardware that links the host computer with the hardware
debug platform is referred to as the *pod*.

The pod requires the following types of information to communicate
with the host computer and hardware debug platform:

- Host software configuration
- Ethernet port assignment (if not using USB pod)

TRACE32 obtains this information from configuration files stored on
the host computer.

Separate configuration files are used for the ARM
and Hexagon processors.

Note

Predefined configuration files are provided with each target
system – users do not have to create these files or modify them.

For more information on pod configuration see the document
training\_icd.pdf in the Lauterbach TRACE32 documentation.

## ARM configuration file

The following code example shows the TRACE32 ARM configuration file
(arm\_mconfig.cfg).

PRINTER=WINDOWS
    
    ; Environment variables
    OS=
    ID=unique_ARM_id
    TMP=C:\T32\Temp
    SYS=C:\T32
    
    ; Ethernet on Host information
    PBI=
    NET
    NODE=ip_address_of_T32_probe
    CORE=1
    
    ; Remote Control Access
    RCL=NETASSIST
    PORT=20000
    Copy to clipboard

## Hexagon configuration file

The following code example shows the TRACE32 Hexagon configuration
file (hexagon\_mconfig.cfg).

PRINTER=WINDOWS
    
    ; Environment variables
    OS=
    ID=unique_Hexagon_id
    TMP=C:\T32\Temp
    SYS=C:\T32
    
    ; Ethernet on Host information
    PBI=
    NET
    NODE=ip_address_of_T32_probe
    CORE=2
    
    ; REMOTE Control Access
    RCL=NETASSIST
    PORT=20001
    Copy to clipboard

Last Published: Oct 06, 2026

[Previous Topic
TRACE32 command](https://docs.qualcomm.com/bundle/publicresource/80-N3040-23/topics/starting-trace32.md) [Next Topic
Loading Hexagon Images](https://docs.qualcomm.com/bundle/publicresource/80-N3040-23/topics/loading-hexagon-images.md)