We are starting to develop a new hardware platform and are currently evaluating the STM32H7R/S series for the main controller.
The question now is which RTOS is best suited here in terms of long-term support from ST. We're going to use a lot of communication interfaces (USB, Ethernet, external WiFi/BT module, CAN), an RTOS with an integrated communication stack would make our work easier.
Zephyr: High initial training effort, but you get a great framework. The two available H7RS-Eval boards are already supported, but in the video Zephyr 4.1: Status of STM32 support – Erwan Gouriou // Zephyr Meetup Grenoble Mar. 26, 2025 by @Erwan Gouriou from March of this year you can see that Zephyr support for the H7RS is not yet complete. Can anyone give an estimate of the extent to which you can already work with it or how much effort is involved in porting drivers from the H7 to the H7RS that are not yet available? I'm new to Zephyr and can't estimate the effort involved.
ThreadX: Support for Ethernet, USB and flash file systems is included, the AIROC radio modules from Infineon are also supported. But ST seems to be turning away from ThreadX and is focusing on FreeRTOS again. See the post from @Maxime_MARCHETTO here: New strategic directions for STM32Cube
One advantage is the CubeMX integration, so that you get a code template here.
FreeRTOS: I won't touch ST's lwIP port for FreeRTOS again. So maybe I have to look at the FreeRTOS-Plus-TCP stack? According to the "New stratetig direction" ST is working on a port of the UsbX and FileX modules for FreeRTOS. But not for NetX(duo). The CubeMX integration is also an advantage here.
Any opinion on this is welcome and will help us make a decision.
