Merge #189

189: Update docs r=therealprof a=modulitos



Co-authored-by: modulitos <[email protected]>

Author: bors[bot]

src/05-led-roulette/flash-it.md

@@ -102,7 +102,9 @@ Remote debugging using :3333
 0x00000000 in ?? ()
 ```
 
-**NOTE**: If you are getting errors like `undefined debug reason 7 - target needs reset` on the OpenOCD GDB server, then you may need to try using `arm-none-eabi-gdb` instead of the `gdb` command, as described above.
+**NOTE**: If you are getting errors like `undefined debug reason 7 - target needs reset`, you can try running `monitor reset halt` as described [here](https://stackoverflow.com/questions/38994596/reason-7-target-needs-reset-unreliable-debugging-setup).
+
+**NOTE**: If the debugger is still not connecting to the OpenOCD server, then you may need to try using `arm-none-eabi-gdb` instead of the `gdb` command, as described above.
 
 By default OpenOCD's GDB server listens on TCP port 3333 (localhost). This command is connecting to
 that port.

src/06-hello-world/README.md

@@ -104,7 +104,7 @@ Breakpoint 1, main () at src/06-hello-world/src/main.rs:10
 10          let mut itm = aux6::init();
 ```
 
-Note that there's a `.gdbinit` at the root of the Cargo project. It's pretty similar to the one we
+Note that there's a `openocd.gdb` at the root of the Cargo project. It's pretty similar to the one we
 used in the previous section.
 
 Before we execute the `iprintln!` statement. We have to instruct OpenOCD to redirect the ITM output

src/11-usart/auxiliary/src/lib.rs

@@ -29,6 +29,9 @@ pub fn init() -> (&'static mut usart1::RegisterBlock, MonoTimer, ITM) {
     let rx = gpioa.pa10.into_af7(&mut gpioa.moder, &mut gpioa.afrh);
 
     Serial::usart1(dp.USART1, (tx, rx), 115_200.bps(), clocks, &mut rcc.apb2);
+    // If you are having trouble sending/receiving data to/from the
+    // HC-05 bluetooth module, try this configuration instead:
+    // Serial::usart1(dp.USART1, (tx, rx), 9600.bps(), clocks, &mut rcc.apb2);
 
     unsafe {
         (

src/13-serial-over-bluetooth/README.md

@@ -22,4 +22,6 @@ Recommended steps to wire this up:
 And that's it! You should be able to run all the programs you wrote in [section 11] without
 modification! Just make sure you open the right serial device / COM port.
 
+**NOTE** If you are having trouble communicating with the bluetooth device, you may need to initialize USART1 with a lower baud rate. Lowering it from 115,200 bps to 9,600 bps might help, as described [here](https://github.com/rust-embedded/discovery/blob/master/src/11-usart/auxiliary/src/lib.rs#L31)
+
 [section 11]: ../11-usart/index.html