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

How to enter ISR in debug mode?

James_GG
Prodigy 50 points

Hi, guys,

Due to new project requirement, I'd like to try ARM Cortex M4 to see if it's a good fit for our new product. I googled and did some home work by myself. It seems CCS 5 will be a nice IDE choice for TI's TIVA C.  

So I downloaded and installed the CCS 5 in my computer and also bought the Tiva C development kit. AFter that , I tried compling and debugging the example projects from TI TivaWare. Everything worked just fine. However, when I tried to use "run to line" to debug into the ISRs (interruption service routines). The system lost its response and pop out a window saying "Get Expression: GEL_Go (0x5d80)". I am not sure what I did wrong. Is that any project configuration setup tricks that I need to know? Or it's just normal that CCS 5 for ARM couldn't debug into the ISRs? I never had any this kinds of problem with MSP430 MCUs.

Anybody could give me any hints? Thank you for your help in advance.

James

  • 0
    Prodigy 50 points

    It seems noboday met this problem before. The interesting thing is ISR debugging  are frequently used during the embedded product development. Anybody met this ISR debugging problem before?  

  • 0 in reply to James_GG
    Prodigy 50 points

    I found that I made a silly mistake. I thought the interruption was triggered, actually it was not. That's why I couldn't enter the ISR during debug. After the external event triggers the interrupts properly, the ISR could be debugged successfully.