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.

TDA4VM: Interrupt Router register access

Part Number: TDA4VM
Other Parts Discussed in Thread: TDA4VH

Dear TI Support Team,

I am I am working with the TI TDA4 J784S4 SoC and referring to the attached SPRUJ52D Technical Reference Manual (TRM). For Interrupt Router configuration, is it possible to access the router registers( eg: for reading the interrupt enable bit) directly without using Tisci client APIs? Kindly check and let me know if R/W access without Tisci is possible for the interrupt router registers? If possible are there any safety concerns to know about?

If it is not possible, then is there any way we could get/retrieve the register configuration via Tisci ?

  • Hi,

    To be more specific, i am developing diagnostics for the NAVSS Interrupt Router. I understand that TISCI manages resource allocation and access control for this module.

    But for implementing diagnostics, i would like to understand the following:

    1. Is it possible or supported to directly access the NAVSS interrupt router registers (e.g., at 0x310E0000) from the application processor, bypassing TISCI?
    2. Are these registers firewalled or restricted to DMSC firmware access only?
    3. From a functional safety perspective, would direct register access be discouraged even if technically possible?
    4. If direct access is blocked, is there a TISCI message or query API that allows retrieving the current routing configuration for verification purposes?

  • Hello,

    For Interrupt Router configuration, is it possible to access the router registers( eg: for reading the interrupt enable bit) directly without using Tisci client APIs?

    To do interrupt routing you definitely need SCICLIENT API and DM has to serve this SCICLIENT request.  

    Direct manipulation of interrupt routing registers are not advisable, the whole system might break since DM will fail to know which core is using which interrupt.

    Regards

    Tarun MUkesh

  • Hi Tarun,

    Thanks for the feedback and I understand your point. 

    I am checking with you, if register access is possible from the kernel level, for performing some diagnostic tests. Like for eg: reading back the register. In these scenarios we will not be modifying the register but just checking the values. In such a case, is it possible to access the router registers without using SCICLIENT API?

    I have a follow-up question as well. If we can only proceed using SCICLIENT APi's, is there any way to retrieve the router register configuration through SCI? 

    Kindly get back to me as soon as possible. Appreciate the quick response.

    Thankyou!

  • Hello,

    I have a follow-up question as well. If we can only proceed using SCICLIENT APi's, is there any way to retrieve the router register configuration through SCI? 

    what exactly you want to do with reading back router register configuration from kernel level ? what kind of diagnostic tests on interrupt routers ?

    Even if you read router registers it will not be clear , how are you planning to read it ?

    Regards

    Tarun Mukesh

  • Hi Tarun,

    We are planning to implement the following diagnostics mentioned in TI's safety manual (SFFS462_J784S4_TDA4AP_TDA4VP_TDA4AH_TDA4VH_SafetyManual_v0.99.pdf):

    e2e.ti.com/.../5315.SPRUJ52-_2D00_-J84S4-AM69A-TRM.pdf

    • INTR1 - Software Read Back of Written Configuration
    • INTR2 - Periodic Software Read Back of Static Configuration Registers
    • INTR3 - Software Test of Basic Functionality

    For implementing these diagnostics, we need access to register configuration. Which is why I am asking if there is any way to access the router configuration through SCI client?

    Also, is DM reading back the register confirming the configuration before sending the Acknowledgement to the TISCI?

    In this scenario, would it be okay to just validate the acknowledgement from the SCI client to ensure safety?

  • Hello Adithya,

    Which is why I am asking if there is any way to access the router configuration through SCI client?

    My understanding is only DM core can access these registers but not any other cores .

    May be you can try reading the registers what you want to do readback then if exception comes it is protected else you could read 

    DM reading back the register confirming the configuration before sending the Acknowledgement to the TISCI?
    Sciclient_rmProgramInterruptRoute is API which routes the interrupts .so let say if any interrupt number is routed already and try to do it again then it will fail , that confirms it will read the numbers router earlier before proceeding to assign.
    Regards
    Tarun Mukesh
  • Hi Tarun,

    Thanks for valuable and quick response. I have understood your points.

    I have one more doubt regarding this : For doing basic functionality test for the Interrupt Router without accessing the register how can i verify the functionality? Can i use the acknowledgement message from the SCICLIENT to confirm that a successful routing has been done?

    Regards,

    Adithya G B

  • Hello Adithya,

    Sorry for the delay due to holiday in TI India.

    I have one more doubt regarding this : For doing basic functionality test for the Interrupt Router without accessing the register how can i verify the functionality? Can i use the acknowledgement message from the SCICLIENT to confirm that a successful routing has been done?

    Yes you can consider acknowledgement from sciclient as successful routing if done correctly. sciclient api's take care of it internally for you need not worry.

    Regards

    Tarun Mukesh