Panel

Live Q&A & Panel Discussion - RTOS Track

Watch Now

48:05

EOC 2025

Panel

Live Q&A & Panel Discussion - RTOS Track

48:05 EOC 2025

Live Q&A & Panel Discussion - RTOS Track

48:05

Live Q&A and Panel Discussion with speakers presenting in the RTOS track.

1 / 5

Please log in or create an account to test your knowledge and see the answers.

Regarding running NuttX on classic 8-bit AVR microcontrollers with 2 KB of RAM, what did the panel recommend as the correct understanding?

A NuttX is fully supported on classic AVR with 2 KB RAM and will run all features reliably.

B The NuttX port to classic AVR is mostly a proof of concept; consider AVR DA/DB parts with ~16 KB RAM and 128 KB flash to use NuttX features properly.

C Any RTOS (including FreeRTOS) will fit comfortably into 2 KB RAM, so no hardware changes are needed.

D You must avoid any RTOS on AVR and rewrite the system as a finite-state machine even if you can use larger RAM parts.

E Only commercial RTOSes can run on classic AVR 2 KB RAM devices; open-source RTOSes cannot.

Why does the QP framework (with active objects) often require only a single stack for many active objects?

A Because active objects run-to-completion and don't block inline, behaving like nested ISRs, so they can share a single stack.

B Because the kernel serializes all active objects onto one non-preemptive thread that never allows nested execution.

C Because each active object allocates stack space dynamically from the heap when it runs.

D Because active objects are implemented entirely as macros with no runtime stack usage.

E Because the kernel disables interrupts globally so only one stack is ever needed.

In the QP model discussion, how are 'event deferral' and 'orthogonal components' related and used?

A They are independent: event deferral temporarily holds events while an active object is busy; orthogonal components are passive state-machine pieces without their own thread or queue.

B Orthogonal components are simply another name for active objects and always have their own event queues.

C Event deferral eliminates the need for any queues or bookkeeping because deferred events are never lost and need no storage.

D You should always convert every active object into an orthogonal component to minimize threads.

E Orthogonal components are only useful for device drivers and cannot be combined into a master active object.

What was Aaron's primary criterion for choosing FreeRTOS for his robot butterfly project?

A Tool accessibility — FreeRTOS was easy to get started with because it’s available in the Arduino IDE for ESP32.

B It had the smallest possible memory footprint compared to all other RTOSes.

C It was the only RTOS that supported the specific IMU hardware he used.

D It was chosen because it was the only RTOS with formal safety certification for robotics.

E He chose it because it enforced static memory allocation by default.

Why does embOS default to static memory allocation, whereas FreeRTOS historically defaulted to dynamic allocation?

A embOS targets resource-constrained embedded devices and avoids dynamic heap allocation because malloc is non-deterministic and can cause fragmentation; FreeRTOS historically used dynamic allocation and added static APIs later.

B embOS uses static allocation because it's required by the C standard for embedded systems, while FreeRTOS ignores standards.

C FreeRTOS always used static allocation and never allowed dynamic allocation.

D embOS defaults to static allocation because dynamic allocation is illegal in embedded programming.

E embOS uses static allocation by default to force developers to write slower but safer code.

Formatting help

italics	surround text with asterisks
bold	surround text with two asterisks
hyperlink	[hyperlink](https://example.com) or just a bare URL
code	surround text with `backticks`
~~strikethrough~~	surround text with ~~two tilde characters~~
quote	prefix with >

Upvotes Newest Oldest

SimonSmith

Score: 0 | 10 months ago | 1 reply

Good to hear the mention of Micrium uC/OS-III, which felt like it died when it was open-sourced a few years back around the time when SiliconLabs took it over and FreeRTOS took off. It's well documented, easy to use and has full source code.
https://github.com/weston-embedded/uC-OS3
https://micrium.atlassian.net/wiki/download/attachments/132386/100-uCOS-III-ST-STM32-003.pdf?version=1&modificationDate=1383921876000&cacheVersion=1&api=v2

acassis

Score: 1 | 10 months ago | no reply

Hi SimonSmith,
that is true, if you use SiliconLabs chips, then uC-OS is a good option!

Partners & Sponsors

CodeSecure

atym

embedd.it

IAR

Become a Sponsor