• 状态 TI Thinks Resolved
  • 已锁定 已锁定
  • 回复 2 回复
  • 答案 1 答案
  • 订户 16 订户
  • 视图 115 视图
  • 用户 0 会员在此处
选项
选项
相关

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.

TCAN1463-Q1: TCAN1463-Q1: No CAN communication randomness on Vehicle

Perry Wang
Prodigy 10 points

Part Number: TCAN1463-Q1

Dear TI team

Recently we have recieved one customer board production sample carrys TI CAN device (P/N :TCAN1463DMTRQ1) which report no can communication on End of Line (EOL) from vehicle Testing‌, After repower the sample on vehicle,Then the CAN communicaiton recovery, It happened only one time and it very difficult to reproduce this failure since then.

From our side, We have tried to validate the "failure" sample on many pressure testes such as high/Low oven test, Thermal shock test, temperature cycle test, simulation the EOL test on vehicle for thousand times etc. while still no see the failure no longer!

One the other way, The customer keeps a very close focus on this issue, we need to  provide more idea for the next action. We have no better idea for the issue, Is there any suggestion from TI to varify the CAN transicever for further analysis?

Thanks and looking forward for more suggestion.

  • 0
    TI__Mastermind 46025 points

    Hello, we have received your case and the investigation will take some time. Thank you for your patience.

  • 0
    TI__Mastermind 46025 points

    Hi,

    Seems to strongly suggest a transient / system level condition since it is non-repeatable and would recommend to always capture the failure when it occurs (TXD, RXD, CANH / CANL and any other relevant IC pins of concern) especially during power-up and bus activity. 

    Hence, may verify for power supply dips / ramps if any chance MCU starts communicating before the device is ready or in the right / normal mode while ensuring no glitches on EN / nSTB pins. May also verify if any chance for GND shifts, poor termination or external testers forcing a bus state, thanks.