Minor improvements for ThreadX detection#93
Merged
haneefdm merged 1 commit intomcu-debug:mainfrom Mar 9, 2026
Merged
Conversation
c006f32 to
7016e1b
Compare
Contributor
Author
- Make _tx_semaphore_created_count, _tx_mutex_created_count and _tx_byte_pool_created_count optional in tryDetect() so that minimal ThreadX applications without all the objects can be detected. - Added number of objects indicator to tab title, similar to FreeRTOS. - Added help/guide text in empty tabs when objects are not found or symbols missing.
7016e1b to
38ceac6
Compare
Contributor
|
Thanks @kennedyho-renesas |
Contributor
|
Thanks @kennedyho-renesas for this really nice improvement! |
Contributor
Author
|
@raphaelmeyer thank you for letting me contribute! |
Contributor
No need to worry. The project is anyway not set up to enforce it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




This PR makes a minor change to how ThreadX is being detected.
The following table shows the before and after of the change.
Before the change, if a FW or application does not create any one of the objects (mutex, semaphore, byte pool), ThreadX will not be detected.

After the change, ThreadX can be detected, and for the tab where the object is not being created, it is shown as an empty tab as follows:
This is more of an initial improvement and can be improved further in the near future to include text indication or help, so that users know why the tab is empty.