helper files update

.cargo/def-config.toml

@@ -2,10 +2,11 @@
 # uncomment ONE of these three option to make `cargo run` start a GDB session
 # which option to pick depends on your system
 # If the RevA board is used, replace jlink.gdb with jlink-reva.gdb
-# runner = "arm-none-eabi-gdb -q -x jlink.gdb"
+# runner = "arm-none-eabi-gdb -q -x jlink/jlink.gdb"
-# runner = "gdb-multiarch -q -x jlink.gdb"
+# runner = "gdb-multiarch -q -x jlink/jlink.gdb"
-# runner = "gdb -q -x openocd.gdb"
+
-# runner = "gdb-multiarch -q -x jlink.gdb"
+# runner = "arm-none-eabi-gdb -q -x jlink/jlink-reva.gdb"
+# runner = "gdb-multiarch -q -x jlink/jlink-reva.gdb"
 
 rustflags = [
   # This is needed if your flash or ram addresses are not aligned to 0x10000 in memory.x

README.md

@@ -7,7 +7,7 @@ git submodule init
 git submodule update
 ```
 
-# Using the `.cargo/config.toml` file
+## Using the `.cargo/config.toml` file
 
 Use the following command to have a starting `config.toml` file
 
@@ -15,4 +15,5 @@ Use the following command to have a starting `config.toml` file
 cp .cargo/def-config.toml .cargo/config.toml
 ```
 
-You then can adapt the `config.toml` to your needs
+You then can adapt the `config.toml` to your needs. For example, you can configure runners
+to conveniently flash with `cargo run`.