• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 35 subscribers
  • Views 472 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.

TCAN1146-Q1: TCAN1146 CANINT set at the time of CAN wake-up test

Daniel Wang (auto)
Expert 3550 points
Part Number: TCAN1146-Q1

Hello friends,

The setting condition of the CANINT bit is that there is a CAN wake-up frame trigger, but in the following test case, when the K15 is successfully powered on and the transceiver is in normal mode, if a valid Can wake-up frame is sent, CANINT=0, not set, it seems to be inconsistent with the datasheet, what is the reason for this phenomenon?

test condition

TCAN1146 Initialization settings

test process

test results

CAN specific frame wake-up capabilities

CANFD passive function

1

on，10hSW_EN=1,47hSWCFG=1

on，

44hSW_FD_PASSIVE=1

1. After the controller is powered on, unplug the K15 line and wait for the controller to sleep
2. Use CANoe to send Normal CAN frames inside and outside the ID range, and judge the wake-up situation by observing the changes in CANoe received messages and the CPU0_PC values of variables
3. Use CANoe to send CAN FD frames within and outside the ID range, and judge the wake-up situation by observing the value CPU0_PC CANoe and received messages.

1. Normal CAN specified frames can wake up the network (CANINT=1), non-specified Normal CAN frames cannot wake up, no error frames

2. CAN FD inside and outside the ID segment cannot wake up without error frames.

3. After K15 is powered on (CANINT=0): The CANINT bit of the normalCAN frame inside and outside the specified ID is sent unchanged, and the value is 0

4. After K15 is powered on: the CAN FD specified frame and non-CAN FD specified frame CANINT bit is not changed, and the value is 0

2

on，10hSW_EN=1,47hSWCFG=1

off，

44hSW_FD_PASSIVE=0

ditto

1. Normal CAN specified frames can wake up the network (CANINT=1), non-specified Normal CAN frames cannot wake up, no error frames

2, CAN FD error frame can wake up the network, CANINT=1.

3. After K15 is powered on (CANINT=0): The CANINT bit of the normalCAN frame inside and outside the specified ID is sent unchanged, and the value is 0

4. After K15 is powered on: the CANINT bit of the CANFD frame inside and outside the specified ID range remains unchanged, and the value is 0

3

off，

10hSW_EN=0,47hSWCFG=1

on，

44hSW_FD_PASSIVE=1

1. After the controller is powered on, unplug the K15 line and wait for the controller to sleep
2. Use CANoe to send Normal CAN frames and CAN FD frames of any ID range, and judge the wake-up situation by observing the changes and CPU0_PC values of CANoe received messages

1. Any Normal CAN or CAN FD frame can wake up, and the 51hCANINT position 1 after wake-up

2. After power-on, send any frame 51hCANINT bit without setting 1

4

off，

10hSW_EN=0,47hSWCFG=1

off，

44hSW_FD_PASSIVE=0

ditto

 Thanks for your support.

  • 0
    TI__Guru 53575 points

    Hi Daniel,

    The wake up pattern (WUP used when SW_EN=0) is not active when the transceiver is in normal mode. This function is meant to detect CAN activity when the transceiver is in a low power mode such as standby or sleep. If the transceiver receiving a CAN frame while it is in normal mode, the information will be passed to the controller via the RXD signal. 

    Let me know I understood your question correctly and if you have any more questions. 

    Regards, 
    Eric Schott 

  • 0 in reply to Eric Schott1
    Prodigy 236 points

    I'm going to tag onto this post. When the MSPM0 has a CAN transceiver that a CANWU packet and toggles the RXD pin low, could this be used on the same pin configured for CAN_RX to wake up the MSPM0? Or does the wake up signal from RX need to fed to a separate GPIO configured for wake? 

  • 0 in reply to Michael Reilly
    TI__Guru 53575 points

    Hi Michael,

    The RXD behavior will be the same as other 14-pin CAN transceivers, so any software that expects this behavior will be compatible with the TCAN1146 wake up regarding the use of this pin. It's typical to reuse the same pin for RXD CAN data and wake information. 

    Regards,
    Eric Schott

  • 0 in reply to Eric Schott1
    Prodigy 236 points

    Awesome thanks for the info.