Using LwIP stack with raw API on MBED TLS without RTOS (using CubeMX)

Forum|Forum|7 years ago
April 30, 2019
3 replies
2161 views

Hello,

the documentation says that MBED TLS can be implemented without LwIP. If I enable LwIP usage in CubeMX, it only supports NetConn API and therefore requires also FREERTOS to be used...

But I'd like to do it without FREERTOS using raw API for LwIP.

I could probably add LwIP manually, but I need the way for CubeMX not to delete those files when regenerating project.

Any solution, example, doc on this?

Are there any other options for non-RTOS TCP protocol addition to MBED TLS ?

Thanks in advance,

regards,

Bulek.

STM32CubeMX

This topic has been closed for replies.

Best answer by thierry BINIGUER

Hello,

From my understanding, your question deals with several points.

First part is about the MBEDTLS : can Cube MX generate MBED TLS project code without LwIP ? yes, it can.

This is achievable by selecting MBEDTLS Middleware alone. All other Middlewares being disabled.

Second part is about the LwIP : Can Cube MX generate LwIP project code using raw API (without FreeRTOS) ? yes, it can

This is achievable by selecting LwIP Middleware alone. All other Middlewares being disabled.

Note LwIP raw API is enabled through the LWIP configuration : Key Options / Advanced Parameters / Callback - Raw Options

Independantly taken, MBEDTLS/LwIP can be enabled from Cube MX.

Third part is about the usage (or not especially here) of FreeRTOS with MBEDTLS

Can Cube MX generate MBED TLS project code using LwIP raw API ? yes, it can but this is provided FreeRTOS is previously selected.

It is because our cube applications program are natively development over FreeRTOS. Cube MX is aligned with Cube.

As you mention, it is then possible to rework and customize the project.

Note it was verified with Cube MX V5.2.0 and STM32F746NGHx.

Regards

thierry BINIGUERBest answer

ST Employee