• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 29 subscribers
  • Views 1973 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.

AWR1843: DPM error causing runtime to crash

Justin Wong
Prodigy 40 points
Part Number: AWR1843

Hi,

I'm working with a AWR1843 radar chip and encountered a DPM error that's causing the runtime to crash. I would appreciate help parsing the error message and debugging the issue.

From the MSS UART I get:

Debug: mmWave Control Initialization was successful
Debug: mmWave Control Synchronization was successful
Debug: Sending rlRfSetLdoBypassConfig with 3 1 0
Debug: Init Calibration Status = 0xffe
Azimuth Tx: 1 (MIMO:0), Elev Tx:0
Ant setting virtualAzim: 4 , virtual Elev :0
 chirpThreshold 1 max = 64, 
Error: DPM Report 4 received with error:-30430 arg0:0x64 arg1:0x80050e8
{module#9}: "src/mss/mss_main.c", line 1391: error {id:0x10000, args:[0x169cc, 0x169cc]}
xdc.runtime.Error.raise: terminating execution

and from the DSS UART I get:

Debug: DPM Module Sync is done
Error: DPM Report 4 received with error:-30430 arg0:0x64 arg1:0x814254
xdc.runtime.Main: "src/dss/dss_main.c", line 187: assertion failure
xdc.runtime.Error.raise: terminating execution
  • 0
    TI__Guru*** 149154 points

    Hi,

    We have to check with SDK development team and get back to you

    thank you

    Cesar

  • 0 in reply to Justin Wong
    TI__Guru*** 149154 points

    Could you please let us know if you made any changes to the src code or profile configuration?

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 40 points

    Hi Cesar,

    The error is coming from a call to reportFxn of the DPM cfg (/mmwave_sdk_03_03_00_03/packages/ti/control/dpm/docs/doxygen/html/struct_d_p_m___init_cfg__t.html). reportType=4, errCode=-30430, arg0=0x64, arg1=0x80050e8

    Additionally, with the same source code, it built without a problem on another computer, but the respective binaries that are  produced differ.

    Thanks,

    Justin

  • 0 in reply to Justin Wong
    TI__Guru*** 149154 points

    Hi,

    Here is some input from our team that helps understand the error code

    Thank you

    Cesar

    This will depend slightly on whether the user is using the HWA implementation or DSP implementation, but this is scratch buffer error.

     

    This error code is broken down into three pieces:

    1. mmWave Error Code
      1. Defined in mmwave_error.h
      2. In our case, we are looking at a DPU error: -30000
      3. Datapath Error Code
        1. Defined in dp_error.h
        2. In our case, we are looking at an AoA error: -400
        3. DPU-specific Error Code (AoA)
          1. Defined in aoaprochwa.h or aocprocdsp.h (depending on the user-specified implementation)
          2. In our case, we are looking at scratch buffer error: -30
          3. The #define has slightly different wordings for error number -30

    We add an error code number each level we go deeper.

    At this point, we can look in the source file and see where this error actually occurs.

    In the HWA implementation, the scratch buffer error occurs at line 2332 of aoaprochwa.c. In the DSP implementation, the scratch buffer error occurs at line 1544 of aoaprocdsp.c.

    So that is how we arrive at the error code of -30430.

  • 0 in reply to Cesar
    Prodigy 40 points

    Thanks! Indeed there was a problem the build system and the aoaprochwa.c wasn't being recompiled.

    -J