Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

DavidKaplan — Thu, 02 Sep 2021 05:52:56 GMT

We verified that now we are getting a little over 29ua in our sleep state which is very good.

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

DavidKaplan — Thu, 02 Sep 2021 03:47:47 GMT

I added NRF_UARTE0_NS->PSEL.TXD = PIN_NUM_UART0_TXD; in ReInit() before enabling the uart and now I can reenable the uart and send debug information.

  NRF_UARTE0_NS->PSEL.TXD      = PIN_NUM_UART0_TXD;
  NRF_UARTE0_NS->PSEL.RXD      = PIN_NUM_UART0_RXD; 
  NRF_UARTE0_NS->ENABLE        = 8;
  NRF_UARTE0_NS->TASKS_STARTRX = 1;
  NRF_UARTE0_NS->TASKS_STARTTX = 1;

I hope to have an inetegration session soon to recheck the current.

Thanks David

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

DavidKaplan — Wed, 01 Sep 2021 13:11:14 GMT

I also tried adding NRF_UARTE0_NS->PSEL.TXD = PIN_NUM_UART0_TXD; in ReInit() but still none of my debug information is sent after the Deint() function.

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

DavidKaplan — Wed, 01 Sep 2021 12:33:53 GMT

Thanks for your response.

This morning I changed the code which waits for the semaphore which is given every second which there is nothing to do.

Previously I had tried using k_cpu_atomic_idle(key) from an example I saw on the forum.

Now I just use k_sem_take(&sec_wakeup_sem, K_FOREVER) again.

I had a session with our hardware guy in LasVegas after updating the code and he reports a very good current consumption of 31ua which spikes very second as expected. He will check the current with a more precise current meter at work.

Now I used the direct uart disable and enable examples also found on the forum but after disabling uart0, enabling uart0 does not restore my printouts for debug information. I called printk() with CONFIG_PRINTK=y in one version and then calling z_impl_k_str_out() directly with CONFIG_PRINTK=n with the same results - no printout after reenabling uart0.

void ami_uart_boot_DeInit(void)
{
#if defined(CONFIG_UART_INTERRUPT_DRIVEN)
  //---------------------------------------------------------------------------
  // Low power
  //  When putting the system in low power and the peripheral is not needed, 
  // lowest possible power consumption is achieved by stopping, and then disabling the peripheral.
  // The STOPTX and STOPRX tasks may not be always needed (the peripheral might already be stopped), 
  // but if STOPTX and/or STOPRX is sent, software shall wait until the TXSTOPPED and/or RXTO event is received in response,
  // before disabling the peripheral through the ENABLE register.
  //---------------------------------------------------------------------------
  NRF_UARTE0_NS->TASKS_STOPRX=1;
  while(NRF_UARTE0_NS->EVENTS_RXTO == 0);
  NRF_UARTE0_NS->EVENTS_RXTO = 0;

  NRF_UARTE0_NS->TASKS_STOPTX = 1;
  while(NRF_UARTE0_NS->EVENTS_TXSTOPPED == 0);
  NRF_UARTE0_NS->EVENTS_TXSTOPPED = 0;

  NRF_UARTE0_NS->ENABLE = 0;
  NRF_UARTE0_NS->PSEL.TXD = 0xFFFFFFFF;
  //---------------------------------------------------------------------------
  // Set BOOT Txd P0.1
  //---------------------------------------------------------------------------
  NRF_P0_NS->OUTSET = (1 << 1);
  //---------------------------------------------------------------------------
  // Set BOOT Rxd P0.0
  //---------------------------------------------------------------------------
  NRF_P0_NS->OUTSET = (1 << 0);
  //---------------------------------------------------------------------------
  // RXD is now an input change to an output high!
  //---------------------------------------------------------------------------
  ami_board_ConfigPin(AMI_BOARD_OUT_BOOT_RXD,GPIO_OUTPUT_HIGH);
#endif
  //---------------------------------------------------------------------------
  // Set Boot driver is NOT active
  //---------------------------------------------------------------------------
  bBootDriverActive   = FALSE;
  //---------------------------------------------------------------------------
  // Cancel staying awake because of Debug & Direct connect
  //---------------------------------------------------------------------------
  ami_main_CancelStayAwake(AQUA_MAIN_AWAKE_BOOT_DIRECT | AQUA_MAIN_AWAKE_DEBUG);
} // ami_uart_boot_DeInit

bool ami_uart_boot_ReInit(void)
{
#if defined(CONFIG_UART_INTERRUPT_DRIVEN)
  //---------------------------------------------------------------------------
  // RXD change back to an input
  //---------------------------------------------------------------------------
  ami_board_ConfigPin(AMI_BOARD_OUT_BOOT_RXD,GPIO_INPUT);
  NRF_UARTE0_NS->ENABLE = 8;
  NRF_UARTE0_NS->TASKS_STARTRX = 1;
  NRF_UARTE0_NS->TASKS_STARTTX = 1;
  //---------------------------------------------------------------------------
  // Set Boot driver is active
  //---------------------------------------------------------------------------
  bBootDriverActive = TRUE;
  return TRUE;
} //ami_uart_boot_ReInit

The debug serial channel stops working but the rest of the code seems to still work so there is no hard fault exception.

Again the debug channel works until I can the Deint() function and then ReInit() when I need to send another string.

What could be my problem?

Thanks

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

Stian Røed Hafskjold — Tue, 31 Aug 2021 14:55:20 GMT

Hi David,

I'm taking over this case from Heidi.

