The part is woken up by the ISR and code execution then occurs.
These may be of some help -
http://www.cypress.com/?rID=78797 AN86233 - PSoC® 4 Low-Power Modes and Power Reduction Techniques
http://www.cypress.com/?rID=96072 AN90114 - PSoC® 4000 Family Low-Power System Design Techniques
http://www.cypress.com/?rID=110007 AN92584 - Designing for Low Power and Estimating Battery Life for BLE Applications
http://www.cypress.com/?id=4&rID=94607 PSOC 4 SysTick
http://www.cypress.com/?id=5509 100 Projects in 100 Days with Bluetooth
There is only the watchdog timer running in deep-sleep, no normal timer. Use that as your interrupt source and you will be woken up as expected.
:) too much info, most I have seen.
So, if it is woken by the ISR, shouldn't my code work?
That was it! Just set WDT1 to 25ms with interrupt and then I only need code in main loop for WakeUp, Do Something, Go back to sleep for another 25ms:
Not sure why direct into deep sleep and then empty main loop shows correct 1ua current and my code ups that to 11ua though.
1ua of that is the LED blip and the rest must be 12mhz PRoC active average over 25ms.
Much better than the table I posted but I still would not have guessed only the WDT's were available in deep sleep
That's why they call it Deep Sleep. ;-)