Mirror/ardupilot
5
0
Fork 0
mirror of https://github.com/ArduPilot/ardupilot synced 2025-02-23 00:04:02 -04:00
Code Issues Packages Projects Releases Wiki Activity

HAL_F4light: fixed board's 1_readme.md

Browse Source
This commit is contained in:
night-ghost 2018-03-06 18:55:08 +05:00 committed by Andrew Tridgell
parent f31b2421cc
commit 72fab7d831
5 changed files with 25 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
libraries/AP_HAL_F4Light/boards/f4light_AirbotV2/1_read_me.md
View File

@ -1,14 +1,16 @@
this is for AirbotV2, AirbotV3, Also Known As Omnibus boards
# Board connection # Board connection
Just see board's documentation. Just see board's documentation.
## Default connection ## Default connection
| Function | Serial | | Function | Serial |
| ------ | ------ | | ------ | ------ |
| USB | Serial0 in MP | | USB | Serial0 in MP |
| Telemetry | UART1 (Serial1) | | Telemetry | UART1 (Serial1) |
| GPS | UART6 (Serial3) | | GPS | UART6 (Serial3) |
| Built-in OSD | Serial2 | | Built-in OSD | Serial2 |
This board REQUIRES external Compass via I2C bus. This board REQUIRES external Compass via I2C bus.
@ -19,7 +21,7 @@ Built-in OSD can be configured via files in root directory of SD card:
- font.mcm is font (select one of https://github.com/night-ghost/minimosd-extra/tree/master/Released/FW_%2B_Char). This file will be deleted after flashing. - font.mcm is font (select one of https://github.com/night-ghost/minimosd-extra/tree/master/Released/FW_%2B_Char). This file will be deleted after flashing.
Firmware supports connection to built-in OSD with CT from my MinimOSD (https://github.com/night-ghost/minimosd-extra). To do this: Firmware supports connection to built-in OSD with CT from my MinimOSD (https://github.com/night-ghost/minimosd-extra). To do this:
- set HAL_CONNECT_COM parameter to 4, then reboot / power cycle - set BRD_CONNECT_COM parameter to OSD's Serial (usually 2), then reboot / power cycle
- USB will be connected to OSD after reboot, supported load/store/fonts in MAVLink mode - USB will be connected to OSD after reboot, supported load/store/fonts in MAVLink mode
OSD will work better when VSYNC out from MAX connected to PC3 (R8 to Vcc). OSD will work better when VSYNC out from MAX connected to PC3 (R8 to Vcc).

8
libraries/AP_HAL_F4Light/boards/f4light_Revolution/1_read_ME.md
View File

@ -1,8 +1,10 @@
this is for stock Revolution/RevoMini boards
I tried to maintain compatibility with the OpenPilot documentation. The main difference - FlexiPort can I tried to maintain compatibility with the OpenPilot documentation. The main difference - FlexiPort can
be Serial and external I2C port is on pins 7&8 of Input port. But this can be changed by HAL_FLEXI_I2C parameter be Serial and external I2C port is on pins 7&8 of Input port. But this can be changed by BRD_FLEXI_I2C parameter
Main Port - telemetry, Serial1. As a variant it can be used as SBUS input with hardware inverter (Parameter HAL_UART_SBUS) Main Port - telemetry, Serial1. As a variant it can be used as SBUS input with hardware inverter (Parameter BRD_UART_SBUS)
FlexiPort - OSD, Serial2 FlexiPort - OSD, Serial2
Uart6 (pins 5&6) - GPS Uart6 (pins 5&6) - GPS
@ -17,7 +19,7 @@ pins 7&8 of Input port are SCL and SDA of external I2C (or Tx and Rx for SoftSer
Output Port for MOTORs Output Port for MOTORs
Connect to PWM output pins in ArduCopter, CleanFlight or OpenPilot order, and set parameter HAL_MOTOR_LAYOUT accordingly Connect to PWM output pins in ArduCopter, CleanFlight or OpenPilot order, and set parameter BRD_MOTOR_LAYOUT accordingly
5&6 PWM Output pins are Rx and Tx of Serial4 - but only for quads (except motor layout 1, see below) or planes 5&6 PWM Output pins are Rx and Tx of Serial4 - but only for quads (except motor layout 1, see below) or planes

2
libraries/AP_HAL_F4Light/boards/f4light_Revolution_EE128/1_read_ME.md
View File

@ -1,3 +1,5 @@
this is for Revolution/RevoMini board with removed 25q16 and soldered 25q128 or 25q256. This is very easy!
I tried to maintain compatibility with the OpenPilot documentation. The main difference - FlexiPort can I tried to maintain compatibility with the OpenPilot documentation. The main difference - FlexiPort can
be Serial and external I2C port is on pins 7&8 of Input port. But this can be changed by HAL_FLEXI_I2C parameter be Serial and external I2C port is on pins 7&8 of Input port. But this can be changed by HAL_FLEXI_I2C parameter

23
libraries/AP_HAL_F4Light/boards/f4light_Revolution_SD/1_read_ME.md
View File

@ -1,8 +1,10 @@
this is for Revolution/RevoMini board with connected SD card adapter. Internal Dataflash is not used.
I tried to maintain compatibility with the OpenPilot documentation. The main difference - FlexiPort can I tried to maintain compatibility with the OpenPilot documentation. The main difference - FlexiPort can
be Serial and external I2C port is on pins 7&8 of Input port. But this can be changed by HAL_FLEXI_I2C parameter be Serial and external I2C port is on pins 7&8 of Input port. But this can be changed by BRD_FLEXI_I2C parameter
Main Port - telemetry, Serial1. As a variant it can be used as SBUS input with hardware inverter (Parameter HAL_UART_SBUS) Main Port - telemetry, Serial1. As a variant it can be used as SBUS input with hardware inverter (Parameter BRD_UART_SBUS)
FlexiPort - OSD, Serial2 FlexiPort - OSD, Serial2
Uart6 (pins 5&6) - GPS Uart6 (pins 5&6) - GPS
@ -17,7 +19,7 @@ pins 7&8 of Input port are SCL and SDA of external I2C (or Tx and Rx for SoftSer
Output Port for MOTORs Output Port for MOTORs
Connect to PWM output pins in ArduCopter, CleanFlight or OpenPilot order, and set parameter HAL_MOTOR_LAYOUT accordingly Connect to PWM output pins in ArduCopter, CleanFlight or OpenPilot order, and set parameter BRD_MOTOR_LAYOUT accordingly
5&6 PWM Output pins are Rx and Tx of Serial4 - but only for quads (except motor layout 1, see below) or planes 5&6 PWM Output pins are Rx and Tx of Serial4 - but only for quads (except motor layout 1, see below) or planes
@ -30,22 +32,15 @@ PWM input is not supported - this is general trend
OpLink port OpLink port
DSM satellite can be connected to Oplink port (hardware Serial5) or to PPM inputs (pins 3&4 of input port) Connection to OpLink port (RevoMini) - used as external SPI for SD card
binding of DSM satellite can be done in 2 ways:
1. with some additional hardware - managed stabilizer 3.3 volts.
2. directly connected to 3.3v, binding will require short power off
Connection to OpLink port (RevoMini)
Pin 1 is Gnd, Pin 1 is Gnd,
pin 2 is +5 (DSM sat requires 3.3!) pin 2 is +5 (SD card requires 3.3!)
pin 3 is PD2 (pin 54) Rx pin 3 is PD2 (pin 54) detect
pin 4 is PA15 (pin 50) Enable for 3.3 stab. pin 4 is PA15 (pin 50) CS
pin 5 is PC10 (pin 51) SCK pin 5 is PC10 (pin 51) SCK
pin 6 is PC12 (pin 53) MOSI pin 6 is PC12 (pin 53) MOSI
pin 7 is PC11 (pin 52) MISO pin 7 is PC11 (pin 52) MISO
Also Oplink port can be used as external SPI
Airspeed & RSSI Airspeed & RSSI

2
libraries/AP_HAL_F4Light/boards/f4light_cl_racing/1_read_me.md
View File

@ -17,6 +17,6 @@ Built-in OSD can be configured via files in root directory of SD card:
* font.mcm for fonts (this file will be deleted after flashing) * font.mcm for fonts (this file will be deleted after flashing)
also supported connection to built-in OSD with CT from my MinimOSD (https://github.com/night-ghost/minimosd-extra) also supported connection to built-in OSD with CT from my MinimOSD (https://github.com/night-ghost/minimosd-extra)
* set HAL_CONNECT_COM parameter to 4, then reboot / power cycle * set BRD_CONNECT_COM parameter to OSD's Serial(usually 2), then reboot / power cycle
* USB will be connected to OSD after reboot, supported load/store/fonts in MAVLink mode * USB will be connected to OSD after reboot, supported load/store/fonts in MAVLink mode