Developing with an RTOS can make it easier to design complex applications, but while an RTOS reduces the complexity of the application source code, it does not reduce the inherent complexity of the application itself.
When you have a task in your system that is supposed to execute at regular intervals, say for instance that it needs to read a sensor value every 5 milliseconds, then you have a system that is sensitive to random delays – also known as .jitter.
In embedded systems using multitasking, you may run into a situation where some of your tasks run slowly or not at all. This is called task starvation (the affected tasks are starved of CPU time) and it can happen for a number of reasons.
There is no doubt a learning curve when you begin using a real-time operating system (RTOS) in your development. Timing, scheduling et cetera will affect your code in ways that are not directly visible in the source code.
Percepio sponsors several Student Racing Car teams with Tracealyzer licenses, mostly in Europe but today we present our first North American team: Purdue Electric Racing.
The Argentinian Air Force has developed a microsatellite, called µSAT-3. And Tracealyzer plays a small but important part in this national satellite project.
Last week Percepio released Tracealyzer version 4.3 with many new features, such as a state machine detail view, stack usage analysis and data export. You will also see major performance improvement when working with very large traces.
We serve cookies. If you think that's ok, just click "Accept all". You can also choose what kind of cookies you want by clicking "Settings".
Read our cookie policy