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.

Stopped by a vector catch

Other Parts Discussed in Thread: CC2630, TIMAC, Z-STACK, CC2650

When debugging my code on a CC2630 I get a "Stopped by a vector catch" message then a "Reset" message.  in my IAR "Debug Log" window and then my code ends up trapped in an endless two line asm loop.  The call stack is simply [abort + 0x2edf].

I found this similar sounding post, but I am using a indeed using a 7x7 package and MODULE_CC26XX_7X7 IS defined in my IAR C preprocessor options window.

I assume that I've done something stupid, but how can I start to instrument things so that I can see what is causing me to choke?  This seems to happen after my initialization code is started, but early in my app code.

thx.

  • Hi Scott,
    I assume you are using some sample application provided by TI.
    Which stack/sample application are you using (Z-stack, TIMAC)?
    Is that a custom board or an EM board?
    You can also look through the Mesh Network forums for answers to your questions.
    Regards,
    Michel
  • It is based on TIMAC.
  • I am surprised that it doesn't work right out of the box.

    Which dev kit are you using? (SmartRF06EB, LaunchPad)?
    Did you follow the startup guide that comes with the TIMAC stack?
    Did you check if there were IAR compiler version compatibility issues (I've seen some posts about some issues but I'm not sure whether that applies to your case)?

    Did you check if the settings are properly configured for your device? The project was configured for a CC2650, so I am not sure whether there are any differences in memory mapping.

    But if your application compiles and you can start debugging, a TI-RTOS menu should appear when your debug session starts. The most useful one in your case would be the Tasks Detailed and Module views.

    Once those views are open, you will be able to see what is going on when you pause the debugger stops. If you see an error messages that looks like "ROV failed" or something like that, it usually means that you most likely have a memory corruption problem (hence, I would check your device configuration).

    If that menu doesn't show up, it will be hard to get much information.

    If you still have problems, I would suggest posting your question in the Mesh Networks forum, they might be better at answering you.



    Regards,
    Michel

  • Michel, thanks for the suggestions.
  • There was a suggested answer and since there has been no active on this thread for more than a week, the suggested answer was marked as verify. Please feel free to select the "Reject Answer" button and reply with more details.