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.

IWR6843ISK : Project initial settings

Part Number: IWR6843ISK
Other Parts Discussed in Thread: MMWAVEICBOOST, , AWR1642, IWR6843, AWR6843

Dear Team,


We have IWR6843ISK + MMWAVEICBOOST and the project we refer to is occupancy and vital signs detection in Automotive Toolbox (3.0.0).

Based on the above, we ask some questions.

1. The standard board of this project is AWR1642. If we change the AWR1642 related contents of the project to IWR6843, does it work fine?

2. If it doesn't work, do we need another change or is it impossible?

3. if possible, can you provide initial settings such as profiles?

Thank you.

  • Hi,

    This lab requires some minor porting and retesting to run on an IWR/AWR6843. And the chirp profiles need to reflect the change in frequency.  We have completed these updates and will be pushed to the Automotive Toolbox in the next few weeks.

     -dave

  • Dear Dave,

    I changed the AWR1642 part to IWR6843 by referring to Migrating to xWR68xx and xWR18xx Millimeter Wave(Rev.B).

    When debugging, the following error occurs.

    [C674X_0] Heap L1 : size 14336 (0x3800), free 12288 (0x3000)
    Heap L2 : size 49152 (0xc000), free 38392 (0x95f8)
    Heap L3 : size 720896 (0xb0000), free -655360 (0xfff60000)
    {module#34}: line 215: error {id:0x10000, args:[0x81ac4d, 0x81ac4c]}
    xdc.runtime.Error.raise: terminating execution
    [Cortex_R4_0] xdc.runtime.Main: "../mss_main.c", line 1072: assertion failure
    xdc.runtime.Error.raise: terminating execution

    I want to know where the problem is.

    For reference, the command was used as the following value.

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 3 0
    adcCfg 2 1
    adcbufCfg -1 0 0 1 1
    profileCfg 0 60 250 10 40 0 0 98 1 64 2200 0 0 40
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    frameCfg 0 1 168 0 107 1 0
    lowPower 0 1
    guiMonitor 0 1 16 1
    dvsGuiMonitor 0 0 0 0 0
    vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000
    motionDetection 0 20 2.0 0

    %OD Demo commands:
    zoneDef 2 20 6 12 6 20 6 32 6
    coeffMatrixRow 0 0 -11.705674 -6.557091 -6.556105 2.793170 2.806355 -0.033616
    coeffMatrixRow 0 1 -9.453702 -0.592442 -5.440082 3.204209 -5.838531 0.348308
    coeffMatrixRow 0 2 -9.492407 -5.426766 -0.588876 -5.904976 3.170924 0.305614
    coeffMatrixRow 0 3 -1.211744 3.400299 3.446914 8.541460 8.544744 -0.413807
    meanVector 0 22.771068 22.756197 -3.955602 -3.970473 0.712385
    stdVector 0 6.086866 6.070428 3.236808 3.262139 0.348652
    oddemoParms 8 0.001
    sensorStart

    Thank you.

  • >I want to know where the problem is.

    So you would start by looking at line 1072 of mss_main.c - the code is pointing you to the assert.  Sometimes this is enough information you give you the hint you need.  You can also set a breakpoint on this line and see the call stack to find where it came from.

    The main VOD demo (lab0003) already supports 1642, 1843 and 6843. You can browse this source looking for SOC_XWR68XX, to see where the code differs for 6843.  You should also compare this code to your port as there are SDK initialization differences as well (I imagine this is what is causing the assert).

    WRT your config, these also need to change for 6843 (ISK):

    channelCfg 15 5 0

    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 4

    I will close your other thread on this topic.

     -dave

  • Dear Dave,

    Thank you for answer.


    No error code in debugging when you proceed as you said. The contents are as follows.

    [C674X_0] Debug: MMWDemoDSS mmWave Control Initialization succeeded
    [Cortex_R4_0] **********************************************
    Debug: Launching the Vital-Signs Monitoring Demo
    **********************************************
    Debug: VitalSignsDemoMSS Launched the Initialization Task
    Debug: VitalSignsDemoMSS mmWave Control Initialization was successful
    Debug: CLI is operational
    [C674X_0] Debug: MMWDemoDSS Data Path init succeeded
    Debug: MMWDemoDSS initTask exit
    [Cortex_R4_0] Sensor has been stopped
    Debug: MMWDemoMSS Received CLI sensorStart Event

    However, when I run the Matlab program, an error occurs.

    In debugging, there are no confirmed errors, but which part do you think is wrong?

    The error is as follows.

    sensorStop
    Done
    flushCfg
    Done
    dfeDataOutputMode 1
    Done
    channelCfg 15 5 0
    Done
    adcCfg 2 1
    Done
    adcbufCfg -1 0 0 1 1
    Done
    profileCfg 0 60 250 10 40 0 0 98 1 64 2200 0 0 40
    Done
    chirpCfg 0 0 0 0 0 0 0 1
    Done
    chirpCfg 1 1 0 0 0 0 0 4
    Done
    frameCfg 0 1 168 0 107 1 0
    Done
    lowPower 0 1
    Done
    guiMonitor 0 1 16 1
    Done
    dvsGuiMonitor 0 0 0 0 0
    Done
    vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000
    Done
    motionDetection 0 20 2.0 0
    Done
    zoneDef 2 20 6 12 6 20 6 32 6
    Done
    coeffMatrixRow 0 0 -11.705674 -6.557091 -6.556105 2.793170 2.806355 -0.033616
    Done
    coeffMatrixRow 0 1 -9.453702 -0.592442 -5.440082 3.204209 -5.838531 0.348308
    Done
    coeffMatrixRow 0 2 -9.492407 -5.426766 -0.588876 -5.904976 3.170924 0.305614
    Done
    coeffMatrixRow 0 3 -1.211744 3.400299 3.446914 8.541460 8.544744 -0.413807
    Done
    meanVector 0 22.771068 22.756197 -3.955602 -3.970473 0.712385
    Done
    stdVector 0 6.086866 6.070428 3.236808 3.262139 0.348652
    Done
    oddemoParms 8 0.001
    Done
    sensorStart
    Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.

    Thank you,

    Sangyun Lee

  • There's one more change your config needs.  For xWR6843, the lowPower command should be: lowPower 0 0.

    We haven't pushed that change to the Resource Explorer yet. Beyond that, you might try stepping through the command send process in Matlab and see what the response is (if any) to sensorStart. It looks like everything to that point was confirmed.