BeRTOS
A 5 minute introduction to BeRTOS

Installing BeRTOS on your system

What do you need when developing an embedded project with BeRTOS?

See the installation instructions page online for help on installing BeRTOS on your system.

Strictly speaking, BeRTOS doesn't need to be 'installed', you can just take .c files and compile them in your project.

However, BeRTOS is a complex system with many dependencies between modules. It's not easy to track the dependencies for each module, so we have developed a set of tools to make dependency tracking automatic.

Contact the support forum and look at the section Coding guidelines if you want help on using BeRTOS without the supporting tools. Be warned, though, that this method is not supported and we can only point you in the right direction.

Project's organization

Each project has its own full BeRTOS sources, configuration and HAL files. Why? Because we think that each project has its own life and it must not interfere with any other project. Let's say you use a shared BeRTOS version for all of your projects. Each time you update, you need to check that each and every project still works correctly. We don't want to do this (and I bet you don't want either). However, it's still easy to update a single project if you want to.

A project named Foo is organized as follows:

See BeRTOS HAL system for more information on HAL files.

Coding guidelines

BeRTOS assumes that the BeRTOS source directory and the project's root directory (as indicated above) are in the include path. This means that you should include configuration files using "..." rather than <...> style, otherwise you will use default configuration values instead of your project's values.

Also, you should change configuration settings using the Wizard. This is because sometimes there are more actions to be done than simply changing a define value.