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

ARM: STM32, still problems with isr_* calls?

Hello - I'm writing a simple usart console application using RTX with MDK-ARM v3.20 on an MCBSTM32. The code ends up in either MemManage_Handler or HardFault_Handler when setting an event via isr_evt_set in the interrupt that services the USART. I get the same result when running the MCBSTM32\RTX_Traffic example, which is similar to my application. Is there anyone out there running this example successfully? Thanks -

Parents
  • Frank,

    Inside STM32 device is a Cortex-M3 (not ARM7/9) which has a completely different Interrupt system. There is no User or System mode but Thread and Handler mode.

    Normal code runs in Thread mode and Handler mode is entered as a result of an exception/interrupt (also true for nested interrupts). Therefore nested interrupts should not be the reason for the problem that Ben reported. Also the mentioned RTX_Traffic example doesn't use nested interrupts.

    Ben,

    I see no problems when running RTX_Traffic on MCBSTM32. You should send the description on how to duplicate the problem with RTX_Traffic to support.intl@keil.com

Reply
  • Frank,

    Inside STM32 device is a Cortex-M3 (not ARM7/9) which has a completely different Interrupt system. There is no User or System mode but Thread and Handler mode.

    Normal code runs in Thread mode and Handler mode is entered as a result of an exception/interrupt (also true for nested interrupts). Therefore nested interrupts should not be the reason for the problem that Ben reported. Also the mentioned RTX_Traffic example doesn't use nested interrupts.

    Ben,

    I see no problems when running RTX_Traffic on MCBSTM32. You should send the description on how to duplicate the problem with RTX_Traffic to support.intl@keil.com

Children