rt-thread project

[Jan27]

I created project in stmcube32mx for h5 microcontroller and it works if I manually replace bl main to bl entry

in file startup_stm32h563zitx.s.

If this manual replacing is a bug or on purpose?

Jan

[KnarfB]

Never heard of such a purpose. 

What does " it works" (or not) mean precisely? Linker errors? 

What version of STM32CubeMX and H5 firmware are you using?

Middlewares? 

Maybe you can post your .ioc file.

hth

KnarfB

 

[Jan27]

Thank you for noticing my post.

After generating the project I noticed that in the file startup_stm32h563zitx.s (discovery board) still

there is bl main. I think it should be bl entry.

Program compiles in every situation but without changing to entry tasks don't run.

/* Call the application's entry point.*/

/* bl main */

bl entry

[lobna]

@Jan27  

Could you please provide the version of CubeMX and CubeIDE you are using?

I generated the project using your .ioc file with CubeMX version 6.16 and STM32CubeIDE version 1.19. I also tested it with bl main, and the execution runs without any issues.

Could you please specify the exact problem you encountered?

BR

Lobna

[KnarfB]

This seems to be a very rt-thread specific topic and you might find specific help in their forum. 

hth

KnarfB

[Jan27]

Ok, it works for me now but I would expect that ST did something that it worked without manual adjusting

or clearly wrote what to do.

Jan

[lobna]

Dear @KnarfB @Jan27 

I will escalate this issue internally to enhance the ST documentation. Meanwhile, you may implement the recommended solution in the file Middlewares\Third_Party\RealThread_RTOS_RT-Thread\src\components.c when using the GCC compiler.
Specifically, at line 159:
/* Add -eentry to the arm-none-eabi-gcc linker arguments */

BR

Lobna

 

[Jan27]

I see, thank you

Jan