518822 can't go into sleep mod for current saving

RE: 518822 can't go into sleep mod for current saving

Simonr — Tue, 19 Nov 2019 11:50:06 GMT

There's an issue with the nRF51 series where the power reset might not work to get you out of debug mode. You can try connecting an external resistor to the SWDCLK pin. We have tested with a 470Ohm external resistor which should help here.

You can also check out this current consumption guide for a multitude of ways to reduce current consumption for the nRF51 series. Give them a try and report back if you still can't fix it.

Best regards,

Simon

RE: 518822 can't go into sleep mod for current saving

Songplus — Tue, 19 Nov 2019 08:08:53 GMT

Simon,I measured the current isn't in debug mode ,no breakpoint in the program,all debug tool and IC PIN were disconnect.Runs the smallest IC system and simplest code ,the 1mA current draw is still existing.Enable and disable the SD ,the problem can't be soluted.

RE: 518822 can't go into sleep mod for current saving

Simonr — Mon, 18 Nov 2019 06:43:10 GMT

When the current increases due to an uninit, it indicates that something with the uninit went wrong and that you get an error/hardfault causing the CPU to keep running continuously. So you'll have to find out what's wrong with your uninit function to fix this 4mA consumption.

Next, a 1.3 mA current draw indicates that the chip is in debug mode when you measured the current initially. You can check out section 11.1.3 "Resuming Normal Mode" in the nRF51 reference manual.

According to the compatibility matrix, the nRF51 revision 3 supports all versions of the S130 SoftDevice.

Best regards,

Simon

RE: 518822 can't go into sleep mod for current saving

Songplus — Sun, 17 Nov 2019 11:33:31 GMT

I test the IC in the smallest system，all GPIO disconnnect.

(1)confige all GPIO pulldown input

nrf_gpio_range_cfg_input(0,31,NRF_GPIO_PIN_PULLUP)

,run t advertising at he S130 . the chip can't work;

(2)Let the GPIO at reset statue,run advertising at he S130 . the chip can work; current consumption is float ,change from 0.4~1mA.

(3)Confige GPIO as ouput one by one,the chip can work; current consumption is about 1mA, run advertising well;

(4)Confige GPIO as ouput one by one, in the main funtion just do "power_manage();" current consumption is 1mA .There is a plus every 250ms,I don't know what happen in the chip.

The test code as follow:

int main(void)   
{
	volatile static uint32_t err_code;
	bool                     erase_bonds=true;	
	uint8_t                  i;

	for(i=0;i<32;i++)//can work
	{
		nrf_gpio_cfg_output(i);	  //make sure the pin isn't float
	}	
	/*	 
	timers_init();		
   ble_stack_init();
   err_code = pstorage_init();
   APP_ERROR_CHECK(err_code);
	 

 
   device_manager_init(erase_bonds);
   db_discovery_init();
   csc_c_init(); 

   Init_user_info_store();
   load_gps_correct(&m_sys_data_store);	
	 
   ph_device_manager_init(false);	
   gap_params_init();	 
   advertising_init();
   services_init();
   hids_init();
   ancs_service_init();
   conn_params_init();

   Init_CentralDevice_Scan();

   Init_App_Comit();
//   ADC_Config();  //unused  	 
//   nrf_gpio_range_cfg_input(0,31,NRF_GPIO_PIN_PULLUP);//add this function，CPU can't work

   advertising_start();
*/

   
	
   for (;;) 
   {

      power_manage();

		 
	 }

}

So, frome the test ,the chip maybe have a big bug ,it isn't goog for using at low power production .Or my operation maybe exist a mistake.Could Nordic engineers give a good solution? I'm waiting...

RE: 518822 can't go into sleep mod for current saving

Songplus — Sun, 17 Nov 2019 11:31:46 GMT

MDK5 Projection in SDK12.3.0 miss too many files.Where are these files ? Too many changes in the lastest SDK ,How to migrate the S130 V1.0.0 to he V2.0.1? Is there a integral project ？If change too much ,we need use a long time to modify our production.

RE: 518822 can't go into sleep mod for current saving

Songplus — Sun, 17 Nov 2019 09:12:47 GMT

Today ,I look up the SDK revisions，found that SoftDevice S130 V2.0.0 support NRF51822 V3.Now my production use S130 V1.0.0,but Chip revision unknow(N51822 QFACA2 1921DC).Is the S130 V1.0.0 supporte V3?

RE: 518822 can't go into sleep mod for current saving

Songplus — Sat, 16 Nov 2019 11:41:08 GMT

I test the IC in the smallest system，all GPIO disconnnect.

(1)confige all GPIO pulldown input

nrf_gpio_range_cfg_input(0,31,NRF_GPIO_PIN_PULLUP)

,run t advertising at he S130 . the chip can't work;

(2)Let the GPIO at reset statue,run advertising at he S130 . the chip can work; current consumption is float ,change from 0.4~1mA.

(3)Confige GPIO as ouput one by one,the chip can work; current consumption is about 1mA, run advertising well;

(4)Confige GPIO as ouput one by one, in the main funtion just do "power_manage();" current consumption is 1mA .There is a plus every 250ms,I don't know what happen in the chip.

The test code as follow:

int main(void)   
{
	volatile static uint32_t err_code;
	bool                     erase_bonds=true;	
	uint8_t                  i;

	for(i=0;i<32;i++)//can work
	{
		nrf_gpio_cfg_output(i);	  //make sure the pin isn't float
	}	
	/*	 
	timers_init();		
   ble_stack_init();
   err_code = pstorage_init();
   APP_ERROR_CHECK(err_code);
	 

 
   device_manager_init(erase_bonds);
   db_discovery_init();
   csc_c_init(); 

   Init_user_info_store();
   load_gps_correct(&m_sys_data_store);	
	 
   ph_device_manager_init(false);	
   gap_params_init();	 
   advertising_init();
   services_init();
   hids_init();
   ancs_service_init();
   conn_params_init();

   Init_CentralDevice_Scan();

   Init_App_Comit();
//   ADC_Config();  //unused  	 
//   nrf_gpio_range_cfg_input(0,31,NRF_GPIO_PIN_PULLUP);//add this function，CPU can't work

   advertising_start();
*/

   
	
   for (;;) 
   {

      power_manage();

		 
	 }

}

So, frome the test ,the chip maybe have a big bug ,it isn't goog for using at low power production .Or my operation maybe exist a mistake.Could Nordic engineers give a good solution? I'm waiting...

RE: 518822 can't go into sleep mod for current saving

Songplus — Fri, 15 Nov 2019 08:17:04 GMT

Hi，When I disabling the GPIOTE，current consumption upto 4mA，I don't know how to do?

RE: 518822 can't go into sleep mod for current saving

Simonr — Thu, 14 Nov 2019 13:35:30 GMT

Please try disabling the GPIOTE peripheral as well, as that will keep the HFCLK running if it's left enabled. You'll have to make sure that all peripherals are disabled before going to sleep mode.

Best regards,

Simon