• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 299 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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

Ari Viljanen
Prodigy 30 points
Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1642

Hi,

When I generate with mmWave Sensing Estimator tool “Chirp Configuration Parameters” for IWR1642. How can I load those to IWR1642boost board? Is there a way to convert those to *cfg file and load with mmWave Demo Visualizer tool (web based) or some other way to load those to the IWR1642boost board and still test with mmWave Demo Visualizer?

  • 0
    TI__Mastermind 23725 points

    Hello

    Can you please help us confirm ifconfig file that you have generated from the tool  is not compatible with the IWR1642 OOB demo?

    Trying to understand how you have encountered this issue.

    Thank you,

    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    Prodigy 30 points

    Example cfg from mmWave Demo Visualizer  (below), but if I want to take chirp parameters from  mmWaveSensingEstimator and change those values to this cfg file. How can I do that? And/or what what is the alternative way to upload chirp parameters to evaluation board. What SW and program shall be installed to my PC to be able to do that? I hope that this cleared the topic?

     

    % ***************************************************************
    % Created for SDK ver:03.04
    % Created using Visualizer ver:3.4.0.0
    % Frequency:77
    % Platform:xWR16xx
    % Scene Classifier:best_range
    % Azimuth Resolution(deg):15
    % Range Resolution(m):0.977
    % Maximum unambiguous Range(m):50
    % Maximum Radial Velocity(m/s):18.55
    % Radial velocity resolution(m/s):0.29
    % Frame Duration(msec):100
    % ***************************************************************
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 3 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 0
    profileCfg 0 77 8 7 18.24 0 0 15 1 64 6250 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    frameCfg 0 1 128 0 100 1 0
    lowPower 0 1
    guiMonitor -1 1 1 0 0 0 1
    cfarCfg -1 0 2 8 4 3 0 15 1
    cfarCfg -1 1 0 8 4 4 1 15 1
    multiObjBeamForming -1 1 0.5
    clutterRemoval -1 0
    calibDcRangeSig -1 0 -5 8 256
    extendedMaxVelocity -1 0
    bpmCfg -1 0 0 1
    lvdsStreamCfg -1 0 0 0
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    CQRxSatMonitor 0 3 4 31 0
    CQSigImgMonitor 0 31 4
    analogMonitor 0 0
    aoaFovCfg -1 -90 90 -90 90
    cfarFovCfg -1 0 0 70.00
    cfarFovCfg -1 1 -18.55 18.55
    sensorStart

  • Former Member
    0 Former Member in reply to Ari Viljanen

    Hello,

    There is no tool currently to generate CFG files using the sensing estimator. Please see this thread for more details on manually updating the cfg file:

    Amanda

  • 0 in reply to Former Member
    Prodigy 30 points

    Yes, this was the case and dilemma for me too. But "To help map (json to cfg) the parameters in the config file you can refer to the description of the values in the SDK user guide.", I did not find from SDK user guide (1642) straight guidance to map those.

  • Former Member
    0 Former Member in reply to Ari Viljanen

    You should take the output shown under "chirp configuration parameters" on the sensing estimator and map it to the parameter names for profile and frame cfg etc described in the SDK user guide.