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.

Stellaris Launchpad baud rate



I am using the Stellaris Launchpad and trying the hello world program from the TivaWare_C_Series-1.0 examples. I am using the code composer studio terminal. The code does not work at 115200 baud on COM3. It seems to work only with 9600 baud.  Is the baud rate on the Stellaris Launchpad limited to 9600 baud?

 

The hello.c program sets the baud rate to 115200 by the following snippet:

UARTStdioConfig (0, 115200, 16000000);

  • As stated - your other/earlier post - UART3 exposes that limitation which is not an MCU limitation but one introduced by Stdio - and which can be fixed by modeling UART3 after lower numbered UART configurations w/in that Stdio code.

  • I am  confused about your reply. I am not using any custom designed board.

    I am using the  Stellaris Launchpad with the Hello world example from the TivaWare_C_Series-1.0 software provided by Ti.

    In this the hello.c program seems to set the baud rate by the following code. If I set the baud rate in this hello.c to 9600 and ccs terminal it seems to work. If I set the baud rate in the hello.c and the CCS terminal to 115200 it does not work.

    1. Does Stellaris Launchpad debug port have baud rate limited to 9600 baud?

    2. If not, what change should I make in the code to make it work?

     

    ConfigureUART(void)

    {

        //

        // Enable the GPIO Peripheral used by the UART.

        //

        ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOA);

        //

        // Enable UART0

        //

        ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_UART0);

        //

        // Configure GPIO Pins for UART mode.

        //

        ROM_GPIOPinConfigure(GPIO_PA0_U0RX);

        ROM_GPIOPinConfigure(GPIO_PA1_U0TX);

        ROM_GPIOPinTypeUART(GPIO_PORTA_BASE, GPIO_PIN_0 | GPIO_PIN_1);

        //

        // Use the internal 16MHz oscillator as the UART clock source.

        //

        UARTClockSourceSet(UART0_BASE, UART_CLOCK_PIOSC);

        //

        // Initialize the UART for console I/O.

        //

        UARTStdioConfig(0, 115200, 16000000);

    }

     

  • vijay kumar14480 said:
    I am not using any custom designed board.

    No one made such (custom board) claim! 

    Your initial post suggest this baud rate limitation is confined to UART3 ("The code does not work at 115200 baud on COM3") - and your latest code now moves to UART0 - thus you present a "moving target" - complicating diagnosis.

    A baud rate limitation has been observed (and reported) on the higher order UART ports when employing "Stdio."

    I don't know how to make this more clear...

  • COM3 is what shows up in my CCS Terminal, so I think it is related to the Code composer studio.

    The code I am using seems to be using  port0.

    So, I do not think the limitation stdio you cite is not applicable here.

     

    Thanks.

     

  • Hi Vijay,

        Try using other serial console like Terra Term or Hyperterminal. Set the baud rate to 115200 COM3(Your PC). See, if you get the same results.

    -kel

  • Hi Markel,

    Excellent. It worked with Terra Term at 115200 baud.

    Looks like CCS terminal will not work at 115200 baud.

    Thanks for solving my issue.

     

  • vijay kumar14480 said:
    Looks like CCS terminal will not work at 115200 baud.

    The problem appears to the combination of the Stellaris Virtual Serial Port and CCS terminal plug-in not working if baud rate is (higher than) 9600 baud - see The CCS5.4 terminal plug-in doesn't display any output from a Stellaris Virtual Serial Port unless the baud rate is dropped to 9600