• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 9 replies
  • Subscribers 347 subscribers
  • Views 15988 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

Cortex-M4: guaranteed wakeup from WFI?

Markus Grabner
Note: This was originally posted on 8th August 2013 at http://forums.arm.com

Hi all!

I'm wondering how to ensure that the Cortex-M4 is always woken up on an interrupt from the WFI instruction when executing code like this:

__disable_irq();
// do something ...
__enable_irq();
__WFI();

If an interrupt is triggered between __enable_irq() and __WFI(), the interrupt handler is processed [font="Arial"]immediately and completed before [/font][font="Courier New"]__WFI() is executed, i.e., [/font][font="Arial"][font="Courier New"]__WFI()[/font] will wait for the next interrupt such that the first one is effectively lost. The ATmega* processors have a very simple solution to this problem: enabling interrupts is always delayed by one clock cycle such that the processor can safely enter sleep mode before interrupts can occur and wake up the processor. Thereby it is guaranteed that the processor is always woken up on an interrupt. How is this done on the Cortex-M4? As far as I know, there is no such enable interrupt delay, or is there a totally different mechanism to ensure wakeup on interrupts?

Thanks & kind regards,
Markus


P.S.: A lengthy discussion on a similar topic is here, though in German language.
[/font]
Parents
  • 0
    Note: This was originally posted on 9th August 2013 at http://forums.arm.com


    __disable_irq();
    // do something ...
    __WFI();
    __enable_irq();

    Sounds impossible, but it is the way to do, all other version causes race conditions and are not reliable.

    Ok, got it. I was just a bit unsure whether this is the correct approach since the manual doesn't even mention the underlying problem (the ATmega* manual at least has a code example with a single-line comment referring to reliable sleep and wakeup).

    Does anybody know of a good introductory text on synchronization on microprocessor/-controller level?

    Thanks & kind regards,
    Markus
Reply
  • 0
    Note: This was originally posted on 9th August 2013 at http://forums.arm.com


    __disable_irq();
    // do something ...
    __WFI();
    __enable_irq();

    Sounds impossible, but it is the way to do, all other version causes race conditions and are not reliable.

    Ok, got it. I was just a bit unsure whether this is the correct approach since the manual doesn't even mention the underlying problem (the ATmega* manual at least has a code example with a single-line comment referring to reliable sleep and wakeup).

    Does anybody know of a good introductory text on synchronization on microprocessor/-controller level?

    Thanks & kind regards,
    Markus
Children
No data