Can you please read out the GPIO registers using nrfjprog to see the state of the GPIOs. Something like this:

$ nrfjprog --family nrf91 --memrd 0x50842500 --n 0x28
0x50842500: 00000000 00000000 00000000 00000000   |................|
0x50842510: 00000000 00000000 00000000 00000000   |................|
0x50842520: 00000000 00000000                     |........|

$ nrfjprog --family nrf91 --memrd 0x50842700 --n 128
0x50842700: 00000002 00000002 00000002 00000002   |................|
0x50842710: 00000002 00000002 00000002 00000002   |................|
0x50842720: 00000002 00000002 00000002 00000002   |................|
0x50842730: 00000002 00000002 00000002 00000002   |................|
0x50842740: 00000002 00000002 00000002 00000002   |................|
0x50842750: 00000002 00000002 00000002 00000002   |................|
0x50842760: 00000002 00000002 00000002 00000002   |................|
0x50842770: 00000002 00000002 00000002 00000002   |................|

Also please post the board schematic. Then I can try to guide you on what state the GPIOs should be in when in idle.

Are you able to post the complete project?

[quote user=""] When after using uart0, when sleeping I did not call the uart0 disable code, I got the 900ua baseline current.

When after using uart0, when sleep I performed the uart0 code above, I got a 480ua to 490ua draw.[/quote]

Based on this statement it sounds to me that the HF clock and all other peripherals that requires the HF clock to run are successfully shut down when you get to 490 uA. Since the HF clock consumes about 4-500 uA (which will add up to 900uA). This leads me to think that the remaining current is not due to any of the peripherals. I'm thinking that maybe there is a thread still running/polling something? Are you able to measure the power profile and see if you get any regular current spikes suggesting regular wake ups (in the 10-20 ms range)?

Thanks,
Stian

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

DavidKaplan — Tue, 31 Aug 2021 10:44:07 GMT

Anything new?

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

DavidKaplan — Wed, 25 Aug 2021 12:17:21 GMT

Anything new?

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

Heidi — Wed, 18 Aug 2021 13:11:15 GMT

Hi! I'm looking into this. I'll have an update for you shortly.

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

DavidKaplan — Sun, 15 Aug 2021 06:45:41 GMT

Anyone can help with this whole thread?

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

DavidKaplan — Thu, 12 Aug 2021 06:07:34 GMT

This morning after disabling the SPI bus, I set the pins to output High and when I switch to PM_STATE_SOFT_OFF the current drops from 100ua to 60ua. So when I do not switch PM_STATE_SOFT_OFF I still get more than 400ua, so something is still active in the module. What could be going on?

Do I need also to configure pins that are not connected? and if so what should they be confugured?

Thanks David.

RE: Big current draw when sleeping, nRF9160 custom board with I2C EEPROM & SI7050, SPI ExternalFlash & LSM6DSL, uart0,uart1 using SES v1.6.1

DavidKaplan — Wed, 11 Aug 2021 06:11:19 GMT

Yesterday in another integration session, I added code that would just shutdown the nRF9160 I think in order to see how much current the custom was drawing otherwise and to see what pins' state should be adjusted to reduce current when sleeping.

The current went from 480ua..490ua to about 100ua. I can guess that something in the nRF9160 is still running that gives the 380ua different when the regulator is not shut off.

//-----------------------------------------------------------------------------
// ami_main_Sleep
//  Description
//   Called to put the board to sleep till RTC one second wakeup
//  Parameters
//  Returns
//-----------------------------------------------------------------------------
void ami_main_Sleep(void)
{
  //-------------------------------------------------------------------------
  // Switch pins to sleep
  //-------------------------------------------------------------------------
  ami_board_AwakeSleepSwPins(true);
  //-------------------------------------------------------------------------
  // IRQ Lock to prevent race situation
  //-------------------------------------------------------------------------
  unsigned int key = irq_lock();
  //-------------------------------------------------------------------------
  // Wait for semaphore from ISR; if acquired, do related work, then
  //  go to next loop iteration (the semaphore might have been given again);
  //  else, make the CPU idle.
  //-------------------------------------------------------------------------
  if (k_sem_take(&sec_wakeup_sem, K_NO_WAIT) == 0) {
    //-----------------------------------------------------------------------
    // Ulock IRQ
    //-----------------------------------------------------------------------
    irq_unlock(key);
    //-----------------------------------------------------------------------
    // continue do processing 
    //-----------------------------------------------------------------------
  }else{
        //-------------------------------------------------------------------
        //
        //-------------------------------------------------------------------
 //       pm_low_power_devices();
        //-------------------------------------------------------------------
        // put CPU to sleep to save power 
        //-------------------------------------------------------------------
        k_cpu_atomic_idle(key);
  //      ?!?
        //-------------------------------------------------------------------
        // 
        //-------------------------------------------------------------------
 //       pm_resume_devices();
  }

//#define AMI_EXTRA_LOW_POWER
#ifdef AMI_EXTRA_LOW_POWER
  while (true){
    struct pm_state_info info;
    k_cpu_idle();
    info.state = PM_STATE_SOFT_OFF;
    pm_power_state_set(info);
  } // while                  
#endif                
  //-------------------------------------------------------------------------
  // Switch pins to awake state
  //-------------------------------------------------------------------------
  ami_board_AwakeSleepSwPins(false);
} // ami_main_Sleep

The modem is off as I call lte_lc_deinit(); beforehand.

I hope this helps...

Any thoughts on what is still running. I did not exactly understand what defines are needed in interrupt mode for the uarts. I need to set a timer to each uart?

Thanks David