TMS320F28379D: TMS320F28379D

Vishanth,

            The fact that you are able to receive successfully indicates that there are no H/W issues. Please download my Application report http://www.ti.com/lit/SPRACE5. and look at the Debug tips provided. Most CAN issues can be resolved by going through this checklist.

Vishanth,

            In a properly designed/configured network, communication errors should be rare. Common reasons for errors are

(i) Loose oscillator tolerance

(ii) Improper sampling-point selection

(iii) Mismatched bit-rates between nodes. This can happen, among other things, due to loose oscillator tolerance

(iv)  Electrical noise. If the noise is transient, the bus should recover on its own once the disturbances vanish. That is how the protocol is designed. 

Bus-off is a severe error condition. You should investigate the root-cause of the errors (leading to bus-off) during communication. 

The TRM chapter explains the CAN protocol implementation in the MCU. i.e. it explains the functions of the various registers/bits. However, it does not explain the protocol itself. For protocol information, refer to these excellent videos:

https://training.ti.com/automotive-can-overview  

https://training.ti.com/ti-precision-labs-canlinsbc-can-and-can-fd-protocol?context=1139747-1138099-1139707-1138111

https://training.ti.com/ti-precision-labs-canlinsbc-can-and-can-fd-overview?context=1139747-1138099-1139707-1138109  

https://training.ti.com/ti-precision-labs-canlinsbc-can-physical-layer?context=1139747-1138099-1139707-1138110     

There are plenty of online resources that explain error-handling in CAN. Many books also deal with this topic extensively. Here is a list of available CAN books:

https://can-newsletter.org/engineering/engineering-miscellaneous/nr_e_cia_can_books_120529/?utm_source=cmn&utm_medium=email&utm_campaign=cmn-202004