When developing an application with a real-time operating system, developers have numerous design decisions to make when starting a project. These design decisions can greatly affect how a system performs, how easy it is to expand an application and even how well a system can tolerate failures.
The following blog series will take an in-depth look at designing a real-time operating system application in a dynamic multiprotocol system (Bluetooth + Proprietary Wireless). It will walk through configuring Micrium OS, discuss task architecture, look in-depth at the Bluetooth and Proprietary Wireless tasks, and look at some safety design patterns.
Table of Contents
Kernel 201: Configuring Micrium OS
Kernel 201: Task Architecture & Communication
Kernel 201: Implementing a Software Watchdog
Kernel 201: Bluetooth Task
Kernel 201: WebBluetooth App
Kernel 201: Proprietary Wireless Task
Kernel 201: UI Tasks
Kernel 201: Blue Gecko Electron Application (Coming soon!)
Kernel 201: Project Resources
The goal of the application discussed throughout the blog series is to run the dynamic multiprotocol application on a Thunderboard Sense 2 board. There is a web application that will communicate over Bluetooth with the Thunderboard using the WebBluetooth API. The Thunderboard will also communicate to a Blue Gecko board via Proprietary Wireless. The image below shows the layout of communication.