Cannot start HF clock after release

RE: Cannot start HF clock after release

moon.kim — Mon, 28 Dec 2020 10:17:30 GMT

When I did this, the current consumption decreased and it was detected.

It seems that the clock has been released as the current consumption has decreased.

nrf_drv_clock_hfclk_release();

do
{
	//sd_app_evt_wait ();
	if (NRF_LOG_PROCESS() == false)
    {
        nrf_pwr_mgmt_run();
    }
	app_usbd_event_queue_process();
}while(gvICLK_get_SleepState() == true);

nrf_drv_clock_hfclk_request(NULL);

RE: Cannot start HF clock after release

Vidar Berg — Mon, 28 Dec 2020 10:13:13 GMT

What happens when you release the clock before entering sleep, does it not wake up again?

RE: Cannot start HF clock after release

moon.kim — Mon, 28 Dec 2020 10:10:09 GMT

If so, is there a way to reduce the current consumption in sleep mode when using USBD?

RE: Cannot start HF clock after release

Vidar Berg — Mon, 28 Dec 2020 09:04:17 GMT

Hi,

It shouldn't be neccessary to keep the clock running in sleep. Are you only receiving the USBDETECTED event if you don't release the HFXO (USBD power-up sequence)?

RE: Cannot start HF clock after release

moon.kim — Wed, 23 Dec 2020 01:54:58 GMT

Thanks

This problem is solved.

However, when the device was in Sleep mode, nrf_drv_clock_hfclk_release() was performed and USB insert wake-up was not executed.

Is there any way to reduce the current while using the USB wake-up event?

RE: Cannot start HF clock after release

Vidar Berg — Mon, 21 Dec 2020 16:36:35 GMT

Hello,

Please make sure your building with the SOFTDEVICE_PRESENT flag, This flag makes it so that the clock driver uses the sd_clock_hfclk_request() Softdevice function to start the clock, rather than trying to access the CLOCK peripheral directly (this is one of the peripherals reserved to the Softdevice).

Best regards,

Vidar