Safety-certified tools Tools for Automotive Applications C-STAT Static analysis C-RUN Runtime analysis Debugging and trace probes Build tools for Linux
On some MCUs, you can choose which H/W pins are used for SWO or ETM trace.
The C-SPY debugger normally configures the trace pins automatically using debugger macro files (*.dmac) from the directory:
To make C-SPY aware of which pins you have selected for SWO or ETM trace, there are usually macro parameters similar to these in the device-specific .dmac files:
To change such a parameter without modifying the .dmac file, use:
Project>Options>Debugger>Extra Options>Use command line options:
Read more about --macro_param in the C-SPY Debugging Guide for Arm.
The following list contains examples of device-specific .dmac files where SWO or ETM trace pins can be configured:
|Microchip||SAMD*.dmac, SAME*.dmac, SAMV*.dmac|
|NXP||iMX*.dmac, K*.dmac, LPC5*.dmac, S32K*.dmac|
To find which .dmac file is used by your device, see the top of the Debug Log window. Look for the lines that begin with Loaded macro file. You can also see which .dmac file is used by looking for the DeviceMacros line in:
On some MCUs, you can choose which H/W pins are used for SWO or ETM trace. That is, you can configure the trace pins, and you can configure C-SPY to match the H/W trace pin configuration.
All product names are trademarks or registered trademarks of their respective owners.