cancel
Showing results for 
Search instead for 
Did you mean: 

Using ThreadX Version 6.1

Gil1
Associate III

Hi All,

I am using ThreadX on an STM32H753. The version of ThreadX being used is 6.1. I use this older version because it is ISO-62304 certified. All is functioning as desired but each time I execute code generation from CubeMX the ThreadX files are overwritten with version 6.4 (not certified). Is there any way I can avoid the update of ThreadX when I regenerate the code from CubeMX?

Thank You,

Gil

1 ACCEPTED SOLUTION

Accepted Solutions
Gil1
Associate III

Issamos,

Thank you for your quick response. I found the Software Packs Component Selector and the STMicroelectronics X-CUBE_AXRTOS-H7 component.

Gil1_0-1761944392804.png

Unfortunately, the only version is 3.3.0. I believe I need to install a previous version of the Azure RTOS expansion package.

Gil1_1-1761944652273.png

But if a previous version is installed it may not be compatible with my version of CubeMX. I believe I have to except this inconvenience.

Gil

View solution in original post

4 REPLIES 4
Issamos
Lead II

Hello @Gil1 

I think you can delete the current version of the X-CUBE-AZRTOS-H7 and download the version that use the ThreadX V6.1. Also, on your .ioc file, you can go to Pinout & configuration -> Software Packs -> Select Components -> open the menu of X-CUBE-AZRTOS-H7 and select the ThreadX version you want:

Issamos_0-1761935785745.png

Sorry for the screenshot (it is not up to date).

Best Regards.

II

Gil1
Associate III

Issamos,

Thank you for your quick response. I found the Software Packs Component Selector and the STMicroelectronics X-CUBE_AXRTOS-H7 component.

Gil1_0-1761944392804.png

Unfortunately, the only version is 3.3.0. I believe I need to install a previous version of the Azure RTOS expansion package.

Gil1_1-1761944652273.png

But if a previous version is installed it may not be compatible with my version of CubeMX. I believe I have to except this inconvenience.

Gil

I think you should test it. If your request is answered, I think it will be better to select the comment that answered your original question as best answer to close this post.

Best Regards.

II

Gil1
Associate III

In this particular project, we are very sensitive to the versions of the development software. Because of this constraint, I do not want to make this change. If a change in versions were acceptable, your solution would be fine. I will mark it so.