From 64570ac7516e5c3bdfaeecbbb426f501b3c8a06d Mon Sep 17 00:00:00 2001 From: Todd Rylaarsdam Date: Mon, 10 Jul 2023 09:28:27 -0500 Subject: [PATCH] Create functions above setup/loop setSketchStats and getSketchStats were not prototyped, so their definitions should go above setup/loop --- .../tutorials/flash-optimized-key-value-store/content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/hardware/04.pro/boards/portenta-h7/tutorials/flash-optimized-key-value-store/content.md b/content/hardware/04.pro/boards/portenta-h7/tutorials/flash-optimized-key-value-store/content.md index 7900f0addb..28420506ba 100644 --- a/content/hardware/04.pro/boards/portenta-h7/tutorials/flash-optimized-key-value-store/content.md +++ b/content/hardware/04.pro/boards/portenta-h7/tutorials/flash-optimized-key-value-store/content.md @@ -242,7 +242,7 @@ Now that you have everything ready, let's retrieve the previous values from the } ``` -To finish the sketch, create `getSketchStats` and `setSketchStats` functions at the bottom of the sketch (after the `setup()` and `loop()`). +To finish the sketch, create `getSketchStats` and `setSketchStats` functions above `setup()` and `loop()`. The `getSketchStats` function tries to retrieve the stats values stored in the Flash using the key `key` and returns them via the `stats` pointer parameter. Our `SketchStats` data struct is very simple and has a fixed size. You can therefore deserialize the buffer with a simple `memcpy`.