-
Notifications
You must be signed in to change notification settings - Fork 31
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
Timing tasks in the range of Microseconds, using QuarkTs with Omnetpp #26
Comments
Hi @HpLightcorner,
you can also use different time bases, for example 50uS
If you do this, all the specifications should be aligned to that base. / * Im assuming that your are using Q_SETUP_TIME_CANONICAL * / qOS_Add_Task (& Task1, Task1Callback, qMedium_Priority, TASK1_PERIOD_SPEC , qPeriodic, qEnabled, NULL ); and the qOS_Run() function must be executed in a base context without any type of time control, basically at the maximum of the CPU (at full speed) or at least at a time significantly faster than the Tick that you are using as time-base. it would be impossible to ask a task for 1uS if the tick is also running at 1uS. ok, so going to your questions: What is your opinion on using a non-preemptive OS for timing below a millisecond? totally possible just to complement, I think this kind of discussions can be moved here :) , https://github.com/kmilo17pet/QuarkTS/discussions let me know if you need more info. Best, |
Hi,
Recently I came across a scenario where I may need to time tasks below 1 Millisecond - mainly within a simulation framework like Omnetpp. I somehow like the idea of using QuarkTS with Omnet as it would allow me to reuse a lot of code I will write for the simulation than in the actual firmware.
The plan is to use Omnetpp Self-Messages to simulate the ticks for QuarkTs. As I won't use a custom IDLE function, I thought about executing the QuarkTs Run Function after every Tick call and/or events. This should then execute all timed and event-driven tasks when I remember the kernel code correctly.
Coming to my questions:
Q_SETUP_TIME_CANONICAL
Thanks for your effort!
The text was updated successfully, but these errors were encountered: