3 ms·
If it must not be linux, I would recommend going for something embedded, like FreeRTOS or similar. The advantages: - Linux + Real Time has become a buzz word, a
by f1shy 4y ago
If it must not be linux, I would recommend going for something embedded, like FreeRTOS or similar. The advantages:
- Linux + Real Time has become a buzz word, and you will find lots of bad information
- If you want to learn HW, nothing better as embedded, where you interact with the hardware.
- The FreeRTOS is so small you can really understand it pretty fast. You can see how it is made, much easier than Linux.
- The essentials you learn with that, will work with Linux later.
- AlotOfReading 4y agoI don't know that I'd recommend learning FreeRTOS for fun because you should basically never be using a traditional RTOS if you can possibly avoid it. Unless you really like reinventing stuff that you get "for free" on Linux, there are remarkably few advantages beyond certifiability (which FreeRTOS in particular doesn't get you), easier porting (just buy something that actually runs Linux) and lower resource use (more work to actually achieve!). As for Linux, your first stop should be the bootlin materials [1]. They're fairly comprehensive and regularly updated. [1] https://bootlin.com/docs/ https://bootlin.com/docs/
- kejaed 4y agoWhile I have not had a chance to work with it yet, there is a path to cert from FreeRTOS in SAFERTOS https://www.highintegritysystems.com/safertos/ https://www.highintegritysystems.com/safertos/
- AlotOfReading 4y agoI spent a fair bit of time at my last job trying to convince people that migrating to SAFERTOS and certifying from there was easier than certifying from FreeRTOS, to no avail. It's more like a fork than a drop-in replacement once you're far along in a project, but it's certainly the better path to take than the alternative. I'd still say the developer and EE experience on Linux is far better than either though.