Skip to content

Plans for new Event Recorder system #4917

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ohagendorf opened this issue Aug 15, 2017 · 5 comments
Closed

Plans for new Event Recorder system #4917

ohagendorf opened this issue Aug 15, 2017 · 5 comments

Comments

@ohagendorf
Copy link
Contributor

Description

  • Type: Bug | Enhancement | Question
  • Related issue: #abc
  • Priority: Blocker | Major | Minor

Question

With the new included RTX5 a new debug possibility was included with it. There exists an event system in the RTOS kernel which can be easily enabled. Currently there seems to exist only the Keil µVision IDE with an Event Recorder, displaying these events during a debug session. And add-on tools like the Tracealyzer. But maybe additional tools will be submitted in the future.

I tested the possibility to use this feature in mbed and it works very well. And I tried to describe the usage in an article: https://developer.mbed.org/users/ohagendorf/notebook/mbed-rtx5-and-uvision-event-recorder/

Are there any plans to include this system natively into mbed? I think, creating events similar to RTX5 in other libraries as already done in the Keil middleware libraries, would improve the debug possibilities substantially.

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 16, 2017

cc @bulislaw @c1728p9 @theotherjimmy

@bulislaw
Copy link
Member

I wouldn't call it a plan yet, but there's a wish :) We recognize possible usefulness of the system, but right now we just don't have the capacity to do much about it.

@c1728p9
Copy link
Contributor

c1728p9 commented Aug 16, 2017

cc @deepikabhavnani

@deepikabhavnani
Copy link

@0xc0170 - I believe the question is answered (no plans at present), should we keep it open as enhancement in future, or close the question?

@0xc0170
Copy link
Contributor

0xc0170 commented Nov 29, 2017

@ohagendorf Thanks for the article and the proposal. The article is good, definitely help few of us.

As above, we will consider this in the future, but currently not planned. Therefore as proposed by @deepikabhavnani we close this one for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants