Mirror/betaflight
1
0
Fork 0
mirror of https://github.com/betaflight/betaflight.git synced 2025-07-19 14:25:20 +03:00
Code Issues Wiki Activity

Fix markdown links to filenames with spaces

Browse source 
Markdown links cannot have actual spaces in the filename.  Use URL-encoded
spaces (%20) instead.

robo-fixed using:
   sed -i -e 's/\(]([^ )]*\) \([^"]\)/\1%20\2/g' **/*.md

If you don't use zhell, you may need to customize the ** part of that command.
This commit is contained in:
Phil Hord 2017-05-26 16:54:52 -07:00 • committed by mikeller
parent 1988097a98
commit 579f6e1de8
8 changed files with 25 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

28
docs/development/Hardware Debugging in Eclipse.md
View file

@ -4,7 +4,7 @@ Build a binary with debugging information using command line or via Eclipse make
Example Eclipse make target
![](assets/eclipse-gdb-debugging/make 1 - OLIMEXINO GDB.PNG)
![](assets/eclipse-gdb-debugging/make%201%20-%20OLIMEXINO%20GDB.PNG)
# GDB and OpenOCD
@ -41,7 +41,7 @@ Here are some screenshots showing Hydra's configuration of Eclipse (Kepler)
If you use cygwin to build the binaries then be sure to have configured your common `Source Lookup Path`, `Path Mappings` first, like this:
![](assets/eclipse-gdb-debugging/config 7.PNG)
![](assets/eclipse-gdb-debugging/config%207.PNG)
Create a new `GDB Hardware Debugging` launch configuration from the `Run` menu
@ -51,11 +51,11 @@ Select the appropriate .elf file (not hex file) - In these examples the target p
DISABLE auto-build
![](assets/eclipse-gdb-debugging/config 1.PNG)
![](assets/eclipse-gdb-debugging/config%201.PNG)
Choose the appropriate gdb executable - ideally from the same toolchain that you use to build the executable.
![](assets/eclipse-gdb-debugging/config 2.PNG)
![](assets/eclipse-gdb-debugging/config%202.PNG)
Configure Startup as follows
@ -73,9 +73,9 @@ monitor reset
```
![](assets/eclipse-gdb-debugging/config 3.PNG)
![](assets/eclipse-gdb-debugging/config%203.PNG)
![](assets/eclipse-gdb-debugging/config 4.PNG)
![](assets/eclipse-gdb-debugging/config%204.PNG)
It may be useful to specify run commands too:
@ -85,31 +85,31 @@ monitor reg pc = (0x00000004)
continue
```
![](assets/eclipse-gdb-debugging/config 13.PNG)
![](assets/eclipse-gdb-debugging/config%2013.PNG)
If you use cygwin an additional entry should be shown on the Source tab (not present in this screenshot)
![](assets/eclipse-gdb-debugging/config 5.PNG)
![](assets/eclipse-gdb-debugging/config%205.PNG)
Nothing to change from the defaults on the Common tab
![](assets/eclipse-gdb-debugging/config 6.PNG)
![](assets/eclipse-gdb-debugging/config%206.PNG)
Start up the J-Link server in USB mode
![](assets/eclipse-gdb-debugging/config 9.PNG)
![](assets/eclipse-gdb-debugging/config%209.PNG)
If it connects to your target device it should look like this
![](assets/eclipse-gdb-debugging/config 10.PNG)
![](assets/eclipse-gdb-debugging/config%2010.PNG)
From Eclipse launch the application using the Run/Debug Configurations..., Eclipse should upload the compiled file to the target device which looks like this
![](assets/eclipse-gdb-debugging/config 11.PNG)
![](assets/eclipse-gdb-debugging/config%2011.PNG)
When it's running the J-Link server should look like this.
![](assets/eclipse-gdb-debugging/config 12.PNG)
![](assets/eclipse-gdb-debugging/config%2012.PNG)
Then finally you can use Eclipse debug features to inspect variables, memory, stacktrace, set breakpoints, step over code, etc.
@ -117,5 +117,5 @@ Then finally you can use Eclipse debug features to inspect variables, memory, st
If Eclipse can't find your breakpoints and they are ignored then check your path mappings (if using cygwin) or use the other debugging launcher as follows. Note the 'Select other...' at the bottom of the configuration window.
![](assets/eclipse-gdb-debugging/config 8 - If breakpoints do not work.PNG)
![](assets/eclipse-gdb-debugging/config%208%20-%20If%20breakpoints%20do%20not%20work.PNG)

2
docs/development/Hardware Debugging.md
View file

@ -2,7 +2,7 @@
The code can be compiled with debugging information, you can then upload a debug version to a board via a JLink/St-Link debug adapter and step through the code in your IDE.
More information about the necessary hardware and setting up the eclipse IDE can be found [here](Hardware Debugging in Eclipse.md)
More information about the necessary hardware and setting up the eclipse IDE can be found [here](Hardware%20Debugging%20in%20Eclipse.md)
A guide for visual studio can be found here:
http://visualgdb.com/tutorials/arm/st-link/