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.

IWR6843LEVM: Sensor crash when modified GTRACK_targetDesc struct

Part Number: IWR6843LEVM

[Gtack lib add parameter to GTRACK_targetDesc struct and set value then rebuild check, but will occurs crash issue]

Hi TI,
We try to add a state into GTRACK_targetDesc struct

but we found there is exist strange issue.

1- If add state and set value, device will occurs crash when running print log a few time (even I don't print it.). 

2- If add state but no set value, device working well when print log.

Need your help:

Is there any suggestion for debug this? 

Thanks.

Gtrack lib rebuild issue.pptx

  • Hello, 

    Have you run the demo from CCS or only by writing the binary to flash and running? You may get more information about why the crash is happening if you run from CCS. Here is a link to the CCS Debug guide for mmWave devices. For the 6843LEVM, the MMWAVE-ICBOOST board will also be required to leverage these debug features in CCS.

    Best Regards,

    Josh

  • Hi Josh,

    One related question occurs.

    I using a parameter to receive "TrackState state"

    The value of state should be range in 0 - 3

    typedef enum
    {
        /** @brief Free (not allocated) */
        TRACK_STATE_FREE = 0,
        /** @brief INIT */
        TRACK_STATE_INIT,
        /** @brief DETECTION State */
        TRACK_STATE_DETECTION,
        /** @brief ACTIVE State */
        TRACK_STATE_ACTIVE
    } TrackState;

    But we found the state value over 3 during our test.

    Can you help to check this?
    (We confirm memset to 0 before receive sensor data)

    Thanks.

  • Hello, 

    It is hard for me to say what might be causing this issue without a clearer picture of the modifications that you have made to the code. From what I can tell the enum looks right and as long as you are setting the state variable to one of the defined states (TRACK_STATE_FREE, TRACK_STATE_INIT, etc...) then I would agree that the value should always be expected to be between 0 and 3. 

    We confirm memset to 0 before receive sensor data

    How have you confirmed this in your debugging? Are you running the demo in CCS as I had previously suggested? I think that stepping through the code line by line will be the best way to determine why this behavior is happening so that is what I would recommend for your next steps if you are not already doing this.

    Best Regards,

    Josh 

  • It's resolved when I back mmWave SDK to 3.5 from 3.6.
    Thanks.