• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 66 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.

J722SXH01EVM: CANFD Gateway Development issue

Aditya Pawar
Prodigy 20 points
Part Number: J722SXH01EVM

Tool/software:

I am working on the J722S EVM board running Linux and performing development of a CAN gateway application with CAN FD support.

I have encountered an issue while testing CAN FD functionality across multiple CAN channels. My observations are as follows:

Observations:

  • mcu_mcan1: CAN FD transmit and receive works successfully (64-byte DLC).
  • mcu_mcan0 & main_mcan0: Standard CAN works, but CAN FD does not work or frames fail to transmit.
    • Error: "No buffer space available" or  CAN FD frame not acknowledged.
    • I verified bitrate setup using “sudo ip link set canX type can bitrate 500000 dbitrate 1000000 fd on”.

Are there any known hardware or firmware limitations for mcu_mcan0 or main_mcan0 regarding CAN FD?

  • 0
    TI__Guru 50723 points

    Hi Aditya,

    I do not remember seeing the "No buffer space available" error message before. There should be no extra hardware/firmware limitations for mcu_mcan0 and main_mcan0 compared to mcu_mcan1. I can give some ideas out that you may try for some initial troubleshooting.

    1. Looking online, I saw some online discussions on the can-utils repository that seem to relate the txqueuelen to the error message.
      1. For troubleshooting, txqueuelen along with other info can be printed out using "ifconfig -a". You may compare between the working mcu_mcan1 and non-working mcu_mcan0 to see if there are any differences that stand out.
      2. For an experiment, this value can be changed with "ifconfig mcu_mcan0 txqueuelen 1000"
    2. Otherwise, all of the issues that I have encountered in the past for MCAN are noted here which I update when new issues are encountered, complete with expected output and error messages: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1474001/faq-tda4ven-q1-how-to-enable-troubleshoot-and-debug-mcan-can-fd-interface-not-working-in-linux. You may go through them to see if any of them sound like they may be related to the observed behavior on your system. 

    Regards,

    Takuma