AWR1843: mmWave Studio CLI Tool cannot be started

Hi,

Could you try to connect Serial Terminal (Teraterm) to AWR1843 over the same COM port at 921600 and check if same command goes well with reponse 'Done' from AWR device.

Regards,

Jitendra

Hi,

Thank you for your reply.

I  tried to connect Serial Terminal (Teraterm) to AWR1843 over the same COM port at 921600, but I couldn't get a response..

The settings of TeraTerm are as follows.

     1. Line feed is AUTO for reception and CR for transmission.

     2. Local echo is ON.

The Binary that I tried to write is as follows.

     1. Binary flashed in mmWaveStudio GUI

        -C:\ti\mmwave_studio_02_01_00_00\rf_eval_firmware\radarss\xwr18xx_radarss.bin

        -C:\ti\mmwave_studio_02_01_00_00\rf_eval_firmware\masterss\xwr18xx_masterss.bin

     2. Binary flashed in mmWaveStudio CLI

        -C:\ti\mmwave_platform_1_2_1\tools\studio_cli\src\pre-built-Binaries\mmwave_Studio_cli_xwr18xx.bin

*I tried both Bin flashed in GUI and CLI, but it didn't work. Which is correct to flash? Bin flashed in GUI  and CLI are the same contents, right?

If application runs properly then at any given command it will return 'Done' text to the terminal. Here, looks like application on AWR device is not running.

Let's take a step back and check xWR1843 mmw demo binary from SDK 3.5 on your AWR1843BOOST. This is to check if device is fine and UART interface is up with USB connection to the PC.

Regards,

Jitendra

Thank you for the advice.
I checked ”xWR1843 mmw demo binary from SDK 3.5 on your AWR1843BOOST”, and it worked fine.

It turns out that the mmwavestudio CLI Tool doesn't start because the SOP was wrong.
After setting and executing the SOP as shown below, the CLI Tool started.

However, when I connected DCA1000 and sent "dcastart", the following error occurred.

It seems that there is no description in the DCA CLI Developers Guide where to flash this Config.
Could you tell me how to flash the DCA1000 config?

You don't need to send separate command to capture data using DCA1000EVM.

But set ENABLE_DCA_CAPTURE to 1 in mmwaveconfig.txt, mmwave_studio_cli.exe will take care of configure device & dca1000 and later capture the data when frame is triggered.

I understand that you don't have to send individual commands as described in the "DCA CLI Developers Guide".
However, when dcastop is done as shown below, DCA1000 is not yet triggered, so I also tried dcastart.

"ENABLE_DCA_CAPTURE" is set to 1 in "mmwaveconfig.txt".
I think it is necessary to set the Config of DCA1000 (equivalent to mmWaveStudio GLI). How about it?

* Attach the "mmwaveconfig.txt" that I use.
Also, attach the Config written in "mmwaveconfig.txt".

#
# Refer Developer's User Guide document for usage details
#

##### CAUTION: Don't change any variable name in this file. #####

#
#mmWave Device Variant
#AWR1443, AWR1642, AWR1843, AWR6843, AWR1243, AWR2243
#IWR1443, IWR1642, IWR1843, IWR6843
#For AWR1243 and AWR2243 device This tool uses SPI interface and uses JSON 
# file for configuration input
#For other devices it uses UART COM port and can use CFG or JSON input file.
#
#@Note: For AWR1243/AWR2243 
#		a. If FW_DOWNLOAD_ENABLE=1 & FLASH_CONNECTED_TO_SENSOR=1
#			then: Flash matching MetaImage binary file to device first.
#       b. Set LVDS Lanes (DCA_LVDS_LANE_MODE=4)
#
MMWAVE_DEVICE_VARIANT=AWR1843

#
#COM port number (@921600 baud rate)
#Same COM port is being used for sending CLI commands
#And after sensorStart same COM port is used to read monitoring data.
#
COM_PORT_NUM=75

