• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 32 subscribers
  • Views 352 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.

IWR6843AOPEVM: Small Obstacle Detection User Guide Issues

Mike Schoonover
Prodigy 20 points
Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: IWR6843, IWR6843ISK, ALP, UNIFLASH, , IWR6843AOP

I am working my through the 'Small Obstacle Detection User Guide' and there a few issues.

I am starting a thread to resolve each of these in one place so maybe others can benefit.

First issue:

 IWR6843 ES2.0 Only This lab is only compatible with ES2.0 version of IWR6843. On ISK, check the device version on your IWR6843 using the on-chip device markings as shown below

  1. If line 4 reads 678A, you have an ES2 device. In this case, this lab is compatible with your EVM.
  2. If line 4 reads 60 GHZi, you have an older ES1 device. In this case, the lab is NOT compatible with your EVM. ES2 IWR6843ISK boards are orderable from the EVM link above.

My chip has neither of these markings. Mine has:

IWR6843   QG   ALP             G1

                                   21ZC1MA

So...is my chip an ES2 device or not?

  • +1
    Prodigy 20 points

    I flashed with: C:\ti\radar_toolbox_1_20_00_11\source\ti\examples\Robotics\Small_Obstacle_Detection\prebuilt_binaries

    I ran the Visualizer and connected with:

    Device: IWR6843
    Demo: Small Obstacle Detection
    Select Configuration: AOP_3d_Tracking_Small_Obstacle_Indoor.cfg

    Reported: ERROR: More zones specified by cfg than are supported in this GUI

    Several  'is not recognized as a CLI command' errors reported.

    Then repeated errors:

    ERROR: No data detected on COM Port, read timed out
    Be sure that the device is in the proper mode, and that the cfg you are sending is valid

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

    Copy of the messages in the PowerShell window:

    Python is 64 bit
    Python version: sys.version_info(major=3, minor=7, micro=9, releaselevel='final', serial=0)
    CLI COM Port found: COM7
    Data COM Port found: COM8
    Demo Changed to: Small Obstacle Detection
    Parser type: Small Obstacle Detection
    Connected
    {'startFreq': 60.75, 'numLoops': 64, 'numTx': 3, 'sensorHeight': 1.0, 'maxRange': 10, 'az_tilt': 0, 'elev_tilt': 0, 'enabled': 0, 'idle': 10.0, 'adcStart': 10.0, 'rampEnd': 59.1, 'slope': 54.71, 'samples': 94.0, 'sampleRate': 3000.0}
    ERROR: More zones specified by cfg than are supported in this GUI
    0
    b'% SDK Parameters\n'
    b'Skipped\n'
    b"\rmmwDemo:/>% See the SDK user's guide for more information\n"
    b'Skipped\n'
    b'\rmmwDemo:/>% "C:\\ti\\mmwave_sdk_[VER]\\docs\\mmwave_sdk_user_guide.pdf"\n'
    b'Skipped\n'
    b'\rmmwDemo:/>sensorStop\n'
    b'Ignored: Sensor is already stopped\n'
    b'\rDone\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:/>% Detection Layer Parameters\n'
    b'Skipped\n'
    b'\rmmwDemo:/>% See the Detection Layer Tuning Guide for more information\n'
    b'Skipped\n'
    b'\rmmwDemo:/>% "<RADAR_TOOLBOX_INSTALL_DIR>\\source\\ti\\examples\\People_Tracking\\docs\\3D_people_tracking_detection_layer_tuning_guide.pdf"\n'
    b'Skipped\n'
    b'\rmmwDemo:/>profileCfg 0 60.75 10.00 10.00 59.10 0 0 54.71 1 94 3000.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 64 0 50 1 0\n'
    b'Done\n'
    b'\rmmwDemo:/>dynamicRACfarCfg -1 4 1 2 2 8 12 4 8 12.00 19.00 0.40 1 1\n'
    b"'dynamicRACfarCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>staticRACfarCfg -1 20 20 2 2 8 8 6 4 23.00 31.00 0.60 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 1.5 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 1 30 10\n'
    b"'staticRangeAngleCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>antGeometry0 -1 -1 0 0 -3 -3 -2 -2 -1 -1 0 0\n'
    b"'antGeometry0' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>antGeometry1 -1 0 -1 0 -3 -2 -3 -2 -3 -2 -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 20.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:/>% Tracker Layer Parameters\n'
    b'Skipped\n'
    b'\rmmwDemo:/>% See the Tracking Layer Tuning Guide for more information\n'
    b'Skipped\n'
    b'\rmmwDemo:/>% "C:\\ti\\mmwave_industrial_toolbox_[VER]\\labs\\people_counting\\docs\\3D_people_counting_tracker_layer_tuning_guide.pdf"\n'
    b'Skipped\n'
    b'\rmmwDemo:/>staticBoundaryBox -1.8 1.8 0.2 1.5 0.0 2.0\n'
    b"'staticBoundaryBox' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>boundaryBox -1.8 1.8 0.2 1.5 0.0 2.0\n'
    b"'boundaryBox' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>sensorPosition 0.5 0 0\n'
    b"'sensorPosition' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>gatingParam 4 2 2 2 10\n'
    b"'gatingParam' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>stateParam 12 12 6 13 5 250\n'
    b"'stateParam' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>allocationParam 15 15 0.05 15 0.5 3\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 400 10 20 260 94\n'
    b"'trackingCfg' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>presenceBoundaryBox -1.8 1.8 0.2 1.5 0.0 2.0\n'
    b"'presenceBoundaryBox' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>% numZones, pointsEntryThreshold, snrEntryThreshold, frameEntryThreshold, pointsMaintainThreshold, snrMaintainThreshold, pointsExitThreshold, frameExitThreshold\n'
    b'Skipped\n'
    b'\rmmwDemo:/>occStateMach 10 10 10 1 1 5 1 15\n'
    b"'occStateMach' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>% ZoneNumber minx maxx miny maxy minz maxz\n'
    b'Skipped\n'
    b'\rmmwDemo:/>zoneDef 0 -1.8 1.8 0.2 1.5 -0.5 1.5\n'
    b"'zoneDef' is not recognized as a CLI command\n"
    b'\rmmwDemo:/>sensorStart\n'
    ERROR: No data detected on COM Port, read timed out
    Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR: No data detected on COM Port, read timed out
    Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ERROR: No data detected on COM Port, read timed out
    Be sure that the device is in the proper mode, and that the cfg you are sending is valid
    ...

  • +1 in reply to Mike Schoonover
    Prodigy 20 points

    I rebooted the computer and started the Visualizer without running anything else. Still fails.

    Reflashed with Robotics\Small_Obstacle_Detection\prebuilt_binaries

    UniFlash reported:

    [8/3/2023, 2:59:19 PM] [INFO] Cortex_R4_0: Initialization complete
    [8/3/2023, 2:59:19 PM] [INFO] Cortex_R4_0: Flashing process starting...
    [8/3/2023, 2:59:19 PM] [INFO] Cortex_R4_0: Connecting to COM Port COM7...
    [8/3/2023, 2:59:19 PM] [INFO] Cortex_R4_0: Reset connection to device
    [8/3/2023, 2:59:19 PM] [INFO] Cortex_R4_0: Set break signal
    [8/3/2023, 2:59:19 PM] [INFO] Cortex_R4_0: Connection to COM port succeeded. Flashing can proceed.
    [8/3/2023, 2:59:19 PM] [INFO] Cortex_R4_0: Reading device version info...
    [8/3/2023, 2:59:19 PM] [SUCCESS] Program Load completed successfully.

    But...I tried the online Visualizer at:

    dev.ti.com/.../

    and it STILL works? Is the chip really getting flashed with the new binary?

     

  • +1
    Prodigy 20 points

    Apparently, my chip IS an ES2 device...as it seemed to work just fine with the 'Small Object Detection' example.

  • +1 in reply to Mike Schoonover
    Prodigy 20 points

    NOTE!!!!

    The online UniFlash did NOT seem to be flashing the code...even though it SAID IT WAS!!!

    I used the downloaded version and the messages are very different.

    After getting the binary flashed properly, the 'IWR6843AOPEVM: Small Obstacle Detection' Example now works in the Radar Toolbox Industrial Visualizer.

    Messages from UniFlash (downloaded version)


    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: Initialization complete.
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: Flashing process starting...
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: Connecting to COM Port COM7...
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: Reset connection to device
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: Set break signal
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: Connection to COM port succeeded. Flashing can proceed.
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: Reading device version info...
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: ** 1 files specified for flashing.
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: Checking file C:/ti/radar_toolbox_1_20_00_11/source/ti/examples/Robotics/Small_Obstacle_Detection/prebuilt_binaries/small_obstacle_detection_6843.bin for correct header for IWR6843AOP.
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: IWR6843AOP device, fileType=META_IMAGE1 detected -> OK
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: !! Files are valid for IWR6843AOP.
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: Format on download was specified. Formatting SFLASH storage...
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: -->Erasing storage [SFLASH]
    [8/3/2023, 3:33:07 PM] [INFO] Cortex_R4_0: -->Sending Erase command to device...
    [8/3/2023, 3:33:22 PM] [SUCCESS] Cortex_R4_0: -->Erase storage completed successfully!
    [8/3/2023, 3:33:22 PM] [INFO] Cortex_R4_0: Downloading [META_IMAGE1] size [626628]
    [8/3/2023, 3:34:39 PM] [INFO] Cortex_R4_0: SUCCESS!! File type META_IMAGE1 downloaded successfully to SFLASH.
    [8/3/2023, 3:34:39 PM] [INFO] Cortex_R4_0: Disconnecting from device on COM port COM7...
    [8/3/2023, 3:34:39 PM] [INFO] Cortex_R4_0: Flashing instance clean-up initiated...
    [8/3/2023, 3:34:39 PM] [INFO] Cortex_R4_0: Instance deinitialized!
    [8/3/2023, 3:34:39 PM] [SUCCESS] Program Load completed successfully.