Page Comparison

...

Anchor10523851052385 Application Code Anchor10344811034481When 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. Anchor10068281006828 \Micrium Anchor10068291006829 \Software Anchor10068301006830 \EvalBoards Anchor10068311006831 \<manufacturer> Anchor10068321006832 \<board_name> Anchor10068331006833 \<compiler> Anchor10068341006834 \<project name> Anchor10068351006835 \*.* Anchor10095341009534   Anchor10068361006836 \Micrium Anchor10068371006837

\Micrium
    \Examples
        \<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 Anchor10095731009573Examples

This sub-directory contains

...

example projects typically using evaluation boards supported by Micriµm.

...

\<manufacturer> Anchor10449791044979

This is the name of the manufacturer of the evaluation board used. The

...

“<” and “>” are not part of the actual name.

...

1044980\<board name> Anchor10449731044973

This is the name of the evaluation board.

...

The “<” and “>” are not part of the actual name.

...

\<compiler>anchor10068471006847

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.

...

1006848\<project name> Anchor10449831044983

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”.

\*.* Anchor10068511006851

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.