📜 ⬆️ ⬇️

RTOS should simplify the development of IoT devices

Keeping in mind that the Internet of Things (IOT) will attract a lot of people who are not qualified developers, Texas Instruments has modified its TI-RTOS, adding features that simplify automated power management and the creation of an IoT endpoint. TI-RTOS v2.12 (latest revision) will help developers maximize battery life in TI SimpleLink and other wireless microcontrollers, while not being experts in hardware programming.

“TI believes that most future microcontroller applications will be IoT compliant,” said IoT ecosystem manager Nick Lethaby in an interview with EE Times. “In addition to the traditional developers of embedded systems, these microcontrollers will use many other people who want to use the power of cloud services in IoT devices. There will be many developers inexperienced in the field of embedded systems, and many who are knowledgeable in this area, but inexperienced in the development of ultra-low-power devices or cloud communications. "

As a result of this change in the composition of the developers, according to TI, the way software development of microcontrollers will also change, Letabi said. He noted that the programming of "bare iron" will give way to applications running on operating systems. When using RTOS, the use of embedded graphical interfaces will decrease as devices such as smartphones and network computing are connected as a means of user interaction and the USB connection is no longer alternative. Connectivity and advanced power management will ensure long battery life, on the other hand, will become an essential feature.

Version 2.12 TI-RTOS addresses these needs by creating all the necessary drivers for cloud connectivity and automating power management processes. TI-RTOS now contains all device drivers for TI MK and stack communication protocols for Wi-Fi, Bluetooth, Smart Zigbee and 6LoWPAN. It also contains protocols for connecting cloud services such as HTTP and the MQTT client, and also supports software updates “over the air.”
')
An integrated power management system is a key feature of the new version. Device drivers and protocol stacks, as well as the user code, interacts with the power supply manager, which manages the MK operation modes, clocking modes, and power domains. This interaction allows the stack or user code to automatically turn on peripheral modules and return them to a low power state when activity ceases. The energy policy manager works as an idle time task in the RTOS, and uses information from the power manager and the real-time clock to put the system to sleep when it is available. The manager's algorithm takes into account the scheduler data, as well as delays associated with entering and exiting each power mode, so that it can determine when sleep is appropriate and automatically wake up the system by the time of the scheduled event.

Source: https://habr.com/ru/post/255445/


All Articles