#
#Global configuration: these define the task to be done
#
#To configure the mmWave RF Front End: [ENABLE_CONFIG_MMWAVE] 1- Yes, 0-No
#To capture Monitoring report to JSON file: [ENABLE_MONITOR_CAPTURE] 1- Yes, 0-No
#To capture Raw ADC data using DCA1000: [ENABLE_DCA_CAPTURE] 1- Yes, 0-No
#To post process the captured ADC data: [ENABLE_POSTPROC]  1- Yes, 0-No 
#				(assuming postproc.exe is available at same path of this tool)
#mmWave Config file can be *.cfg or JSON format: [CONFIG_FILE_FORMAT] 1-cfg, 0-json
#
ENABLE_CONFIG_MMWAVE=1
ENABLE_MONITOR_CAPTURE=1
ENABLE_DCA_CAPTURE=1
ENABLE_POSTPROC=1
CONFIG_FILE_FORMAT=1

#
#Path for mmWave Config JSON or .cfg file (including file name). 
#JSON file must be generated by SensingEstimator or mmWave Studio
# Set CONFIG_FILE_FORMAT accordingly.
#
CONFIG_JSON_CFG_PATH=..\..\src\profiles\profile_monitor_xwr18xx.cfg
#CONFIG_JSON_CFG_PATH=..\..\src\profiles\22xx_monitor.mmwave.json
#CONFIG_JSON_CFG_PATH=C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\JSONSampleFiles\18xx\mmwavestudio_test.setup.json
#CONFIG_JSON_CFG_PATH=C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\JSONSampleFiles\18xx\mmwavestudio_test2.mmwave.json

#
#Path to store the monitoring report in JSON format
#Each report in seperate JSON file
#Note: make sure this path and directory exist
#
MONITORING_JSON_PATH=..\monitor_report_dir

#
#Number of monitoring report to store in JSON file
#Set to zero for infinite time till terminated (CLI CMD: "quit")
#or CLI CMD : "monCaptureStop"
#
NUMBER_OF_MONITOR_REPORT_STORE=10000

#
#Path to store Captured ADC data binary file
#
CAPTURED_ADC_DATA_PATH=..\captured_adc_AWR1843

#
#DCA1000 Configurations
#It captures the num. of frames worth data which is given in JSON or CFG file
#DCA_FILE_PREFIX: File prefix for each ADC data DCA1000 captures.
#   e.g. with ‘adc_data’ prefix, file name would be adc_data_Raw_0.bin
#DCA_MAX_REC_FILE_SIZE_MB:Max size of each ADC data file DCA1000 captures, at 
#   this size limit it splits captured data into next binary file. 
#DCA_DATA_FORMAT_MODE: 1: 12Bit, 2: 14Bit, 3: 16Bit mode 
#@Note make sure this format matches with data-format in CFG or JSON config parameters.
#DCA_LVDS_LANE_MODE : 2 or 4 LVDS lanes (AR1243/2243 - 4 lane, AR1642/1843/6843 - 2 lane)
#
DCA_FILE_PREFIX=adc_data
DCA_MAX_REC_FILE_SIZE_MB=1000
DCA_DATA_FORMAT_MODE=3
DCA_LVDS_LANE_MODE=2

#
#PostProc exe utility path
#This tool is provided along with CLI tool, so you may not touch this input text
#
POST_PROC_EXE_PATH=..\mmw_post_proc\mmwave_postproc.exe

#
#Set this parameter when you need to run this CLI tool with CCS image running
# i.e. Not running from Flashed App-Image but loading application from CCS.
# In that case application sometime responses slowely for CLI CMD so in the 
# tool we will add delay for each CLI CMD so it doesn't get expire with error.
# 0: Running from Flash, 1: running from CCS
#
CCS_DEBUG=0

#
#Below Configuration is mainly used for AWR1243/AWR2243 device
#When Communication happens over SPI interface using mmwavelink library
#

#
#If Firmware Download is disabled with AWR1243/AWR2243 device
#0: Yes, 1: No firmware download
#For this tool, it is recommended to flash the firmware and set this option to '1'
# As this tool doesn't contains all version of FW for AWR1243/AWR2243.
#
FW_DOWNLOAD_DISABLE=1

