IWR1642BOOST: Can't receive "Done" from IWR1642BOOST when sending CLI using my own Win32 C program

Hi,
Could you please check the things listed below:
1.Does this EVM work when Visualizer send the cfg?
2.Are you using external USB to UART cable or on-board XDS110?
3.Does other Terminal Serial Port (UART) tools works?

Regards,
Wesley

1. Yes, this EVM works with the Visualizer.

2. I'm using onboard XDS110.

3. If I send the config file using Realterm, it will work. I can see the "Done" string being echoed.

Is the \n per line correct and sent as character array? It makes me wonder why I can receive the echo command from the EVM but not the "Done" string, given the device has already been configured by the Visualizer. If fresh from boot up, I don't receive anything.

Hey Mary,

the '\n' should be correct.

Since you are using Windows and I assume you are parsing a text file for your commands: Did you check your parsed line for a '\r'?

In the ROS demo code there is something like this 

// Remove Windows carriage-return if present
line.erase(std::remove(line.begin(), line.end(), '\r'), line.end());

afterwards, '\n\ ist appended

line.append("\n");

Good luck,

Enric

Ah sorry, I should have read your post completly.
So your commands are hard coded.

Maybe you will need a 'stopSensor' at the beginning?


I think looking at the ROS demo code would be a good idea otherwise, since there are the commands send via a C programm.

Hi,

If the EVM can work with online GUI, please check if your own software can send the config right or not.

The config file is send in scripts, with 115200bps through Application/User Port.

Thanks.

Hello,

I have resolved the missing "Done" string.

I remembered that C strings are always terminated by \0. Initially I was sending the whole char array including the hidden \0. I tried not sending the last byte and now I can see the "Done" string being echoed.

HOWEVER, after successful config, my sensor still couldn't start. Am I missing something at the end of the commands? Why is it still not starting even though it says it was configured correctly?
_____________________________________________________________
Here's what I'm sending:

const char aTxLine1[] = "dfeDataOutputMode 1\n";
const char aTxLine2[] = "channelCfg 15 3 0\n";
const char aTxLine3[] = "adcCfg 2 1\n";
const char aTxLine4[] = "adcbufCfg 0 1 1 1\n";
const char aTxLine5[] = "profileCfg 0 77 30 7 62 0 0 60 1 128 2500 0 0 30\n";
const char aTxLine6[] = "chirpCfg 0 0 0 0 0 0 0 1\n";
const char aTxLine7[] = "chirpCfg 1 1 0 0 0 0 0 2\n";
const char aTxLine8[] = "frameCfg 0 1 128 0 50 1 0\n";
const char aTxLine9[] = "lowPower 0 0\n";
const char aTxLine10[] = "guiMonitor 1 1 0 0\n";
const char aTxLine11[] = "doaCfg 600 1875 30 1\n";
const char aTxLine12[] = "SceneryParam -2 2 0.05 6\n";
const char aTxLine13[] = "GatingParam 4 3 2 0\n";
const char aTxLine14[] = "StateParam 10 5 10 100 5\n";
const char aTxLine15[] = "AllocationParam 250 0.01 5 1 2\n";
const char aTxLine16[] = "VariationParam 0.289 0.289 1.0\n";
const char aTxLine17[] = "trackingCfg 1 2 250 20 200 50 90\n";
const char aTxLine18[] = "sensorStart\n";

____________________________________________________________
Here's the result of configuration:

dfeDataOutputMode 1
Done
mmwDemo:/>

channelCfg 15 3 0
Done
mmwDemo:/>

adcCfg 2 1
Done
mmwDemo:/>

adcbufCfg 0 1 1 1
Done
mmwDemo:/>

profileCfg 0 77 30 7 62 0 0 60 1 128 2500 0 0 30
Done
mmwDemo:/>

chirpCfg 0 0 0 0 0 0 0 1
Done
mmwDemo:/>

chirpCfg 1 1 0 0 0 0 0 2
Done
mmwDemo:/>

frameCfg 0 1 128 0 50 1 0
Done
mmwDemo:/>

lowPower 0 0
Done
mmwDemo:/>

guiMonitor 1 1 0 0
Done
mmwDemo:/>

doaCfg 600 1875 30 1
Done
mmwDemo:/>

