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: IWR1642BOOST

Part Number: IWR1642BOOST
Other Parts Discussed in Thread: UNIFLASH, , IWR1642, IWR1443BOOST

Hi,

I am trying to do mmwave sdk 1642 demo, using mmwave demo visulaizer with sdk 1.2 adn tool box 1.6.2.

I am able to flash it using uniflash.But I am not able to get the plot since it is showing the error once it is loaded with configuration file.

pls help me to resolve this issue

logs:


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

mmwDemo:/>% Created for SDK ver:01.02
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 0
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 = 0x7f2

DSS Exception: dss/dss_main.c, line 1519.

  • Hi Karthik,

    Does this happen when you try to load a .cfg file manually using the load config button under the plots tab?


    Cheers,
    Akash
  • yes Akash..this error displayed on console when i load manually
  • Hi,

    This happened when I I tried load confg from visualizer, but now when I repated the same thing, It shows HW connecetd but not showing any plot on the visualier.

    Kindly help me to resolve the issue, I tried with sdk1.2,2.0 but the effect is same.

    No console messages when I load config.
    My board is IWR1642BOOST rev A ES1 (no ES2 sticker on board)
  • Hi,

    This happened when I I tried load confg from visualizer, but now when I repated the same thing, It shows HW connecetd but not showing any plot on the visualier.

    Kindly help me to resolve the issue, I tried with sdk1.2,2.0 but the effect is same.

    No console messages when I load config.
    My board is IWR1642BOOST rev A ES1 (no ES2 sticker on board)
  • Hi,

    As per your doc of compatibility, for ES1 IWR i have downloaded toolbox 2.3.0 and using sdk 1.2.0.5 I am not able to get anything on console with flashing by using .bin file in debug folder of sdk1.2.05 folder.
    But using CCS when I generate binary files with toolbox 2.3.0 I have console messages, by loading confg to mmwave.

    logs:

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

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

    mmwDemo:/>% Created using Visualizer ver:2.1.0.3
    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 0
    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 = 0x7f2

    DSS Exception: ../dss_main.c¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾¾þ, line 1790.


    pls help me to solve this

  • You need to flash it with the mmWave binary, not the CCS debug binary.


    Cheers,
    Akash
  • Hi, As shown in image, is it same file you mentioned in previous post? need to be loaded through Uniflash?

    Till now I was flashing from C:\ti\mmwave_sdk_01_02_00_05\packages\ti\utils\ccsdebug\ccsbebug.bin file as mentioned in the setup guide.

  • Correct you'll need to load it through uniflash and then try the visualizer again.


    Cheers,
    Akash
  • Hi Akash,

    Yes It worked fine with SDK2.0 file, but same problem when i used sdk1.2.

    one question relatd to visualizer.

    When I enable 4 Rx and 2 Tx, I will get x and y co-ordinate of the object.

    But when I enable only 1tx and 1Rx, tye object green point lies only on perpendicular line to center point.

    In last discussion I was told that, in mmewave demo we will get x,y,z co-ordinates,which are used to display the object.

    Now in case of 4tx, 4Rx case the Y co-ordinate is directly Y value which is got from outputdemo.h or it is processed value?

    regards

    Karthik

  • Hi Karthik,

    If it works with SDK2.0 then it is likely you have ES2.0 IWR1642.

    The 1Tx 1Rx configuration does not enable any angular information which is why it is only appearing as a single point.

    For x, y, z coordinates you'll need 3Tx 4Rx but since the IWR1642BOOST only has 2 Tx you can only receive x and y coordinates. You'll need IWR1443BOOST for 3D detection.

    For the 2Tx 4 Rx case the Y coordinate you are seeing is the post-processed value.

    Since this discussion of Tx/Rx is outside the scope of this thread, I'd recommend opening a new thread if you'd like to continue this discussion.

    Cheers,
    Akash
  • Hi Akash,

    "if it works with SDK2.0 then it is likely you have ES2.0 IWR1642. "- but I did not see any sticker on the board.

  • Hi Karthik,

    You can tell on the actual chip marking itself. Please see the errata page: www.ti.com/.../swrz073b.pdf

    If the label is 502AC then you have ES2.0.


    Cheers,
    Akash