Cortex-M Debugging

When configuring Cortex-M debugging, you must configure a few settings in µVision so that it knows you want to use ULINK2 for these tasks.

• Debug Driver Configuration
  To debug programs running on target hardware, you must configure µVision to use ULINK2 as the debugger you use for target debugging.
• Trace Configuration
  To use the trace feature provided by the Cortex-M hardware, you must configure µVision to set up the parameters that control the various trace activites.
• Flash Download Configuration
  To program on-chip and external Flash memory on your target hardware, you must configure µVision to use the appropriate programming algorithms based on the memory-map and Flash devices used. Programming algorithms for most on-chip Flash memory is selected automatically.

Note

• ULINK automatically configures to the debug features offered by the core used in the target system. It reads the CPU ID to determine the Cortex core and core version and checks which core debug peripherals are present.

  With this information ULINK is able to determine:

  • the number of Flash breakpoints.
  • the number of watchpoints.
  • the possible use of ITM, ETM and TPIU