system OFF

RE: system OFF

Susheel Nuguru — Fri, 07 Dec 2018 20:44:31 GMT

Please open a new case mentioning which chip version you tested this with and SDK version too.

There are some errata workarounds in the startup files, that might effect your readings, but before we investigate that, please open new case giving us more details on the setup.

RE: system OFF

Bluesky — Thu, 06 Dec 2018 03:14:36 GMT

Hi, I would like to ask how can i get the current consumption that was stated in the datasheet which is 0.7uA and the value I get from the reading is about 8-9 uA.

My code is just simple as below,

#include "boards.h"

/**
* @brief Function for application main entry.
*/
int main(void)
{
NRF_POWER->SYSTEMOFF = 1;
}
/** @} */

RE: system OFF

Susheel Nuguru — Mon, 07 Mar 2016 14:50:58 GMT

That is right, there is no other way. I think there is a memory corruption in your system which is writing to this specific register. If should be easy to set a write access breakpoint and see when it is triggered.(in Keil i know its possible, do not know how you do it in other debuggers)

RE: system OFF

tvjz — Mon, 07 Mar 2016 14:01:51 GMT

I am sorry for my unclear question. Indeed I meant that I am experiencing chip mysteriously going into system off. So the answer is that somewhere the code must write into the POWER->SYSTEMOFF register in order to make the MCU to go into system OFF. There's just no other way. Right?

RE: system OFF

Susheel Nuguru — Mon, 07 Mar 2016 12:23:38 GMT

I am little confused, are you experiencing mysterious wake ups or the chip mysteriously going into system off?

The only way to go to system off is writing to POWER->SYSTEMOFF register which is exactly what sd_power_system_off() does.

The only ways to wakeup from system off are wakeup mechanism (read more about DETECT signal) or Reset. If you are in debug mode then the chip does not go to system off but emulates the system off (explained more in emulated system off mode section)