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.

AWR1642BOOST: OOB demo auxiliary com port -waiting on data.

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: UNIFLASH

Hello,

I'm trying to run the OOB demo using the online demo visualizer. I'm getting stuck after I set up my com port and press configure. The auxiliary com port gets stuck on "waiting for data". I have re flashed the OOB using the uni flash follow the flash instructions in the sdk user guide. First I put jumpers on SOP0 and SOP2  and power cycled the device and press the GPI01. Then using the uniflash application I format flash the device then load the xwr16xx_mmw_demo bin file to the device. Then I removed the SOP2, power cycled and pressed the GPI01 again. Last I tried to run the demo. Did I do something wrong? Is is possible  the device is faulty? I did have problems for a while  just getting the comports to connect.

I'm using mmwave_sdk_03_02_00_04

  • Hi,

    Are you using a 3A power supply?

    Is this a new board?

    Thank you

    Cesar

  • Christopher,

    You are missing one final step of running the Out-of-Box Demo. You need to send the CLI commands to the device to actually start the demo.

    This can be done in one of two ways. 

    1. You can use the "Send Config to mmWave Device" option on the Visualizer This is found on the "Configure" tab. Make sure you have selected the proper options in the "Setup Details" section and adjusted the settings in the "Scene Selection" section. After you have finalized your selections, hit the "Send Config to mmWave Device" and then click over to the "Plots" tab.

    2. You can upload a configuration file (*.cfg) using the Visualizer and skip the "Configure" tab. You would go to the "Plots" tab and select the "Load from PC and Send" option. Example configuration files included in the SDK can be found here: C:\ti\mmwave_sdk_03_02_00_04\packages\ti\demo\xwr16xx\mmw\profiles. Simply select one of these configuration files and press ok.

    If you have completed either one of these steps correctly, you should see the four plots active in the Visualizer.

    Regards,
    Kyle

  • Hello,

    So I tried what you have suggest. i repeated the process I explained and then pressed the send configure option with no luck. After pressing configure I still get the waiting on data. 

    Interestingly enough in regards to Cesar's email I am using a cgsw-0502000 power supply witch produces 2 amps but i have ran this example on another computer a while ago with the same power supply and it worked. could this be the problem.?  

  • This is a used board from my university and Im using a cgsw 0502000 power supply. Could this be the problem?  I have managed to run the demo on another computer some time ago however. 

  • Christoper,

    Please make sure you are using a power supply that provides 5V and at least 2.5A.

    In the mmWave Demo Visualizer, did you also make sure to select the right COM ports for your device?

    This is done by going to "Options" --> "Serial Port"

    Then you need to select the ports based on the COM ports that show up in Windows Device Manager.

    From the images that you uploaded in you previous post, I could select the following options:

    CFG_port: COM14

    DATA_port: COM13

    Regards,
    Kyle

  • As was stated in the original post  the uart and data com ports were set up correctly. The correct power supply is also being used but I'm still getting the same result.

  • Christopher,

    Can you upload all of your entries from the "Console Messages" section from the mmWave Demo Visualizer? Upload all of the output printed to that console window so we can analyze for error messages.

    Regards,

    Kyle

  • Christopher,

    For reference, this is what I see in my "Console Messages" section when I run the mmWave Demo Visualizer:

    These are all of the messages that I see:

    -------------------------------------------------------------------------------------
    mmwDemo:/>% Carrier frequency GHz 77
    Skipped

    mmwDemo:/>% Ramp Slope MHz/us 68
    Skipped

    mmwDemo:/>% Num ADC Samples 256
    Skipped

    mmwDemo:/>% ADC Sampling Rate Msps 5.5
    Skipped

    mmwDemo:/>% ADC Collection Time us 46.55
    Skipped

    mmwDemo:/>% Extra ramp time required (start time) us 7
    Skipped

    mmwDemo:/>% Chirp time (end time - start time) us 51
    Skipped

    mmwDemo:/>% Chirp duration (end time) us 58
    Skipped

    mmwDemo:/>% Sweep BW (useful) MHz 3165.09
    Skipped

    mmwDemo:/>% Total BW MHz 3944
    Skipped

    mmwDemo:/>% Max beat freq (80% of ADC sampling rate) MHz 4.4
    Skipped

    mmwDemo:/>% Max distance (80%) m 9.71
    Skipped

    mmwDemo:/>% Range resolution m 0.047
    Skipped

    mmwDemo:/>% Range resolution (meter per 1D-FFT bin) m/bin 0.047
    Skipped

    mmwDemo:/>%
    Skipped

    mmwDemo:/>% Inter-chirp duration us 7
    Skipped

    mmwDemo:/>% Number of chirp intervals in frame - 64
    Skipped

    mmwDemo:/>% Number of TX (TDM MIMO) 2
    Skipped

    mmwDemo:/>% Number of Tx elevation antennas 0
    Skipped

    mmwDemo:/>% Number of RX channels - 4
    Skipped

    mmwDemo:/>% Max umambiguous relative velocity kmph 26.97
    Skipped

    mmwDemo:/>% mileph 16.86
    Skipped

    mmwDemo:/>% Max extended relative velocity kmph 53.95
    Skipped

    mmwDemo:/>% mileph 33.72
    Skipped

    mmwDemo:/>% Frame time (total) ms 4.16
    Skipped

    mmwDemo:/>% Frame time (active) ms 3.712
    Skipped

    mmwDemo:/>% Range FFT size - 256
    Skipped

    mmwDemo:/>% Doppler FFT size - 32
    Skipped

    mmwDemo:/>% Radar data memory required KB 272
    Skipped

    mmwDemo:/>% Velocity resolution m/s 0.47
    Skipped

    mmwDemo:/>% Velocity resolution (m/s per 2D-FFT bin) m/s/bin 0.47
    Skipped

    mmwDemo:/>% Velocity Maximum m/s 7.49
    Skipped

    mmwDemo:/>% Extended Maximum Velocity m/s 14.99
    Skipped

    mmwDemo:/>% Maximum sweep accorss range bins range bin 0.66
    Skipped

    mmwDemo:/>%
    Skipped

    mmwDemo:/>sensorStop
    Ignored: Sensor is already stopped

    Done

    mmwDemo:/>flushCfg
    Done

    mmwDemo:/>dfeDataOutputMode 1
    Done

    mmwDemo:/>channelCfg 15 3 0
    Done

    mmwDemo:/>adcCfg 2 1
    Done

    mmwDemo:/>adcbufCfg -1 0 1 1 1
    Done

    mmwDemo:/>profileCfg 0 77 7 7 58 0 0 68 1 256 5500 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:/>bpmCfg -1 0 0 1
    Done

    mmwDemo:/>frameCfg 0 1 32 0 100 1 0
    Done

    mmwDemo:/>lowPower 0 1
    Done

    mmwDemo:/>guiMonitor -1 1 1 1 0 0 1
    Done

    mmwDemo:/>cfarCfg -1 0 2 8 4 3 0 15.0 0
    Done

    mmwDemo:/>cfarCfg -1 1 0 8 4 4 1 15.0 1
    Done

    mmwDemo:/>multiObjBeamForming -1 1 0.5
    Done

    mmwDemo:/>calibDcRangeSig -1 0 -5 8 256
    Done

    mmwDemo:/>extendedMaxVelocity -1 0
    Done

    mmwDemo:/>clutterRemoval -1 0
    Done

    mmwDemo:/>compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    Done

    mmwDemo:/>measureRangeBiasAndRxChanPhase 0 1.5 0.2
    Done

    mmwDemo:/>aoaFovCfg -1 -90 90 -90 90
    Done

    mmwDemo:/>cfarFovCfg -1 0 0.25 9.71
    Done

    mmwDemo:/>cfarFovCfg -1 1 -7.49 7.49
    Done

    mmwDemo:/>CQRxSatMonitor 0 3 4 127 0
    Done

    mmwDemo:/>CQSigImgMonitor 0 63 8
    Done

    mmwDemo:/>analogMonitor 0 0
    Done

    mmwDemo:/>lvdsStreamCfg -1 0 0 0
    Done

    mmwDemo:/>sensorStart
    Debug: Init Calibration Status = 0x7fe

    Done

    -------------------------------------------------------------------------------------

    Regards,
    Kyle