diff options
| author | TiejunZhou <[email protected]> | 2021-06-07 11:45:38 +0800 |
|---|---|---|
| committer | GitHub <[email protected]> | 2021-06-07 11:45:38 +0800 |
| commit | a891c3f9033b80bad838ab3e96e83e049981e175 (patch) | |
| tree | 26f448b508a5cc9cd0bfa775c465273fa692decb /README.md | |
| parent | f5056f4923410b99c87ab909d24ae77bf41923b6 (diff) | |
| parent | db7a3972a8bc3db98e33e48c38ba9927123e5083 (diff) | |
Merge pull request #112 from azure-rtos/freertos-readmev6.1.7_rel
FreeRTOS readme
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -85,6 +85,10 @@ Each official release (preview or GA) will be tagged to mark the commit and push Azure RTOS provides OEMs with components to secure communication and to create code and data isolation using underlying MCU/MPU hardware protection mechanisms. It is ultimately the responsibility of the device builder to ensure the device fully meets the evolving security requirements associated with its specific use case. +# Adaptation layer for ThreadX + +Azure RTOS ThreadX is an advanced real-time operating system (RTOS) designed specifically for deeply embedded applications. To help ease application migration to Auzre RTOS, ThreadX provides [adaption layers](https://github.com/azure-rtos/threadx/tree/master/utility/rtos_compatibility_layers) for various legacy RTOS APIs (FreeRTOS, POSIX, OSEK, etc.). + # Licensing License terms for using Azure RTOS are defined in the LICENSE.txt file of this repo. Please refer to this file for all definitive licensing information. No additional license fees are required for deploying Azure RTOS on hardware defined in the LICENSED-HARDWARE.txt file. If you are using hardware not defined in the LICENSED-HARDWARE.txt file or have licensing questions in general, please contact Microsoft directly at https://azure-rtos.ms-iot-contact.com/ |