• State Not Answered
  • Locked Locked
  • Replies 19 replies
  • Subscribers 21 subscribers
  • Views 6407 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

code works on stepping but goes to interrupt when run

VIVEK Gopalakrishnan

Hi,

Iam working on a luminary micro based cortex M3 processor. Iam not using any RTOS. Iam trying to use system timer tick (luminary software based) packet transmitter code.

The code works on stepping using debugger but goes to interrupt when run (which is just going to the same place). Because of this i couldnt test my code at all.

Please help me understand why this problem is happening and how to solve it.

Thanks,
vivek

Parents
  • 0 in reply to Kaushik Das

    HI,

    Which start up file are you using? There are many interrupts which are not handled (no routines declared). In such a case the code flows to default interrupt. The PC will definitely go into defsult handler if you get some interrupt routine which is unhandled. Systick interrupt was the one which gave me trouble. check for the interrupt status registers to find out which interrupt has occurred.
    You might not be expecting the interrupt. You can try putting zero instead of a routine name(this might not be a good solution, but good for a trial) or declare a routine.

Reply
  • 0 in reply to Kaushik Das

    HI,

    Which start up file are you using? There are many interrupts which are not handled (no routines declared). In such a case the code flows to default interrupt. The PC will definitely go into defsult handler if you get some interrupt routine which is unhandled. Systick interrupt was the one which gave me trouble. check for the interrupt status registers to find out which interrupt has occurred.
    You might not be expecting the interrupt. You can try putting zero instead of a routine name(this might not be a good solution, but good for a trial) or declare a routine.

Children
No data