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.

TMS320F28379D: CAN Communication between two different MCUs (TMS570LS0432 and TMS320F28379D)

Part Number: TMS320F28379D


Hello to TI community

                            I have successfully implemented the CAN communication program and verified the data in PCAN view on my desktop for both the MCU TMS570LS004 and TMS320F28379D.

Also, I could able to transfer the data from one MCU (TMS320F28379D) to another in the same family.

Similarly, I could able to do the same experiment in another family of MCU TMS570LS004.

Now I want to do the same experiment between the TMS320F28379D as CAN_RX and  TMS570LS004 CAN_Tx. 

But I could not able to receive the DATA on TMS320F28379D  which is sent by MCU TMS570LS004.

Is it possible to transfer and receive the data of two different families through CAN communications?

If it is possible, Can you please help me out with this issue, also please provide me a relevant document where can I sort this problem.

Thanks in anticipation

P. Ramesh

  • Ramesh,

                    Yes, it is possible to achieve CAN communication (both TX & RX) between two different families. Remember, CAN is an industry-standard protocol; it is not a protocol specific to TI. Any MCU from any company will be able to communicate with any other MCU(s) from any other company through CAN.

    But I could not able to receive the DATA on TMS320F28379D  which is sent by MCU TMS570LS004.

    Check the following:

    Is the data really being sent by the TMS570? You can easily verify this with PCAN?

    Is the receive mailbox on 28379D correctly configured to receive the frame?

     

    Please refer to www.ti.com/lit/sprace5 for more debug tips.

  • Thanks for your kind information. Apologies for posting a small question. 

    The issues are resolved.

    I have sent the data through a TMS570 in extended data form and received it on TMS320F28379D standard data format. later I found these issues and resolved them.

    Once again thanks for your kind information.