LAUNCHXL-F280025C: CAN Communication

Savitha,

         Debugging your code is not something we can support on the e2e forum. However, here are some helpful resources: 

Please download my Application report http://www.ti.com/lit/SPRACE5. It has many tested examples. I request you to look at the Debug tips provided. Most CAN issues can be resolved by going through this checklist. 

I have created a video to help with the first communication project using DCAN: https://training.ti.com/getting-started-dcan-module. This is based on the same device you are using. Please take a look. 

In CAN, transmission is not considered successful unless the reception is successful. Reception is considered successful when at least one node received the transmitted frame without any errors and transmitted the ACK bit to the transmitter. I have explained this in my Application report. 

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  

Since you are using LaunchPads, we can rule out any H/W issues and focus on the S/W. Mismatched bit-rate could be a  reason for node going bus-off (in addition to other error conditions). But even that is not a possibility since you are using the C2000ware example, which is tested. That only leaves the wiring, which I have clearly explained in the video. All I can tell you is to carefully go through my debug tips in SPRACE5. 

I regret I am unable to help further.