Fix markdown links to filenames with spaces
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
mikeller
parent
1988097a98
commit
579f6e1de8
|
|
@ -43,7 +43,7 @@ Notes:
|
|||
|
||||
### Sparky
|
||||
|
||||
See the [Sparky board chapter](Board - Sparky.md).
|
||||
See the [Sparky board chapter](Board%20-%20Sparky.md).
|
||||
|
||||
## Configuration
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Here are the general hardware specifications for this boards:
|
|||
set serialrx_provider = 1 (0 for 1024bit, 1 for 2048bit)
|
||||
set spektrum_sat_bind = 5
|
||||
|
||||
For more detail of the different bind modes please refer the [Spektrum Bind](Spektrum bind.md) document
|
||||
For more detail of the different bind modes please refer the [Spektrum Bind](Spektrum%20bind.md) document
|
||||
|
||||
Deltang receivers in serial mode will work like any other Spektrum satellite receiver (10bit, 22ms) only the bind process will be different.
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ The MotoF3 also provides built-in power distribution for four ESCs, an on-board
|
|||
|
||||
MotoLab boards all use the built-in USB interface on the STM32F3 microcontroller. New versions of Cleanflight can be installed using Cleanflight Configurator through the USB interface. Installation of new firmware is described here:
|
||||
|
||||
[USB Flashing](USB Flashing.md)
|
||||
[USB Flashing](USB%20Flashing.md)
|
||||
|
||||
Firmware installation using Windows operating system is complicated because the default device driver for the STM32 USB interface in DFU programming mode is not compatible with the Configurator flash tool. The required DFU mode driver must be manually installed. The default driver for the USB port in normal (VCP) mode is also required for connection to Configurator. Additional details on the drivers and their installion is provided here:
|
||||
|
||||
|
|
|
|||
|
|
@ -72,4 +72,4 @@ Buzzer support on the CC3D requires that a buzzer circuit be created to which th
|
|||
PA15 is unused and not connected according to the CC3D Revision A schematic.
|
||||
Connecting to PA15 requires careful soldering.
|
||||
|
||||
See the [CC3D - buzzer circuit.pdf](Wiring/CC3D - buzzer circuit.pdf) for details.
|
||||
See the [CC3D - buzzer circuit.pdf](Wiring/CC3D%20-%20buzzer%20circuit.pdf) for details.
|
||||
|
|
|
|||
|
|
@ -60,8 +60,8 @@ or other display corruption.
|
|||
|
||||
More can be read about this procedure here: http://www.multiwii.com/forum/viewtopic.php?f=6&t=2705&start=10
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Connections
|
||||
|
||||
|
|
|
|||
|
|
@ -99,12 +99,12 @@ If the aircraft won't arm, count the red Warning LED flashes and find out the re
|
|||
Some advanced configurations and features are documented in the following pages, but have not been touched-upon earlier:
|
||||
|
||||
* [Profiles](Profiles.md)
|
||||
* [PID tuning](PID tuning.md)
|
||||
* [In-flight Adjustments](Inflight Adjustments.md)
|
||||
* [PID tuning](PID%20tuning.md)
|
||||
* [In-flight Adjustments](Inflight%20Adjustments.md)
|
||||
* [Blackbox logging](Blackbox.md)
|
||||
* [Using a Sonar](Sonar.md)
|
||||
* [Spektrum Bind](Spektrum bind.md)
|
||||
* [Spektrum Bind](Spektrum%20bind.md)
|
||||
* [Telemetry](Telemetry.md)
|
||||
* [Using a Display](Display.md)
|
||||
* [Using a LED strip](LedStrip.md)
|
||||
* [Migrating from baseflight](Migrating from baseflight.md)
|
||||
* [Migrating from baseflight](Migrating%20from%20baseflight.md)
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ Build a binary with debugging information using command line or via Eclipse make
|
|||
|
||||
Example Eclipse make target
|
||||
|
||||
|
||||
|
||||
|
||||
# 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:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
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
|
||||
|
||||
|
||||
|
||||
|
||||
Choose the appropriate gdb executable - ideally from the same toolchain that you use to build the executable.
|
||||
|
||||
|
||||
|
||||
|
||||
Configure Startup as follows
|
||||
|
||||
|
|
@ -73,9 +73,9 @@ monitor reset
|
|||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
It may be useful to specify run commands too:
|
||||
|
||||
|
|
@ -85,31 +85,31 @@ monitor reg pc = (0x00000004)
|
|||
continue
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
If you use cygwin an additional entry should be shown on the Source tab (not present in this screenshot)
|
||||
|
||||
|
||||
|
||||
|
||||
Nothing to change from the defaults on the Common tab
|
||||
|
||||
|
||||
|
||||
|
||||
Start up the J-Link server in USB mode
|
||||
|
||||
|
||||
|
||||
|
||||
If it connects to your target device it should look like this
|
||||
|
||||
|
||||
|
||||
|
||||
From Eclipse launch the application using the Run/Debug Configurations..., Eclipse should upload the compiled file to the target device which looks like this
|
||||
|
||||
|
||||
|
||||
|
||||
When it's running the J-Link server should look like this.
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -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/
|
||||
|
|
|
|||
Loading…
Reference in New Issue