#
#If sFlash is connected with AWR1243/AWR2243 device
#1: Yes, 0: nosFlash is connected with sensor
#
#
FLASH_CONNECTED_TO_SENSOR=1

#
#power on master arguments, please modify if needed (for AWR1243/AWR2243)
#rlClientCbs_t: CRC_TYPE 0:16Bit/1:32Bit/2:64Bit, 
#ACK_TIMEOUT : ACK Timeout for mmWaveLink
#
CRC_TYPE=1;
ACK_TIMEOUT=5000;

#END
#
#End of Config File
#

Hi,

Do you send dcaStop command manually to CLI tool?

And what happens when you run default mmwave_studio_cli.exe and  mmwaveconfig.txt which comes along with the package? Does that run properly at your end?

Regards,

Jitendra

Yes, I have manually sent the dcastop command to CLI Tool.
What I wrote in the previous comment is almost the same as the default result.

* The difference between the default "mmwaveconfig.txt" and the one I modified is as follows.
Change of COM_PORT_NUM
Changed DCA_MAX_REC_FILE_SIZE_MB (100MB->1000MB)

As mentioned in my previous comment, I think the following error statement needs to be resolved.
[ERROR]DCA1000 is not configured. check input txt file
How do you configure the DCA1000?

I guess there is slight miscommunication at either end.

TO configure DCA1000EVM you don't need to send any manual command to studio_cli.exe.

But based on "ENABLE_DCA_CAPTURE=1 in "mmwaveconfig.txt", exe itself will take care of DCA1000 configuration and later triggering the data capture.

Thanks for helping me with the research, let me go over the steps again.

"mmwave_studio_cli_developer's_guide.pdf" is what I'm working with.
dev.ti.com/.../node

*Advance preparation
 Install mmwave_sdk_03_05_00_04
 Download mmwave_platform_1_2_1
 Install FTDI driver
 Install Matlab runtime

*Steps to run
1. Using Uniflash, flash the file "C:\ti\mmwave_platform_1_2_1\tools\studio_cli\src\pre-built-Binaries\mmwave_Studio_cli_xwr18xx.bin
　At this time, the AWR1843 pinout is in Flash mode.

2. Connect AWR1843 and DCA1000, and start AWR1843 in Function Mode.

3. Correct the COM number in "C:\ti\mmwave_platform_1_2_1\tools\studio_cli\gui\mmw_cli_tool\mmwaveconfig.txt" to "Application/User" in AWR1843

4. Execute "C:\ti\mmwave_platform_1_2_1\tools\studio_cli\gui\mmw_cli_tool\mmwave_studio_cli.exe" from the command prompt.

Completed without any errors.
ENABLE_DCA_CAPTURE is enabled, but adc_data_Raw_0.bin is not generated.
CAPTURED_ADC_DATA_PATH is set to "C:\ti\mmwave_platform_1_2_1\tools\studio_cli\gui\captured_adc_AWR1843".

Therefore, I ran the aforementioned dcastart/dcastop/sensorstart/sensorstop, etc., but to no avail.

Please let me know if there is any error in the procedure.

I understood now, that  if is mainly datacapture issue not device configuration issue.

Did you make sure

1. DCA1000EVM is connected with AWR2243BOOST over MIPI connector (blue cable) which is responsible for LVDS streaming from AWR2243BOOST to DCA1000EVM.

2. Ethernet cable is connected from DCA1000EVM and PC is set to static IP as mentioned in the user guide. Try to disconnect wi-fi during CLI experiment.

3. To confirm DCA1000EVM functionality, you can try with mmWave Studio GUI to configure and capture the ADC data.

Thank you for your reply.
1 and 3 have already been checked, but 2 hasn't been checked yet, so I'll check it tomorrow.

I tried what you instructed me to do.

1. DCA1000EVM and AWR "1843 "BOOST are connected by MPIP (blue cable).

2.I disconnected WiFi during the CLI experiment.
 I checked the Ethernet communication status with task manager, and there seemed to be some responses when DCA1000EVM/AWR1843BOOS was connected. However, there was no particular response when starting the CLI.

