Step1: Setting target environment in Controller Tester - User Guides

Select Debugger on the target environment setting page of the Controller Tester. Only a list of debuggers supported is displayed, depending on the toolchain selected for the project.
Set the debugger to TRACE32.

The setting items are displayed according to the selected information. The items you need to set when using the TRACE32 debugger are shown in the table below.
Some of the settings are required.

trace32_exe_file_path	TRACE32 executable file path. Each target has a different executable file, so you need to make sure that the target executable is the correct one. Required
target_binary_path	Path to the binary file for loading into the target environment. Check and enter the path where the target binary file is created in your IDE or build script. Required.
chip	Enter the chip name of the target you are using. It is used when auto-generating a cmm script, so you need to enter the correct chip name.
user_defined_cmm_script_file_path	Custom cmm script file path. For targets that do not support automatic generation of cmm scripts, you must write a script to set the debugger and target usage environment, or enter the path to the cmm script file you are using.

Supported target list that can generate cmm script automatically

Step2: Run the target test

Need more help with this?
Don’t hesitate to contact us here.