NETXDUO

 Nx_MQTT_Client application description :


This application provides an example of Azure RTOS NetX/NetXDuo stack usage. It shows how to exchange data between client and server using MQTT protocol in an encrypted mode supporting TLS v1.2 .


The main entry function tx_application_define() is called by ThreadX during kernel start, at this stage, all NetX resources are created. 

  • A NX_PACKET_POOLis allocated
  • A NX_IP instance using that pool is initialized
  • The ARP, ICMP, UDP and TCP protocols are enabled for the NX_IP instance
  • A DHCP client is created.
The application then creates 3 threads with the different priorities:

AppMainThread (priority 10, PreemtionThreashold 10) : created with the TX_AUTO_START flag to start automatically.

AppMQTTClientThread (priority 3, PreemtionThreashold 3) : created with the TX_DONT_START flag to be started later.

AppSNTPThread (priority 5, PreemtionThreashold 5) : created with the TX_DONT_START flag to be started later


** The AppMainThread starts and perform the following actions: 

  • creates a dns_client with USER_DNS_ADDRESS (default value defined IP_ADDRESS(1, 1, 1, 1) on app_netxduo.h.
  • starts the DHCP client
  • waits for the IP address resolution
  • resumes the AppSNTPThread

** The AppSNTPThread, once started:

  • it connects to an SNTP server to get the current time.
  • resumes the AppMQTTClientThread


** The AppMQTTClientThread, once started:

  • creates an mqtt_client

  • connects mqtt_client to the online MQTT broker; connection with server will be secure and a tls_setup_callback will set TLS parametres. By default MQTT_PORT for encrypted mode is 8883

  • mqtt_client subscribes on a predefined topic TOPIC_NAME “Temperature” with a Quality Of Service QOS0
  • depending on the number of message “NB_MESSAGE” defined by user, mqtt_client will publish a random number generated by RNG. If NB_MESSAGE = 0, it means that number of messages is infinitely.
  • mqtt_client will get messages from the MQTT broker and print them.





link 2: https://github.com/STMicroelectronics/x-cube-azrtos-f4/tree/main/Projects/STM32F429ZI-Nucleo/Applications/NetXDuo/Nx_MQTT_Client



Commentaires

Enregistrer un commentaire

Posts les plus consultés de ce blog

Azure RTOS with Stm32

Image
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
Lire la suite

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