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.

IWR6843ISK-ODS: IWR6843ISK-ODS #D People Counting demo not working

Part Number: IWR6843ISK-ODS
Other Parts Discussed in Thread: UNIFLASH, MMWAVEICBOOST, IWR6843, IWR6843ISK, IWR6843AOPEVM

Tool/software:

1. I have flashed binary from following path using uniflash  (SPO0 and SPO2 In ON condition):

    C:\Users\mmwave_industrial_toolbox_4_12_0\mmwave_industrial_toolbox_4_12_0\labs\People_Counting\3D_People_Counting\prebuilt_binaries\3D_people_count_68xx_demo.bin 

    Flashing is successful

2. Now I have removed SOP2 jumper From MMWAVEICBOOST board.

3. Rebooted setup.

4. Opened Virtualizer from following path:

   C:\Users\\mmwave_industrial_toolbox_4_12_0\mmwave_industrial_toolbox_4_12_0\tools\Visualizer\mmWave_Industrial_Visualizer.exe 

5. Here selected following:

    a. Demo : 3D people counting

    b. Clicked in connect

    c. Configuration :C:\Users\110813\Downloads\mmwave_industrial_toolbox_4_12_0\mmwave_industrial_toolbox_4_12_0\labs\People_Counting\3D_People_Counting\chirp_configs\ODS_6m_default.cfg

    d. Clicked on Start and Send Configuration

Getting Following on console:

Python is 64 bit
Python version: sys.version_info(major=3, minor=6, micro=0, releaselevel='final', serial=0)
CLI COM Port found: COM3
Data COM Port found: COM4
Demo Changed to: 3D People Counting
{'startFreq': 60.75, 'numLoops': 64, 'numTx': 3, 'sensorHeight': 3.0, 'maxRange': 10, 'az_tilt': 0, 'elev_tilt': 0, 'idle': 30.0, 'adcStart': 25.0, 'rampEnd': 59.1, 'slope': 54.71, 'samples': 96.0, 'sampleRate': 2950.0}
Sensor Height from cfg = 2.0
Parser type: 3D People Counting
Connected
b'% SDK Parameters\n'
b''
b"% See the SDK user's gide for more informatin\n"
b''
b'% "C:\\ti\\mmwave_sdk_[VR]\\docs\\mmwave_sdk_use_guide.pdf"\n'
b''
b'sensorStop\n'
b''
b'flushCfg\n'
b''
b'dfeDataOutputMode 1\n'
b''
b'channelCfg 15 7 0\n'
b''
b'adcCfg 2 1\n'
b''
b'adcbufCfg -1 0 1 1 1\n'
b''
b'lowPower 0 0\n'
b''
b'\n'
b''
b'% Detection Layer Paraeters\n'
b''
b'% See the Detection Laer Tuning Guide for moe information\n'
b''
b'% "C:\\ti\\mmwave_industial_toolbox_[VER]\\labspeople_counting\\docs\\3_people_counting_detetion_layer_tuning_guid.pdf"\n'
b''
b'profileCfg 0 60.75 30.0 25.00 59.10 657930 054.71 1 96 2950.00 2 136 \n'
b''
b'chirpCfg 0 0 0 0 0 0 01\n'
b''
b'chirpCfg 1 1 0 0 0 0 02\n'
b''
b'chirpCfg 2 2 0 0 0 0 04\n'
b''
b'frameCfg 0 2 96 0 5500 1 0\n'
b''
b'dynamicRACfarCfg -1 4 2 2 8 12 4 12 5.00 8.0 0.40 1 1\n'
b''
b'staticRACfarCfg -1 6 22 2 8 8 6 4 8.00 15.000.30 0 0\n'
b''
b'dynamicRangeAngleCfg - 0.75 0.0010 1 0\n'
b''
b'dynamic2DAngleCfg -1 30 0.0300 1 0 1 0.30 0.5 8.00\n'
b''
b'staticRangeAngleCfg -10 8 8\n'
b''
b'antGeometry0 0 0 -1 -1-2 -2 -3 -3 -2 -2 -3 -\n'
b''
b'antGeometry1 0 -1 -1 00 -1 -1 0 -2 -3 -3 -2\n'
b''
b'antPhaseRot 1 -1 -1 1 -1 -1 1 1 -1 -1 1\n'
b''
b'fovCfg -1 70.0 70.0\n'
b''
b'compRangeBiasAndRxChanhase 0 1 0 1 0 1 0 1 01 0 1 0 1 0 1 0 1 0 1 1 0 1 0\n'
b''
b'\n'
b''
b'% Tracker Layer Parameers\n'
b''
b'% See the Tracking Layr Tuning Guide for mor information\n'
b''
b'% "C:\\ti\\mmwave_industial_toolbox_[VER]\\labspeople_counting\\docs\\3_people_counting_tracer_layer_tuning_guide.df"\n'
b''
b'staticBoundaryBox -3 30.5 7.5 0 3\n'
b''
b'boundaryBox -4 4 0 8 03\n'
b''
b'sensorPosition 2 0 15\n'
b''
b'gatingParam 3 2 2 3 4\n'
b''
b'stateParam 3 3 12 500 6000\n'
b''
b'allocationParam 20 1000.1 20 0.5 20\n'
b''
b'maxAcceleration 0.1 0. 0.1\n'
b''
b'trackingCfg 1 2 800 3046 96 55\n'
b''
b'presenceBoundaryBox -33 0.5 7.5 0 3\n'
b''
b'sensorStart\n'
b''
Traceback (most recent call last):
File "gui_threads.py", line 40, in run
outputDict = self.parser.readAndParseUart()
File "gui_parser.py", line 74, in readAndParseUart
if (magicByte[0] == magicWord[index]):
IndexError: index out of range
Traceback (most recent call last):

