patacongo

6 ms·

1.
by patacongo 7y ago
Fitbit?
2.
by patacongo 7y ago
Ultimately, an RTOS can only provide you with the tools to create a hard real-time system. The RTOS cannot guarantee that your application can meet any deadlines. That requires the proper use of those tools by the application. If you impr
3.
by patacongo 7y ago
The defunct Google project Ara and it its living decendents TizenRT (tinyara) and the Motorola MDK.
4.
by patacongo 7y ago
> Almost any RTOS on the Cortex-M profile will fully utilize the NVIC, giving you a hardware-managed preemptive FIFO scheduler even in interrupt context. NuttX's lack of this feature is a severe weakness, and a major reason to avoid
5.
by patacongo 7y ago
> NuttX is a POSIX compliant operating system, and it likes to use the same naming convention of many of the functions and files you'd find in your standard UNIX/Linux system. When you try to write a unit test for your embedded
6.
by patacongo 7y ago
The BBC Microbit supports a NXP/Freescale KL26Z. That chip is supported by NuttX so the answer would be yes, with some additional board level support. The NXP/Freescale KL26 has very limited resources, however. I would not recomm
7.
by patacongo 7y ago
NuttX also has strict licensing and coding standard enforcement. Such things are a necessary component of QA and I would think that all serious RTOS's have similar standards.
8.
by patacongo 7y ago
To be clear, they switched from a 3 or 4 year old version of Nuttx (prior to interrupt optimatizations) to current ChibiOS.
9.
by patacongo 7y ago
> - uses a pure software interrupt and redirects to your ISR's, so you incur additional overhead for all interrupts in your system Not true. Like Nucleus OS, NuttX supports two class of interrupts, What nucleus calls "managed&