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.

IWR1642BOOST: Does the CONSOLE MESSAGE from the Out-of-Box demo results Confirm an ES 2.0 device?

Part Number: IWR1642BOOST

Attempts to run the people counter demo failed: my IWR1642BOOST did not have an ES2.0 sticker, the IWR1642 chip indicates it is ES 2.0.   A windows 7 box is configured with:

  • mmwave industrial toolbox 2.5.1 (requires ES2.0 IWR1642BOOST)
  • Uniflash 4.4.0
  • mmwave_SDK 02_00_00_04

Attempts to run C:\ti\mmwave_industrial_toolbox_2_5_1__win\mmwave_industrial_toolbox_2_5_1\labs\lab0011-pplcount\lab0011_pplcount_quickstart\pplcount_gui.exe have failed (crashed).  The device was flashed to restore it to its OOB (out of box) state using the .bin file:

C:\ti\mmwave_sdk_02_00_00_04\packages\ti\demo\xwr16xx\mmw\xwr16xx_mmw_demo.bin

The Out of Box Demo configured as SDK 2.0 was performed from a Chrome Browser:  

The complete CONSOLE MESSAGES are here: https://pastebin.com/1kCU5yuj

Given that the web-terminal is configured for a 2.0 SDK and the EVM is flashed with 2.0.0.4: If the IWR1642BOOST is a ES 1.0 device: what the be the expected Console messages?

Does the CONSOLE MESSAGE from the OOB results Confirm an ES 2.0 device?  Please provide a few sentences that provide the line of reasoning that shows how you arrived at the conclusion.  Thank you

  • Hi Raymond,

    I am unable to access your pastebin file.

    The only indicator you should need is if your IC has a 502 (ES1.0) or 502A (or 502AC, indicating ES2.0).


    Cheers,
    Akash
  • @Akash: Thanks for the response,  the goal is to electronically verify ES2.0 functionality with the SDK 2.0.0.4 based on your previous postings regarding IC nomenclature.    Thanks for the pastern feedback: I was able to open it however, pastern data is posted below.  Any references (web links) to decode \ interpret the pastern results is appreciated.  I would like an engineer, that is familiar with the pastebin results to provide a short analysis / interpretation of the key data that confirms that the demo is working properly: attempts to run the people counting quick start demo failed.  

    @Forum Administrator: IMHO, I think it is time for  a forum 'sticky' post regarding:

    1. ES2.0 labeling and SDK compatibility because there is conflicting information regarding labeling of ES2.0 devices (i.e. requiring a ES2.0 sticker)
    2. QuickStart pamphlet (packaged with IWR1642BOOST) cites broken link  

    'Stickies' would save others the trouble of what device they have and chasing broken web links.  I am not the first to post to the forums regarding the first issue.   Maybe it would be best to just fix the broken link (instead of a sticky?):

    http://ti.com/StartIWR1642

    PASTEBIN

    ========

    mmwDemo:/>% ***************************************************************
    Skipped

    mmwDemo:/>% Created for SDK ver:02.00
    Skipped

    mmwDemo:/>% Created using Visualizer ver:2.0.0.2
    Skipped

    mmwDemo:/>% Frequency:77
    Skipped

    mmwDemo:/>% Platform:xWR16xx
    Skipped

    mmwDemo:/>% Scene Classifier:best_range_res
    Skipped

    mmwDemo:/>% Azimuth Resolution(deg):15
    Skipped

    mmwDemo:/>% Range Resolution(m):0.044
    Skipped

    mmwDemo:/>% Maximum unambiguous Range(m):9.02
    Skipped

    mmwDemo:/>% Maximum Radial Velocity(m/s):1
    Skipped

    mmwDemo:/>% Radial velocity resolution(m/s):0.13
    Skipped

    mmwDemo:/>% Frame Duration(msec):100
    Skipped

    mmwDemo:/>% Range Detection Threshold (dB):15
    Skipped

    mmwDemo:/>% Doppler Detection Threshold (dB):15
    Skipped

    mmwDemo:/>% Range Peak Grouping:enabled
    Skipped

    mmwDemo:/>% Doppler Peak Grouping:enabled
    Skipped

    mmwDemo:/>% Static clutter removal:disabled
    Skipped

    mmwDemo:/>% ***************************************************************
    Skipped

    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 429 7 57.14 0 0 70 1 256 5209 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:/>frameCfg 0 1 16 0 100 1 0
    Done

    mmwDemo:/>lowPower 0 1
    Done

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

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

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

    mmwDemo:/>peakGrouping -1 1 1 1 1 255
    Done

    mmwDemo:/>multiObjBeamForming -1 1 0.5
    Done

    mmwDemo:/>clutterRemoval -1 0
    Done

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

    mmwDemo:/>extendedMaxVelocity -1 0
    Done

    mmwDemo:/>bpmCfg -1 0 0 1
    Done

    mmwDemo:/>lvdsStreamCfg -1 0 0 0
    Done

    mmwDemo:/>nearFieldCfg -1 0 0 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:/>CQRxSatMonitor 0 3 5 123 0
    Done

    mmwDemo:/>CQSigImgMonitor 0 127 4
    Done

    mmwDemo:/>analogMonitor 1 1
    Done

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

    Done

  • Hi Raymond,

    This query has been answered in this thread: e2e.ti.com/.../2541022


    Cheers,
    Akash