Why domo is not working?

Please find images of board

  • Hi,

    Can you update to the latest toolbox release and try again? You can use the 3d people tracking project, it is the same code.

    Best,

    Nate

  • Can you please let me know latest version of toolbox. Or can you please share the link of latest toolbox.

  • I Used radar toolbox version 2.30.00.12 still not able to startSendor

  • I used radar toolbox: radar_toolbox_2_30_00_12 and used following steps:

    1.  Connected SOP0 and SOP2 Jumpers and flashed following bin file:

         C:\ti\radar_toolbox_2_30_00_12\source\ti\examples\Industrial_and_Personal_Electronics\People_Tracking\3D_People_Tracking\prebuilt_binaries\3D_people_track_6843_demo.bin

    2. After Successful flashing: Removed SOP2 Jumper (To go into functional mode)

    3. Now opened virtualizer from following path:

    C:\ti\radar_toolbox_2_30_00_12\tools\visualizers\Applications_Visualizer\Industrial_Visualizer\Industrial_Visualizer.exe

    4. In Virtualizer click on connect. Device connected as shown in below image:

    5. Clicked on select configuration and selected following configuration:

    C:\ti\radar_toolbox_2_30_00_12\source\ti\examples\Industrial_and_Personal_Electronics\People_Tracking\3D_People_Tracking\chirp_configs\ODS_6m_default.cfg 

    6. Clicked on Start and Send Configuration following is console log:

    INFO [gui_core.py:265] CLI COM Port found: COM3
    INFO [gui_core.py:274] Data COM Port found: COM4
    INFO [gui_parser.py:287] Connected
    b'sensorStop\n'
    b'Done\n'
    b'\rmmwDemo:/>flushCfg\n'
    b'Done\n'
    b'\rmmwDemo:/>dfeDataOutputMode 1\n'
    b'Done\n'
    b'\rmmwDemo:/>channelCfg 15 7 0\n'
    b'Done\n'
    b'\rmmwDemo:/>adcCfg 2 1\n'
    b'Done\n'
    b'\rmmwDemo:/>adcbufCfg -1 0 1 1 1\n'
    b'Done\n'
    b'\rmmwDemo:/>lowPower 0 0\n'
    b'Done\n'
    b'\rmmwDemo:/>profileCfg 0 60.75 30.00 25.00 59.10 657930 0 54.71 1 96 2950.00 2 1 36 \n'
    b'Done\n'
    b'\rmmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1\n'
    b'Done\n'
    b'\rmmwDemo:/>chirpCfg 1 1 0 0 0 0 0 2\n'
    b'Done\n'
    b'\rmmwDemo:/>chirpCfg 2 2 0 0 0 0 0 4\n'
    b'Done\n'
    b'\rmmwDemo:/>frameCfg 0 2 96 0 55.00 1 0\n'
    b'Done\n'
    b'\rmmwDemo:/>dynamicRACfarCfg -1 4 4 2 2 8 12 4 12 5.00 8.00 0.40 1 1\n'
    b"'dynamicRACfarCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>staticRACfarCfg -1 6 2 2 2 8 8 6 4 8.00 15.00 0.30 0 0\n'
    b"'staticRACfarCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>dynamicRangeAngleCfg -1 0.75 0.0010 1 0\n'
    b"'dynamicRangeAngleCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>dynamic2DAngleCfg -1 3.0 0.0300 1 0 1 0.30 0.85 8.00\n'
    b"'dynamic2DAngleCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>staticRangeAngleCfg -1 0 8 8\n'
    b"'staticRangeAngleCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>antGeometry0 0 0 -1 -1 -2 -2 -3 -3 -2 -2 -3 -3\n'
    b"'antGeometry0' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>antGeometry1 0 -1 -1 0 0 -1 -1 0 -2 -3 -3 -2\n'
    b"'antGeometry1' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>antPhaseRot 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1\n'
    b"'antPhaseRot' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>fovCfg -1 70.0 70.0\n'
    b"'fovCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>compRangeBiasAndRxChanPhase 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0\n'
    b'Done\n'
    b'\rmmwDemo:/>staticBoundaryBox -3 3 0.5 7.5 0 3\n'
    b"'staticBoundaryBox' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>boundaryBox -4 4 0 8 0 3\n'
    b"'boundaryBox' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>sensorPosition 2 0 15\n'
    b"'sensorPosition' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>gatingParam 3 2 2 3 4\n'
    b"'gatingParam' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>stateParam 3 3 12 500 5 6000\n'
    b"'stateParam' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>allocationParam 20 100 0.1 20 0.5 20\n'
    b"'allocationParam' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>maxAcceleration 0.1 0.1 0.1\n'
    b"'maxAcceleration' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>trackingCfg 1 2 800 30 46 96 55\n'
    b"'trackingCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>presenceBoundaryBox -3 3 0.5 7.5 0 3\n'
    b"'presenceBoundaryBox' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>sensorStart\n'
    b'Debug: Init Calibration Status = 0x1e\n'
    ERROR [gui_parser.py:79] ERROR: No data detected on COM Port, read timed out
    ERROR [gui_parser.py:80] Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR [gui_parser.py:79] ERROR: No data detected on COM Port, read timed out
    ERROR [gui_parser.py:80] Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR [gui_parser.py:79] ERROR: No data detected on COM Port, read timed out

    In Device manager able to see COM port:

    How to resolve this Error?

    Image of sensor for reference: 

    Image of MMWAVEICBOOST for reference:

    Please let me know if I am missing any step? 

    Regards,

    Arifchand

  • Hi,

    Something is going wrong in the flashing process. The device is not recognizing the commands for the people counting demo. Can you show screenshots of successfully flashing the board?

    Best,

    Nate

  • Please find snapshot of successfully flashing:

    Also find the log of flashing as below:

    1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Initialization complete.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Flashing process starting...
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Connecting to COM Port COM3...
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Reset connection to device
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Set break signal
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Connection to COM port succeeded. Flashing can proceed.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Reading device version info...
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: ** 1 files specified for flashing.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Checking file C:/ti/radar_toolbox_2_30_00_12/source/ti/examples/Industrial_and_Personal_Electronics/People_Tracking/3D_People_Tracking/prebuilt_binaries/3D_people_track_6843_demo.bin for correct header for IWR6843.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: IWR6843 device, fileType=META_IMAGE1 detected -> OK
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: !! Files are valid for IWR6843.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Format on download was specified. Formatting SFLASH storage...
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: -->Erasing storage [SFLASH]
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: -->Sending Erase command to device...
    [1/27/2025, 11:56:22 AM] [SUCCESS] Cortex_R4_0: -->Erase storage completed successfully!
    [1/27/2025, 11:56:22 AM] [INFO] Cortex_R4_0: Downloading [META_IMAGE1] size [625668]
    [1/27/2025, 11:57:38 AM] [INFO] Cortex_R4_0: SUCCESS!! File type META_IMAGE1 downloaded successfully to SFLASH.
    [1/27/2025, 11:57:38 AM] [INFO] Cortex_R4_0: Disconnecting from device on COM port COM3...
    [1/27/2025, 11:57:38 AM] [INFO] Cortex_R4_0: Flashing instance clean-up initiated...
    [1/27/2025, 11:57:38 AM] [INFO] Cortex_R4_0: Instance deinitialized!
    [1/27/2025, 11:57:38 AM] [SUCCESS] Program Load completed successfully.

    Regads,

    Arifchand

  • Thank you - it appears that the flashing is successful. Can you open a serial port at 115200 baud and see what the output is for the sensor? It should show a banner with the people counting demo when it's back in functional mode. I am asking this because the output you showed earlier showed the system accepting the CLI commands that correspond to the out-of-box demo, but not the ones that correspond to the people counting demo.

    Best,

    Nate

  • 1. Should I open a serial port using application like Putty and show output of that on that terminal? 

    2. Or should I run flash and run out-of-box demo? (If yes which cfg file should I use?)

    Please let me know steps.

    Regards,

    Arifchand

  • Please open a serial port applciation and show output.

    Best,

    Nate

  • Hello,

    I connect with COM3 with 115200 baud rate. Nothin appeared on the terminal.

    If possible we can have a call and try to resolve this.

    Regards,

    Arifchand

  • Hello,

    Any update on this issue? Any further steps to be performed?

    Regards,

    Arifchand

  • Hello Nathan,

    Any update on this issue? Any further steps to be performed?

    Regards,

    Arifchand

  • Hi Arifchand, 

    Sorry for the delay here, Nathan has been out of office. When you connect to the com port in putty, can you please confirm the device has been switched to functional mode after flashing (don't forget to reset/power-cycle after removing the jumper connection for sop2)? Also, when connected at 115200, if you press 'enter' in the terminal window do you get any response?

    Best Regards,

    Josh

  • Hello,

    After successful flashing. Followed following steps:

    1. switch of power supply

    2. Removed SOP2 jumper to enter into functional mode

    3. switch on power supply(here reset/power-cycle happen)

    4. Connect to COM port using putty with 115200 baud rate

    Nothing appears at the putty terminal.

    Even after pressing enter nothing appears on the terminal

    Regards,

    Arifchand Mulani

  • Hi,

    Can you confirm you're connecting to the correct COM port? Based off the output that you showed above, you should at least see a banner or something in the terminal.

    INFO [gui_core.py:265] CLI COM Port found: COM3
    INFO [gui_core.py:274] Data COM Port found: COM4
    INFO [gui_parser.py:287] Connected
    b'sensorStop\n'
    b'Done\n'
    b'\rmmwDemo:/>flushCfg\n'
    b'Done\n'
    b'\rmmwDemo:/>dfeDataOutputMode 1\n'
    b'Done\n'
    b'\rmmwDemo:/>channelCfg 15 7 0\n'
    b'Done\n'
    b'\rmmwDemo:/>adcCfg 2 1\n'
    b'Done\n'
    b'\rmmwDemo:/>adcbufCfg -1 0 1 1 1\n'
    b'Done\n'
    b'\rmmwDemo:/>lowPower 0 0\n'
    b'Done\n'
    b'\rmmwDemo:/>profileCfg 0 60.75 30.00 25.00 59.10 657930 0 54.71 1 96 2950.00 2 1 36 \n'
    b'Done\n'
    b'\rmmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1\n'
    b'Done\n'

    Is this above behavior still replicable?

    Are you also sure you're following all the steps in the guide correctly?

    https://dev.ti.com/tirex/explore/node?a=1AslXXD__1.00.01.07&a=1AslXXD__2.30.00.12&node=A__AQysBCTq3bbJofcBLdm7MA__radar_toolbox__1AslXXD__2.30.00.12&r=1AslXXD__1.00.00.26

    Best,

    Nate

  • I used radar toolbox: radar_toolbox_2_30_00_12 and used following steps:

    1. Power off device

    2.  Connected SOP0 and SOP2 Jumpers. 

    3. Power on device

    4.  flashed following bin file: 

         C:\ti\radar_toolbox_2_30_00_12\source\ti\examples\Industrial_and_Personal_Electronics\People_Tracking\3D_People_Tracking\prebuilt_binaries\3D_people_track_6843_demo.bin

    Please find snapshot of successfully flashing:

    Also find the log of flashing as below:

    1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Initialization complete.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Flashing process starting...
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Connecting to COM Port COM3...
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Reset connection to device
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Set break signal
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Connection to COM port succeeded. Flashing can proceed.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Reading device version info...
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: ** 1 files specified for flashing.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Checking file C:/ti/radar_toolbox_2_30_00_12/source/ti/examples/Industrial_and_Personal_Electronics/People_Tracking/3D_People_Tracking/prebuilt_binaries/3D_people_track_6843_demo.bin for correct header for IWR6843.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: IWR6843 device, fileType=META_IMAGE1 detected -> OK
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: !! Files are valid for IWR6843.
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: Format on download was specified. Formatting SFLASH storage...
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: -->Erasing storage [SFLASH]
    [1/27/2025, 11:56:11 AM] [INFO] Cortex_R4_0: -->Sending Erase command to device...
    [1/27/2025, 11:56:22 AM] [SUCCESS] Cortex_R4_0: -->Erase storage completed successfully!
    [1/27/2025, 11:56:22 AM] [INFO] Cortex_R4_0: Downloading [META_IMAGE1] size [625668]
    [1/27/2025, 11:57:38 AM] [INFO] Cortex_R4_0: SUCCESS!! File type META_IMAGE1 downloaded successfully to SFLASH.
    [1/27/2025, 11:57:38 AM] [INFO] Cortex_R4_0: Disconnecting from device on COM port COM3...
    [1/27/2025, 11:57:38 AM] [INFO] Cortex_R4_0: Flashing instance clean-up initiated...
    [1/27/2025, 11:57:38 AM] [INFO] Cortex_R4_0: Instance deinitialized!
    [1/27/2025, 11:57:38 AM] [SUCCESS] Program Load completed successfully.

    5. Power off device 

    6. After Successful flashing: Removed SOP2 Jumper (To go into functional mode)

    7. Power on device 

    8. Now opened visualizer from following path:

    C:\ti\radar_toolbox_2_30_00_12\tools\visualizers\Applications_Visualizer\Industrial_Visualizer\Industrial_Visualizer.exe

    9. In visualizer  click on connect. Device connected as shown in below image:

    10. Clicked on select configuration and selected following configuration:

    C:\ti\radar_toolbox_2_30_00_12\source\ti\examples\Industrial_and_Personal_Electronics\People_Tracking\3D_People_Tracking\chirp_configs\ODS_6m_default.cfg 

    11. Clicked on Start and Send Configuration

    Checked visualizer command prompt. following is log on visualizers command prompt:

    INFO [gui_core.py:265] CLI COM Port found: COM3
    INFO [gui_core.py:274] Data COM Port found: COM4
    INFO [gui_parser.py:287] Connected
    b'sensorStop\n'
    b'Done\n'
    b'\rmmwDemo:/>flushCfg\n'
    b'Done\n'
    b'\rmmwDemo:/>dfeDataOutputMode 1\n'
    b'Done\n'
    b'\rmmwDemo:/>channelCfg 15 7 0\n'
    b'Done\n'
    b'\rmmwDemo:/>adcCfg 2 1\n'
    b'Done\n'
    b'\rmmwDemo:/>adcbufCfg -1 0 1 1 1\n'
    b'Done\n'
    b'\rmmwDemo:/>lowPower 0 0\n'
    b'Done\n'
    b'\rmmwDemo:/>profileCfg 0 60.75 30.00 25.00 59.10 657930 0 54.71 1 96 2950.00 2 1 36 \n'
    b'Done\n'
    b'\rmmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1\n'
    b'Done\n'
    b'\rmmwDemo:/>chirpCfg 1 1 0 0 0 0 0 2\n'
    b'Done\n'
    b'\rmmwDemo:/>chirpCfg 2 2 0 0 0 0 0 4\n'
    b'Done\n'
    b'\rmmwDemo:/>frameCfg 0 2 96 0 55.00 1 0\n'
    b'Done\n'
    b'\rmmwDemo:/>dynamicRACfarCfg -1 4 4 2 2 8 12 4 12 5.00 8.00 0.40 1 1\n'
    b"'dynamicRACfarCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>staticRACfarCfg -1 6 2 2 2 8 8 6 4 8.00 15.00 0.30 0 0\n'
    b"'staticRACfarCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>dynamicRangeAngleCfg -1 0.75 0.0010 1 0\n'
    b"'dynamicRangeAngleCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>dynamic2DAngleCfg -1 3.0 0.0300 1 0 1 0.30 0.85 8.00\n'
    b"'dynamic2DAngleCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>staticRangeAngleCfg -1 0 8 8\n'
    b"'staticRangeAngleCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>antGeometry0 0 0 -1 -1 -2 -2 -3 -3 -2 -2 -3 -3\n'
    b"'antGeometry0' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>antGeometry1 0 -1 -1 0 0 -1 -1 0 -2 -3 -3 -2\n'
    b"'antGeometry1' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>antPhaseRot 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1\n'
    b"'antPhaseRot' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>fovCfg -1 70.0 70.0\n'
    b"'fovCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>compRangeBiasAndRxChanPhase 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0\n'
    b'Done\n'
    b'\rmmwDemo:/>staticBoundaryBox -3 3 0.5 7.5 0 3\n'
    b"'staticBoundaryBox' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>boundaryBox -4 4 0 8 0 3\n'
    b"'boundaryBox' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>sensorPosition 2 0 15\n'
    b"'sensorPosition' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>gatingParam 3 2 2 3 4\n'
    b"'gatingParam' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>stateParam 3 3 12 500 5 6000\n'
    b"'stateParam' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>allocationParam 20 100 0.1 20 0.5 20\n'
    b"'allocationParam' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>maxAcceleration 0.1 0.1 0.1\n'
    b"'maxAcceleration' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>trackingCfg 1 2 800 30 46 96 55\n'
    b"'trackingCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>presenceBoundaryBox -3 3 0.5 7.5 0 3\n'
    b"'presenceBoundaryBox' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>sensorStart\n'
    b'Debug: Init Calibration Status = 0x1e\n'
    ERROR [gui_parser.py:79] ERROR: No data detected on COM Port, read timed out
    ERROR [gui_parser.py:80] Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR [gui_parser.py:79] ERROR: No data detected on COM Port, read timed out
    ERROR [gui_parser.py:80] Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR [gui_parser.py:79] ERROR: No data detected on COM Port, read timed out

    In Device manager able to see COM port:

    12. Closed Visualizer terminal and app.  

    13. Turn off device (wait for more than 1 min)

    14 Turn on device

    15. Open Putty application connect to COM3 with 115200 baud rate

    16. Nothing appears on putty terminal. Even after pressing enter nothing appears on putty terminal.

    Still Demo is not working. Let me know if I am missing anything.

    Let me know when can we connect over call for better understanding issue.

    Regards,

    Arifchand

  • Hello Nathon, Also attaching a video of the process to better understand the issue. 

    Please find the attached video.

    Need help to resolve this issue.

    Regards,

    Arifchand 

  • Hello,

    Shared all steps followed and also the video while following steps. Please refer to that and let me know if anything is missing. 

    Need help to resolve this issue. 

    Regards,

    Arifchand

  • Hello Nathan, 

    Did you get chance to check video of all steps followed. Any update on this issue?

    Any steps further needed to perform to resolve this issue? Please let me know anything that has to done from my side.

    Regards,

    Arifchand Mulani

  • Hello Nathan,

    Did you get chance to go through video of all steps followed. Is there anything missing?

    Let me know if anything that has to be checked at myside.

    Need help to resolve this issue.

    Regards,

    Arifchand

  • Hello,

    Is there any update on this issue.

    Regards,

    Arifchand Mulani

  • Hello Nathan,

    Did you get chance to go through the video. Any update on this issue?

    Need help to resolve this issue. Let me know if anything has to be done from my side.

    Regards,

    Arifchand Mulani

  • Hi,

    Can you try with the USB plugged into the FTDI port unplugged? Perhaps this is getting in the way of the UART. This demo doesn't need the FTDI to run.

    Best,

    Nate

  • Hello Nathan,

    I removed FTDI cable and followed same process. Still demo is not working.

    Regards,

    Arifchand Mulani

  • Hi,

    I wonder if there is something wrong with the board hardware. Are you able to test on a different board that plugs into the MMWAVEICBOOST? Such as the IWR6843ISK or IWR6843AOPEVM?

    Best,

    Nate