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.

MCU-PLUS-SDK-AM263X: Changing CAN interface to MCAN0

Part Number: MCU-PLUS-SDK-AM263X
Other Parts Discussed in Thread: SYSCONFIG, TMDSHSECDOCK, TMDSHSECDOCK-AM263

Hello all,

I have changed "mcan_loopback" example from SDK  and disabled internal loopback so that I can see transmitted data on MCAN_TX. The changed code works fine when I use MCAN1 which is connected to TCAN_1042 on AM263xCC EVM board. but When I change MCAN1 to MCAN0 (in SysConfig) I cannot see data transmission on MCAN0_TX which should be available on HSEC_MCAN0_TX (Pin 82 of J13A connector).

Would you please help me on this issue?

BR

Saman

  • Saman, 

    There is no on-board CAN transceiver for the MCAN0 peripheral, so there will be no CAN data transmitted.

    I would suggest purchasing the TMDSHSECDOCK-AM263 if you want to use MCAN0 - there is an on-board CAN transceiver connected to the MCAN0 RX/TX signals that would allow you to use that peripheral.

    Regards,

    Brennan

  • Hi Brennan,
    You are right. since I am using the old version of TMDSHSECDOCK, there is no CAN transceiver on board for MCAN0.

    Is there any handshake between SDK CAN controller and CAN transceiver chip which is required for CAN-TX data transmitted?

    I mean, isn't it possible to have data on CAN-TX pin without having CAN transceiver chip on board?

    BR

    Saman

  • Saman,

    What is the use case for this? Any data coming off the MCU MCAN pins is essentially meaningless without a CAN transceiver to show the differential pair.  In order to effectively utilize the MCAN0 peripheral, you need to use an off-board CAN transceiver and connect to those HSEC pins.  Or, purchase TMDSHSECDOCK-AM263 which has the on-board transceiver for MCAN0.

    Regards,

    Brennan