Other Parts Discussed in Thread: TMS320F28075, C2000WARE, TMS320F280025C,
We have a custom design with an TMS320F28075 that has one of the two CAN buses fully operational on it. We ported the code from the design over to the LAUNCHXL-280025C, removed support for the extra CAN bus, but the CAN bus does not successfully transmit. The CAN bus immediately goes into the bus-off state. When attempting to receive messages no activity is seen in the code that handles getting the messages.
Loop back mode was then attempted to be turned on with no success either.
I then took one of the example designs from the C2000ware driverlib folder and could not manage to get that code to successfully transmit or receive messages on the LAUNCHXL-280025C.
At this point I took the same example design and tried to run it on the design with the TMS320F28075. There I was able to transmit with the example code, but was not successful in getting that to receive CAN data. Loopback mode with the example code was used, but that did not work. I then tried to get our CAN design to run in loopback mode, but that failed as well.
Examining the register sets and functionality of the DCAN peripherals for the TMS320F28075 and TMS320F280025C, they seem to be the same with exception of a few missing bits in registers and only one CAN bus instead of two. Can someone confirm this for me and attempt to explain why code that works on the TMS320F28075 does not work on the TMS320F280025C?