• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 33 subscribers
  • Views 345 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.

TCAN1145EVM: support needed for Selective wakeup feature configuration for 29 bit extended CAN ID

Shreyas Apte
Prodigy 10 points
Part Number: TCAN1145EVM


Hello,

 

We are using TCAN1145 in our application to Sleep and Wake Up our circuitry through local wakeup as well as using Selective CAN ID.

we have successfully implemented drivers for Local wakeup functionality and is working fine. But we are facing issue while implementing Selective CAN based wakeup functionality. We have referred your application note where standard 11 bit selective CAN id is configured for wakeup. In our application we are using extended (29 bit) CAN  IDs. We want to configure our the transceiver to wakeup only at particular CAN ID (e.g. 0x12345). We followed the same sequence to configure all the registers required for selective wakeup functionality as given in application note for extended CAN id ((SW-ID3 bit5) IDE - Extended). After activating Sleep mode, transceiver gets wakeup after receiving any CAN ID on bus.  

Can you share any sample code of selective wakeup configuration for extended CAN ID settings? 

also we wanted to know, can we disable wakeup through CAN functionality? If yes which registers needs to be configure for the same?

  • 0
    TI__Guru 53575 points

    Hi Shreyas,

    Please send me an email requesting the demo drivers and I can send them to you directly. Otherwise, please give me permission to send them to the email linked to your E2E account.

    The TCAN1145 will wake from any WUP (any CAN frame) when selective wake is not enabled properly. In this case, it sounds like there may be something missing in the configuration causing any frame to wake the device. Make sure all of the steps in datasheet section 10.4.5.2 are followed and the SWERR interrupt flag reads 0 to confirm there are no errors in configuration. After the device wakes from sleep, the INT_1 register can be checked to see what the source of the wake was. If the FRAME_OVF flag is set for example, this would mean that the transceiver has recognize too many CAN errors while in sleep mode. This is common if CAN FD frames were used without being configured to be ignored for example.  

    Unfortunately there is on way to completely disable wake from the CAN bus with this device. This is a feature that is planned for future devices that support partial networking. For now a workaround could be to set the wake up frame to one that is not expected to appear on the CAN bus.

    Regards,
    Eric Schott 

  • 0 in reply to Eric Schott1
    Prodigy 10 points

    Hi Erich,

    Thanks for the reply.

    You can send me demo drivers on the email linked to my E2E account.

  • 0 in reply to Shreyas Apte
    TI__Guru 53575 points

    Hi Shreyas,

    I've sent over the demo drivers. If you have any other general questions on this device please ask them on this E2E thread to help future users who may have similar questions.

    Regards,
    Eric Schott