⚠️ Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
The 58x family retains the state of the pin before going to sleep, not the configuration or the functionallity of the pin, that's why when the device wake's up the periph_init() function its called in order to re-configure the pins in each wakeup and the pins return their default application state.
Just to clarify, when you say the state of the pin is retained, does that mean if I was to set a pin as an output and to drive high, it would remain high while sleeping?
Hi edwardwhite,
The 58x family retains the state of the pin before going to sleep, not the configuration or the functionallity of the pin, that's why when the device wake's up the periph_init() function its called in order to re-configure the pins in each wakeup and the pins return their default application state.
Thanks MT_dialog
Just to clarify, when you say the state of the pin is retained, does that mean if I was to set a pin as an output and to drive high, it would remain high while sleeping?
Hi edwardwhite,
Exactly, it will stay high during sleep, and will be reconfigured in wake up by the periph_init() function.
Thanks MT_dialog