Problems with stm32f103zet6 using stm2cubeIDE to build freertos projects

[ZnMnCr]

When I chose to use stm32cubeide to create a new rtos project for zet6, this is what I did:

Also select the V2 version of freertos and leave the rest as defaults：

After selecting Generate Project and compiling, I am having problems:

Description Resource Path Location Type
fatal error: freertos_mpool.h: No such file or directory cmsis_os2.c /zet6RTOS/Middlewares/Third_Party/FreeRTOS/Source/CMSIS_RTOS_V2 line 33 C/C++ Problem

 

and If I choose to comment out these two header files, it tells me that systick is undefined

How should this be resolved? Thanks.

 

 

 

[STTwo-32]

Hello @ZnMnCr 

You can't comment both including line since you need them to make some functions work.

You just have to check your paths and include the necessary paths for those two files. 

Best Regards.

STTwo-32 

[ZnMnCr]

When I managed to find the two header files and add them to the CMSIS_RTOS_V2 directory of this project and build it. That still had a lot of problems, and new errors in the newly added freertos_os2.h，

Also, the stm32cubeide version is:

STM32CubeIDE

Version: 1.16.0

Build: 21983_20240628_1741 (UTC)

OS: Linux, v.5.15.0-117-generic, x86_64 / gtk 3.24.20

Java vendor: Eclipse Adoptium

Java runtime version: 17.0.11+9

Java version: 17.0.11

Description Resource Path Location Type
#error "Definition INCLUDE_xTaskGetCurrentTaskHandle must equal 1 to implement Thread Management API." freertos_os2.h /zet6RTOS/Middlewares/Third_Party/FreeRTOS/Source/CMSIS_RTOS_V2 line 134 C/C++ Problem

Description Resource Path Location Type

#include expects "FILENAME" or <FILENAME> freertos_os2.h /zet6RTOS/Middlewares/Third_Party/FreeRTOS/Source/CMSIS_RTOS_V2 line 31 C/C++ Problem

and The system can't find this header file：

 

 

[ZnMnCr]

 

If  I change the Firmware Package Version,the project compiles and passes.

 

[STTwo-32]

Hello @ZnMnCr @ANorm @APuht 

After testing this behavior, I've been able to reproduce it on my side and I've escalated to the concerned team for correction on the coming versions of CubeF1 and CubeMX (under internal ticket number 189410). As a temporary workaround, you may have to use the previous version of the CubeF1 or use FreeRTOS with CMSIS V1. 

Update: This issue has been solved on the STM32CubeMX V6.13.0. Thank you so much for escalating this.

Best Regards.

STTwo-32