From 836aafc0754314053d0db04e79910f3eca1bc0f6 Mon Sep 17 00:00:00 2001 From: Christoph Siedentop Date: Sun, 19 Jul 2020 16:57:55 -0700 Subject: [PATCH] Book: Add note about how fast cycle periods can lead to excessive logging. --- embedded-workshop-book/src/time.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/embedded-workshop-book/src/time.md b/embedded-workshop-book/src/time.md index 2396fc9..7992495 100644 --- a/embedded-workshop-book/src/time.md +++ b/embedded-workshop-book/src/time.md @@ -11,3 +11,5 @@ This program will blink (turn on and off) one of the LEDs on the board. The time The other time related API exposed by the `dk` HAL is the `dk::uptime` function. This function returns the time that has elapsed since the call to the `dk::init` function. This function is used in the program to log the time of each LED toggle operation. ✅ Try changing the `Duration` value passed to `Timer.wait`. Try values larger than one second and smaller than one second. What values of `Duration` make the blinking imperceptible? + +❗If you set the duration to below 100ms, try removing the `log::info!` command in the loop. Too much logging will fill the logging buffer and cause the loop to slow down, resulting in the blink frequency to reduce after a while.