Fixup readme and issues template

Author: facchinm

.github/ISSUE_TEMPLATE/compilation_bug_report.md

@@ -15,6 +15,7 @@ A clear and concise description of what the bug is.
 Issues without the full verbose output will be discarded as invalid.
 
 **Mandatory: attach the sketch**
+or a Minimal reproducible example
 Issues without the sketch will be discarded as invalid.
 
 **Additional context**

.github/ISSUE_TEMPLATE/miscellaneous_bug_report.md

@@ -1,6 +1,6 @@
 ---
 name: Miscellaneous bug report
-about: Sketch compile but doesn't upload, or similar issues
+about: Sketch compiles but doesn't upload, or similar issues
 title: ''
 labels: ''
 assignees: ''

.github/ISSUE_TEMPLATE/runtime_bug_report.md

@@ -1,6 +1,6 @@
 ---
 name: Runtime bug report
-about: Sketch compile and uploads but doesn't run correctly (or doesn't run at all)
+about: Sketch compiles and uploads but doesn't run correctly (or doesn't run at all)
 title: ''
 labels: ''
 assignees: ''
@@ -14,17 +14,19 @@ A clear and concise description of what the bug is.
 **Full verbose** compilation output, ideally with `arduino-cli` invocation or from IDE 2.3.3+
 Issues without the full verbose output will be discarded as invalid.
 
-**Output of debug UART**
-Complete output of the console crash, starting from
+**Output of Serial Monitor**
+1. If you have an USB-to-Serial adapter, paste the complete output of the console crash, starting from
 ```*** Booting Zephyr OS build v3.7...```
-Runtime issues without the **full UART output** will be discarded as invalid.
+2. If you don't, compile the sketch in `Debug` mode (see [Toubleshooting section](/troubleshooting)) and paste the output after invoking `sketch` command
+Runtime issues without the **full output** will be discarded as invalid.
 
 **Output of readelf**
+You can find the loaction of the elf file by compiling in Verbose mode and looking near the end of the compilation output (after `Linking everything together..`)
 Paste (or attach) the output of `arm-none-eabi-readelf -a $your_sketch_elf_file`
 
 **Optional: attach the elf file**
 
-**Output: attach the sketch**
+**Optional: attach the sketch**
 
 **Additional context**
 Add any other context about the problem here.

README.md

@@ -45,17 +45,17 @@ export ZEPHYR_SDK_INSTALL_DIR=$folder_where_you_installed_the_sdk
 ```
 The firmwares will be copied to [firmwares](/firmwares) folder.
 
-If the board is fully supported by Zephyr, they can also be directly falshed with `west flash` 
+If the board is fully supported by Zephyr, they can also be directly flashed with `west flash`
 
 ## Use the core in Arduino environment
 
 After runnign the `bootstrap` script, you should be able to symlink the core to `$sketchbook/hardware/arduino-git/zephyr` and it will appear in the IDE/CLI. Boards FQBN will then become `arduino-git:zephyr:name_from_boards_txt`
 
-## Toubleshooting
+## Troubleshooting
 
 **Q: My Sketch doesn't start (Serial doen't appear)**
 
-**A:** Connect a USB-to-UART adapter to the default UART (eg. TX0/RX0 on Giga, TX,RX on Nano) and read the error message
+**A:** Connect a USB-to-UART adapter to the default UART (eg. TX0/RX0 on Giga, TX,RX on Nano) and read the error message (with the sketch compiled in `Default` mode). If you don't own a USB-to-UART adapter, compile the sketch in `Debug` mode; this will force the shell to wait until you open the Serial Monitor. Then, run `sketch` command and *probably* you'll be able to read the error (if generated by `llext`). For OS crashes, the USB-to-UART adapter is the only way to collect the crash.
 
 **Q: I did it and I get a `<err> llext: Undefined symbol with no entry in symbol table ...`**
 
@@ -65,7 +65,7 @@ After runnign the `bootstrap` script, you should be able to symlink the core to
 
 **A:** Open the `.conf` file for your board, add the required `CONFIG_`, recompile/upload the loader.
 
-**Q: I get an OS crash**
+**Q: I get an OS crash, like `<err> os: ***** USAGE FAULT *****`**
 
 **A:** This is usally do to some buffer overflow/coding error in the user's own code. However, since the project is still in Beta, a [good bug report](#bug-reporting) could help identifying an issue in our code.
 
@@ -77,6 +77,10 @@ After runnign the `bootstrap` script, you should be able to symlink the core to
 
 To report a bug, open the [issues](/issues) and follow the instructions. Any issue opened without the needed information will be discarded.
 
+## ArduinoBLE
+
+BLE stack is enabled for Nano 33 BLE; please use [this branch](https://github.com/facchinm/ArduinoBLE/tree/zephyr_hci) to test it.
+
 ## TODO
 
 - [ ] Unify overlay in [loader](/loader/boards) with the one provided in [variant](/variant) for interoperability with GSoC project
@@ -88,6 +92,7 @@ To report a bug, open the [issues](/issues) and follow the instructions. Any iss
 - [ ] Replace [llext_exports.c](/loader/llext_exports.c) with proper symbols generation (via inclues)
 - [ ] Provide better usability for `Debug` builds (eg. shell over USB)
 - [ ] Fix corner cases with `std::` includes (like `<iterator>`)
+- [ ] Get rid of all warnings
 
 ## ADVANCED: Add a new target board