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.

Linux/TDA2EVM5777: System-link Buffer issue in VSDK3.04, Getting NULL pointer in "bufAddr[0]"

Part Number: TDA2EVM5777

Tool/software: Linux

Hi,

I’m in the process of migrating my application running on TDA2x EVM, from VSDK3.03 to VSDK3.04.

In brief, I have a chain running as shown:

Null_src (A15-Linux) ->  ALg_link(EVE) -> Null_sink (A15-Linux)

While trying to get the input buffers in Null_sink from the Alg link (EVE), using “System_getLinksFullBuffers”, I’m observing that the bufAddr[0] in the System_VideoFrameBuffer received are pointing to Null.

I’m using buffers in in-place mode.

The same application is working well under VSDK3.03, however when it is built under VSDK3.04, this issue is seen.

Can you please provide your inputs to resolve this issue.

 

Thanks in advance,

Regards,

Ranjith Bhide

  • Hi,

    Can you please check the bufType of the buffer got from System_getLinksFullBuffers in NULL_Sink link.
    Inside your alg link running on eve, just check the bufaddr when you receive the input and check the same when you send that buffer.

    Is the alg link is yours or TI?

    Regards,
    Anuj
  • Hi Anuj,

    Thanks for the response.

    This cause of the issue was found.
    There is a new member variable "hlosTranslationDisable" added to structure System_Buffer, which needs to be initialized to FALSE during init. Failing which the Physical-Virtual address translation was not happenning which was causing this issue.

    After setting the hlosTranslationDisable field as FALSE for all the system buffers the issue was resolved.

    Regards,
    Ranjith Bhide