Using freeRTOS to control BLE and FPU caculation and how to do low power

RE: Using freeRTOS to control BLE and FPU caculation and how to do low power

Susheel Nuguru — Fri, 19 Nov 2021 08:08:04 GMT

seems like you did enable it

#define configUSE_TICKLESS_IDLE 1

RE: Using freeRTOS to control BLE and FPU caculation and how to do low power

Bruse — Mon, 15 Nov 2021 07:41:51 GMT

Hi Susheel,

I'm not sure. It seems I have not enable tickless idle in FreeRTOSConfig.h file.

Which is the macro definition in FreeRTOSConfig.h file? Attachment is my file.

devzone.nordicsemi.com/.../4667.FreeRTOSConfig.h

RE: Using freeRTOS to control BLE and FPU caculation and how to do low power

Susheel Nuguru — Fri, 12 Nov 2021 09:59:35 GMT

Seems like your code looks good now.

[quote user="Bruse"]By the way, power_manage function has not been called, do I need to call it somewhere to enter low power states?[/quote]

If you have enable tickless idle in FreeRTOSConfig.h file, then you do not explicitly do anything as tickless idle will handle sleep for you, but if you are not using tickless idle, then you need to call the power_manage function to make the chip go to sleep in idle states.

RE: Using freeRTOS to control BLE and FPU caculation and how to do low power

Bruse — Fri, 12 Nov 2021 02:36:57 GMT

Thanks!

I have add taskYield to the AppTask_demo task as follow. In the process_ble_commands, it also would calll API function to send data to APP or forward data to APP from peripheral, or send data to peripheral, or forward data to peripheral from APP. Would it be a problem although it works well now.

static void AppTask_demo(void * pvParameter)
{	
		if (pdPASS != xTimerStart(m_test_timer, OSTIMER_WAIT_FOR_QUEUE))
		{
				APP_ERROR_HANDLER(NRF_ERROR_NO_MEM);
		}					
		while(1)
		{
			  process_ble_commands();  	
				taskYIELD();
		}
}

By the way, power_manage function has not been called, do I need to call it somewhere to enter low power states?

RE: Using freeRTOS to control BLE and FPU caculation and how to do low power

Susheel Nuguru — Thu, 11 Nov 2021 12:44:51 GMT

Hi Zhong,

The basic design is simple and correct. Few points to remember though

using uart_printf should only be a debug option and should not be included in release versions since uart logging is power intense as it uses HFCLK
AppTask_demo does not seem to be yielding. Look at taskYield. Everytask that you create must yield at some point to make the idle thread run at some point so that your device can enter low power states.