Table C-2 he table below shows the source files used in both kernels. Note that a few of the files have the same or similar name.
Panel | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
|
...
|
...
os_prio.c
...
(9)
...
os_mbox.c
...
|
...
|
...
|
...
|
...
|
...
|
...
Table C-2 µC/OS-II and µC/OS-III files
...
Panel | ||
---|---|---|
| ||
(1) |
...
µC/OS-II does not have this file, which is now provided for convenience so you can add application hooks. You should copy this file to the application directory and edit the contents of the file to satisfy your application requirements. |
...
(2) |
...
did not exist in µC/OS-II. This file needs to be added to a project build for µC/OS-III. |
...
(3) |
...
In µC/OS-II, all configuration constants were placed |
...
in |
...
in |
...
contains application-specific configurations such as the size of the idle task stack, tick rate, and others. |
...
(4) |
...
In µC/OS-III, |
...
is reserved for configuring certain features of the kernel. For example, are any of the semaphore services required, and will the application have fixed-sized memory partition management? |
...
(5) |
...
These are the port files and a few variables and functions will need to be changed when using a µC/OS-II port as a starting point for the µC/OS-III port.
The name of |
...
(6) In µC/OS-III, |
...
(7 |
...
) |
...
The code to determine the highest priority ready-to-run task is isolated in µC/OS-III and placed in |
...
( |
...
8) µC/OS-II provides message mailbox services. A message mailbox is identical to a message queue of size one. µC/OS-III does not have these services since they can be easily emulated by message queues. |
...
( |
...
9) Management of messages for message queues is encapsulated in |
...
( |
...
10) The statistics task and its support functions have been extracted out of |
...
( |
...
11) All the µC/OS-III variables are instantiated in a file called |
...
( |
...
12) In µC/OS-III, the size of most data types is better adapted to the CPU architecture used. In µC/OS-II, the size of a number of these data types was assumed. |
...
( |
...
13) In µC/OS-II, the main header file is called ucos_ii.h. In µC/OS-III, it is renamed to |