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.

AWR1642: Can't get the vitalSigns example to run

Part Number: AWR1642

Hi, 

I am trying to run the example in the mmwave_automotive_toolbox_2_4_3.

After downloading the vitalSigns_16xx.bin,  I execute VitalSignsRadar_Demo.

Then I get the following logs,

Configuration File Path is %s/n "E:/WORK/mmwave_automotive_toolbox_2_4_3/labs/lab0001-driver-vital-signs/vitalSigns_host/profiles/xwr1642_profile_VitalSigns_20fps_Front.cfg"
"sensorStop"
"flushCfg"
"dfeDataOutputMode 1"
"channelCfg 15 3 0"
"adcCfg 2 1"
"adcbufCfg -1 0 0 1 0"
"profileCfg 0 77 7 6 57 0 0 70 1 200 4000 0 0 48"
"chirpCfg 0 0 0 0 0 0 0 1"
"frameCfg 0 0 2 0 50 1 0"
"lowPower 0 1"
"guiMonitor 0 0 0 0 1"
"calibDcRangeSig -1 0 0 0 0"
"vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000"
"motionDetection 1 20 2.0 0"
"sensorStart"
""
"sensorStop"
"flushCfg"
"dfeDataOutputMode 1"
"channelCfg 15 3 0"
"adcCfg 2 1"
"adcbufCfg -1 0 0 1 0"
"profileCfg 0 77 7 6 57 0 0 70 1 200 4000 0 0 48"
"chirpCfg 0 0 0 0 0 0 0 1"
"frameCfg 0 0 2 0 50 1 0"
"lowPower 0 1"
"guiMonitor 0 0 0 0 1"
"calibDcRangeSig -1 0 0 0 0"
"vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000"
0.3
0.9
4
"motionDetection 1 20 2.0 0"
"sensorStart"
""
Chirp Duration in us is : 50
Chirp Bandwidth in kHz is : 3500
Maximum Range in Meters is : 8.57143
Range-FFT size is : 256
Range-Bin size is : 0.0334821
Range-Bin Start Index is : 8
Range-Bin End Index is : 26
Total Payload size from the UART is : 260
Padding Factor is : 9
Total Payload size from the UART is : 288

I can't get any signal, so I try to execute the those commands in the cfg file through putty.

mmwDemo:/>sensorStop
Done
mmwDemo:/>flushCfg
Done
mmwDemo:/>dfeDataOutputMode 1
Done
mmwDemo:/>channelCfg 15 3 0
Done
mmwDemo:/>adcCfg 2 1
Done
mmwDemo:/>adcbufCfg -1 0 0 1 0
Done
mmwDemo:/>profileCfg 0 77 7 6 57 0 0 70 1 100 2000 0 0 40
Done
mmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1
Done
mmwDemo:/>frameCfg 0 0 2 0 50 1 0
Done
mmwDemo:/>lowPower 0 1
Done
mmwDemo:/>guiMonitor 0 0 0 0 1
Done
mmwDemo:/>calibDcRangeSig -1 0 0 0 0
Error: Number of averaged chirps is not power of two
Error -1
mmwDemo:/>vitalSignsCfg 0.1 0.7 256 320 1 0.1 0.05 300000 300000
Done
mmwDemo:/>motionDetection 1 20 0.04 0
Done
mmwDemo:/>sensorStart
Debug: Init Calibration Status = 0x7fe
Done

It seems the cfg is something wrong?

  • Hi,
    This print should be coming only when CalibDCRange feaure is enable via CLI command, as this is not enabled in your config file, so you can ignore this error message. It won't impact any of functionality of the application.
    Try to remove 'calibDcRangeSig -1 0 0 0 0' command from *.cfg file and then run with VitalSignsRadar_Demo tool.


    Regards,
    Jitendra
  • mmwDemo:/>sensorStop
    Done
    mmwDemo:/>flushCfg
    Done
    mmwDemo:/>dfeDataOutputMode 1
    Done
    mmwDemo:/>dfeDataOutputMode 1
    Done
    mmwDemo:/>dfeDataOutputMode 1
    Done
    mmwDemo:/>adcbufCfg -1 0 0 1 0
    Done
    mmwDemo:/>profileCfg 0 77 7 6 57 0 0 70 1 200 4000 0 0 48
    Done
    mmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1
    Done
    mmwDemo:/>frameCfg 0 0 2 0 50 1 0
    Done
    mmwDemo:/>
    mmwDemo:/>
    mmwDemo:/>lowPower 0 1
    Done
    mmwDemo:/>guiMonitor 0 0 0 0 1
    Done
    mmwDemo:/>vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000
    Done
    mmwDemo:/>motionDetection 1 20 2.0 0
    Done
    mmwDemo:/>sensorStart
    Debug: Init Calibration Status = 0x11e
    Error -1

    I remove that line, and now I still get error.

  • Hi,
    Could you connect to CCS (MSS core) at this error condition and provide values of these memory [0xF0601000 - 0xF0601040] and [0xF0602000 - 0xF0602040] from memory browser of CCS. It'll help us to find the cause of this error.


    Regards,
    Jitendra
  • Due to inactivity we are closing this thread.
    Please reply back to re-open this thread if needed.

    Regards,
    Jitendra