From bf8d3d7e295ced906debeb926d445532969cb35d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1s=20Apol=C3=B3nia?= <75183079+tomasApo@users.noreply.github.com> Date: Tue, 19 Jul 2022 18:32:24 +0100 Subject: [PATCH] Improved ligability for hardware.md When following section 2.2 Hardware, I would get stuck trying to launch gdp but wouldn't get stuck in section 2.1 QEMU. There is a disparity between the code two sections even though they achieving the same function. My suggestion is to warn the user about the different versions of gdp vs gdp-multiarch in the same fashion as the QEMU section. --- src/start/hardware.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/start/hardware.md b/src/start/hardware.md index 5af7804a..485ba853 100644 --- a/src/start/hardware.md +++ b/src/start/hardware.md @@ -176,9 +176,13 @@ Info : stm32f3x.cpu: hardware has 6 breakpoints, 4 watchpoints On another terminal run GDB, also from the root of the template. ``` text -$ -q target/thumbv7em-none-eabihf/debug/examples/hello +gdb-multiarch -q target/thumbv7em-none-eabihf/debug/examples/hello ``` +**NOTE**: like before you might need another version of gdb instead of `gdb-multiarch` depending +on which one you installed in the installation chapter. This could also be +`arm-none-eabi-gdb` or just `gdb`. + Next connect GDB to OpenOCD, which is waiting for a TCP connection on port 3333. ``` console