• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 332 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AWR1443BOOST: mmWave CLI command sending stuck at dfeDataOutputMode

Bo JIN
Prodigy 30 points
Part Number: AWR1443BOOST
Other Parts Discussed in Thread: IWR6843, , AWR1443

Hi, 

I am currently using mmWave Studio CLI to do the data capturing. I have two setup, one is IWR6843+DCA1000, the other one is AWR1443BOOST+DCA1000.

The document I follow is " Developer’s Guide: TI mmWave Studio CLI" (https://dev.ti.com/tirex/explore/node?node=AD9z.2Ydz0RjPF.ZURidPg__Z2F8GEn__LATEST)

For 6843 set up, the CLI flow can be ran smoothly. While for 1443 setup, the flow stuck at the first line 

I must type quit to exit CLI application.

The .cfg file used for 1443 is modified from the working copy of 6843. The content is as following:

dfeDataOutputMode 1
channelCfg 15 1 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
profileCfg 0 77 20 6 60 0 0 29.982 0 256 5000 0 0 220
chirpCfg 0 0 0 0 0 0 0 1
frameCfg 0 0 128 0 11 1 0
lowPower 0 1
lvdsStreamCfg -1 0 1 0

The comport setting and .cfg path in mmwaveconfig.txt are all adjusted accordingly.

Did I miss out anything or make some mistake in the flow or in the .cfg file?

Thanks

  • 0
    TI__Guru 68140 points

    Hi,

    Have you flashed mmwave_Studio_cli_xwr14xx.bin from pre-built-Binaries directory?

    And make sure that your AWR1443 is the latest revision not ES1.0

  • 0 in reply to Jitendra Gupta
    Prodigy 30 points

    Yes, I have flashed the pre-built-binary accordingly. Before I flashing in the binary, I even cannot send the command through comport.

    As for the revision, currently I have no access to the hardware, but my impression tells the AWR1443 is not ES1.0. Will reconfirm once I get my hand on the setup again.

  • 0 in reply to Bo JIN
    TI__Guru 68140 points

    Once you get the setup (HW), please check that application is executed after the binary is flashed and booted in function mode.

    You can check that by connecting serial terminal application (like teraterm to application/UART COM port at 921600 baudrate). You should see mmwdemo command prompt printed on the terminal screen.

    Studio CLI exe works only if application executes properly (above print output).

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 30 points

    Thanks for the information.

    My device is ES3.0

    I have re-flash the device, it is successful. Then I change the SOP to functional mode and use the terminal application to connect, it cannot display the command prompt. So does that mean the device is not booting? I will try to replace the device and try again. Is there anything else I can try to identify the problem?

  • 0 in reply to Jitendra Gupta
    Prodigy 30 points

    I change to another 1443, flash it. Terminal application also cannot connect.

    Since both device shows the same symptoms, more likely some configuration I may get wrong. But I have no clue on it.

    The CLI I am using is from mmwave_platform_1_2_1_win

  • 0 in reply to Bo JIN
    TI__Guru 68140 points

    Could you once try in debugging mode? 
    Flash xwr14xx_ccsdebug.bin from SDK in SOP-5  mode and then reboot & connect to R4F in SOP4 mode from CCS to load mmwave_Studio_cli_xwr14xx_mss.xer4f

    See this way you are able to see some prints on console.