• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 916 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.

CCS: Error_policyMin not Providing Info

Jordan Melnychuk1
Prodigy 145 points

Tool/software: Code Composer Studio

I'm trying to debug an issue that sends my controller into Error_policyMin, but the information passed into the function (file, line, id, ...) is either NULL or seems to have garbage values.  I can't figure out what setting I need to change to use this functionality.  I used uart_echo as the starting point for this project and use the TI compiler.

Thanks,

--Jordan

  • 0
    Prodigy 145 points

    I found that the issue was due to a bad realloc that I didn't check for NULL on, but still didn't see anything in TI Error_policyMin that would have pointer me to it.  I noticed that the TIRTOS libraries allow for an error block but I'm using the POSIX wrappers instead.  Do I need to somehow add a call back error handler to my timers/threads for me to be able to use the TI error handlers and get more info on where the crash occured?

    Thanks,

    --Jordan

  • 0 in reply to Jordan Melnychuk1
    TI__Guru 58425 points

    Hi Jordan,

    I think this like could share some light on how the error module work and how/what data you could extract from the pre-defined policies:

    http://dev.ti.com/tirex/explore/content/simplelink_cc13x2_26x2_sdk_3_40_00_02/docs/tirtos/sysbios/docs/cdoc/index.html#xdc/runtime/Error.html

    Note that "Error_policyMin" really only give you the error ID. You can implement your own functions or hooks to handle errors in your application the way you want. You can also look into the "m3Hwi.excHandlerFunc = null;" which can be configured to capture HWI exceptions yourself instead of having the default function raise an error for you.

    As a start, you could simply try to change the Error policy but this comes at the cost of code footprint. It is common that people that want to log the exceptions end up implementing their own exception handler function.