This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

How to put the nrf52832 into deep sleep mode

Hello,

I am currently using nRF52832 with SDK v11.0.0 and S132 v2.0.0. I am also using the soft device as my application requires. I have been trying to put the CPU into SYSTEM OFF mode using the following:

// Configure the "main" button:

nrf_gpio_cfg_sense_input( BUTTON_MAIN_PIN, NRF_GPIO_PIN_PULLUPNRF_GPIO_PIN_SENSE_LOW );

// Enter SYSTEM OFF mode

sd_power_system_off();

There is one major problem -- the system is still pulling a lot of current ~3.5mA. I don't understand what is going on. I read this in the manual, in section 18.2: "

Before entering System OFF mode, the user must make sure that all on-going EasyDMA transactions have been completed. This is usually accomplished by making sure that the EasyDMA enabled peripheral is not active when entering System OFF. "

Questions: -Am I using the correct function call for my version of the SDK to put the system in System OFF mode?

                  - Is the EasyDMA consuming that much current?! If so, how do I disable EasyDMA and ensure all transactions are complete?

                   - What other calls am I missing?

Parents
  • Hi

    Power cycling the board after programming it should be sufficient to get out of debug mode. Just turn the chip off and remove any power sources (battery, USB connector, etc.), then attach the power source and turn the DK on again. You shouldn't need any explicit code for this. Additionally, when the JLink debugger is connected, debug mode should be able to be turned off with the JLink commander using the "writeDP 1 0" command, although I haven't tried this myself. Hopefully, the EasyDMA workaround will work out for you.

    Best regards,

    Simon

    PS: I'll be out of office for the remainder of this week, but I'll get back to you upon my return!

Reply
  • Hi

    Power cycling the board after programming it should be sufficient to get out of debug mode. Just turn the chip off and remove any power sources (battery, USB connector, etc.), then attach the power source and turn the DK on again. You shouldn't need any explicit code for this. Additionally, when the JLink debugger is connected, debug mode should be able to be turned off with the JLink commander using the "writeDP 1 0" command, although I haven't tried this myself. Hopefully, the EasyDMA workaround will work out for you.

    Best regards,

    Simon

    PS: I'll be out of office for the remainder of this week, but I'll get back to you upon my return!

Children
No Data
Related