3. I have confirmed that I can capture using mmWaveStudio GUI.

I tried multiple times and only once did PostProc start in the CLI. However, the contents were empty because I was not able to get adc_data_Raw_0.bin.

-----------
mmWave Config Done!
dcastop
[WARNING] DCA1000 is not yet triggered
sensorstart
[ERROR] Sensor is already triggered!
sensorstop
sensorstart
dcastop
[WARNING] DCA1000 is not yet triggered
dcastart
[ERROR] DCA1000 Trigger error!
dcastop
DCA1000 Capture is done!
Post processing the captured data...
..\mmw_post_proc\mmwave_postproc.exe C:\ti\mmwave_platform_1_2_1\tools\studio_cli\gui\captured_adc_AWR1843 C:\ti\mmwave_platform_1_2_1\tools\studio_cli\src\profiles\profile_monitor_xwr18xx.cfg C:\ti\mmwave_platform_1_2_1\tools\studio_cli\gui\captured_adc_AWR1843\adc_data_Raw_0.bin AWR1843すべての警告は状態 'off' です。

GuiState =

x_axis_types: {1x3 cell}
x_axis_type_idx: 2
x_axis_type: 'phy'
time_domain_yaxis_types: {1x2 cell}
time_domain_yaxis_type_idx: 1
time_domain_yaxis_type: 'codes'
time_domain_xaxis_types: {1x3 cell}
time_domain_xaxis_type_idx: 1
time_domain_xaxis_type: 'time'
non_coherent_integration_option: 0
non_coherent_integration_across_chirps: 0
non_coherent_integration_across_chirps_and_antennas: 0
take_rms: 1
compensate_for_windowing_option: 1
chirp_picture_options: 2
time_domain_auto_scale_options: 1
mimo_mode: 0
bpm_mode: 0
perform_interference_cancellation: 0
interference_threshold: -53
interference_cancellation_window_indx: 1
overlay_detected_points: 0
seperate_real_imag: 0
oversampling_ratio_log2: 0
window_optionidx: 2
detection_options: [1x1 struct]
allow_time_domain_non_coherent_integration: 0
IsPostProcGuiActive: 0
IsOptionsGuiActive: 0
PlayAsMovie: 0
PlayAsMovie_Actual: 0
PlayAsMovie_SlowMovies: 0
are_samples_to_be_removed: 0
num_samples_to_drop: 0
enable_hold_on: 0
numRepeat: 0
frameslider: [1x1 struct]
subframeslider: [1x1 struct]
burstloopslider: [1x1 struct]
burstslider: [1x1 struct]
chirpTypeslider: [1x1 struct]
chirpslider: [1x1 struct]
NumberOfPlotsOnDisplayArr: [1 2 4 9]
NumberOfPlotsOnDisplayIndx: 3
NumberOfPlotsOnDisplay: 4
h_subplot_option: [1 4 6 7 6 7 6 7 6]
h_subplot_channel_select: [1 1 2 3 3 4 4 5 5]
h_subplot_device_select: [1 1 1 1 1 1 1 1 1]
TI_image: [1x1 struct]
subplot_location: {1x4 cell}
subplot: [1x1 struct]
subplot_max_dimensions: [2x2 double]
slider: [1x1 struct]
List_of_options: {1x30 cell}
not_perchannel_graph: [1x13 double]
not_common_graph: [1x15 double]
List_of_options_channel_select: {1x5 cell}
List_of_options_device_select: {1x4 cell}
List_of_options_channel_select_string: 'Common|Chan 1|Ch...'
List_of_options_device_select_string: 'Dev 1'
List_of_options_string: '<html><b>Basic P...'
ui_data_selection_location: {1x4 cell}
ui_channel_selection_location: {1x4 cell}
play_button: [1x1 struct]
option_button: [1x1 struct]
table: [1x1 struct]
remove_dc: 0
Show_image_band: 1
MultiProfileProcessingOption: 1
version: 4.9200
force_cont_stream_mode: 0
process_measure_APIs: 0
movie_play_back_options: [1x1 struct]
movie_record_options: [1x1 struct]
main_figure_id: [1x1 Figure]
menu_handle_load_log_file: [1x1 Menu]
menu_handle_load_bin_file: [1x1 Menu]
menu_handle_calibrate: [1x1 Menu]
menu_handle_microdoppler: [1x1 Menu]
ui_device_selection_location: {1x4 cell}
-----------

