Versions Compared

Version Old Version 2 New Version Current
Changes made by

Former user

WES Admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The figure below shows the µC/OS-III architecture and its relationship with other software components and hardware. When using µC/OS-III in an application, the user is responsible for providing application software and the µC/OS-III configuration sections.

Panel
borderWidth0
titleµC/OS-III Architecture

Image Added


Panel
bgColor#f0f0f0

(1) The port developer is responsible for providing the µC/OS-III CPU Specific portion. A µC/OS-III port consists of writing or changing the contents of four kernel-specific files: os_cpu.h, os_cpu_a.asm, os_cpu_a.inc and os_cpu_c.c.

(2) A port also involves writing or changing the contents of two CPU specific files: cpu.h and cpu_a.asm. cpu_core.c is generally generic and should not require modifications.

(3) A Board Support Package (BSP) is generally necessary to interface µC/OS-III to a timer (which is used for the clock tick) and an interrupt controller.

(4) Some semiconductor manufacturers provide source and header files to access on-chip peripherals. These are contained in CPU/MCU specific files. You generally don’t need to modify any of these and thus, you can use them as-is.

Porting µC/OS-III is quite straightforward once the subtleties of the target processor and the C compiler/assembler are understood. Depending on the processor, a port consists of writing or changing between 100 and 400 lines of code, which takes a few hours to a few days to accomplish. The easiest thing to do, however, is to modify an existing port from a processor that is similar to the one intended for use.

...