OCEOS/oceos use

Introduction

OCEOS is provided as an object library, documentation and example source code.
Setup for the use of OCEOS requires the user to prepare the development environment. At a minimum this requires the installation for compilers, debug tool, editors, …etc.

The OCEOS build and test environment requires the following:

1. SPARC Build environment (compiler, linker, libraries, etc.) Download here.
2. ARM Build environment Download here and Download here
3. Debug software tool e.g. OCE’s DMON. Evaluation download.

Content of Customer Release

Documentation/
             OCEOS_User_Manual.pdf   // OCEOS User Manual
Examples/
         AreaDisplay/                // OCEOS project to display sizes of data areas described HERE
         arm_startup/                // Some start up files for Microchip Cortex-M3 and M7 developments boards, used in DEMO projects below
         asw/                        // DEMO project of main OCEOS features
         SampleProject/              // Skeleton project that can be used to start development  
         tut1/                       // This project demonstrates starting tasks with different priorities.
         tut2/                       // This project familiarize the developer with the use a mutexes.
         tut3/                       // This project demonstrates the use of semaphores for task synchronization.
         tut4/                       // This project introduces the use of timer interrupts to start the task.
         tut5/                       // This project introduces the use of data queue with timeouts.
include/                             // OCEOS header files
OCEOS_GCC_LIB/
              liboceos.lib           // OCEOS library that can be linked with application
              README.txt             // Notes

Building the example application

OCE Technology provides sample make files that can be used by application developer. Those files are located in demo projects of Examples folder. If make is called from one of the demo projects, than user requires only to modify variable TOOLCHAIN_PATH in tools_config_arm.mk to point to toolchain folder. User can use make files to build project for one of the supported development board. User requires to modify make files to add own development board. Make file available parameters for ARM:

• Build target: all
• ARM_BUILD=1
• TOOLCHAIN=armclangv6|gcc|segger|iar
• RELEASE=0|1
• MCPU=cortex-m3|cortex-m7
• BOARD=ATSAM3X8E|ATSAMV71Q21
• FPU=0|1
• SAMV71_CONSOLE=0|1

Example:
make all FPU=1 TOOLCHAIN=gcc RELEASE=1 MCPU=cortex-m7 BOARD=ATSAMV71Q21

Make file available parameters for SPARC:

• Build target: all
• TOOLCHAIN=gcc|clang
• RELEASE=0|1
• MREX=1
• BSP=gr716|pm698|gr712rc|gr740|agga4|at697

Example:
make all TOOLCHAIN=clang BSP=gr716
or 
make all TOOLCHAIN=clang BSP=gr716 MREX=1

Drivers Porting Example

TODO How to port project from other ROTS