IWRL6432: Set gDebugTargetCode to 1

Hi

Thanks for your query. Please allow us a couple of days to respond

Regards

Hi Santosh,

Thanks for the reply.

Will TI recommend setting gDebugTargetCode to 1 at release mode if the assert fail encountered?

Or what action should take when that assert failed?

Regards,

Anna

Hello.

That flag should only be 1 if you are debugging.  Are you failing the assert without gTargetDebugCode 1?  What demo are you running and which configuration are you using?  It may indicate that the UART is taking too long to send or you are sending a lot more data than you are expecting to send.

Sincerely,

Santosh

Hi Santosh,

Understand. Like you said, if send too much data such as enable all the parameter in "guiMonitor" we will posibily encountered the assert failed since the UART is taking too long to send. 

We are using motion and presence detection example. We've add some features among the example.
So in other words, if the feature we add is taking too much time, and unable to complete before next frame started may lead to some problem depends on what we implememt. We should keep that assert check to make sure everything complete before next frame started. Am I correct?

Regards,

Anna

Hi Santosh,

I get it, thanks.

Regards,

Anna