• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 892 views
  • Users 0 members are here
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

Interrupts lost

Genp

I have a project with STM32F105 controller.
2 interrupts are used - UART1_RX and CAN1_RX.
Project developed with MDK-ARM v.4.21.
Everything worked ok until I recompiled it with the MDK-ARM v.4.22A
Now my interrupts are not firing.
The same thing happened on another project with the same controller.

Any idea on what could cause such a problem ?

Thank you,
Gennady

Parents
  • 0 in reply to Genp

    I have a project with STM32F105 controller.
    2 interrupts are used - UART1_RX and CAN1_RX.
    Project developed with MDK-ARM v.4.21.
    Everything worked ok until I recompiled it with the MDK-ARM v.4.22A
    Now my interrupts are not firing.
    not at all, or not often enough?

    are you not familiar with the phrase 'debugging'?. Anyhow, the debugging is quite simple, look at the affected SFRs and backtrack when you find the missing/extra bits. "breakpoint stepping" followed by stepping while looking at the relevant SFR will lead you to the offending place. Not a big deal

    Erik

Reply
  • 0 in reply to Genp

    I have a project with STM32F105 controller.
    2 interrupts are used - UART1_RX and CAN1_RX.
    Project developed with MDK-ARM v.4.21.
    Everything worked ok until I recompiled it with the MDK-ARM v.4.22A
    Now my interrupts are not firing.
    not at all, or not often enough?

    are you not familiar with the phrase 'debugging'?. Anyhow, the debugging is quite simple, look at the affected SFRs and backtrack when you find the missing/extra bits. "breakpoint stepping" followed by stepping while looking at the relevant SFR will lead you to the offending place. Not a big deal

    Erik

Children
No data