question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to debug with FreeRTOS awareness enabled

See original GitHub issue

Hi there,

Up until recently I was able to debug fine using the following config:

                "name": "X Debug Release",
                "cwd": "${workspaceFolder:X}",
                "executable": "${workspaceFolder:X}/project/X/build/release/X.elf",
                "request": "launch",
                "type": "cortex-debug",
                "servertype": "jlink",
                "device": "STM32L451VE",
                "runToMain": false,
                "rtos": "FreeRTOS",
                "svdFile": "${workspaceFolder:X}/toolchain/STM32L4x1.svd"

However, recently when trying to launch this config I get the following log: "monitor" command not supported by this target. Removing the line "rtos": "FreeRTOS", allows debugging to launch as usual but without FreeRTOS awareness.

arm-none-eabi-gdb version: 8.3.0.20190709-git JlinkGDBServer version: V6.94a

This was working well up until recently and I’m unsure what has changed. Any help is much appreciated, thanks.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:13 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
Maruscommented, Jan 27, 2021

Interesting - as the v6.94 doesn’t break it in general for all FreeRTOS versions - but certainly seems to have issues with that particular one. On our side, we can’t do anything about it as it just seems to crash the GDB server - which at that point puts it out of our hands. Glad you found a work-around.

0reactions
bryce-cahillcommented, Jan 27, 2021

Interesting find @Marus. However, I just manually downgraded the jlink-software-and-documentation package from version v6.94 to v6.88a (a version that I found I had working in the past) and thread aware debugging is working again. Unfortunately without going through all the versions in-between I would be hard pressed to tell you which version of the package broke things.

Thanks for having a look at this.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting Tips for FreeRTOS Thread Aware Debugging ...
This article describes tips and tricks to get FreeRTOS thread aware debugging in Eclipse, organized by debug probe connection/vendor. For thread ...
Read more >
FreeRTOS RTOS Kernel Awareness not working on CubeIDE ...
0, it's no longer working. I'm using a Segger J-Link. My Debug setting are in the picture below. This is for the device...
Read more >
Troubleshooting Tips for FreeRTOS Thread Aware ... - DZone
This article describes tips and tricks to get FreeRTOS thread aware debugging in Eclipse, organized by debug probe connection/vendor.
Read more >
Debug not working FreeRTOS · Issue #314 · Marus/cortex ...
I'm not able to debug either, when enabling FreeRTOS integration. Breakpoints are not being hit, and the pause button is not responsive.
Read more >
Debug with kernel aware plug-in Eclipse? - FreeRTOS
Hi I tried to install the Wittenstein plug-in today in my AVR32 Studio (V2.1.0). Unfortunately I can't choose the new views in the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found