• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 700 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TMS320F28335: F28335 eCAN - CANES

TMS320F28335: CANES SA1 is 1

Susan Yang
Genius 9955 points
Part Number: TMS320F28335


Dear team,

My customer is using eCAN of  28335.  

CANTEC=0  CANREC=129 CANES has SA1 error. 

After the eCAN of TMS320F28335 is disconnected and reconnected, it cannot sent anymore. 

The customer uses the can cycle sending mode of TMS320F28335. A CAN module of the computer is used as the receiving node. There was an SE error at the beginning, what is the reason? How to solve it? When customer switch between the main power supply and the backup power supply, eCAN can no longer communicate.

  • 0
    TI__Guru* 95315 points

    Is the node under bus-off condition? This can be determined by examining CANMC.CCR bit. Does the node transmit a frame successfully even once? 

    Please download my Application report http://www.ti.com/lit/spra876 and look at the Debug tips provided. Most CAN issues can be resolved by going through this checklist.

  • 0
    Prodigy 150 points

    the node is not under bus-off condition.because the CANMC.CCR bit is 0.

    It was normal at first, but there was an SE error at the beginning, what is the reason? How to solve it?

    When customer switch between the main power supply and the backup power supply, eCAN can no longer communicate.CANES has SA1 error. 

  • 0 in reply to koko wilton
    TI__Guru* 95315 points

    The TRM says the below:

    The SA1 bit is always at 1 after a hardware reset, a software reset, or a Bus-Off condition. This bit is cleared when a recessive bit is detected on the bus. 

    So, one of the reasons for SA1 bit to be set is the node going bus-off. Without access to the hardware, it is hard for me to theorize the reason for the SE error. Please run the CAN_TXLOOP example from my Application Report and let me know what you find. Also look for Error frames on your CAN bus analyzer.