topic Re: Waking up from deep-sleep with timer32/WDTOSC in LPCXpresso IDE

Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:50 GMT

Content originally posted in LPCWare by ktownsend on Fri Mar 26 10:58:30 MST 2010
I've been trying to write some generic code to enter deep sleep mode with the LPC1114 (easy enough), and then wakeup after a fixed number of seconds using 32-bit timer 0 off WDTOSC.

Entering deep sleep is fine, but it I haven't been able to get the device to wakeup using the timer, and I'm really starting to scratch my head on this.

My apologies if the code below is partial, but I'm using a header file I wrote myself since I hate having magic-numbers everywhere [reg1 = 0xA033F300] ... it should be clear with the names what values are being set, though.

The methods below are used with the following test code in main:

    U32 pmuRegVal;
 
    // Configure wakeup sources before going into sleep/deep-sleep.
    // By default, pin 0.1 is configured as wakeup source (falling edge)
    pmuInit();
 
    // Put peripherals into sleep mode (leave WDTOSC enabled)
    pmuRegVal = SCB_PDSLEEPCFG_IRCOUT_PD |
                SCB_PDSLEEPCFG_IRC_PD |
                SCB_PDSLEEPCFG_FLASH_PD |
                SCB_PDSLEEPCFG_BOD_PD |
                SCB_PDSLEEPCFG_ADC_PD |
                SCB_PDSLEEPCFG_SYSPLL_PD;
 
    // Enter deep sleep mode (wakeup after 5 seconds)
    pmuDeepSleep(pmuRegVal, 5);

It's a long read, but here are the key methods if someone is brave enough to look through them. If there are any clear examples of waking up from deep sleep on a timer capture that would be useful as well.

