ECos tools

This is a repository for some minimal eCos tools.

Prerequisites

ecosconfig requires the tcl compiler to work. For Debian or Ubuntu development platforms the proper package is named tcl8.5, you can install it using: sudo apt-get install tcl8.5. For Gentoo platforms the package is named dev-lang/tcl, you can install it using: sudo emerge dev-lang/tcl.

Put ecosconfig in a system-wide localisation (like /usr/local/bin) so that both are available from command line, using e.g. sudo mv ecosconfig /usr/local/bin

Warning

ecosconfig is a 32bit application, thus if you are using a 64bit OS you have to provide 32bit run-time libraries for compatibility. In Debian-based Linux distributions these could be installed using the command sudo apt-get install ia32-libs.

Note

configtool, a graphical tool for editing .ecc files, is also provided in this repository for convenience but not a prerequisite.

Usage

make.sh and config file

Copy make.sh and example.config to the repository where you are developing your eCos application, renaming the latter to <your-app-name>.config, and edit the file to set the appropriate paths/options based on the instructions included in the file.

Compiler

If the appropriate compiler (read automatically from the .ecc file) is not available in your PATH, you may create an optional <your-app-name>.tpath file in the same directory. Put the absolute path to the toolchain's bin/ directory there (i.e. echo "</path/to/toolchain>/bin" > <your-app-name>.tpath). Do not version the file with the toolchain path in your repository! (e.g. add it to .gitignore). The path given in the file will be added to your PATH in the compilation process without polluting the global PATH variable.

Compilation

The make.sh script uses the <your-app-name>.config and <your-app-name>.tpath files to get the necessary information on how to compile your application.

If you do not supply the --config parameter, the first .config (and a respective .tpath file, if present) in the working directory will be inferred. This way, in the most common use case where you have just one configuration you're working with, you can just use ./make.sh to compile.

This will build:

• the eCos kernel if the .ecc is set to compile eCos and the FILES variable is empty
• your eCos application and the kernel if the FILES variable is set
• RedBoot if the .ecc is set to compile RedBoot

In case you need to explicitly specify the config, run ./make.sh --config=<your-app-name> instead.

Available flags

• -o=<fname>|--output-filename=<fname> - set an output filename if building an application, default is <your-app-name>
• -t|--tests - build the eCos test suite
• -r|--rebuild - force rebuilding the kernel

Notes

• the eCos build output will be in the <your-app-name>_build/ directory
• remember to --rebuild after you change your .ecc!