S32G274A - FreeRTOS memory allocation method issue

[Shenghao]

Hi NXP,

There is an build error if I try to select "“support dynamic allocation” setting.

Could you help to confirm the dynamic allocation selection support on FreeRTOS?

Following are my procedure.

Building target: Linflexd_Uart_Ip_Example_S32G274A_M7

If we use “support dynamic allocation” setting, the build will be success.

If we select to “support static allocation”, the build will be failed and come out following error message.

Thanks.

[Shenghao · Accepted solution]

Hi NXP, 

I've derived below information for customer reference.

https://freertos.org/zh-cn-cmn-s/a00110.html
If you need to use "static allocation", configSUPPORT_STATIC_ALLOCATION need to be set as 1, and you will need to use xTaskCreateStatic to create the task and include vApplicationGetIdleTaskMemory() and vApplicationGetTimerTaskMemory() to allocate the memory szie for them.

However, they concernd if they modify the code by themselves, it might impact the Austosar application.

Is this possible? 

Thanks.

[Daniel-Aguirre]

Hi,

Regarding the "configSUPPORT_STATIC_ALLOCATION", this can be modified within Config Tools, as shown below:

And it should automatically, once the code is updated, replace the previous configuration with the newer one.

As for the modifications, given this is FreeRTOS-related (and required by the scheme), we recommend sending this inquiry to FreeRTOS itself, for them to clarify these points. We cannot see any information regarding the impact on Autosar implementation for this scheme. We do apologize.

Please, let us know.

[FreeRTOS_org]

Any function that starts "Application" has to be provided by the application writer - they are basically callbacks.  These two particular functions are described on the FreeRTOS configuration documentation page.