Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
We have a critical roadblock to getting a product to production due to power consumption. It has been found that the issue is the devlpm_registerForLowPowerQueries() works upon out of the box after a fresh 'Programming' of the device but after the Device has gone into DEEP SLEEP and awakes from DEEP SLEEP the callback function that is defined in the devlpm_registerForLowPowerQueries() no longer gets called to allow the device to go into IDLE/SLEEP mode. I have attached both a BLE_TRACE output where you can see the callback function getting called before going into DEEP_SLEEP and then after the Device wakes up the callback function to check to allow the device to go into IDLE/SLEEP is no longer called even through the same devlpm_init() and devlpm_registerForLowPowerQueries() gets called?