...
The table below shows the name of µC/CPU files and where they should be placed on the computer used to develop a µC/OS-III-based application. The file names in bold are files you will need to create or modify for your own port.
| Panel | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Panel | ||
|---|---|---|
| ||
|
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
cpu.h
Many CPUs have different word lengths and cpu.h declares a series of type definitions that ensure portability. Specifically, we don’t use the C data types int, short, long, char, etc. at Micrium. Instead, clearer data types are defined. Consult your compiler documentation to determine whether the standard declarations described below need to be changed for the CPU/compiler you are using. You should note that the typedefs below are not all grouped together in cpu.h and also, cpu.h contains additional comments about these data types.
...