I'm using the nRF52840 DK to develop my application using FreeRTOS while trying to achieve the lowest possible consumption. I'm having some issues so I went back to the ble_app_hrs_freertos_pca10056_s140 example.
I'm on SDK 16.0.0 and while running this example the current used by the nRF52 is around 7 mA which indicates me it's not going to sleep mode, the CPU is always running. Now, if I comment out the vTaskResume() line from the vApplicationIdleHook() function I get a current consumption between 100-300uA (using a multimeter) which is what I would expect. The problem now is I'm not flushing logs so nothing is written in the console. So, I change the vApplicationIdleHook() like this in order to wake the task only if there are pending logs to be processed, which shouldn't be needed because after flushing all the logs in the logger_thread() the system should go to sleep but it's not happening:
/**@brief A function which is hooked to idle task.
* @note Idle hook must be enabled in FreeRTOS configuration (configUSE_IDLE_HOOK).
*/
void vApplicationIdleHook( void )
{
#if NRF_LOG_ENABLED
if (NRF_LOG_PROCESS())
{
vTaskResume(m_logger_thread);
}
#endif
}
Now when running I get the expected 100-300uA power consumption and the log output but when trying to connect to it using the nRF Connect Android app it stays on "Connecting" or connects but fails with error 22 when discovering services! This is also exactly what I'm experiencing on the program I'm writing for my product but I see this also happens on the examples, so, is this a FreeRTOS port bug, a softdevice bug, an SDK bug or am I doing something wrong?
