diff --git a/Documentation/platforms/arm/stm32f4/index.rst b/Documentation/platforms/arm/stm32f4/index.rst
index 7242a16b56..607024f956 100644
--- a/Documentation/platforms/arm/stm32f4/index.rst
+++ b/Documentation/platforms/arm/stm32f4/index.rst
@@ -519,6 +519,33 @@ Protected Mode Build
      If you do this a lot, you will probably want to invest a little time
      to develop a tool to automate these steps.
 
+Flashing and Debugging
+======================
+
+NuttX firmware Flashing with STLink probe and OpenOCD::
+
+   openocd -f  interface/stlink.cfg -f target/stm32f4x.cfg -c 'program nuttx.bin 0x08000000; reset run; exit'
+
+Remote target Reset with STLink probe and OpenOCD::
+
+   openocd -f interface/stlink.cfg -f target/stm32f4x.cfg -c 'init; reset run; exit'
+
+Remote target Debug with STLink probe and OpenOCD:
+
+ 1. You need to have NuttX built with debug symbols, see :ref:`debugging`.
+
+ 2. Launch the OpenOCD GDB server::
+
+     openocd -f interface/stlink.cfg -f target/stm32f4x.cfg -c 'init; reset halt'
+
+ 3. You can now attach to remote OpenOCD GDB server with your favorite debugger,
+    for instance gdb::
+
+     arm-none-eabi-gdb --tui nuttx -ex 'target extended-remote localhost:3333'
+     (gdb) monitor reset halt
+     (gdb) breakpoint nsh_main
+     (gdb) continue
+
 Supported Boards
 ================