Kevin.

 
/**************************************************************************/
/*! 
    \brief Initialises the power management unit
    Initialise the power management unit, and configure pin 0.1 to act as
    a wakeup source from sleep or deep-sleep mode.
    For sleep and deep-sleep modes, entered via pmuSleep(), P0.0..11 and
    P1.0 can be used as a wakeup source.  For deep power-down mode, entered
    via pmuPowerDown(), only a low level on pin 1.4 (WAKEUP) can wake the
    device up.
*/
/**************************************************************************/
void pmuInit( void )
{
  /* Enable all clocks, even those turned off at power up. */
  SCB_PDRUNCFG &= ~(SCB_PDRUNCFG_WDTOSC_MASK | 
                    SCB_PDRUNCFG_SYSOSC_MASK | 
                    SCB_PDRUNCFG_ADC_MASK);
  /* Enable wakeup interrupts (P0.1..11 and P1.0 can be used) */
  NVIC_EnableIRQ(WAKEUP1_IRQn);      // P0.1
  /* Configure pin 0.1 as wakeup source (MAT2 on 32-bit Timer 0) */
  IOCON_PIO0_1 &= ~IOCON_PIO0_1_FUNC_MASK;
  IOCON_PIO0_1 |= (IOCON_PIO0_1_FUNC_GPIO |
                   IOCON_PIO0_1_HYS_ENABLE);
  /* Set pins to input for wakeup */
  gpioSetDir( 0, 1, gpioDirection_Input );
  /* Only edge trigger. activation polarity on P0.1 is FALLING EDGE. */
  SCB_STARTAPRP0 = ~SCB_STARTAPRP0_MASK;      // ~0xFFFFFFFF;
  /* Clear all wakeup source */ 
  SCB_STARTRSRP0CLR = SCB_STARTRSRP0CLR_MASK;
  /* Enable Port 0.1 as wakeup source. */
  SCB_STARTERP0 |= SCB_STARTERP0_ERPIO0_1;
  return;
}
/**************************************************************************/
/*! 
    Setup the clock for the watchdog timer.  The default setting is 10kHz.
*/
/**************************************************************************/
static void pmuWDTClockInit (void)
{
  /* Configure watchdog clock */
  /* Freq. = 0.5MHz, div = 50: WDT_OSC = 10kHz  */
  SCB_WDTOSCCTRL = SCB_WDTOSCCTRL_FREQSEL_0_5MHZ | 
                   SCB_WDTOSCCTRL_DIVSEL_DIV50;
  /* Set clock source (use external crystal) */
  SCB_WDTCLKSEL = SCB_WDTCLKSEL_SOURCE_INPUTCLOCK;
  SCB_WDTCLKUEN = SCB_WDTCLKUEN_UPDATE;
  SCB_WDTCLKUEN = SCB_WDTCLKUEN_DISABLE;
  SCB_WDTCLKUEN = SCB_WDTCLKUEN_UPDATE;
  /* Wait until updated */
  while (!(SCB_WDTCLKUEN & SCB_WDTCLKUEN_UPDATE));
  /* Set divider */
  SCB_WDTCLKDIV = SCB_WDTCLKDIV_DIV1;
  /* Enable WDT clock */
  SCB_PDRUNCFG &= ~(SCB_PDRUNCFG_WDTOSC);
  // Switch main clock to WDT output
  SCB_MAINCLKSEL = SCB_MAINCLKSEL_SOURCE_WDTOSC;
  SCB_MAINCLKUEN = SCB_MAINCLKUEN_UPDATE;       // Update clock source
  SCB_MAINCLKUEN = SCB_MAINCLKUEN_DISABLE;      // Toggle update register once
  SCB_MAINCLKUEN = SCB_MAINCLKUEN_UPDATE;
  // Wait until the clock is updated
  while (!(SCB_MAINCLKUEN & SCB_MAINCLKUEN_UPDATE));
}
/**************************************************************************/
/*! 
    \brief  Turns off select peripherals and puts the device in deep-sleep
            mode.
    This function will put the device into deep-sleep mode.  Most gpio
    pins can be used to wake the device up, but the pins must first be
    configured for this in pmuInit.  By default, only pin 0.1 (ISP) is
    configured as a wakeup source.
    The device can be configured to wakeup from deep-sleep mode after a
    specified delay with the wakeupSeconds parameter.  This will configure
    32-bit timer 0 to set a match on pin 0.1 (ISP), which will wakeup
    the device up.  The timer will be configured to run off the WDT OSC
    while in deep-sleep mode, meaning that WDTOSC should not be powered
    off (using the sleepCtrl parameter) when a wakeup delay is specified.
    The sleepCtrl parameter is used to indicate which peripherals should
    be put in sleep mode (see the SCB_PDSLEEPCFG register for details).
 
    @param[in]  sleepCtrl  
                The bits to set in the SCB_PDSLEEPCFG register.  This
                controls which peripherals will be put in sleep mode.
    @param[in]  wakeupSeconds
                The number of seconds to wait until the device will
                wakeup.  If you do not wish to wakeup after a specific
                delay, enter a value of 0.
*/
/**************************************************************************/
void pmuDeepSleep(U32 sleepCtrl, U32 wakeupSeconds)
{
  SCB_PDAWAKECFG = SCB_PDRUNCFG;
  sleepCtrl &= ~(1 << 9);               // MAIN_REGUL_PD
  sleepCtrl |= (1 << 11) | (1 << 12);   // LP_REGUL_PD
  SCB_PDSLEEPCFG = sleepCtrl;
  SCB_SCR |= SCB_SCR_SLEEPDEEP;
  /* Configure system to run from WDT and set TMR32B0 for wakeup          */
  if (wakeupSeconds > 0)
  {
    // Make sure WDTOSC isn't disabled in PDSLEEPCFG
    SCB_PDSLEEPCFG &= ~(SCB_PDSLEEPCFG_WDTOSC_PD);
    // Disable 32-bit timer 0 if currently in use
    timer32Disable(0);
    // Reconfigure clock to run from WDTOSC
    pmuWDTClockInit();
    /* Enable the clock for CT32B0 */
    SCB_SYSAHBCLKCTRL |= (SCB_SYSAHBCLKCTRL_CT32B0);
 
    /* Configure PIO0.1 as Timer0_32 MAT2 */
    IOCON_PIO0_1 &= ~IOCON_PIO0_1_FUNC_MASK;
    IOCON_PIO0_1 |= IOCON_PIO0_1_FUNC_CT32B0_MAT2;
    /* Set appropriate timer delay */
    TMR_TMR32B0MR0 = PMU_WDTCLOCKSPEED_HZ * wakeupSeconds;
 
    /* Configure match control register to raise an interrupt and reset on MR0 */
    TMR_TMR32B0MCR = (TMR_TMR32B0MCR_MR0_INT_ENABLED | TMR_TMR32B0MCR_MR0_RESET_ENABLED);
 
    /* Configure external match register */
    TMR_TMR32B0EMR &= ~(0xFF<<4);                   // Clear EMR config bits
    TMR_TMR32B0EMR |= TMR_TMR32B0EMR_EMC2_TOGGLE;   // MR2 (GPIO0.1) Toggle
 
    /* Enable the TIMER0 interrupt */
    NVIC_EnableIRQ(TIMER_32_0_IRQn);
 
    /* Start the timer */
    TMR_TMR32B0TCR = TMR_TMR32B0TCR_COUNTERENABLE_ENABLED;
  }
  // Send Wait For Interrupt command
  __asm volatile ("WFI");
  return;
}

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:51 GMT

