8 months ago.

uVision debugging issue with "Call Stack + Locals" and "System and Thread viewer"

/media/uploads/cakehuang/keil_debugging.png Hi Team,

I am debugging mbed-os-example-ble\BLE_Button, the experience is not very good. I found the "Call Stack + Locals" is not updating correctly and "System and Thread viewer"(Debug\OS Support) is not updating at all.

How to solve this?

I am using uVision to debug.

The steps I did to get uVision project file are: $ git clone $ cd mbed-os-example-ble $ cd BLE_Button $ mbed deploy $ mbed compile -t ARM -m NRF52_DK $ mbed export -i uvision -m NRF52_DK


Comment on this question

1 Answer

8 months ago.

Hi Cake,

The System and Thread Viewer in uVision doesn't have support for RTX5 yet as described here:

As Mbed is built on RTX5 you won't be able to use it.

You can however make use of a RTX5 viewer description file and this will give you a custom view you may not have seen before. This is described here:

From the Manage dialog you will want to add this file:


Then when debugging under "View-Watch Windows" you will have a new option "RTX RTOS". Attached is a screen capture of a session we just ran with a ULINKpro with the BLE Button demo. We think this will help!


As for the Call Stacks and Locals pane, that isn't revealing much information probably because there isn't much of a call stack to show for those threads. Please contact Keil support if you have further questions about these views as they will know their limits/capabilities:

-Ralph, Team Mbed

Thank you so much for your professional answer.

posted by Tony Huang 22 May 2018

One current solution that I am aware of is Percepio's Tracealyzer: The Tracealyzer looks very shiny.

posted by Zachary Havens 24 May 2018

To post an answer, please log in.