diff --git a/docs/rsc/eclipse006.jpg b/docs/rsc/eclipse006.jpg new file mode 100644 index 000000000..fd56acdb5 Binary files /dev/null and b/docs/rsc/eclipse006.jpg differ diff --git a/docs/rsc/eclipse007.jpg b/docs/rsc/eclipse007.jpg new file mode 100644 index 000000000..9332d5777 Binary files /dev/null and b/docs/rsc/eclipse007.jpg differ diff --git a/docs/rsc/eclipse008.jpg b/docs/rsc/eclipse008.jpg new file mode 100644 index 000000000..f602fa81e Binary files /dev/null and b/docs/rsc/eclipse008.jpg differ diff --git a/docs/rsc/eclipse009.jpg b/docs/rsc/eclipse009.jpg new file mode 100644 index 000000000..fb8264b11 Binary files /dev/null and b/docs/rsc/eclipse009.jpg differ diff --git a/docs/rsc/eclipse010.jpg b/docs/rsc/eclipse010.jpg new file mode 100644 index 000000000..d92381ba2 Binary files /dev/null and b/docs/rsc/eclipse010.jpg differ diff --git a/docs/rsc/eclipse011.jpg b/docs/rsc/eclipse011.jpg new file mode 100644 index 000000000..1da305279 Binary files /dev/null and b/docs/rsc/eclipse011.jpg differ diff --git a/docs/rsc/eclipse012.jpg b/docs/rsc/eclipse012.jpg new file mode 100644 index 000000000..e40725fa4 Binary files /dev/null and b/docs/rsc/eclipse012.jpg differ diff --git a/docs/rsc/eclipse013.jpg b/docs/rsc/eclipse013.jpg new file mode 100644 index 000000000..bc8441eef Binary files /dev/null and b/docs/rsc/eclipse013.jpg differ diff --git a/docs/src/eclipse2.dox b/docs/src/eclipse2.dox index 18c4d565a..88a222fc8 100644 --- a/docs/src/eclipse2.dox +++ b/docs/src/eclipse2.dox @@ -160,7 +160,47 @@ * - Set an initial breakpoint in the main function. * - Start the target (which will immediately stop on the breakpoint). * . - * **To be completed** + * The first thing to do is to open the "Debug Configurations..." dialog: + *

+ * @image html eclipse006.jpg + *
+ * The configuration dialog will appear, we must create a native Zylin + * configuration: + *

+ * @image html eclipse007.jpg + *
+ * Now we must give the configuration a name, "ARMCM3-STM32F103-GCC (flash and + * run)" in this example, then setup the various configuration pages as follow: + *

+ * The "Main" tab: + * @image html eclipse008.jpg + *

+ * The "Debugger" tab: + * @image html eclipse009.jpg + *

+ * The "Commands" tab: + * @image html eclipse010.jpg + *
+ * Note that the "Commands" tab contains the part that changes depending on + * the target. The complete commands sequence (it is not fully visible in the + * image) for STM32 is: + * @code + * monitor soft_reset_halt + * monitor wait_halt + * monitor poll + * monitor flash probe 0 + * monitor stm32x mass_erase 0 + * monitor flash write_bank 0 ch.bin 0 + * monitor soft_reset_halt + * symbol-file ch.elf + * thbreak main + * continue + * @endcode + *

+ * The "Common" tab: + * @image html eclipse011.jpg + *
+ * Now the debug configuration is complete. * * @subsection eclipse2_configuring_openocd Configuring and running OpenOCD * OpenOCD must be run, with appropriate parameters, before starting your @@ -184,10 +224,16 @@ * debug configuration (we created just one but you may have multiple * debug configurations in your project, as example I usually create * another debug configuration that just starts the target without - * uploading the code).
+ * uploading the code). + *

+ * @image html eclipse012.jpg + *
* The debugger will be initialized, you will see the operation in progress on * the console then Eclipse will switch to the debug perspective and you will * see your program stopped on the default breakpoint in the main function. + *

+ * @image html eclipse013.jpg + *
* From there you can perform all the usual debugging tasks, set breakpoints, * single step execution, variables, memory and registers inspection etc. * Please refer to the Eclipse documentation about those "normal" operations.