Content originally posted in LPCWare by yanzhongsan on Fri Mar 26 18:43:57 MST 2010
what is your compiler? IAR or LPCXpresso

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:51 GMT

Content originally posted in LPCWare by bigamer on Mon Apr 05 20:12:41 MST 2010
What's the progress of Waking up from deep-sleep with timer32 using WDTOSC? :)

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:52 GMT

Content originally posted in LPCWare by hfischer on Mon Apr 05 23:17:38 MST 2010
Hi,

KTownsend you try to toggle the Pin which is the wakeup irq pin without an loopback from a other pin, right?
I dont know, if this is possible. I realized a timer match wakeup from deep sleep by an loopback.
Connecting the matchpin with one of the possible wakeup irq pins runs perfect.
Does the timer match toggle the pin, did you check this?

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:52 GMT

Content originally posted in LPCWare by ktownsend on Tue Apr 06 05:51:35 MST 2010

Quote: hfischer
Hi,

KTownsend you try to toggle the Pin which is the wakeup irq pin without an loopback from a other pin, right?
I dont know, if this is possible. I realized a timer match wakeup from deep sleep by an loopback.
Connecting the matchpin with one of the possible wakeup irq pins runs perfect.
Does the timer match toggle the pin, did you check this?

If I understand correctly, when a match occurs on 0.1 (CT32B0_MAT2), I toggle (for example) pin 0.3, assuming 0.3 is configured as a wakeup source? I don't suppose you would be able to post a few lines of code showing how you got it working, since that would probably be the clearest way to see how to go about setting the HW up. Thanks for the tip, though.

Kevin.

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:53 GMT

Content originally posted in LPCWare by hfischer on Tue Apr 06 06:40:34 MST 2010
Hi,

yes this is exactly what i mean. But here you get the Init for the Pin and the timer. Maybe it helps

  //Wakeup-IRQ Pin0_2
  LPC_SYSCON->STARTRSRP0CLR |= BIT2; // reset startlogic Pin 2 pending
  LPC_SYSCON->STARTAPRP0|=BIT2;      // rising edge for IRQ detection
  LPC_SYSCON->STARTERP0|=BIT2;       // enable the IRQ signal in start logic

