• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 187 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP-EXP430F5529LP: MSP430F55xx_uscia0_uart_01.c not working

Ted Fryberger
Intellectual 750 points
Part Number: MSP-EXP430F5529LP

Using the MSP-EXP430F5529 LaunchPad (red, rev 1.8)

Downloaded several UART program examples from Resource Explorer:

MSP430F55xx_uscia0_uart_01.c

MSP430F55xx_uscia0_uart_02.c

Both do a loopback test on pins listed below, put a jumper across these to connect them (also tried without the jumper)

P3.3       USCI_A0 Tx

P3.4       USCI_A0 Rx

Using a PC terminal emulator: Tera Term, Putty, CCS Terminal; get port address from Device Manager after LP connected with USB cable

Port settings for terminal & port are identical and match what each program wants

Tera Term set to local echo so I can see what I type, but there is no return of the same character, why not?

  • 0
    Guru 88720 points

    Hm. That does look odd -- these Examples set everything up, but never "kick off" the loopback cycle. In other (analogous) examples there's an incrementing TXData variable that's compared against the data received, but I don't see that here. Try adding something like:

    UCA0TXBUF = 'A';   // Start the loopback cycle

    just before the LPM statement.

    These programs don't use UCA1, so you won't see anything in the Launchpad backchannel (USB to your terminal program). A breakpoint in the ISR can help illustrate the flow.

    [Edit: An alternate, perhaps more useful, way to use these is to jumper P3.3/.4 to the RXD/TXD headers on the "bridge" header (USB side). Then you can type in your terminal program and see the echo.]

  • 0
    Intellectual 750 points

    Thanks Bruce, I'll try that

  • +1
    Intellectual 750 points

    Tried the first suggestion and it didn't do anything. Tried your second suggestion of connecting the 5529 USCI_A0 Tx and Rx lines to the isolation block headers, and I'm getting some sort of echo back - can't read it, but a consistent binary symbol. I'm going to punt on this and look for more useful examples. Thanks

**Attention** This is a public forum