When I run it again, it says that I need DCA1000 Config.
-----------
dcastart
[ERROR] DCA1000 is not configured, check input txt file
dcastop
[WARNING] DCA1000 is not yet triggered
dcastart
[ERROR] DCA1000 is not configured, check input txt file
sensorstart
[ERROR] Sensor is already triggered!
sensorstop
sensorstart
moncapstart
[ERROR] Monitor Report Capture is already running!
-----------

I think you need to resolve this.

It is strange that with CLI tool DCA1000 capture doesn't work but with mmWave Studio it works.

I tried today again with AWR1843BOOST + DCA1000EVM and able to capture the data & process.

I'm trying to find out any other point which is somehow stopping capture on your end.

 - Make sure that mmWave Studio GUI is not started while you use CLI tool.

 - Disconnect DCA1000 from Studio GUI, or restart the PC and start first thing is Studio CLI (with network connection proper).

Regards,

Jitendra

Thanks for the reply.

I checked yesterday after rebooting my PC, so the mmWave Studio GUI should not be running.
Therefore, I do not think there is any problem with the environment I am trying.

Could you please attach the mmwaveconfig.txt file that you are using? I would like to compare it with mine.

I was reviewing the Windows Defender Firewall settings and found the following

mmWave Stduio -> Allow
mmWave Stduio CLI -> Block

I will change this setting and check the operation of mmWaveStudioCLI tomorrow.

After changing the Windows Defender Firewall settings, the CLI tool now works.

CLI tool can accept either cfg or JSON for input configuration.

Do the following changes in mmwaveconfig.txt : 

MMWAVE_DEVICE_VARIANT=AWR1843

CONFIG_FILE_FORMAT=0 

CONFIG_JSON_CFG_PATH=SET_JSON_PATH_HERE

You need to use 20210527_test.mmwave.json not 20210527_test.setup.json file in mmwaveconfig.txt.

Here is converted cfg file (from your JSON), which you can use otherwise

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% This is auto generated CFG file from JSON file. %
% Compatible with Studio CLI application ONLY. %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg -1 0 0 1 1
profileCfg 0 77.00 10 5 40 0 0 88.06 0 256 7502 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
frameCfg 0 0 1 0 1.00 1 0.00
lowPower 0 0
lvdsStreamCfg -1 0 1 0
calibMonCfg 0 0
monCalibReportCfg 1 1 0
sensorStart

Thanks for the reply.
When setting 20210527_test.mmwave.json in mmwaveconfig.txt, is the following correct?

CONFIG_FILE_FORMAT=0
CONFIG_JSON_CFG_PATH=C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\JSONSampleFiles\1
8xx\20210527_test.mmwave.json

When I tried this, the CLI Tool did not work correctly with an error.

> This is auto generated CFG file from JSON file
Does the above mean that you have converted 20210527_test.mmwave.json to a CFG file? Did you use the Tool to do that or did you convert it manually?

By loading auto_generated_CFG in mmwaveconfig.txt as follows, does it mean that the CLI works with the GUI equivalent?

CONFIG_FILE_FORMAT=1
CONFIG_JSON_CFG_PATH=... \... \src\profiles\20210527_test.mmwave.json_auto_generated.cfg

Hello,

Thanks for the information. 

The team is looking into this and will get back to you next week. 

Thankyou for your patience. 

Regards,

Ishita

Hello,

How is it going since then?

Please reply as soon as possible.

Hi,

When you run Studio CLI with JSON file for AWR1843 device then first it converts JSON to CFG file. And then send each CLI cmd (from converted cfg file) to device over UART. 