void TIMER_16_1_WakeUp_Init(uint16_t u16_M0_Value)
{
  LPC_SYSCON->SYSAHBCLKCTRL |= BIT8;    // enable AHBclock to access
  LPC_TMR16B1->MR0 = u16_M0_Value;
  LPC_TMR16B1->MCR = BIT1;             // Reset on MR0
  LPC_TMR16B1->EMR = BIT4|BIT5;        // toggle Match0 Pin

  LPC_TMR16B1->PWMC = BIT0;

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:54 GMT

Content originally posted in LPCWare by ktownsend on Tue Apr 06 15:15:00 MST 2010

Quote: hfischer

Connecting the matchpin with one of the possible wakeup irq pins runs perfect.
Does the timer match toggle the pin, did you check this?

I've been testing this a bit more to see if I can get it to work with only one pin (it would be a shame to have to use two pins just to wakeup from deep sleep). The MAT pin (0.1/CT32B0_MAT2) is definately toggling every 5s after entering deep-sleep, but if I configure 0.1 as a wakeup source it never seems to enter the wakeup ISR.

If I physically connect 0.1 to 0.11, and configure 0.11 as a wakeup it works fine ... but it means I have to connect the two pins together on the PCB which I really hate. I'll have to see if I can get an answer from NXP about whether this can be done with only one pin. Thanks for your help, though, getting it to work with two pins.

Kevin.

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:54 GMT

Content originally posted in LPCWare by ktownsend on Tue Apr 06 16:58:34 MST 2010
hfischer:

I was able to get it working with just one pin. I'm not sure how useful this is since it's using a custom header file, but it should still be understandable as psuedo-code

There are still a few issues to work out, but now that I can at least wakeup predictably the rest should be relatively trivial to work out (reconfiguring the system clock after wakeup, etc.).

Kevin

 
/**************************************************************************/
/*! 
    @brief  Turns off select peripherals and puts the device in deep-sleep
            mode.
    The device can be configured to wakeup from deep-sleep mode after a
    specified delay by supplying a non-zero value to the wakeupSeconds
    parameter.  This will configure CT32B0 to toggle pin 0.1 (CT32B0_MAT2)
    after x seconds, waking the device up.  The timer will be configured
    to run off the WDT OSC while in deep-sleep mode, meaning that WDTOSC
    should not be powered off (using the sleepCtrl parameter) when a
    wakeup delay is specified.
    The sleepCtrl parameter is used to indicate which peripherals should
    be put in sleep mode (see the SCB_PDSLEEPCFG register for details).
 
    @param[in]  sleepCtrl  
                The bits to set in the SCB_PDSLEEPCFG register.  This
                controls which peripherals will be put in sleep mode.
    @param[in]  wakeupSeconds
                The number of seconds to wait until the device will
                wakeup.  If you do not wish to wakeup after a specific
                delay, enter a value of 0.
    @code 
    uint32_t pmuRegVal;
 
    // Configure wakeup sources before going into sleep/deep-sleep
    // By default, pin 0.1 is configured as wakeup source
    pmuInit();
 
    // Put peripherals into sleep mode
    pmuRegVal = SCB_PDSLEEPCFG_IRCOUT_PD |
                SCB_PDSLEEPCFG_IRC_PD |
                SCB_PDSLEEPCFG_FLASH_PD |
                SCB_PDSLEEPCFG_BOD_PD |
                SCB_PDSLEEPCFG_ADC_PD |
                SCB_PDSLEEPCFG_SYSPLL_PD;
 
    // Enter deep sleep mode (wakeup after 5 seconds)
    pmuDeepSleep(pmuRegVal, 5);
    @endcode
*/
/**************************************************************************/
void pmuDeepSleep(uint32_t sleepCtrl, uint32_t wakeupSeconds)
{
  SCB_PDAWAKECFG = SCB_PDRUNCFG;
  sleepCtrl &= ~(1 << 9);               // MAIN_REGUL_PD
  sleepCtrl |= (1 << 11) | (1 << 12);   // LP_REGUL_PD
  SCB_PDSLEEPCFG = sleepCtrl;
  SCB_SCR |= SCB_SCR_SLEEPDEEP;
 
  /* Configure system to run from WDT and set TMR32B0 for wakeup          */
  if (wakeupSeconds > 0)
  {
    // Make sure WDTOSC isn't disabled in PDSLEEPCFG
    SCB_PDSLEEPCFG &= ~(SCB_PDSLEEPCFG_WDTOSC_PD);
 
    // Disable 32-bit timer 0 if currently in use
    timer32Disable(0);
 
    // Reconfigure clock to run from WDTOSC
    pmuWDTClockInit();
 
    /* Enable the clock for CT32B0 */
    SCB_SYSAHBCLKCTRL |= (SCB_SYSAHBCLKCTRL_CT32B0);
 
    /* Configure 0.1 as Timer0_32 MAT2 */
    IOCON_PIO0_1 &= ~IOCON_PIO0_1_FUNC_MASK;
    IOCON_PIO0_1 |= IOCON_PIO0_1_FUNC_CT32B0_MAT2;
 
    /* Set appropriate timer delay */
    TMR_TMR32B0MR0 = PMU_WDTCLOCKSPEED_HZ * wakeupSeconds;
 
    /* Configure match control register to raise an interrupt and reset on MR0 */
    TMR_TMR32B0MCR |= (TMR_TMR32B0MCR_MR0_INT_ENABLED | TMR_TMR32B0MCR_MR0_RESET_ENABLED);
 
    /* Configure external match register to set 0.1 high on match */
    TMR_TMR32B0EMR &= ~(0xFF<<4);                   // Clear EMR config bits
    TMR_TMR32B0EMR |= TMR_TMR32B0EMR_EMC2_HIGH;     // Set MR2 (0.1) high on match
 
    /* Use RISING EDGE for wakeup detection. */
    SCB_STARTAPRP0 |= SCB_STARTAPRP0_APRPIO0_1;
 
    /* Clear all wakeup sources */ 
    SCB_STARTRSRP0CLR = SCB_STARTRSRP0CLR_MASK;
 
    /* Enable Port 0.1 as wakeup source. */
    SCB_STARTERP0 |= SCB_STARTERP0_ERPIO0_1;
 
    /* Enable wakeup interrupt (P0.1..11 and P1.0 can be used) */
    //NVIC_EnableIRQ(WAKEUP0_IRQn);    // P0.0
    NVIC_EnableIRQ(WAKEUP1_IRQn);      // P0.1  (CT32B0_MAT2)
    //NVIC_EnableIRQ(WAKEUP2_IRQn);    // P0.2
    //NVIC_EnableIRQ(WAKEUP3_IRQn);    // P0.3
    //NVIC_EnableIRQ(WAKEUP4_IRQn);    // P0.4
    //NVIC_EnableIRQ(WAKEUP5_IRQn);    // P0.5
    //NVIC_EnableIRQ(WAKEUP6_IRQn);    // P0.6
    //NVIC_EnableIRQ(WAKEUP7_IRQn);    // P0.7
    //NVIC_EnableIRQ(WAKEUP8_IRQn);    // P0.8
    //NVIC_EnableIRQ(WAKEUP9_IRQn);    // P0.9
    //NVIC_EnableIRQ(WAKEUP10_IRQn);   // P0.10
    //NVIC_EnableIRQ(WAKEUP11_IRQn);   // P0.11 (CT32B0_MAT3)
    //NVIC_EnableIRQ(WAKEUP12_IRQn);   // P1.0
 
    /* Start the timer */
    TMR_TMR32B0TCR = TMR_TMR32B0TCR_COUNTERENABLE_ENABLED;
  }
  // Send Wait For Interrupt command
  __asm volatile ("WFI");
  return;
}

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:55 GMT

Content originally posted in LPCWare by bigamer on Tue Apr 06 19:00:49 MST 2010
Hi Kevin,

How much is the power consumption after MCU entered Deep-sleep with your "just one pin" wake-up method?
In my opinion, the loopback with two pin is much more reasonable, just like this, a timer match-out on the port pin will fed back into the startlogic to wake up the MCU.

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:56 GMT

Content originally posted in LPCWare by ktownsend on Tue Apr 06 19:45:03 MST 2010

Quote: bigamer
Hi Kevin,

How much is the power consumption after MCU entered Deep-sleep with your "just one pin" wake-up method?
In my opinion, the loopback with two pin is much more reasonable, just like this, a timer match-out on the port pin will fed back into the startlogic to wake up the MCU.

I don't think there is any difference in power consumption if you use one pin or two. I get 250uA if I go directly into deep sleep with no timer to wakeup (which is high, but I have a number of parts of the board and I'm not shutting every peripheral off in deep sleep). If I setup a timer to cause a wakeup after 5 seconds, I get the exact same 250uA. I had to set the MAT2 to switch from low to high on match for lowest power, but there's no difference between using one pin or two in power consumption, except you lose one less pin.

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:56 GMT

