cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with stm32f103zet6 using stm2cubeIDE to build freertos projects

ZnMnCr
Associate II

When I chose to use stm32cubeide to create a new rtos project for zet6, this is what I did:ZnMnCr_0-1724505961850.png

ZnMnCr_1-1724506047585.png

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

ZnMnCr_2-1724506066821.png

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

ZnMnCr_3-1724506183663.png

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

ZnMnCr_4-1724506230864.png

How should this be resolved? Thanks.

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
STTwo-32
ST Employee

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. 

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

8 REPLIES 8
STTwo-32
ST Employee

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 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

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

ZnMnCr_0-1724547572648.png

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

ZnMnCr_1-1724547595982.png

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

ZnMnCr_2-1724547831368.png

and The system can't find this header file:

ZnMnCr_3-1724547874734.png

 

 

 

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

ZnMnCr_5-1724548173822.png

 

What is the firmware version that you have used before ?

Best Regards.

STTwo-32 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

I used the latest available version before.

Thanks. I just encountered the same problem. I'm glad that I found your solution.

I also confirm the problem. In version 1.8.6 for the stm32f103c8t6 microcontroller using Freertos, the project does not build with the same error. In version 1.8.5 the project is assembled without problems

STTwo-32
ST Employee

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. 

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.