Super-Simple-Tasker
qpc
Our great sponsors
| Super-Simple-Tasker | qpc | |
|---|---|---|
| 3 | 3 | |
| 129 | 883 | |
| 3.9% | 3.2% | |
| 4.8 | 6.2 | |
| about 2 months ago | 29 days ago | |
| C | C | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Super-Simple-Tasker
-
At what point would you consider using an RTOS?
Lately I have been working with interrupt driven task frameworks on ARM Cortex-M. Basically they are using the ARM NVIC as a task scheduler. Examples for C/C++ include this one: Super Simple Tasker. For Rust there is RTIC. Both are based on similar ideas of using NVIC as scheduling engine. Very efficient resource-wise but use a somewhat different programming paradigm than traditional RTOS threads.
-
Seeking Innovative Project Suggestions
Take a look at the open-source Super-Simple Tasker project on GitHub. This project implements a preemptive RTOS/scheduler in the hardware of the ARM Cortex-M. It is related to such concepts and projects as:
-
How to deal with fast control loops in a RTOS environment?
I agree with KenaDra that such a kernel would be ideal for fast control loops and hard real-time requirements, so the OP should definitely take a look. Specifically for STM32 (ARM Cortex-M), there are some hardware implementations of such kernels that take advantage of the NVIC. An example is the SST for ARM Cortex-M. This kernel will outperform any traditional RTOS kernel on Cortex-M.
qpc
-
FreeRTOS Communication between tasks - Physical design
The QP/C framework already seems to solve all your problems, so if you're asking how to organize your code, this is the best answer you can get. It also seems a little inconsistent that you are taking FreeRTOS, so you are not considering writing your own RTOS kernel. But at the same time, you are rolling out your own event-driven framework as though it was somehow easier, which is not the case and probably quite the opposite.
- Generic HSM implementation in C
-
I made a state machine compiler that outputs C
HSM-test code in C (on GitHub)
What are some alternatives?
lwesp - Lightweight and versatile AT parser library for ESP8266 and ESP32 devices.
rt-thread - RT-Thread is an open source IoT real-time operating system (RTOS).
rulos - Ravenna Ultra-Low-Altitude Operating System: An embedded OS for AVR and ARM CPUs
arm-none-eabi-gcc-xpack - A binary distribution of the Arm Embedded GCC toolchain
crect - A C++, compile-time, reactive RTOS for the Stack Resource Policy based Real-Time For the Masses kernel
modern-embedded-programming-course - Companion repository to the "Modern Embedded Systems Programming" video course.
PIF-Image-Format - Image format, tools & librares for limited embedded systems
QuarkTS - An open-source OS for embedded applications that supports prioritized cooperative scheduling, time control, inter-task communications primitives, hierarchical state machines and CoRoutines.
qpcpp - QP/C++ Real-Time Embedded Framework/RTOS for embedded systems based on active objects (actors) and hierarchical state machines
zephyr - Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
nanopb - Protocol Buffers with small code size
FreeAct - FreeAct is a minimal Active Object (Actor) framework for FreeRTOS