• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 413 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

AWR1843: mmWave Studio CLI Tool cannot be started

AWR1843: Setting values do not match between mmWaveStudio GUI and mmWaveStudio CLI

Wakana Nakai
Prodigy 55 points
Part Number: AWR1843

I have a question about the setting values of mmWaveStuido CLI Tool.

Question 1
The decimal point in ProfileCfg is truncated.

JSON file generated by mmWaveStudio GUI
　"adcStartTimeConst_usec": 5.5,
　"rampEndTime_usec": 40.630001068115234,
　"freqSlopeConst_MHz_usec": 88.061996459960938,

Log when running mmWaveStuido CLI Tool
　profileCfg  0 77.00 10 5 40 0 0 88.06 0 256 7502 0 0 30


Question 2
It seems that the setting value of DataConfig cannot be checked in the CLI Tool log, is there any way to check it?

*It is the following part of mmWaveStudio GUI

  • 0
    TI__Mastermind 31680 points

    Hello User,

    Thankyou for reaching out on TI E2E forums. 

    Our expert will get back to your concern by tomorrow or early next week. 

    Thankyou for your patience. 

    Regards,

    Ishita

  • +1
    TI__Guru 69960 points

    1.  Looks like these are converted to integer instead of float value which is causing converted cfg file to have truncated values.

    Fix: 

    gui\mmw_cli_tool\serial_comm\mmwave_json_parser.c  :  int writeCliCfg() function

    Under

    for (idx = 0; idx < gMmwSensCfg.rfCfg.profileCfgCnt; idx++)

    {

    .....

    .....

    /* change sprintf code snippet to save final converted values in float */

    sprintf(cliStr, "%s %d %.2f %.2f %.2f %.2f %d %d %.2f %d %d %d %d %d %d %c", defaultCliCmd[PROFLIE_CFG], profCfgPtr->profileId, \
    (float)START_FREQ_GHZ_CONVERSION(profCfgPtr->startFreqConst), (float)profCfgPtr->idleTimeConst / 100, \
    (float)profCfgPtr->adcStartTimeConst / 100, (float)profCfgPtr->rampEndTime / 100, profCfgPtr->txOutPowerBackoffCode, \
    profCfgPtr->txPhaseShifter, (float)FREQ_SLOP_MHz_CONVERSION(profCfgPtr->freqSlopeConst), profCfgPtr->txStartTime, \
    profCfgPtr->numAdcSamples, profCfgPtr->digOutSampleRate, profCfgPtr->hpfCornerFreq1, \
    profCfgPtr->hpfCornerFreq2, profCfgPtr->rxGain, teminatStr);

    Rebuild the Studio CLI tool

    2. Studio CLI doesn't provide much flexibility to control the datapath (i.e. those LVDS lane, data length, speed etc.) You need to change that in the device application available under src directory.

  • 0 in reply to Jitendra Gupta
    Prodigy 55 points

    Thank you for your answer.

    1. I have solved the problem with the following modification.

    C:\ti\mmwave_platform_1_2_1\tools\studio_cli\gui\mmw_cli_tool\serial_comm\mmwave_json_parser.c

    		sprintf(cliStr, "%s %d %.2f %.2f %.2f %.2f %d %d %f %d %d %d %d %d %d %c", defaultCliCmd[PROFLIE_CFG], profCfgPtr->profileId, \
			(float)START_FREQ_GHZ_CONVERSION(profCfgPtr->startFreqConst), (float)profCfgPtr->idleTimeConst / 100, \
			(float)profCfgPtr->adcStartTimeConst / 100, (float)profCfgPtr->rampEndTime / 100, profCfgPtr->txOutPowerBackoffCode, \

    2. I understand.