🎉 We're happy to announce new public releases! ðŸŽ‰

  • SWAT v1.1r1 - Software tracing solution now supporting more architectures and operating systems - see SWAT Release Notes.
  • TriCore v6.2r2 Inspector v1.0r8 - An automated method for identifying toolset issues in compiled output code.
  • VX-toolset for Arm - v8.0r1 - A certified compiler toolset for safety-critical embedded software development on Arm cores.
Contact us to get access!

Arm Cortex NXP LPC435x: Startup

07-May-2025

Per LPC435x specification, Cortex-M0 is not accessible through the SWD debug interface. It’s accessible only through the JTAG debug interface.

It’s recommended to use the JTAG debug interface when debugging LPC435x, which allows debugging both Cortex-M4 and Cortex-M0 cores.


If only the SWD debug interface is available on the target debug connector, only Cortex-M4 can be debugged.


Possible solution

1. Go to Hardware | CPU Options | Cores | CortexM0.

2. Uncheck the Automatically observe this core option.

Without this adjustment, winIDEA might become unresponsive when attempting to connect to the Cortex-M0 core.


More resources in winIDEA Help

Was this answer helpful?