• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 332 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.

DM8618 RDK framework Registers reading

Amir Gatt
Prodigy 250 points


Hi,

 

I am working on the DM8618 using RDK framework, and would appreciate your help with the following:
1. I would like to have the capability to read used parameters from registers in VPSS and HDVICP.  When I Examine RDK code, it seems that all GET status commands from M3 return software parameters only, and not the parameters which are used in registers. I wonder why it was done this way, and how to modify the code so that the real hardware registers are returned.

2. I am also trying to understand how does the errors reported from M3 cores to the ARM A8 processor, it seems that eventually only pass/fail is transferred but not the reason for failures, is that true?

 

Thanks

Amir Gatt

  • 0
    TI__Guru 59700 points

    I would like to have the capability to read used parameters from registers in VPSS and HDVICP.  When I Examine RDK code, it seems that all GET status commands from M3 return software parameters only, and not the parameters which are used in registers. I wonder why it was done this way, and how to modify the code so that the real hardware registers are returned.

      -- If you would like to read the value of specific registers you could use the mem_rdwr utility that is part of DVR RDK package .There are over 100,000 registers in HDVICP & HDVPSS .Is there a particular register value you are looking for to be returned.

    I am also trying to understand how does the errors reported from M3 cores to the ARM A8 processor, it seems that eventually only pass/fail is transferred but not the reason for failures, is that true

     - Yes this is correct. Unfortunately there is no programmatic way to get the reason for the failure. THe reason for the error are usually printed on the console so if you looking for debugging the reason for failure this may be useful..