Azure RTOS with Stm32

Introduction to Azure RTOS with Stm32


1.The STM32 middleware :


The STM32 middleware solution is constructed around Microsoft Azure RTOS MW and other in-house (ST USB, OpenBL) and open source stacks (FreeRTOS, FatFS, LwIP, mbedTLS, LibJPEG). All are integrated and customized for STM32 MCU devices and enriched with corresponding application examples based on STM32 evaluation boards.





2.Microsoft Azure RTOS :

Azure RTOS is a professional grade, highly reliable and market proven middleware suite:

  • Integrated and full featured RTOS. 
  • Industrial grade networking stack: optimized for performance coming with many IoT protocols. 
  • Advanced Flash file system (FS) / Flash translation layer (FTL): fully featured to support NAND/NOR Flash memories.
  • USB Host and Device stacks coming with many classes.
  • Safety pre-certifications (from MSFT): IEC 61508 SIL4, IEC 62304 Class C and ISO 26262 ASIL D
  • Security pre-certifications (from MSFT): EAL4+ for TLS/DTLS, FIPS 140-2 for software cryptographic library

With Azure RTOS complementing the extensive STM32Cube ecosystem providing free development tools, software bricks, and software Expansion Packages, STM32 users can also leverage the rich services of Azure RTOS, which meet the needs of tiny, smart, connected devices.

 



3. Azure RTOS ThreadX Real-Time Operating System :

The ThreadX core provides the common RTOS features, such as management of threads, semaphores, mutexes and SW timers. The block diagram below shows the different functional blocks in the ThreadX core.



4.NETXduo:


Azure RTOS NetX Duo is a dual IPv4 and IPv6 TCP/IP network stack designed specifically for deeply embedded, real-time, and IoT applications. It has various sets of features. Alongside the TCP/IP IPv4/IPv6 network stack, it provides a crypto library implementing the standard crypto and hash methods, and a TLS/DTLS library to support secure network connections.


  • The NetX Duo core offers a full TCP/IP IPv4IPV6 compliant stack with 3 types of API: TCP/IP, UDP/IP and RAW API.
  • The TLS* core implements the secure connection API. Based on both the Crypto core and NetX Duo core, it supports the TLS and DTLS protocols with their different variants. (TLS 1.0 TLS 1.2, TLS 1.3).

It also supports the X509 public signed certificates protocol.

  • Addon protocols are a pre-supported set of network applicative protocols that ease the integration of the networking feature in the end user application. The main supported protocols are the following:

DHCP, DNS, mDNS, HTTP, HTTPS, FTP, TELNET, MQTT, SMTP, POP3, SNTP, SNMP, and so on.

4.1.STM32 Integration:

NetX Duo can run on any networking hardware, such as Ethernet, WiFi modules, cellular modems, and so on. It requires a low-level driver to interact between the physical layer already chosen, and the NetX Duo core requests (initialize, transmit data, receive data).




5.Azure RTOS deployment within STM32 and STM32Cube portfolio :

1/ Install the embedded software packs :





2/Add packs software component :





 
The TLS protocol addresses network security problems such as tampering and eavesdropping between a client and server. When your clients establish a TLS handshake to your API through the custom domain, the security policy enforces the TLS version and cipher suite options your clients can choose to use.

Commentaires

Enregistrer un commentaire

Posts les plus consultés de ce blog

AZURE-RTOS ThreadX in the STM32Cube ecosystem

Image
  ThreadX 1.Blink Led :  step 0 : Prepare project for CubeMX and CubeIDE step1  :blink led 1.Create first thread  :  step2 : Add ThreadX in CubeMX In CubeMX Tab: Software packs Select components Open X-Cube-Azure-H7 Opne RTOS :  Select ThreadX / Core Click OK Step3 : Add ThreadX into CubeIDE project  Configure ThreadX mode Select software packs Select X-Cube-Azure-H7 RTOS ThreadX Save project CTRL+S(this will generate ThreadX files to our project) Selection of TimeBase : TIM6 If  HAL library  don’t have separated  time source the compilation will fail because both libraries want to use SysTick_Handler interrupt . ThreadX basic : ThreadX is called from main.c over  MX_AZURE_RTOS_Init  function. Inside is a call to  tx_kernel_enter  which will initialize ThreadX and start it. Before ThreadX is started. The  tx_application_define  is called where used can allocate his memory, create tasks and other items from ThreadX. After this function ends ThreadX is started.   Basic thread states  Thr
Lire la suite

STM32F7_HAL_ETH_MQTT_CLIENT

Image
  STM33F7 _ FREERTOS _ LWIP _MQTT 1/ Introduction MQTT :   link :   https://azurertosactia.blogspot.com/2022/10/iot.html 2/  Ethernet Network     link :   https://azurertosactia.blogspot.com/2022/10/ethernet.html 3/  STM32H7 _ Ethernet :  link :   https://azurertosactia.blogspot.com/2022/10/stm32h7-eth.html 4/ Configuration Ethernt Freertos  link :  https://azurertosactia.blogspot.com/2022/10/stm32-ethernet.html 5/ Implementation : Added MQTTInerface.c/h files to port paho MQTT library for STM32 HAL + FREERTOS + LWIP Added Socket & Netconn API based port functions for timer and network ** MQTTInterface.h : **  MQTTInterface.c : **  . main.c : **  FreeRTOS.c : Github link :   https://github.com/Belkacem-roukaya/STM32F7_HAL_ETH_MQTT_CLIENT Reference : https://www.eclipse.org/paho/ https://github.com/eclipse/paho.mqtt.embedded-c https://www.instructables.com/id/How-to-implement-embedded-Mqtt-Client-using-W5500-/ http://blog.naver.com/pcppcp454/221380882726 https://blog.naver.com/pcppc
Lire la suite