Content originally posted in LPCWare by bigamer on Tue Apr 06 21:26:11 MST 2010

Quote: KTownsend
I don't think there is any difference in power consumption if you use one pin or two. I get 250uA if I go directly into deep sleep with no timer to wakeup (which is high, but I have a number of parts of the board and I'm not shutting every peripheral off in deep sleep). If I setup a timer to cause a wakeup after 5 seconds, I get the exact same 250uA. I had to set the MAT2 to switch from low to high on match for lowest power, but there's no difference between using one pin or two in power consumption, except you lose one less pin.

Hi Kevin,
Thanks for your test!
Can you upload the total project that you just test with?

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:57 GMT

Content originally posted in LPCWare by hfischer on Wed Apr 07 00:59:25 MST 2010
Hi Kevin,

thanks for your test and the code.
I will try it in time. I have a power consumption of 11 to 8.5 microA depending on the MCU (two have 11 and one had 8.5 until killing it with dc-voltage-supply :p ).

So I have to see, if the one-pin solution will work with identical power-consumption. It is really important for me to save power in the deep-sleep but wake up periodically.

Thanks a lot and regards.

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:58 GMT

Content originally posted in LPCWare by ktownsend on Wed Apr 07 03:19:30 MST 2010

Quote: hfischer
Hi Kevin,