SceneryParam -2 2 0.05 6
Done
mmwDemo:/>

GatingParam 4 3 2 0
Done
mmwDemo:/>

StateParam 10 5 10 100 5
Done
mmwDemo:/>

AllocationParam 250 0.01 5 1 2
Done
mmwDemo:/>

VariationParam 0.289 0.289 1.0
Done
mmwDemo:/>

trackingCfg 1 2 250 20 200 50 90
Done
mmwDemo:/>

sensorStart
Done
mmwDemo:/>

Hi,
Could you please check if the UART is correct?
For mmwave demo, 2 UART is required for data and configuration transmit.
Application/User Uart: Configuration port 115200bps: UART_RX <- USB-UART cable <- PC
Auxilliary Data Port: Data port 921600bps: MSS_LOGGER-> USB-UART cable -> PC

Then, could you please use UART terminal link Putty to check if PC has received any data. Thanks.

Regards,
Wesley

Yes UART is correct. As i said, I was able to send the CLI config and receive the "Done" string via the Application/User/115200bps UART.

Still, after it was configured by my user program, I still can't see the sensor starting and no data is being outputted in Data port/921600bps.

Using Visualizer, everything works fine.

Can you help me review what I'm sending using my C program? I think there is something I might have missed but I couldn't figure it out. I thought everything will be solved once I receive Done strings.

Hi Mary,

when I look at the commands of the visualizer, the visualizer sends these commands in the beginning:

sensorStop

flushCfg

Maybe these are missing?

Oh and I found in SDK User Guide on page 12:

"On every reconfiguration, it sends a 'sensorStop' command to the device first to stop the active run of the mmWave

device. Next, it sends the command 'flushCfg' to flush the old configuration before sending the new configuration. It is
mandatory to flush the old configuration before sending a new configuration. Additionally, it is mandatory to send all the
commands for that demo/platform even if the user desires the functionality to be disabled i.e. no commands are
optional."

Good luck,

Enric

Thank you for your suggestion.

I have tried sending the sensorStop and flushCfg to the EVM using Realterm tool. While the sensorStop does stop the data logging in the Data UART port, I couldn't restart the data logging using sensorStart even if I send flushCfg and resend the whole CLI commands again. The only thing that will recover the data logging is when I press the reset button on the EVM and resend the whole CLI config again. Does anyone know why is this so?

So there's two issues that I would like to understand:

1. What could I be missing in my C program CLI config that I cannot make the EVM start streaming data? Should it be that the EVM should be able to start once the "SensorStart" command is successfully received?

2. Why is it that when I send sensorStop the EVM the data logging will stop and cannot recover unless I press the reset button?

Thanks all for your insights!

Hi,

Please make sure the CLI command you send through your GUI/Realterm is same as TI's GUI.

Thanks,

Wesley

That is what I already did. And I think that I am sending the same commands as TI Visualizer. Still, it won't work.

I believe I have missed something. That is why I come to this forum to ask help.

Hi,

Please make sure you can get the data using 2 Terminal Serial Port (UART) Monitor tools like PUTTY manually. One is set to 115200 bps for command, the other one is set to 921600 bps for data. Then type in configuration in command terminal with 'enter' on each line. Then you can get the data in data terminal.

If you can not get the data, please check your hardware connection and PC setting. Thanks.

Regards,

Wesley

As I said in many of my previous posts, I tried it with realterm. It's working.

What i can't figure out is why when I try my C program, it doesn't work.

Hi,
If the realterm can work. We can easily identify it's your own PC software issue.
Then it should be solved by yourself.
Thanks.

I know it should be solved by myself. I am not asking you to solve it for me. I'm asking  for the following questions repeatedly in the previous posts but you keep on saying check the UART port. 

1. What could I be missing in my C program CLI config that I cannot make the EVM start streaming data? Should it be that the EVM should be able to start once the "SensorStart" command is successfully received? Note that done strings are being received.

2. Why is it that when I send sensorStop the EVM the data logging will stop and cannot recover unless I press the reset button?

Hi,

Could you please binary compare the command you send through your PC software and official GUI?

Once EVM receive all the right command finish with " SensorStart", it will reply "Done", then the device begin to work.

To recover data logging, could you please try to send the CFG file again?

Thanks.