Keil Logo

µVISION DEBUGGER: HW and SW requirements of debug features in µVISION


Information in this knowledgebase article applies to:

  • MDK v5.x
  • µVision Debugger

QUESTION

We use MDK for many years and in general debugging works fine. But in some cases a certain debug features, such as Logic Analyzer, Event Recorder etc., don't work at all for some reasons.

What are the minimum software and hardware requirements to be configured for debug features in µVision?

ANSWER

It requires the target HW supports either SWO or ETM trace. SWO trace or ETM trace need to be properly configured in µVision debug settings.

Restrictions are listed here.

It requires the target HW supports ETM trace. ETM trace need to be properly configured in µVision debug settings. The debug adapter HW used with µVision needs to support streaming ETM trace, such as ULINKpro. So far third party debug adapter HWs, such as J-Trace Pro, don't support ETM streaming trace in µVision, in other words, cannot work with Performance Analyzer.

Moreover, the streaming ETM trace requires 4-bit trace port to be selected and initialized in µVision.

It is the same with Performance Analyzer, that requires a running ETM trace, more specifically streaming ETM trace using 4-bit trace port. Thus, so far third party debug adapter HWs, such as J-Trace Pro, cannot work with Code Coverage in µVision. ULINKpro is recommended.

Some debug info shown in this System Analyzer viewer, such as power consumption, measured core clock frequency etc. requires a ULINKplus debug adapter.

Other debug info in this viewer, such as RTX5 events, threads, requires enabling and setting up event recorder properly. The "Source" variant needs to be selected in "Manage Run-Time Environment - CMSIS - RTOS2 - Keil RTX5".

Debug info, such as Exceptions, requires enabling and setting up either SWO or ETM trace.

  • Event Recorder

It doesn't require the target HW supports SWO or ETM trace. Follow this user guide and this manual to set up Event Recorder properly.

It only supports the old Keil RTXv4.x based on CMSIS RTOS v1. If your project with Keil RTXv4.x is built with ARMCLANG v6.x compiler toolchain, follow this ARMCLANG: "System and Thread Viewer" is empty debugging RTXv4to make it work.

It only supports the old Keil RTXv4.x based on CMSIS RTOS v1. It requires the target HW supports SWO or ETM trace. Trace needs to be properly configured in µVision debug settings.

It only supports Keil RTXv5.x based on CMSIS RTOS v2.

More Information

SEE ALSO

Last Reviewed: Wednesday, November 7, 2018


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.