With CODEO you can conveniently setup your target device via the project configurator. Here, you find all the necessary tools to manage your target and your applications. The IDE grants access to target devices for remote debugging and timing analysis for runtime information.
CODEO is flexible: You may cross-develop for target devices within Windows and testing it with QEMU.
Setup & Development Options
The graphical environment for the ELinOS toolchain provides all the features to help developers create modern embedded systems. CODEO comprises the latest GNU Compiler Collection (GCC) and Binutils and the the C/C++ Development Tooling (CDT) plugin. The graphical feature and kernel configurators as well as direct access to the target file system are integrated in the IDE.
Feature, Kernel and File System Configurator
ELinOS makes use of the Eclipse C/C++ Development Tooling (CDT) plugin.
Debugging & Analysis
For developing applications in CODEO, several tools are provided to trace and analyse application behaviour during runtime, monitor system resources and remote debug software on the target system.
The ELinOS toolchain comprises among other QEMU, perf, LTTng, GNU project debugger (GDB) and Valgrind for testing and debugging. The broad variety of tools help examine application functional behaviour diversely.
QEMU sets embedded software developers in the place to set up and run an embedded Linux instance in the development host environment. This makes it more comfortable for developers to build, test and debug a system without the need to deploy software onto a real target. QEMU supports network features.
With perf embedded systems can be evaluated regarding their performance. Perf helps identifying and erasing bottlenecks, thus speeding up embedded systems.
Valgrind is a framework that comes with debugging and profiling tools that – among other functionalities – help prevent erroneous code (e.g., buffer overflows).
Linux Trace Toolkit Next Generation (LTTng) supports developers in finding bugs that are otherwise hard to identify.
For analysis purposes the System Viewer tool is available. It sets you in the place to monitor system resources while running ELinOS on a target system (real or virtualized). System Viewer provides information on basic system setups such as architecture, kernel version and system time and general information on interrupts, processes, IO memory and ports with name and address spaces, loaded kernel modules and used system memory. Furthermore, it shows currently used interprocess communication pipes, active semaphores, shared memory, message queues and used sockets.