• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 188 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWRL6432: Set gDebugTargetCode to 1

Yu An Chen
Prodigy 60 points
Part Number: IWRL6432

Hi experts,

Following code is locate in mmwDemoFrameStartISR(),

is the assert just used to check if the UART data of current frame have been transmitted completely before next frame started? Are there other uses?

If set gDebugTargetCode to 1, is there any potential risk? 



Regards,

Anna

  • 0
    TI__Expert 8810 points

    Hi

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

    Regards

  • 0 in reply to Abhishek Karkisaval
    TI__Genius 13690 points

    Hello.

    Yu An Chen said:
    is the assert just used to check if the UART data of current frame have been transmitted completely before next frame started? Are there other uses?

    Yes that is the intended purpose of that check.  There is no risk to setting gDebugTargetCode to 1 as that just disables that check when running in debug mode.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 60 points

    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

  • 0 in reply to Yu An Chen
    TI__Genius 13690 points

    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

  • 0 in reply to Santosh Krishnan
    Prodigy 60 points

    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

  • +1 in reply to Yu An Chen
    TI__Genius 13690 points

    It won't cause any problem processing-wise, but it could cause problems with the data being output as old data that still hasn't been written out being overwritten by new data from the current frame.

    Yu An Chen said:
    We should keep that assert check to make sure everything complete before next frame started. Am I correct?

    Yes.  If you want to have your program only continue on if everything is transmitted out before the start of the next frame, then keep that assert in.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 60 points

    Hi Santosh,


    I get it, thanks.

    Regards,

    Anna