• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 34 subscribers
  • Views 875 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.

DS90UB953-Q1: ASIL Level for DS90UB953-Q1 and DS90UB954-Q1

Hao Wang14
Expert 4415 points
Part Number: DS90UB953-Q1

Hi Team,

When DS90UB953-Q1 and DS90UB953 are used for camera, can it guarantee ASIL B requirements?

Thanks and Best Regards!

Hao

  • 0
    TI__Guru** 103215 points

    Hello Hao,

    ASIL is a system level requirement - for more discussion on functional safety topics please send a message internally 

    Best Regards,

    Casey 

  • 0 in reply to Casey McCrea
    Prodigy 70 points

    hi Casey,

    Thanks for your reply.

    The question above is raise by me(thanks Hao for posting it on E2E). And the details of the question are as follows,

    Assuming the camera-related pipeline is "Sensor-> Serializer(DS90UB953) -> Deserializer(DS90UB954) ->Host", both output signal of Sensor and input signal of Host are compliant with MIPI (Simplified to "Payload data +CRC").

    1. Is there a decoding and encoding operation for CRC in 953 and 954? If so, what are the operations?

    2. Can them be configured to decode CRC of signal from Sensor on Host side only? If so, how to configure them?

    Bset Regards,

    xiaowei

  • 0 in reply to xiaowei duan
    TI__Guru** 103215 points

    Hello Xiaowei,

    953 and 954 both check the CRC for each long packet received and can flag an error if the CRC does not match the data, but they do not alter the CRC. The CRC will be retained in the output of 954 as well so that the SoC CSI-2 receiver can do a check per the MIPI standard. 

    Best Regards,

    Casey 

  • 0 in reply to Casey McCrea
    Prodigy 70 points

    Hi Casey,

    Thank you very much and the content of the reply is the answer I want. There are two questions based on reply above, please confirm agin.

    1. Is it necessary to be specially configured in order not to alter the CRC in long packet？(Because there are some registers in Datasheet to configure CRC, such as "Transmitter CRC Generator" in 953, "Enable FPD-Link III encoder CRC" in 954 ......)

    2. Do 953 and 954 not alter ECC in short packet? ("alter ECC" means decode ECC and recalculate ECC as new ECC) Need to be configured？

    Best Regards

    xiaowei

  • 0 in reply to xiaowei duan
    TI__Guru** 103215 points

    Hello Xiaowei,

    There are no registers that need to be configured for CSI-2 CRC to be forwarded as part of the normal CSI-2 packet structure. The registers that you mentioned are related to the FPD-Link CRC, rather than the CSI-2 CRC. 

    954 will alter the packet header and recalculate ECC only if you re-map the virtual channel for the data through the 954 CSI-2 forwarding controls. Because if you re-assign the data virtual channel before forwarding, then the ECC needs to be recalculated to match. 

    Best Regards,

    Casey 

  • 0 in reply to Casey McCrea
    Prodigy 70 points

    hi casey,

    Thanks agian for your professional reply and i have no other questions about 953 and 954.

    Best Regard,

    xiaowei