• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 34 subscribers
  • Views 732 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.

TCAN1145-Q1: selective wake up failed

Sherry Liang
Genius 10255 points
Part Number: TCAN1145-Q1

Dear team,

My customer test the selective wake up function. The device ID=0x2F2, and the CAN data is 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01. The register configuration is as below, but they can't wake up our device successfully. And then they find that there are two frames sending this CAN node, one is our wakeup frame, and the other is non wakeup frame which also includes device ID(0x001) and 8 byte CAN data. When they stop to send the non wakeup frame to this CAN node, this CAN node can wake up successfully after receiving the wake up frame. But when these two frames both send to this CAN node, it can't wake up. Could you please help analyze this phenomenon?

      TCAN1145_SetCanIDReg32(0x0B);

      TCAN1145_SetCanIDReg33(0xC8);

      TCAN1145_SetCanIDMaskReg37(0x0);//0xFF

      TCAN1145_SetCanIDMaskReg38(0x03);//0xE0

      TCAN1145_SetCanIDMaskReg39(0xFF);

      TCAN1145_SetCanIDMaskReg44(0xD4);

      TCAN1145_SetCanIDMaskReg45(0x00);

      TCAN1145_SetCanIDMaskReg46(0x1F);

      TCAN1145_SetCanIDMaskReg47(0x80);

      TCAN1145_SetModeCtl(TCAN1145_SW_EBABLE, TCAN1145_NORMAL_MODE);

Thanks & Best Regards,

Sherry

  • 0
    TI__Guru 74282 points

    Sherry,

    An engineer has been assigned to this thread and will respond accordingly.

    Regards,

    Eric Hackett 

  • 0
    TI__Guru 53575 points

    Hi Sherry,

    I don't see anything wrong with the SW config or ID Mask values here. The ID is configured for 0x2F2 as you described, but the data mask remains disabled as DATA_MASK_EN is set as 0 in ID_MASK_DLC (register h38 bit 0). This means only the ID portion is used to determine if a wake up frame is valid - the length and information in the data portion of the frame is ignored. 

    It's odd to hear that the device only appears to recognize the wake up frame (WUF) when it is sent on it's own. Is it possible to capture scope shots of the bus during both frames, good WUF and incorrect frame (ID=0x01)? I would like to see if there's any electrical differences between these two test cases from the perspective of the receiver. This will also help us identify if there's any issue that could be causing the device to wake from frame error overflow rather than waking from a correct WUF.

    I will send you an email offline with some demo code for this device which contains some low level drivers. This will help make the configuration more readable and may help with the translation between desired config and writing the correct bits. 

    Regards,
    Eric Schott