2026-03-05 2:26 AM - last edited on 2026-03-06 1:17 AM by Gyessine
Hello,
all my tools are updated to last ones, and software packages too.
I start an empty project using X Cube FreeRtos 1.5 (just a default task).
Play the soft with debug, and after a few seconds, press "Suspend" button to break the running program.
Then, there are a lot of calls to vPortSetupTimerInterrupt function (port.c) in the call stack.
The tick is by default 1ms and cpu clock to 250Mhz.
Not sure that is normal?
thanks for your help
Laurent
Solved! Go to Solution.
2026-03-12 6:00 AM - edited 2026-03-12 11:54 PM
Dear Lobna,
ZIP File attached for the both project.
So the project done with CubeMX 6.16.1 / CubeIDE 2.0.0 / FreeRTOS 1.4 works normally.
The same project done with CubeMX 6.17.0 / CubeIDE 2.1.0 / FreeRTOS 1.5 doesn't work (see bitmap in first message).
The board is an user board, using the STM32H533CET processor. I don't think the board is the source of issue, because the project use only the default FreeRTOS task and no peripherals is used, and project CubeMX 6.16.1 works on this board, and the same project with CubeMX 6.17.0 doesn't work.
Best regards,
Laurent.
2026-03-12 6:12 AM - edited 2026-03-12 6:13 AM
Hello @lclor ,
If I may intervene here.
@lclor wrote:here is the download link for the projects : https://we.tl/t-Kxp0JD2RrT
It's not recommended to post a link to your project but rather to zip the project and attach it here in the post or use GitHub and share the link. Other platforms such as Google drive and others are not recommended for use.
2026-03-16 11:58 PM
Dear Lobna,
Do you have some news about the trouble?
Thanks in advance,
Best regards,
Laurent
2026-03-30 10:46 PM
The default comes from STM32CubeIDE, a ticket is opened.
2026-04-03 4:30 AM
Dear @Iclolor
As you know After investigation, the execution flow of the application is correct, and the issue lies only in the representation of the call stack in the debugger. For internal tracking, the opened ticket number is: CDM0061147
BR
Lobna
2026-04-03 4:38 AM
2026-04-03 5:47 AM
Could you please indicate which ticket you are referring to?
After an internal discussion with @lobna , it seems you had a private discussion when @lobna shared with you the ticket number.
Meanwhile, I need to unmark your post and mark the post of @lobna as solution as she's the one that worked on the case and provided the answer.
Thank you for your understanding.