thanks for your test and the code.
I will try it in time. I have a power consumption of 11 to 8.5 microA depending on the MCU (two have 11 and one had 8.5 until killing it with dc-voltage-supply :p ).

So I have to see, if the one-pin solution will work with identical power-consumption. It is really important for me to save power in the deep-sleep but wake up periodically.

Thanks a lot and regards.

I'd be surprised if there is a difference. I just switched everything to use the IRC when going into deep sleep (which is recommended anyway), and this gets me down to 70uA in deep sleep (compared to 250uA with the external crystal) with CT32B0 running off WDTOSC at 10khz. Most of that 70uA is external peripherals, though I might be able to shave a bit off by fine tuning some pins, etc.

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:58 GMT

Content originally posted in LPCWare by bigamer on Wed Apr 07 18:07:00 MST 2010
Good job!

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:59 GMT

Content originally posted in LPCWare by bigamer on Thu Apr 08 21:14:34 MST 2010

Quote: KTownsend
I'd be surprised if there is a difference. I just switched everything to use the IRC when going into deep sleep (which is recommended anyway), and this gets me down to 70uA in deep sleep (compared to 250uA with the external crystal) with CT32B0 running off WDTOSC at 10khz. Most of that 70uA is external peripherals, though I might be able to shave a bit off by fine tuning some pins, etc.

Hi Kevin,

