Is there a difference between TX_APP_MEM_POOL_SIZE in the app_azure_rtos_config.h and APP_BYTE_POOL_SIZE in app_threadx.h when using ThreadX?

[GreenGuy]

I have created an application using CubeMX inside CubeIDE and setting the ThreadX memory pool size in CubeMX sets the value generated in the app_azure_rtos_config.h. CubeMX also generates app_threadx.c and app_thread.h, but in app_threadx.h most examples show a #define APP_BYTE_POOL_SIZE inside the USER CODE BEGIN PD section.

Should these values in two different places be the same?

And should this be best accomplished by including app_azure_rtos_config.h in the app_threadx.h file and defining the APP_BYTE_POOL_SIZE as TX_APP_MEM_POOL_SIZE with a #define?

[Haithem Rahmani]

Hi @Community member​ ,

Could you please provide more details on which STM32 product you are working and which Azure RTOS version you are using?

regards

Haithem.

[GreenGuy]

STM32H743 - Specifically STM32H743i-EVAL board

Azure RTOS STM32H7 2.1.0

Note: I tried 3.0.0 but so many things were broken that I fell back to 2.1.0

[Haithem Rahmani · Accepted solution]

Hi @Community member​ ,

the "APP_BYTE_POOL_SIZE" define is useless, it was removed with the 3.0.0.

Sorry for any inconvenience it may have caused.

regards

haithem.

[GreenGuy]

Ah I see. And the TX_APP_MEM_POOL_SIZE set in CubeMX is being pulled in by app_azure_rtos.c and that is all the is needed and during the App_ThreadX_Init(), the memory_ptr is then pointing to that pool.

Thx