sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Documentation: Fix openocd command instruction

Browse Source 
A user reported me an issue while following our documentation
then looking his command line error I noticed the openocd stlink
interface was wrong: st-link-v2.cfg -> stlink-v2.cfg
This commit is contained in:
Alan C. Assis 2021-11-04 10:53:17 -03:00 committed by Abdelatif Guettouche
parent 440787c0c1
commit b248dd0d3a
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/quickstart/debugging.rst
View File

@ -59,7 +59,7 @@ start ``openocd`` with the following command:
.. code-block:: console
$ openocd -f interface/st-link-v2.cfg -f target/stm32f1x.cfg
$ openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg
This will start a ``gdb`` server. Then, start ``gdb`` with:
@ -138,7 +138,7 @@ Finally, to enable NuttX integration, you need to supply an additional ``openocd
.. code-block:: console
$ openocd -f interface/st-link-v2.cfg -f target/stm32f1x.cfg -c '$_TARGETNAME configure -rtos nuttx'
$ openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg -c '$_TARGETNAME configure -rtos nuttx'
Since ``openocd`` also needs to know the memory layout of certain datastructures, you need to have ``gdb``
run the following commands once the ``nuttx`` binary is loaded:

2
Documentation/quickstart/running.rst
View File

@ -52,7 +52,7 @@ Now, to flash the binary to your board, connect the USB cable and do:
.. code-block:: console
$ cd nuttx/
$ openocd -f interface/st-link-v2.cfg -f target/stm32f1x.cfg -c 'init' \
$ openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg -c 'init' \
-c 'program nuttx/nuttx.bin verify reset' -c 'shutdown'
Access NuttShell