• State Resolved
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 191 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM2612: Safety function

Lu Bruce
Prodigy 40 points

Part Number: AM2612

Hi TI experts,

I can find the VBUSM taget timeout diagnostic routine in the latest SDK version (11.00.00.28), but I haven't found the implementation method of the VBUSP taget timeout diagnosis. Could you please confirm how this diagnosis should be implemented?

 

image.png

  • 0
    TI__Expert 5956 points

    Hi Lu Bruce,

    Apologies for the late response here. We're working on this, please expect a response by 22/1.

    Thanks and Regards,

    Sahana

  • 0
    TI__Expert 5956 points

    Hi Lu Bruce,

    Lu Bruce said:
    I can find the VBUSM taget timeout diagnostic routine in the latest SDK version (11.00.00.28), but I haven't found the implementation method of the VBUSP taget timeout diagnosis.

    This is because VBUSP target timeout is a Hardware diagnostic as mentioned in the following table in the Safety Manual. The timeout is already implemented in the hardware, and no software configuration is needed for it.

    Hence, you wouldn't find an SDL routine corresponding to this diagnostic.

  • 0
    Prodigy 40 points

    Hi Sahana,

    May I ask if there is a register that can monitor the timeout status of VBUSP.

    By the way, the definition of the register (50D181xx) was not found in document spruj94a, but it can be found in the latest SDK 11.0.0.28. Hasn't document spruj94a been updated yet?

     

    Regards

    Bruce

  • 0 in reply to Lu Bruce
    TI__Expert 5956 points

    Hi Bruce,

    Apologies for the late response as there was a holiday in India.

    Lu Bruce said:
    May I ask if there is a register that can monitor the timeout status of VBUSP.

    I do not see any register to monitor this timeout, let me get back to you by 28/1 on how this is signaled to the Master.

    Lu Bruce said:
    By the way, the definition of the register (50D181xx) was not found in document spruj94a, but it can be found in the latest SDK 11.0.0.28. Hasn't document spruj94a been updated yet?

    I've raised a JIRA internally to have this updated.

    Regards,

    Sahana

  • 0 in reply to Sahana H G
    Prodigy 40 points

    Hi Sahana,

    Thanks for your reply.

    Please inform me if the document is updated.

    Best Regards,

    Bruce

  • +1 in reply to Lu Bruce
    TI__Expert 5956 points

    Hi Bruce,

    Regarding your question about monitoring VBUSP timeout status:

    Lu Bruce said:
    May I ask if there is a register that can monitor the timeout status of VBUSP.

    The VBUSP target will issue a timeout after 256 cycles of bus stall from the start of the access. When this timeout condition occurs, it results in a data abort exception. Since the timeout triggers a data abort, the timeout condition can be detected through the ARM Cortex-R5F exception handling mechanism by reading the fault status registers within your data abort exception handler:

    Relevant CP15 Registers:

    DFSR (Data Fault Status Register) - CP15 c5, 0, c0, 0

    Contains the fault status information and fault type
    Access via: MRC p15, 0, <Rt>, c5, c0, 0
    DFAR (Data Fault Address Register) - CP15 c6, 0, c0, 0

    Contains the virtual address that caused the data abort
    Access via: MRC p15, 0, <Rt>, c6, c0, 0

    Lu Bruce said:
    Please inform me if the document is updated.

    Will do.

    Thanks and Regards,

    Sahana