• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 597 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-DRA7X: Application killed by OOM due to lack of DRM memory with VISION SDK 03_02_00_00

Divya B M
Prodigy 100 points
Part Number: PROCESSOR-SDK-DRA7X


Hello,

I am trying to run an application that requires around 300MB of DRM memory on Jacinto 6 with an image built using Vision SDK 03_02_00_00(Linux OS).

This application will be using components like IVA that will be accessing DRM memory.The following E2E post was followed for enabling IPUMM:

https://e2e.ti.com/support/arm/automotive_processors/f/1020/p/608999/2256824 

Running the application is triggering OOM killer. 

None of the memory numbers in VISION SDK have been changed so far in the VISION SDK installation..

1) What are the files that needs to be modified in order to increase the DRM memory available in VISION SDK?

2) Will there be any module that will be affected by increasing the DRM memory?

Regards,

Divya

  • 0
    TI__Genius 14650 points

    Hi Divya,

    There are many reserved memory sections for VSDK. If your use-case uses lesser memory, you can decrease the shared region size and other reserved memory section. The changes that are needed are:

    1. VSDK: Decrease the 'SR1_FRAME_BUFFER_SIZE' entry in the file apps/build/<platform_id>/mem_segment_definition_linux.xs to reduce the shared-memory size. In the same file other reserved-mem entries are present (such as SR2), and can be resized as required.

    2. Linux Kernel: In the device-tree file update the entry 'vsdk_sr1_mem' to reflect the updated shared-memory size. The 'reserved_mem' node in the device-tree lists other entries which are reserved.

    It's important that the entries in VSDK and device tree in kernel are in sync, and that the use-case running on VSDK doesn't use more memory that the SR size allocated.

    Regards
    Shravan