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.

TMS320F28377D: Leveraging McBSP to communicate between two F28377

Part Number: TMS320F28377D

Hi team,

My customer is evaluating the performance of using McBSP to achieve the communication between 2 F28377.

I am looking at this example mcbsp_ex5_ext_loopback, which I believe should be the correct starting point.

According to my understanding, the connection between 2 MCU should be like this, where 1 and 2 represent 2 MCUs.

MFSX1->   MFSR2

MCLKX1-> MCLKR2

MDX1->     MDRX2  

MFSR1 ->  MFSX2

MCLKR1 ->  MCLKX2

MDRX1   ->  MDX2

Here are some questions:

1) Are the connection correct, is there any extra connection needed?

2) In the demo code, I noticed the Tx frame-sync is set as internal, while the Rx frame sync source as external

    Does this mean the TX frame-sync is an output which is generated automatically, and RX frame-sync is input, waiting for pulse from the TX frame-sync of another MCU?

Thanks for your help here.

Regards,

Brian

  • Hi,

    I am looking at this example mcbsp_ex5_ext_loopback, which I believe should be the correct starting point.

    yes, this example uses two different McBSP instances on the same board but would be a good starting point.

    1) Are the connection correct, is there any extra connection needed?

    yes, the connections look correct.

    Does this mean the TX frame-sync is an output which is generated automatically, and RX frame-sync is input, waiting for pulse from the TX frame-sync of another MCU?

    This means that the FSX signal for transmitter is generated internally through sample rate generator which is also reflected on the FSX pin while the FSR source  is set as external which should be supplied externally through pin.

    Thanks
    Vasudha