Hi. It looks that you have HFCLK running all the time. This is probably caused by small issue in power management code. Please try to remove the calls to nrf_power_task_trigger() from soc/arm/nordic_n

#ble #nrf52480

Hi. Great to hear that! Do you have any information about resource usage (Flash/RAM used, CPU load etc)? Piotr ZIĘCIK | Senior Firmware Engineer M +48 698 726 973| Kraków, Poland nordicsemi.com | devz

Hi. Since Krzysztof already left the office, I will try to answer that. When logs are deffered, you need to call LOG_PROCESS() periodically to format log messages and push them to the backends. If CON

Hello. I can recommend looking into https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRFready-Smart-Remote-3-for-nRF52-Series Unfortunately it is not based on the Zephyr, however it implem

Hi. Could you please be a bit more precise? What reliability problem do you have in mind? Best Regards, Piotr Zięcik

Hi. I do not think that per-module error codes are good idea. First, you cannot to this: foo_error_t foo(void) { boo_error_t error = boo(); if (error != BOO_SUCCESS) return error; // Here you are chan