Kernel 201: Designing a Dynamic Multiprotocol Application with Micrium OS
06/165/2019 | 08:07 PM
Introduction
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.
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.
Blog Posts
Micrium OS
thank you
0
Hello, according to your introduction, I successfully ran the Kernel 201 program on Thunderboard board。Now I'm going to change the SDK to the latest version gecko_sdk_suite v2.7,After compiling and downloading, the program can run, and bluetooth finds Kernel 201. After clicking the connection, an error occurs, and the next interface cannot be entered。The new SDK does not have RTCC, and changing to sl_sleeptimer does not solve the problem。Could you tell me what the problem is?
0
Hello Steven,
Significant changes were made to certain components of the SDK after this example was created.
I would recommend that you follow the SDK requirements documented in the Project Resources page.
Updating to the latest SDK may require a rework of the examples.