Application Code
When Micriµm provides example projects, they are placed in a directory structure shown below. Of course, a directory structure that suits a particular project/product can also be used.
\Micrium
\Software
\EvalBoards
\<manufacturer>
\<board_name>
\<compiler>
\<project name>
\*.*
\Micrium
This is where we place all software components and projects provided by Micriµm. This directory generally starts from the root directory of the computer.
\Software
This sub-directory contains all software components and projects.
\EvalBoards
This sub-directory contains all projects related to evaluation boards supported by Micriµm.
\<manufacturer>
This is the name of the manufacturer of the evaluation board. The “<” and “>” are not part of the actual name.
\<board name>
This is the name of the evaluation board. A board from Micriµm will typically be called uC?Eval?xxxx where “xxxx” represents the CPU or MCU used on the board. The “<” and “>” are not part of the actual name.
\<compiler>
This is the name of the compiler or compiler manufacturer used to build the code for the evaluation board. The “<” and “>” are not part of the actual name.
\<project name>
The name of the project that will be demonstrated. For example, a simple µC/OS-III project might have a project name of “OS-Ex1”. The “-Ex1” represents a project containing only µC/OS-III.
\*.*
These are the project source files. Main files can optionally be called app*.*. This directory also contains configuration files os_cfg.h, os_cfg_app.h and other required source files.