TDA4VH-Q1: Facing issue while enabling MCAN5 and MCAN3 in j784s4 evm

Hi Roshan,

Muxing looks correct in shared screenshot.

Can you confirm if internal loopback mode works for the configured CAN devices? Following step 3 of this FAQ:  [FAQ] TDA4VEN-Q1: How to enable, troubleshoot, and debug MCAN, CAN-FD interface not working in Linux 

And if internal loopback works, could you try an external loopback (connecting MCAN5 to another known working MCAN interface)?

Regards,

Takuma

I tested the internal loop back test, it is working fine.

but I am not receiving any external data.

Hi Roshan,

Could you try commenting out the standby-gpios property for transceiver4 and transceiver5 nodes? 

And could we also get a picture of how the Main MCAN5 is connected? 

Regards,

Takuma

I did the testing of commenting out standby gpios already, but it was not working. 

Please look into this picture, I can not show the physical device right now, because I am away from the device now.

I am using J44 for CAN5 and J41 for CAN3.
In J44 there are 3 pins in the order - CAN-H, GND and CAN-L. The connection from CAN5 given to CAN16 through wires. connected CAN-H of CAN5 to CAN-H of CAN16 and CAN-L of CAN16 to CAN-L of CAN16.
I was able to send/receive data from/to other CAN interfaces CAN4, CAN16, MCU CAN0 and MCU CAN1.

Hi Roshan,

Just noticed while reviewing dts while I was trying to implement on my end.

There is a resource conflict with mcasp0_pins_default and the pinmuxing for main mcan 3 and 5 in the shared screenshot for devicetree. I was thinking that resource conflict would give a runtime error, so I missed it. 

Can you try removing the pinmuxing for mcasp0 and removing any nodes that may be depending on that mcasp pinmuxing?

Regards,

Takuma