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.

LP-CC2652RB: Why UART2_open() will send a byte?

Part Number: LP-CC2652RB
Other Parts Discussed in Thread: CC2652RB, , LAUNCHXL-CC26X2R1, SIMPLELINK-CC13XX-CC26XX-SDK, SYSCONFIG, SIMPLELINK-CC13X2-26X2-SDK

Hi Ti,

I am working in simplelink_cc13x2_26x2_sdk_4_30_00_54\examples\rtos\CC2652RB_LAUNCHXL\drivers\uart2echo\tirtos\ccs and make a little modify as below:

      

Then compiler and flash to LP-CC2652RB, the result as following: The UART2 module will send one byte(0xC0 here, but in my project is 0x00) when calling UART2_open().

Why this happend and How to remove the byte at opening?

Thank you!

  • Hi junde,

    I am not experiencing the same problem as you've described using a LAUNCHXL-CC26X2R1 and the same SysConfig/project settings as provided.  Please evaluate the newest SIMPLELINK-CC13XX-CC26XX-SDK, try using a different terminal program, and provide oscilloscope or logic analyzer screenshots of the erratic behavior if you continue to experience issues.

    Regards,
    Ryan

  • The low level keep ~61us, at baud rate 115200bit/s, 

    61us / (1s / 115200 bit) = 7 bit

    There is a start bit '0', so actually it seems transmit "0 0 0 0 0 0 0 1 1 1 1...". 

    That's why I get 0xC0 in Tx.

  • Several improvements have been made to the UART2 driver since SIMPLELINK-CC13X2-26X2-SDK v4.30, please evaluate with the newest SIMPLELINK-CC13XX-CC26XX-SDK v6.10 and determine whether it resolves the issue.  If so, it may be possible to copy both UART2.c/h and the uart2 folder from from simplelink_cc13xx_cc26xx_sdk_6_10_00_29\source\ti\drivers directly into your v4.30 project directory to resolve the issue.

    Regards,
    Ryan