- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- MCUXpresso Training Hub
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
-
- Home
- :
- MCUXpresso Software and Tools
- :
- LPCXpresso IDE FAQs
- :
- SWO Trace Error Messages
SWO Trace Error Messages
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
SWO Trace Error Messages
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The LPCXpresso IDE will attempt to identify when SWO trace configuration has not been successful and report details of what has gone wrong. Below are a list of common errors, together with details of what may have caused them:
SWD debug connection required to use SWO Trace. JTAG debug connection was detected
SWO Trace functionality is only available when connecting to the target MCU using SWD. This message is displayed if you are connected via JTAG, in which case you will need to switch to using SWD. For most Cortex M3/M4 MCUs, debug connections are made using SWD by default so this message is not likely to be seen. However with LPC43xx parts, JTAG is used by default.
Need a valid clock speed to collect SWO data.
This message is displayed if you have not entered a clock setting value into the SWO Config view (typically leaving it set to 0).
Failed to detect compatible probe firmware.
This message is displayed if the LPCXpresso IDE has been unable to detect the channel used for SWO over the debug probe link. This typically suggest that your are using old or incompatible firmware. Disconnect your debug session, power down your debug probe and ensure that the debug probe is configured for dfu booting. Then when you start a new debug session, LPCXpresso should attempt to download the current redlink firmware.
For the target clock speed there is no suitable baud rate to communicate between probe and target.
This message is displayed if the LPCXpresso IDE has been unable to generate an appropriate SWO communication baud rate from the selected target clock speed. You may need to reconfigure your project to use a different clock speed.
Failed to configure the probe for SWO - may not be supported with this firmware.
This message is displayed if the LPCXpresso IDE has been unable to detect the channel used for SWO over the debug probe link. This typically suggest that your are using old or incompatible firmware. Disconnect your debug session, power down your debug probe and ensure that the debug probe is configured for dfu booting. Then when you start a new debug session, LPCXpresso should attempt to download the current redlink firmware.
Failed to configure the target for SWO - may not be supported on this target.
This message is typically displayed if SWO not supported on this target or the selected target clock speed is wrong.
On Mac LPCXpresso may need to be started using the 'Open lpcxpresso' link to use SWO functionality
There is currently an issue with SWO Trace support on Mac OS X hosts such that if LPCXpresso IDE as been started from Launchpad, or by clicking on the lpcxpresso.app, then SWO Trace may not work. In such cases, LPCXpresso IDE will attempt to warn you that this may be because of how you started the IDE up. You should then try launching LPCXpresso IDE by clicking on the "install_dir/Open lpcxpresso" alias (or by running it from a terminal).
For more information:
