μC/USB-Device uses some RTOS abstraction ports to interact with the RTOS. Instead of being a simple wrapper for common RTOS service functions (TaskCreate(), SemaphorePost(), etc...), those ports are in charge of allocating and managing all the OS resources needed. All the APIs are related to the μC/USB-Device module feature that uses it. This offers you a better flexibility of implementation as you can decide which OS services can be used for each specific action. gives an example of comparison between a simple RTOS functions wrapper port and a features-oriented RTOS port.
Because of the features oriented RTOS port design, some μC/USB-Device modules will need their own OS port. These modules are listed here:
- μC/USB-Device core layer
- Audio Class
- Human Interface Device Class (HID)
- Mass Storage Class (MSC)
- Personal Healthcare Device Class (PHDC)
Moreover, all the demo applications for each USB class that Micrium provides interact with the RTOS. The demo applications do not benefit from an RTOS port. Therefore, if you plan to use them with an RTOS other than μC/OS-II or μC/OS-III, you will have to modify them.
summarizes the interactions between the different μC/USB-Device modules and the RTOS.