Yes, loading auto_generated_CFG in mmwaveconfig.txt, means that CLI works with GUI equivalent config parameters.

Ther is a minor bug in the CLI tool while it uses *.json for AWR1843 instead of *.cfg file and under specific condition when *json file is generated from mmWave Studio. With this bug, it is generating wrong CLI cmd format in the *.cfg file which was further sent to Device over UART and device returns error.

Here is the fix if you want to rebuild the CLI tool at your end-

\gui\mmw_cli_tool\mmw_config.h

typedef enum cldCmdStrIdx
{
DFE_OUT_MODE = 0,
CHANNEL_CFG,
ADC_CFG,
ADC_BUF_CFG,
PROFLIE_CFG,
CHIRP_CFG,
LEG_FRAME_CFG,
ADV_FRAME_CFG,
SUB_FRAME_CFG,
LOW_POWER,
LVDS_STREAM,
CQ_SAT_MON_CFG,
CQ_IMG_MON_CFG,
//ANA_MON_CFG, //this command is not available and setting wrong indexing to defaultCliCmd in writeCliCfg function.
CALIB_MON_CFG,
MON_CALIB_REPORT_CFG,
TX_POWER_MON_CFG,
TX_BALL_MON_CFG,
RX_GAIN_PH_MON_CFG,
TEMP_MON_CFG,
SYNTH_FREQ_MON_CFG,
PLL_CTRL_MON_CFG,
DUAL_CLK_MON_CFG,
RX_IF_STAGE_MON_CFG,
EXT_ANA_SIG_MON_CFG,
PM_CLK_SIG_MON_CFG,
RX_INT_ANA_MON_CFG,
GPADC_SIG_MON_CFG,
SENSOR_START
}CLI_CMD_STR_IDX_e;

And set ENABLE_MONITOR_CAPTURE=0 for this experiment as no monitoring is enabled in JSON file.

Regards,

Jitendra

Hi, thanks for the reply.
I have modified \gui\mmw_cli_tool\mmw_config.h and Rebuild.

Preparation
* install Visual studio 2017
* Install mmwaveDFP

1. Open Visual studio 2017

2. Open the following
C:\ti\mmwave_platform_1_2_1\tools\studio_cli\gui\mmw_cli_tool
mmwave_studio_cli.sln

3. Add [C:\ti\mmwave_dfp_02_02_03_01] to the include directory

4. Build
The following error occurred.

mmw_spi_comm.c line 916
'lotNo': not a member of 'rlRfDieldCfg'.
'waferNo': not a member of 'rlRfDieldCfg'.
'devX': not a member of 'rlRfDieldCfg'.
'devY': not a member of 'rlRfDieldCfg'.

The following one line was commented out to resolve the above error.
C:\ti\mmwave_platform_1_2_1\tools\studio_cli\gui\mmw_cli_tool\serial_comm
mmw_spi_comm.c

Line 916
// PRINT_FUNC("Lot Number [%d] \nWafer Number [%d] \nDie Coordinates in Wafer ([%d], [%d]) \n\n", dieId.lotNo, dieId.waferNo, dieId.devX, dieId.devY);

Rebuild again resulted in the following error.

Unable to open C:\ti\mmwave_dfp_02_02_03_01\ti\control\mmwavelink\vs\Debug\mmwavelink.lib

I have [mmwavelink.lib] in the above directory but I am getting an error.
Please follow up to resolve the Build error.

Regards,

Wakana

Hi Wakana,

Studio CLI supports AWR2243 ES1.0 and built with mmwave_dfp_02_02_00_01.

While changing to DFP 2.2.3.1 (AWR2243 ES1.1) you need to first change the include path in sln file (which you did already).

And rebuild the mmwavelink library, looks like it is not updated in this DFP version.

I have included C:\ti\mmwave_dfp_02_02_03_01\ti\control\mmwavelink\vs\mmwavelink.vcxproj to mmwave_studio_cli.sln and rebuilt first mmwavelink library then Studio_cli project, which worked at my end.

Regards,

Jitendra