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.

AWRL1432: debug assert code keep or not

Part Number: AWRL1432

Tool/software:

Hi,

My customer use the motion detection demo as reference code, in mmwDemoFrameStartISR there is below code. For customer production code, keep gDebugTargetCode =0, and call DebugP_assert, right? Any suggestion to make the SW more robustness is welcome, thanks. 

if (gDebugTargetCode == 0)
{
DebugP_assert(mmwMssMCB->interSubFrameProcToken == 0);
}

Andy

  • Hi Andy,

    Yes, your assumption is correct. gDebugTargetCode should = 0. We recommend customers go through thoroughly and test/verify their programs work to meet whatever requirements they have set for their product. Please keep in mind the motion and presence demo code is for demo purposes only, and is not guaranteed to meet any particular standards.

    Regards,

    Tim