News for hackers. Stuff that matters.

JoelSherrill

Re:RTEMS Real Time Operating System on Wednesday August 03, 2022 @10:15AM (#32331972)
This is ESA's fourth RTEMS qualification effort AFAIK. This time they are working with the community and have submitted things like requirements for a subset of RTEMS and requirements based tests. This is tracking the git master and SMP is included. We worked with NASA IV&V folks to get an outline for the RTEMS Software Engineering Guide which provides information expected in a qualification review.

Quietly an RTEMS core developer submitted GCC support for running gcov or gprof on embedded targets and getting the information off. This will be used to get coverage reports which meet ESA expectations. We do have very high code coverage.

ESA has also sponsored formal analysis of some parts of RTEMS.

I am quite happy ESA is working so well with our core developers and community this time.

Re:RTEMS Real Time Operating System on Wednesday August 03, 2022 @10:02AM (#32331787)
The Harvard architecture shouldn't be a problem. Xtensa has a gcc port so that's covered. It is mostly a matter of no one has volunteered to do it or paid for someone to do it. If someone wants to port it, we'd be happy to guide you.
Re:RTEMS Real Time Operating System on Wednesday August 03, 2022 @09:57AM (#32331719)
This isn't uncommon for an OS to provide its own tooling. This is how you get the GCC language runtimes tailored for the OS. We support C, C++, and Ada fully out of the box. Our current GCC should be tracking gcc 12.

Did you know that we provide a tool to build all tooling from source including application of patches? It's similar in concept to BSD ports. This gives users full source and the ability to put it under configuration control for long term projects.

Re:RTEMS Real Time Operating System on Wednesday August 03, 2022 @09:54AM (#32331675)
RTEMS now has a choice of network stacks. You can choose from libbsd which is a port of (currently) FreeBSD 12 services including TCP/IP, USB, SD/MMC, and more including the network shell commands. We have an implementation of core kernel services which make porting the code easier. There was an article in the FreeBSD Journal about this a few years ago.

We also have a port of lwip which is appropriate for smaller systems.

Finally we have the older legacy FreeBSD stack which we don't recommend for new projects but some BSPs still only have drivers in there.