• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 457 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM5708: VPDMA firmware versions

Nicholas DiNino
Prodigy 240 points
Part Number: AM5708

From Customer:

We're still trying to understand why the video port hardware is causing L3 interconnect errors by accessing the GPMC subsystem every time we experience an HSYNC which causes our VPDMA reload descriptor to fire. In this investigation, I've found that there's more than one version of VPDMA firmware which can be loaded.

 What's the difference between the VPDMA firmware version 1B8 and version 288?

Both version 1B8 and 288 firmware are present in the TI PDK version 1.0.5 for the AM57xx parts but it's unclear why there's two different versions at all. All of the VPDMA firmware loading functions appear to let the caller decide which firmware is desired but default to using the 1B8 version. The firmware byte stream is all that we're provided with, the PDK does not appear to have source code for the VPDMA firmware, and the byte streams are quite different looking.

Currently we are using the 1B8 firmware for multiple projects. It works fine on ourproducts using AM571x and AM572x. We are only having issues with AM570x.

  • 0
    TI__Guru**** 393215 points
    What SDK is this - Linux or RTOS?
  • 0 in reply to Biser Gatchev-XID
    TI__Prodigy 240 points
    Biser,

    *Update* We control the VPDMA via TI RTOS on the M4 core. I deleted my incorrect post.

    Regards, Nick
  • 0 in reply to Nicholas DiNino
    TI__Prodigy 240 points
    Team,

    The customer was able to solve the problem after finding an issue in their code. Thank you for the support.



    I've found the issue we were having with the VPDMA causing L3 Interconnect access errors. It was our M4 code's fault, our code was not setting up the VPDMA Outbound data descriptor correctly. The VPDMA was in fact doing exactly what we told it to do and then causing the L3 Interconnect errors.

    We had set the "Write Descriptor" VPDMA data descriptor bit when we do not need or want this functionality and because of this the VPDMA was attempting to write out a new Inbound descriptor to within the GPMC's memory space.

    Using either the 1B8 or the 288 VPDMA firmware resulted in the same problem. Fixing our descriptor setup solves the problem and we'll continue to use the 1B8 firmware version as it's working so far for us.

    You can feel free to close the E2E question.
    Thanks for your help!