Part Number: PROCESSOR-SDK-J784S4
Tool/software:
Hello everyone,
We are testing the CAN setup on the Linux Bootloader (SPL + U-Boot) on the A72 Linux core by following the instructions in section 4.9.3 of the provided J784S4 MCAN User Guide.
We attempted the internal loopback (as it’s mentioned that this does not require any additional setup) between two terminals on the board. One terminal executes the cansend command, while the other uses candump to listen for and receive any incoming messages. We tested this on all three enabled CAN interfaces (mcu_mcan0, mcu_mcan1, main_mcan16), but nothing is being received.
Additionally, we tried using an external transmitter by connecting Vector's VN1610 jumper wires to J46 on the EVA board and the USB-C to the PC. We used an application that utilizes Vector's XL Driver Library API to send data to the CAN bus, but still, nothing is being received.
y connecting Vector's VN1610 jumper wires to J46 on the EVA board and the USB-C to the PC, with an application utilizing Vector's XL Driver Library API to send data to the CAN bus, but still nothing is being received.
It's worth mentioning that all relevant steps from related questions have been verified:
-
After executing the command to turn on CAN interfaces mentioned in the CAN Utilities section of the Linux MCAN Driver Guide, the following interfaces are shown:
ip addr show | grep can 4: mcu_mcan0: mtu 16 qdisc pfifo_fast state UP group default qlen 10 link/can 5: mcu_mcan1: mtu 16 qdisc pfifo_fast state UP group default qlen 10 link/can 6: main_mcan16: mtu 16 qdisc pfifo_fast state UP group default...
- The code changes mentioned in this Git commit have been verified and are present in our DTS files.
Also, is there any way to enable debug logs for CAN to diagnose if anything under the hood is problematic?
Regards,
Dušan
