Keil Logo

ARM: RTX5 awareness in µVISION debugger when using ARMCC


Information in this knowledgebase article applies to:

  • ARM CMSIS/RTX5 V5.3.0 or newer
  • ARMCC

SYMPTOM

I am using ARMCC to build my project that uses CMSIS RTX5. Some OS objects, like threads, are created with custom control blocks, specified in the attribute parameter. I even used the section attribute as described in the manual to put the control blocks in the required sections. But when starting the debug session, I don't see this objects in the Component Viewer window for RTX5. The threads also don't appear in the Call Stack + Locals window.

For debugging my application, I need information about that RTX5 objects in the debugger. What can be done about this?

CAUSE

µVision Component Viewer gets the information from the application by reading a certain object "os_cb_sections" from the target image. This object is only referred by the debugger.

Unfortunately there is no reliable way to make sure, the debugger symbol does not get removed during building the project. So, when the objects with custom control blocks are not show, "os_cb_sections" is not in the flashed image.

RESOLUTION

To make sure, that the required object gets not removed, add the following option:

--keep=os_cb_sections

in the Options for Target ... - Linker - Misc Controls field and build and flash the project again. After that, the Component Viewer and the Call Stack + Locals window should be aware of the objects.

MORE INFORMATION

Last Reviewed: Monday, April 16, 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.