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.

CCS/CC1352R: UART serial port interface Mac CCS terminal

Part Number: CC1352R


Tool/software: Code Composer Studio

I am working to learn CCS and the 1352 development board.  I have worked for several weeks and many hours learning.  However, one thing continues to challenge me.  I can't seem to get a consistent tool to work with the UART.  I am trying to run the POSIX Project Zero project and echo the character entered.  I have tried the "SerialTools" app, "CoolTerm" app, and the terminal inside CCS.  I can successfully connect to the serial port on all of them and I have double checked the settings but no luck on getting an echo of what I type.  When I move on to use the terminal to change the LED it doesn't work.  Clearly I am not doing something right regarding the UART.

Is there a clear instruction for the Mac on how to use the UART in Terminal for CCS?  Will that work?

Thanks in advance and I apologize for such a seemingly simple question.

  • Hi Travis,

    Are you only interested in getting an echo from the device? Then try out the uartecho example found under the drivers folder in the SDK.
  • Yes sir.  That is the example project used for the POSIX project zero.  I just cannot seem to get it to work.  What tool should I use for the Mac?  Is there anything I would need to consider in the code when using a Mac?

    What is interesting though is that the BLE5 project zero does print to the terminal fine.  I'm trying to see the differences between the two programs. The UART echo is designed to teach that concept but it doesn't work.  Most examples won't print to terminal but the BLE5 project zero does.  The first thing that jumps out at me is the UartLog.c file.  I haven't scrubbed it enough or tried to add that file and associated code to the UARTEcho example yet to see if that fixes it.  I'll continue to work this because I obviously think this is important to be able to interact with the program via terminal.

    Thanks for the help.

  • Have you tried PuTTY?
  • Never mind.  Your answer was perfect.  I dowloaded the wrong development board version.  It is working perfectly now.