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.

MSP430FR2433: UART example 01 on Resource explorer

Part Number: MSP430FR2433
Other Parts Discussed in Thread: MSP430G2553

Tool/software:

Tool: CCS 12.7.1

Hi all!

Someone experienced this error while running this resource explorer UART example?

In addtion, soma weird characters appears, without typing.

Any help is appreciated!

  • Hi Italo,

    I have never seen this error.  Are you running this code on the MSP430FR2433 LaunchPad?

    Were you able to successfully program with error before this and now you see the error?

  • This symptom can appear if a program has a .data/.bss which is "too big", and the Watchdog goes off during C initialization. A TI Example seems an improbable candidate for this, since they're all pretty small.

    There was an artifact with the FR2433 Launchpad (and another one, I think): It is delivered with a program which uses the RTC, in particular RTCIE. The first time you program it, the debugger reset doesn't reset the RTC, and the interrupt goes off in the new code, which goes to the Fault ISR. I (vaguely) recall a different visible symptom, but this was also back in CCSv8, and maybe something has changed in the meantime. Power-cycling the Launchpad (after loading the new code) should clear this particular condition.

  • Hi Italo,

    Are you still seeing this issue?

  • Hi!

    Seems like the issue was resolved somehow. Maybe some initialization bug.

  • Well, I tried again and now this error occurred: 

    MSP430: Trouble Reading Memory Block at 0xc51a on Page 0 of Length 0x12: Could not read device memory

    Additionally, CCS lags and weird characters still appearing. Tried power-cycling, but no results.

  • Hi Italo,

    Are you having this issue with the MSP430FR2433 Launch Pad, or is this your custom PCB?  If custom PCB, what programmer are you using?

    In either case, check the VDD is +3.3V and stable on the MCU.

  • Hi!

    I'm using the LaunchPad, and the strange thing is that before I coded without interrupt, and it "worked". The characters appeared correctly on debugging mode, but when executing, they appeared weirdly.

  • Hi Italo,

    I tried the example code without any modifications to the code and it works on my Launch Pad.  Note: when running in debug mode, there will be a 3-4 sec delay in response due to the low bandwidth of the debugger.  If you reset the device and operate in normal run mode, you should see whatever you type on a terminal application get echoed back to the terminal.

  • Hello!

    I tried another snippet using on-board LED to check communication completeness between TX and RX. I suppose I'm misusing the console to see the echoes; even the simplest codes do not return anything in terminal.

  • Well, I tried another approach, replicating What successfully worked on msp430g2553, but didn't on it

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    #include <msp430.h>
    void Software_Trim(); // Software Trim to get the best DCOFTRIM value
    void ser_output(unsigned char*);
    #define MCLK_FREQ_MHZ 1 // MCLK = 1MHz
    unsigned char TXData[] = "Test\n\r";
    int main(void)
    {
    WDTCTL = WDTPW | WDTHOLD; // Stop watchdog timer
    __bis_SR_register(SCG0); // Disable FLL
    CSCTL3 = SELREF__REFOCLK; // Set REFO as FLL reference source
    CSCTL1 = DCOFTRIMEN | DCOFTRIM0 | DCOFTRIM1 | DCORSEL_0;// DCOFTRIM=3, DCO Range = 1MHz
    CSCTL2 = FLLD_0 + 30; // DCODIV = 1MHz
    __delay_cycles(3);
    __bic_SR_register(SCG0); // Enable FLL
    Software_Trim(); // Software Trim to get the best DCOFTRIM value
    CSCTL4 = SELMS__DCOCLKDIV | SELA__REFOCLK; // set default REFO(~32768Hz) as ACLK source, ACLK = 32768Hz
    // default DCODIV as MCLK and SMCLK source
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • Interesting.

    Do you have an oscilloscope or logic probe that you can check the TX line and confirm the baud rate is 9600?

  • Hello!

    Configured my logic analyzer to async serial with 9600 baud rate and this was displayed:

    The upper line is the TX. The hexadecimal data depicted correctly corresponds to the ASCII of each character. So I suppose that It's working.

  • Hi Italo,

    Yes, looks like the device is echoing the data properly.  So given that, where are you still having issues?

  • Nothing is printed in my computer terminal.

    Now that I can see the transmission is occuring, and it is correct, I wonder what's wrong with the cable or any other configuration...

  • If you are running this on the FR2433 launchpad, you need to open your device manager on your PC and determine which COM PORT is assigned to "MSP430 application UART".  Be sure to specify this to your terminal application and it is also set to work at 9600 baud.

    Take a look at section 5 FAQ in the launchpad user guide.

**Attention** This is a public forum