How to test your code to wake device up periodically? Can I have a look your main() function? Thanks in advance!

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:55:59 GMT

Content originally posted in LPCWare by ktownsend on Sun Apr 11 13:09:53 MST 2010

Quote: bigamer
Hi Kevin,

How to test your code to wake device up periodically? Can I have a look your main() function? Thanks in advance!

If you look in the comments, you can see the code required. But you will need to modify the code to use the CMSIS header files, etc. It should really be treated as psuedo-code, but it should be clear if you look at it with the user manual open, and try to reproduce the same code yourself.

I haven't published the M0/LPC1114 code yet since it is still in progress, but if you are unsure about certain values in the header file the file I made for the LPC1343 should be identical for PMU and the timer:

http://code.google.com/p/lpc1343codebase/source/browse/trunk/lpc134x.h

Kevin.

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:56:00 GMT

Content originally posted in LPCWare by hfischer on Fri Apr 16 01:44:23 MST 2010
Hi Kevin,

trying the code snippet, you posted, I'm wondering about setting M0 and M2 registers for only one pin synchron reset event? Is it an error, or do your really use this code as it is mentioned?

Thanks a lot,

Regards

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:56:01 GMT

Content originally posted in LPCWare by ktownsend on Fri Apr 16 01:53:17 MST 2010

Quote: hfischer
Hi Kevin,

trying the code snippet, you posted, I'm wondering about setting M0 and M2 registers for only one pin synchron reset event? Is it an error, or do your really use this code as it is mentioned?

Regards

You only need one ... I must have forgotten to remove something since I tested a number of combinations to get everything working. Sorry. I'll have to go through the code again and make sure there's no 'leftovers'. :-)

Kevin.

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:56:01 GMT

Content originally posted in LPCWare by johnhe on Fri Apr 16 18:43:58 MST 2010
Hi Kevin

You reported on another forum you would try my sample code from this forum that achieves 6uA in deep sleep.

I would appreciate if you inform us

1) If you did in fact try my sample code.
2) If you did, do you agree or disagree with my results.

Thanks

John Heenan

Re: Waking up from deep-sleep with timer32/WDTOSC

lpcware — Thu, 16 Jun 2016 02:56:02 GMT

Content originally posted in LPCWare by johnhe on Sat Apr 17 02:38:41 MST 2010
There appears to be a lot of confusion. Hopefully this will help.

From the LPC111x user manual section 3.7.3:

"In Deep-sleep mode (see Section 3–8) for details), the chip is in Sleep mode, the system clock is disabled,"

So what is the system clock?

From the LPC111x user manual section 3.4.11:

"The main system clock clocks the core, the peripherals, and the memories."

So in deep sleep, the clock is disabled higher up the hierarchy than for normal sleep. Normal sleep just disables the clock to the core. For sleep purposes the interrupt controller (NVIC) should be considered a peripheral and not part of the core. The interrupt controller also requires a clock. For deep sleep 'start logic' connected to pins provides a workaround to this requirement.

Since the system clock is disabled in deep sleep there is a disconnect between a relevant oscillator that may not be shut down during deep sleep and between timer peripherals.

While a timer peripheral will wake up from normal sleep, a timer peripheral cannot be used to wake up from deep sleep with the LPC1114, even if its oscillator is not shut down.

There is no separate RTC domain for the LPC1114 to generate a start logic interrupt.

It is conceivable the watch dog oscillator can be used to reset the LPC1114 from deep sleep, if the watch dog internal oscillator is used. However there is no usable start logic to wake up the LPC1114 if the watch dog is configured for (single use) interrupt use instead of reset use.

In my sample code demonstrating 6uA deep sleep in http://knowledgebase.nxp.com/showthread.php?t=187 it only requires one line to be commented out to show a timer waking up the LPC1114 LPCXpresso from normal sleep, instead of staying in deep sleep.

John Heenan