Diff: targets/hal/TARGET_NXP/TARGET_LPC13XX/sleep.c

Revision:

14:096882eb0961

Parent:

13:0645d8841f51

--- a/targets/hal/TARGET_NXP/TARGET_LPC13XX/sleep.c	Mon Aug 05 14:12:34 2013 +0300
+++ b/targets/hal/TARGET_NXP/TARGET_LPC13XX/sleep.c	Mon Aug 05 14:54:27 2013 +0000
@@ -18,9 +18,6 @@
 #include "mbed_interface.h"
 
 void sleep(void) {
-    // ensure debug is disconnected
-    mbed_interface_disconnect();
-    
     // PCON[PD] set to sleep
     LPC_PMU->PCON = 0x0;
     
@@ -31,36 +28,7 @@
     __WFI();
 }
 
-/*
-* The mbed lpc1768 does not support the deepsleep mode
-* as a debugger is connected to it (the mbed interface).
-*
-* As mentionned in an application note from NXP:
-*
-*       http://www.po-star.com/public/uploads/20120319123122_141.pdf
-*
-*       {{{
-*       The user should be aware of certain limitations during debugging.
-*       The most important is that, due to limitations of the Cortex-M3
-*       integration, the LPC17xx cannot wake up in the usual manner from
-*       Deep Sleep and Power-down modes. It is recommended not to use these
-*       modes during debug. Once an application is downloaded via JTAG/SWD
-*       interface, the USB to SWD/JTAG debug adapter (Keil ULINK2 for example)
-*       should be removed from the target board, and thereafter, power cycle
-*       the LPC17xx to allow wake-up from deep sleep and power-down modes
-*       }}}
-*
-*       As the interface firmware does not reset the target when a
-*       mbed_interface_disconnect() semihosting call is made, the
-*       core cannot wake-up from deepsleep.
-*
-*       We treat a deepsleep() as a normal sleep().
-*/
-
 void deepsleep(void) {
-    // ensure debug is disconnected
-    mbed_interface_disconnect();
-    
     // PCON[PD] set to deepsleep
     LPC_PMU->PCON = 0x1;