• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 40 subscribers
  • Views 231 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.

CC3220SF-LAUNCHXL: How to find culprit for configASSERT

Manish_Thakur
Genius 5085 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF

Hiya Experts,

Can canyone please give a proper explaintion about configASSERT.

1)What it is?

2)why it comes?

3)How to avoid that?

4)How to debug that?

Please because sometimes I'm getting that assert and unable to find reasons for that.

in many forums I have checked and observed that most people says it is coming from an Interrupt but I don't have a clear concept about that. If anyone can explain please enlighten me.

  • 0
    TI__Mastermind 40965 points

    Hi Manish,

    Are you using FreeRTOS? The configASSERT function seems to be a FreeRTOS function that is triggered when an RTOS error is detected.

    There are a few ways that CC3220 programs typically encounter an assert:

    1. Memory corruption is detected
    2. The stack has been corrupted
    3. The heap has run out of memory or otherwise stopped functioning correctly

    With that being said, I advise you check the running state of FreeRTOS to ensure that your stacks and heaps look good. I would also suggest you check your code to ensure you are not incorrectly dereferencing pointers or otherwise performing unsafe memory operations.

    As FreeRTOS is not a TI product, please contact FreeRTOS support for help on your issue. Our ability to support FreeRTOS on the forums is limited.

    Regards,

    Michael

  • 0 in reply to Michael Reymond
    Genius 5085 points

    Hi Michael,

    Thanks for your points. I just wanted to know that reasons for aseert on CC3220SF. Thanks for the info I'll take care of all the points you said.

    In case, if you have more points with you do share I'll mark this as resolved.