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.

TMS570LC43X Problem with UART communication

Other Parts Discussed in Thread: HALCOGEN

Hello,

I´m trying to make two LaunchPads TMS570LC43X communicate over UART.

I configurated the board over Halcogen and used SCI3 as UART pins (because they are on the booster pack).

SCI3 should be on J1 Pins 3 (RX )and 4(TX)

Just for testing purpose I tried to send in a while(1) loop.

And the receiver should in the interrupt toggel a user led.


Should be an easy task. But I cannot figure out where my error is.

Can you please take a look at my code and help me?

Thanks in advance

Chris

Code:

1663.ti_uart.rar

  • Hi Chris,

      Let's first check the obvious. Did you configure the PINMUX? The SCI3 RX/TX are multiplexed with N2HET1 pins. The N2HET1 pins are the primary function signals. If you want to use the J1 and J4 you need to configure the PINMUX to bring out the SCI3 pins. If you use HalCoGen, please select the SCI3 checkbox like below screenshot. 

  • Hello Charles,


    I already activated SCI3 there. But my mistake was somewhere else.

    But now it works fine.

    Thanks :)

    Question:

    When I switch on sender before receiver. And sender is just sending in while(1). Nothing else.

    Than I start receiver. In this case receiver is not receiving anything.

    But if I, after receiver is switched on, unwire the rx and reconnect, receiving is working fine.

    could it be, that during configuration of sci3 its not allowed to send data to this one?

    Thank you very much :)

  • Hi Chris,
    Reading your code quickly I don't think you enable the interrupts in the VIM module for SCI3 and SCI4. I assume the SCI3TX is connected to SCI4RX, right?

    You need to go to HalCoGen->VIM Channel 96-127 tab to enable interrupt for SCI4 if you are going to use SCI4 to receive data in interrupt mode.
  • Hello Chris,

    can you maybe explain what your mistake was and how you solved it?
    Maybe it can help me (and others of course) in the future if they have the same problem.

    regards,

    Markus
  • Hi Chris,
    Is your question answered? If your question is answered can you please close the thread by clicking the 'Verify Answer' button? Thanks.