thank You for the quick response.
We checked hint
> GPIO state in deep sleep <https://community.cypress.com/thread/3995>
It really works fine with GPIOs defined as output.
But we have the opposite problem:
We define P33 as unused 0x600 or input 0x000 and
get it back as output 0x4600 after wakeup.
So something is changing our GPIO definition during entering deep sleep
or during wakeup !!
It would be very helpful to find a workaround as software,
because we want to avoid a change of our PCB
Cypress Semiconductor logo <http://www.cypress.com>
Cypress WICED Community
strange behavior of GPIO P33:
reply from btta
Bluetooth Forums - View the full discussion
It is not obvious what could be the issue. Besides ADC, did you configure P33 as something else, like puart? From your log, 0x4600 did implied output enabled with input disabled, just like puart Tx.
> It is not obvious what could be the issue. Besides ADC, did you
> configure P33 as something else, like puart? From your log, 0x4600 did
> implied output enabled with input disabled, just like puart Tx.
we do not configure P33 as something else. After PwrOn or reset
everything is fine, we read 0x600 as configuration.
Even immediatly before entering deep sleep / LPM it is 0x600.
After wakeup we read 0x4600 !
So, who is changing the configuration and how can we avoid this.
This is our main issue and our only problem!