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.

TCAN2411-Q1: SBC Wake‑up Triggered by CAN Error Frames in Selective Wake (PNC)

Part Number: TCAN2411-Q1

Hello TI Team,
 
Good Morning!!
We are currently facing an issue with Selective Wake using Partial Networking (Node‑based PNC mechanism).
During PN sleep mode, the SBC wakes up when CAN error frames occur. To prevent this, we attempted to disable the FRAME_OVF_EN setting; however, this did not resolve the issue, and the SBC continues to wake up on error frames.
We would like your guidance on the following points:
  • How to avoid SBC wake‑up caused by CAN error frames
  • Whether additional wake‑source or dominant‑pulse related configurations need to be disabled
  • Recommended PN / wake configuration settings to ensure wake‑up occurs only on a valid PN wake frame
Could you please share the required configuration details or best‑practice settings to resolve this issue?
SBC details : TCAN2411RHBRQ1
Thank you in advance for your support.
  • Hi Satish,

    Thanks for reaching out on E2E. Our SBC expert Matt is out of office, but he returns next week. 

    However, INT_EN_1 is just the interrupt mask. The FRAME_OVF function is always enabled. Error frames will always wake up the device as this is a necessary function. All CAN transceivers are supposed to wake up on CAN error frames. 

    However, you can increase the number of error frames that are needed to wake up the device. This can be done by setting FRAME_CNT_THRESHOLD to the max value (so it takes 256 error frames to wake up the device instead of the default 32). 

    Best,

    Ethan

  • Hello Ethan,
    I hope you are doing well.

    We are currently using the Vector AUTOSAR stack for SBC configuration. During our testing, we observed that when the ECU wakes up due to a CAN error frame, both Event 1 (CAN bus wake-up) and Event 2 (error wake-up) are being set.

    As per our understanding, only Event 2 (error wake-up) should ideally be triggered for an error frame wake-up scenario. However, in our current setup, both events are reported simultaneously.

    Could you please confirm whether this behavior is expected in SBC handling? Additionally, it would be helpful to understand if:

    • This is due to CAN bus activity inherently detected along with the error frame, and
    • Any configuration changes are required if we intend to capture only the error wake-up event.

    Your clarification on this would help us ensure correct interpretation and handling of wake-up sources.

    Looking forward to your guidance.

  • Hi Satish, 

    I'm unfamiliar with the specifics of those CAN frames generated by the Vector box. However, there are multiple possibilities that could be causing your device to wake up:

    1.) The selective wake registers aren't being programmed properly. 

    2.) The Event 1 CAN frame is still being interpreted as an error frame (could be CAN FD which is interpreted as an error if  SW_FD_PASSIVE is disabled)

    3.) There is another wake event happening at the same time, such as a rising edge on a WAKE pin (unlikely)

    I'm think scenario #1 is the most likely since I'm assuming the Event 1 CAN frame just send a simple WUP on the CAN bus. When selective wake is not enabled (or improperly configured), this will wake up the device since it is a BWRR. Can you walk me through step-by-step how you are enabling selective wake on this device? If you read section 6.2 of the firmware guide, it gives the exact process of how to do this (see link and screenshot below). Selective wake won't work if this process isn't followed perfectly. 

    Regards,

    Matt