Skip to main content
Associate
July 27, 2024
Question

STM32F746 LWIP + FreeRTOS CMSIS V2

  • July 27, 2024
  • 6 replies
  • 1953 views

Hi,

I'm using an STM32F746G-DISCO board and I'm just trying to build a build a simple project with LWIP and FreeRTOS using CMSIS V2 however after enabling the minimum hardware using CubeMX I am unable to get any ping replies from the board. If I use CMSIS V1 for the config, then the board responds with ping.

The reason why I want to get this working with V2 is that I'm planning to use TouchGFX in my project and when creating project using the TouchGFX, it defaults to CMSIS V2 and I've not seen any option to change that. I've tried generating project using TouchGFX and then changing it using CubeMX to CMSIS V1 however then the project falls apart and it seems like HAL_Delay which is used in some of the initialisation functions stops working.

I'm using CubeIDE 1.16.0.

Attaching the project for reference.

6 replies

ST Employee
August 13, 2024

Hello @marcinq ,

I confirm this issue you are facing with CMSIS V2 as I'm able to reproduce it with the shared IOC file.
This case was reported internally as it needs more investigation.ticket number 188613(for internal reference only)
I'll update you with the status as soon as possible.
thank you for pointing this out.
Regards

marcinqAuthor
Associate
August 15, 2024

Hello STea,

Thanks for your response. I will await further updates.

 

Marcin

alister
Senior III
August 22, 2024

https://community.st.com/t5/stm32cubemx-mcus/bugs-caveats-misc-fixes-stm32h7s-cube/td-p/710992 describes a bug-fix re CMSIS v2 with lwIP task stack sizes on the STM32H7S/Rx.

Visitor II
April 3, 2025

Hi,

can you send your file if its resolved, me also facing with same issue

Associate II
July 25, 2025

Hi there,

I am also facing this issue. (OS is not being used in lwip section when freertos cmsis v2 is selected, however works with v1). 

Has it been solved? 

 

Thank you,

Associate II
July 25, 2025

Hello marcinq,

Hi STea,

I am also facing this issue.

Were you able to resolve this issue or did you find a work around? Please share if you did.

also @STea has this bug been resolved?

 

Thank you,