Update tutorial content

Author: canchebagur

content/learn/02.microcontrollers/04.debugging/assets/debugging_img10.png

@@ -234,7 +234,8 @@ A simple example will demonstrate the implementation of some of the debugging te
 
 ```arduino
 /*
-  LSM9DS1 accelerometer, gyroscope, and magnetometer tasks operation with debugging.
+  Program:
+  - Debugging_techniques_example.ino
 
   Description:
   - This example combines data from the LSM9DS1 accelerometer, gyroscope, and magnetometer into a single code. On top of it,
@@ -243,7 +244,7 @@ A simple example will demonstrate the implementation of some of the debugging te
   The circuit:
   - Arduino Nano 33 BLE Sense.
 
-  Based on examples created by Riccardo Rizzo, Jose García, and Benjamin Dannegård.
+  Code based on examples created by Riccardo Rizzo, Jose García, and Benjamin Dannegård.
   Modified by Taddy Ho Chung and José Bagur (16/02/22).
 */
 
@@ -428,32 +429,33 @@ As shown, the complete code unifies the accelerometer, gyroscope, and magnetomet
 
 It is crucial to know when to stop the code from debugging. While the code shown above can be debugged at runtime, it is much easier to know when to stop or how to stop the code operation. For instance, stopping within the first run gives the following result: 
 
-![Only one runtime instance of the debugging array.](assets/debug_dump_print.png)
+![Only one runtime instance of the debugging array.](assets/debugging_img11.png)
 
 In the Arduino Serial Monitor, we can observe that it has a `1` good mark and a `1` bad mark. The good mark came from the gyroscope having ready the data for use, while the bad mark came from the accelerometer as the data was not ready. So it is possible to see that the accelerometer does not have enough time to get the data ready before it gets to the measurement task. We can try by running a certain number of instances before it gets to the array dump sector, and the result can be seen as follows: 
 
-![5 runtime instance of the debugging array.](assets/debug_dump_print_iter.png)
+![5 runtime instance of the debugging array.](assets/debugging_img12.png)
 
-The accelerometer performed its task without any issue except the first runtime instance, resulting in `9` good marks but `1` bad mark due to this behavior. The `Serial.println(F())`  instruction of module setups and task runtimes also shows us if the code could get past the operations without any issue. By this, it is possible to know the code structure does not misbehave, but for the first time when the device is starting, the accelerometer requires more time to get the data ready in the first instance.
+The accelerometer performed its task without any issue except the first runtime instance, resulting in `9` good marks but `1` bad mark due to this behavior. The `Serial.println(F())` instruction of module setups and task runtimes also shows us if the code could get past the operations without any issue. By this, it is possible to know the code structure does not misbehave, but for the first time when the device is starting, the accelerometer requires more time to get the data ready in the first instance.
 
-Additionally, it is possible to modify the loop code by simply adding a `digitalWrite(LED_BUILTIN, HIGH)` instruction before tasks are called instruction and a `digitalWrite(LED_BUILTIN, LOW)` instruction after the tasks are executed to measure the time it takes to complete them. This can also be helpful to understand the power consumption it draws from this runtime instance:
+Additionally, it is possible to modify the loop code by simply adding a `digitalWrite(12, HIGH)` instruction before tasks are called instruction and a `digitalWrite(12, LOW)` instruction after the tasks are executed to measure the time it takes to complete them using GPIO 12 of the board and an oscilloscope. This can also be helpful to understand the power consumption it draws from this runtime instance:
 
 ```arduino
 void loop() {
   for (int i = 0; i < 5; i++) {
-    digitalWrite(LED_BUILTIN, HIGH); 
+    digitalWrite(12, LOW);
     accelerometer_task();
     gyroscope_task();
     magnetometer_task();
-    digitalWrite(LED_BUILTIN, LOW); 
+    digitalWrite(12, HIGH); 
   }
   
   save_debug_buffer();
-
   debug_stop();
 }
 ```
 
+![Using an oscillocope and a GPIO to measure the time it takes to complete tasks.](assets/debugging_img10.png)
+
 ## Final Thoughts about Debugging
 
 Debugging is a necessary step for developing robust and reliable embedded systems software. We can end this article by mentioning the **four** most essential phases of debugging stated by Robin Knoke in this [article](https://www.embedded.com/debugging-embedded-c/) about debugging embedded C that was published in the Embedded Systems Programming magazine: