TDA4VM: error when using vxCreateImage

Shine

Part Number: TDA4VM

Hello Champs,

Customer used sdk7.3 and met below error message when using vxCreateImage to create image.

MEM: ERROR: Alloc failed with status = 12 !!!
3149.341098 s: VX_ZONE_ERROR:[tivxMemBufferAlloc:80] Shared mem ptr allocation failed
3149.341109 s: VX_ZONE_ERROR:[ownAllocImageBuffer:309] could not allocate memory
3149.341115 s: VX_ZONE_ERROR:[ownGraphAllocateDataObject:923] Memory allocation for data reference failed
3149.341123 s: VX_ZONE_ERROR:[vxVerifyGraph:1989] Memory alloc for data objects failed
3149.341185 s: VX_ZONE_ERROR:[vxVerifyGraph:2098] Graph verify failed

Thanks
Regards
Shine

over 3 years ago

0 Brijesh Jadav over 3 years ago

TI__Guru**** 504815 points

Hi Shine,

Typically vxCreateImage will not allocate buffer memory, unless you are trying to map this buffer in the application space. It looks like it is running out of the memory. What is the size of the image ? How many number of images you are allocating? Can you please provide more information? Have they changed default memory map in SDK to reduce frame buffer size?

Regards,

Brijesh

0 Shine over 3 years ago in reply to Brijesh Jadav

TI__Genius 13655 points

Hi Brijesh,

Thanks for your great support.

1. The size of the image is 3840*1080. He is allocating 1 image.

2. Customer used default memory map in SDK without any change.

3. Customer ran an app code after creating Image. The app code will occupy RAM size (free) on a72. If not he didn't run the app code, the image creation will success. So he wanted to know the relationship between the app code and the image creation.

How to resolve the issue?

Thanks
Regards,
Shine

0 Brijesh Jadav over 3 years ago in reply to Shine

TI__Guru**** 504815 points

Hi Shine,

I did not get, which app core is customer running on A72? Is it some OpenVX example? Why is it using up entire memory?

Essentially, code is not able to find free memory of size 8 to 16MB, so is failing.

Regards,

Brijesh

0 Shine over 3 years ago in reply to Brijesh Jadav

TI__Genius 13655 points

Hi Brijesh,

1. Customer ran their own code on A72, it is not openvx example. The code used most of the memory.

2. Customer wanted to know how to change the default system memory map to resolve the image creation issue.

Thanks
Regards,
Shine

0 Brijesh Jadav over 3 years ago in reply to Shine

TI__Guru**** 504815 points

Hi Shine,

Shine said:
Customer ran their own code on A72, it is not openvx example. The code used most of the memory.

But OpenVX uses its own carved memory. OpenVX uses internally dma-buf framework of Linux for managing buffers and around 512MB memory is reserved for the dma-buf framework. Is customer application also using/allocating memory from this region? If this is case, it needs to be increased.

We can follow instruction given on below link to allocate more memory for dma-buf.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/developer_notes_memory_map.html

Regards,

Brijesh

0 Shine over 3 years ago in reply to Brijesh Jadav

TI__Genius 13655 points

Hi Brijesh,

What memory does the 512MB dma-buf refer to? Does it refer to “DDR_SHARED_MEM”? Customer can't find it in system_memory_map.html.

Thanks
Regards,
Shine

+1 Brijesh Jadav over 3 years ago in reply to Shine

TI__Guru**** 504815 points

Hi Shine,

Yes, DDR_SHARED_MEM region is what i am talking about. This region is defined as below node in k3-j721e-rtos-memory-map.dtsi file.

vision_apps_shared_region: vision_apps_shared-memories {
compatible = "dma-heap-carveout";
reg = <0x00 0xb8000000 0x00 0x20000000>;
};

Regards,

Brijesh

Processors

Processors forum

TDA4VM: error when using vxCreateImage