Compiler/LAUNCHXL-CC1350: CC1350 UART Limited To Echoing Characters

Matt Dion

Part Number: LAUNCHXL-CC1350

Tool/software: TI C/C++ Compiler

Hi,

I'm new to the embedded and coding world, but I am on a school project that requires me to communicate with a GPS via UART and relay the GPS data wirelessly. I used the uartecho project as my basis and edited it to initially send a string to configure the GPS. I simply changed the line that declares echoPrompt to:

const char echoPrompt[] = "$PMTK314,1000*31:\r\n";

and nothing happens, although I am able to echo characters. I didn't get echoPrompt even before I changed the code even though I started the serial session before before compiling. Any help would be greatly appreciated.

Thanks,

Matt

over 6 years ago

0 TER over 6 years ago

TI__Guru**** 317180 points

Ok, not sure if I got all the details:
When you run the program out of the box without modifications you never see a prompt but when you press a key you see this in the terminal window? Try to press the reset button on the LP to see if something is written then.

0 Keith Barkley over 6 years ago

Guru 35620 points

Start a debug session and start the terminal while the program is being held at main().

Are you using the RTOS or Non-RTOS example?

0 Matt Dion over 6 years ago in reply to Keith Barkley

Prodigy 50 points

I've tried using both, but I am currently using the RTOS example

0 Matt Dion over 6 years ago in reply to TER

Prodigy 50 points

I tried the reset button on the LP and I still don't see the prompt, but the character echoing works.

0 Keith Barkley over 6 years ago in reply to Matt Dion

Guru 35620 points

In UARTecho.c put a long (a second or so) delay before "UART_write(uart, echoPrompt, sizeof(echoPrompt));"
to give the UART time to get ready.

0 TER over 6 years ago in reply to Keith Barkley

TI__Guru**** 317180 points

It should be no need for adding extra delay. If you have the terminal up and running you should see the prompt after you reset the LP. I assume you have set up the terminal for correct baud rate and on correct COM port?

0 Keith Barkley over 6 years ago in reply to TER

Guru 35620 points

He must, he sees the echo, that is why it is weird.

0 Matt Dion over 6 years ago in reply to TER

Prodigy 50 points

Yes I am using the same baud rate (115200) as specified in the example program and the correct COM port (I've tried both PuTTy and RealTerm). I even added a 1 second delay and it did not work. I even tried updating the the newest CCS on my desktop (I was setting everything up on my laptop previously) and compiling it from there and nothing has changed. Could there perhaps be a problem with the board (such as firmware)?

0 TER over 6 years ago in reply to Matt Dion

TI__Guru**** 317180 points

Not sure you don't get this to work. The example works without problems out of the box if I run it unmodified. It's no difference in the UART_write() call that output the prompt and the one that output the echo.

0 TER over 5 years ago in reply to TER

TI__Guru**** 317180 points

Did you manage to get this working in the end?

0 Matt Dion over 5 years ago in reply to TER

Prodigy 50 points

Apologies for the late response (it was finals week). I was able to get everything working on a different board (the 1350 launch pad with the SMA connectors) but never got it working on the 1350 launchpad without the SMA connectors

Sub-1 GHz

Sub-1 GHz forum

Compiler/LAUNCHXL-CC1350: CC1350 UART Limited To Echoing Characters