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: lab0003_occupancy_detection can not run

Part Number: AWR1642

Hi expert,

I'm trying to run lab0003_occupancy_detection in mmwave_automotive_toolbox_2_2_0 package on AWR1642 ES2.0 EVM. But the test is failed.  My test steps is 

1. Burn odd_demo_16xx.bin in mmwave_automotive_toolbox_2_2_0\labs\lab0003_occupancy_detection\prebuilt_binaries

2. Remove SOP2 and power up EVM

3. Run od_demo as below 

xxx\mmwave_automotive_toolbox_2_2_0\labs\lab0003_occupancy_detection\gui\od_demo.exe 64 65 xxx\mmwave_automotive_toolbox_2_2_0\labs\lab0003_occupancy_detection\chirp_configs\od_demo_car_0318_1p0.cfg 1 0

There is no output in the demo visualization window. Please help to check what is wrong. Thank you.

Regards,

Allen

  • Hello Allen,

    Could you check by download the pre-built binaries of MSS and DSS using CCS and see if you have the same issue?

    -Raghu
  • Hi Raghu,

    I tried but got same issue.

    From CCS log, the Sensor is stalled after 'Sensor has been stopped'.

    [C674X_0] Debug: MMWDemoDSS mmWave Control Initialization succeeded
    [Cortex_R4_0] **********************************************
    Debug: Launching the Millimeter Wave Demo
    **********************************************
    Debug: MMWDemoMSS Launched the Initialization Task
    Debug: MMWDemoMSS mmWave Control Initialization was successful
    Debug: CLI is operational
    Sensor has been stopped

    Regards,

    Allen

  • Allen,

    Please ensure that that pins on SOP0 are still tied together with a jumper. SOP0 should remain closed for both the flashing and running process.

    Try using the following command: od_demo.exe 64 65 ..\chirp_configs\od_demo_car_0318_1p0.cfg 1 0 in the command.

    Call this from the xxxx\mmwave_automotive_toolbox_2_2_0\labs\lab0003_occupancy_detection\gui folder

    The Sensor is not stalled. The "Sensor has been stopped" entry comes after the "sensorStop" CLI command is issued to the device. This is part of normal operation as the sensorStop command is a mandatory command for any configuration (*.cfg) file.

    Regards,
    Kyle