This forum is about you. Feel free to discuss anything is related to embedded and electronics, your awesome projects, your ideas, your announcements, not necessarily related to ChibiOS but to embedded in general. This forum is NOT for support.
I've just recently seen a new RTOS around, which is called BeRTOS: http://www.bertos.org/
From my point of view, it looks very much like ChibiOS:
both can allocate threads statically
both have a HAL
both work on my favorite platforms (AVR and STM32)
However:
ChibiOS has faster switching
ChibiOS looks better designed
BeRTOS has a very handy HAL wizard
BeRTOS' HAL has more drivers
So, is there any way that we can compare them both more thoroughly? Maybe a benchmark or a comparison by someone who is more knwledgeable in OS design than me?
Or can we at least integrate some of the HAL drivers or expand ChibiOS' ones to encompass more external peripherals, or maybe make our own wizard (and personally I would consider an online auto-updating sdk) ?
Or can we at least integrate some of the HAL drivers or expand ChibiOS' ones to encompass more external peripherals, or maybe make our own wizard (and personally I would consider an online auto-updating sdk) ?
Patches are welcome.
Now a few thoughts. BeRTOS has very abstract driver modules. For example, nmea parser ports without any problems to ChibiOS (I will merge it to my own project, thanks for link). But is it really need in ChibiOS? Graphics display driver looks portable to. Tmp75 driver... it is simplest I2C device that I seen and write and support separate drivers is overkill.
Offtopic: Config wizard written in python. I love python.
I agree with Barthess, things like parsers, crypto routines, CRC etc are nice to have do no qualify like drivers because those are portable and with no hardware or OS dependencies if well written.
We are trying to stay focused on "RTOS" else I would be throwing in a lot of unrelated (even if useful) code. Added code also has a cost in terms of: - Documentation. - Testing. - Maintenance. Better stay focused and do well one thing.
About the wizard, well there is one for ChibiOS too but so far I haven't been pushing it (it is written in a template language named FreeMarker).
The concept is a bit different, you create in Eclipse an XML (guided by a schema) that describes your application in terms of modules, functions, threads, semaphores, Mailboxes, Drivers etc then there is a generator that produces a ChibiOS-compliant project with source files, configuration files and makefiles ready to be compiled, if even generates all the Doxygen tags in the source. The fun thing is that the ChibiWizard engine is basically done but it does not have a decent GUI yet. Probably I will give it some bandwidth after the 2.4.0 release, my idea is to make it an Eclipse plugin with something like drop-in-the-project visual components (much like Delphi if you know it).
