Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 941 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.

AWR1843BOOST: Demo Visualizer Not Working

MHD Hitham Al Mnjed
Prodigy 30 points
Part Number: AWR1843BOOST
Other Parts Discussed in Thread: AWR1843

Hello,

I have the AWR1843BOOST non-secure ES2, I have been trying to run the mmWave Demo using the Demo Visualizer, but it always hangs and is never fully connected. When I send some config, it throws an error at line 2960 in mss_main.c

I tried using the pre-built.bin METAIMAGE from SDK 3.2 and 3.3  to get the same result,it says 'connecting 2 of 2 targets'. I tried compiling another image using CCS still the same issue.

Surprisingly, when I flash the demo from xwr16xx, it connects and I can using the Demo Visualizer just fine (with only two TX of course).

Lastly I tried following the CCS debug mode, I connect the targets and load the images, then connect using the Visualizer and send config, here is the outcome I get:

Can you please help me with this, I can't move on with development on this board.

Thanks,

Hitham

  • 0
    TI__Guru 69500 points

    Hi Hitham,

    I just tried SDK 3.3 pre-built mmw demo binary with AWR1843BOOST and clicked 'Send Config to mmwave device' button in the visualizer with default setting/config. It works as expected.

    Could you share the configuration you are sending? Or just copy here the visualizer console output.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 30 points

    Hi Jitendra,

    I just tried it again with another AWR1843 board, its the same results (everything is default). I did exactly like what you wrote.

    Here is the visualizer console output:


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

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

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

    mmwDemo:/>% Frequency:77
    Skipped

    mmwDemo:/>% Platform:xWR18xx
    Skipped

    mmwDemo:/>% Scene Classifier:best_vel_res
    Skipped

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

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

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

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

    mmwDemo:/>% Radial velocity resolution(m/s):0.04
    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:/>% Angle of Arrival FoV: Full FoV
    Skipped

    mmwDemo:/>% Range FoV: Full FoV
    Skipped

    mmwDemo:/>% Doppler FoV: Full FoV
    Skipped

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

    mmwDemo:/>sensorStop
    Ignored: Sensor is already stopped

    Done

    mmwDemo:/>flushCfg
    Done

    mmwDemo:/>dfeDataOutputMode 1
    Done

    mmwDemo:/>channelCfg 15 5 0
    Done

    mmwDemo:/>adcCfg 2 1
    Done

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

    mmwDemo:/>profileCfg 0 77 180 7 15 0 0 100 1 64 9142 0 0 30
    Done

    mmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1
    Done

    mmwDemo:/>chirpCfg 1 1 0 0 0 0 0 4
    Done

    mmwDemo:/>frameCfg 0 1 128 0 100 1 0
    Done

    mmwDemo:/>lowPower 0 0
    Done

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

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

    mmwDemo:/>cfarCfg -1 1 0 8 4 4 1 15 1
    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:/>lvdsStreamCfg -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 1 0 1 0 1 0 1 0
    Done

    mmwDemo:/>measureRangeBiasAndRxChanPhase 0 1.5 0.2
    Done

    mmwDemo:/>CQRxSatMonitor 0 3 4 19 0
    Done

    mmwDemo:/>CQSigImgMonitor 0 31 4
    Done

    mmwDemo:/>analogMonitor 0 0
    Done

    mmwDemo:/>aoaFovCfg -1 -90 90 -90 90
    Done

    mmwDemo:/>cfarFovCfg -1 0 0 10.97
    Done

    mmwDemo:/>cfarFovCfg -1 1 -2.49 2.49
    Done

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

    Exception: ./mss/mss_main.c, line 2966.

    Best,

    Hitham

  • 0 in reply to Jitendra Gupta
    Prodigy 30 points

    Hi Jitendra,

    Any update on this matter? 

    I need help on this please.

    Best,

    Hitham

  • 0 in reply to MHD Hitham Al Mnjed
    TI__Guru 69500 points

    Hi Hitham,

    The cause of failure here is the boot time calibration on the specific AWR1843BOOST. 

    Init Calibration Status = 0xdfe ; it should be 0xffe

    To bypass this failure you can change the mmwave source and rebuild the library.

    mmwave_link.c: MMWave_asyncEventHandler() ->  calibrationStatus = ptrRFInitCompleteMessage->calibStatus & 0xFFFU;

    After removing above marked code, rebuild the mmwave library (ti\control\mmwave) and then rebuild the mmw demo application.

    One of FAE supporting your company is facing the same issue, we are already debugging this issue with his help.

    Regards,

    Jitendra