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.

CCS/TMS320F28035: a fallback for ecan failure

Part Number: TMS320F28035

Tool/software: Code Composer Studio

hello Sir/Madam,

we have product on passenger car and recently we met a few cases that CAN commucation failure when tring to start-up the car.

we cannot reproduce the phenomenon in lab.

i conclude the case here,

1. eCAN cannot transmit, because other node on the vehicle report receive timeout.

2. eCAN can receive, because our product could goto sleep according to the networking manament protocol and recovery on the next wakeup.

3. eCAN not enter busoff, because no busoff records in our product's memory.

Do you have any ideas on which fault in the eCAN could lead to the above description?

if there is no clues, we wants to implement a reset as fallback.

but we want to distinguish "No ACK error"(CAN bus is open and our product is alone )  , "bus off" and "other errors that cause transmit failed for sometime, like 500ms".

eCAN wll freeze the CANES when there is an error shown which make it difficult to distinguish "No ACK" and "other errors that cause transmit failed".

Do you have any suggestion on the reset fallback?

by the way, we use NXP TJA1043T as the CAN transceiver.

i am looking forward for your relay.

thanks a lot !

 

Do you have any ideas for the