# WP7700 is unable to shutdown in ULPM mode **URL:** \ **Category:** mangOH Red\ **Created:** [July 24, 2019, 5:58pm UTC](https://mangoh.discourse.group/t/wp7700-is-unable-to-shutdown-in-ulpm-mode/2811 "2019-07-24T17:58:22Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![aashwini](https://avatars.discourse-cdn.com/v4/letter/a/9f8e36/32.png) [@aashwini](https://mangoh.discourse.group/u/aashwini)\ **Post date:** [July 24, 2019, 5:58pm UTC](https://mangoh.discourse.group/t/wp7700-is-unable-to-shutdown-in-ulpm-mode/2811/1 "2019-07-24T17:58:22Z")
I am trying to use gpio36 as both input pin and a boot source for wakeup from ulpm. I constantly monitor the state of the gpio pin and when I change the state of the pin (via a push button), in the event handler I set the gpio as a boot source and then call ulpm\_shutdown(). Even though it doesn’t give me any error calling the le\_ulpm\_shutdown() function, it also didn’t go to ultra-low power mode. I am expecting some message to appear in the serial console regarding that. Is there any other way to check it? ---
**Author:** ![aashwini](https://avatars.discourse-cdn.com/v4/letter/a/9f8e36/32.png) [@aashwini](https://mangoh.discourse.group/u/aashwini)\ **Post date:** [July 25, 2019, 10:14pm UTC](https://mangoh.discourse.group/t/wp7700-is-unable-to-shutdown-in-ulpm-mode/2811/2 "2019-07-25T22:14:35Z")
I tried using the pmtool to test the ulpm shutdown: 1. pmtool bootOn gpio 36 high > SUCCESS! 1. pmtool shutdown > Initiated shutdown of MDM > on the serial console: pm\_set\_mcu\_ulpm\_enable: Request PM1 1. when I provide a 1.8v source to the gpio36: on the serial console: gpio\_check\_and\_wake: wake-n\_gpio26 STATE=WAKEUP swimcu\_gpio\_irq\_event\_handle: Re-enabled irq 0 type B for MCU GPIO 0 gpio\_check\_and\_wake: wake-n\_gpio26 STATE=SLEEP gpio\_check\_and\_wake: wake-n\_gpio26 STATE=WAKEUP swimcu\_gpio\_irq\_event\_handle: Re-enabled irq 0 type B for MCU GPIO 0 gpio\_check\_and\_wake: wake-n\_gpio26 STATE=SLEEP I am using legato 19.04 version with toolchain SWI9X06Y\_02.22.12.00. Any ideas what is going on?