mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-04-14 10:07:39 +08:00
298 lines
10 KiB
Markdown
298 lines
10 KiB
Markdown
# BeagleBone Blue
|
|
|
|
<LinkedBadge type="warning" text="Experimental" url="../flight_controller/autopilot_experimental.md"/>
|
|
|
|
:::warning
|
|
PX4 does not manufacture this (or any) autopilot.
|
|
Contact the [manufacturer](https://beagleboard.org/blue) for hardware support or compliance issues.
|
|
:::
|
|
|
|
[BeagleBone Blue](https://beagleboard.org/blue) is an all-in-one Linux-based computer.
|
|
Although it is optimized for robotics, this compact and inexpensive board has all necessary sensors and peripherals needed by a flight controller.
|
|
This topic shows how to set up the board to run PX4 with [librobotcontrol](https://github.com/beagleboard/librobotcontrol) robotics package.
|
|
|
|
|
|
|
|
## OS Image
|
|
|
|
_BeagleBone Blue_ images can be found here:
|
|
|
|
- [Latest stable OS image](https://beagleboard.org/latest-images).
|
|
- [Test OS images](https://rcn-ee.net/rootfs/bb.org/testing/) (updated frequently).
|
|
|
|
Information about flashing OS images can be found on [this page](https://github.com/beagleboard/beaglebone-blue/wiki/Flashing-firmware).
|
|
Other useful information can be found in the [FAQ](<https://github.com/beagleboard/beaglebone-blue/wiki/Frequently-Asked-Questions-(FAQ)>).
|
|
|
|
:::tip
|
|
Optionally you can update to a realtime kernel, and if you do, re-check if _librobotcontrol_ works properly with the realtime kernel.
|
|
:::
|
|
|
|
The latest OS images at time of updating this document is [AM3358 Debian 10.3 2020-04-06 4GB SD IoT](https://www.beagleboard.org/distros/am3358-debian-10-3-2020-04-06-4gb-sd-iot).
|
|
|
|
## Cross Compiler Build (Recommend)
|
|
|
|
The recommended way to build PX4 for _BeagleBone Blue_ is to compile on a development computer and upload the PX4 executable binary directly to the BeagleBone Blue.
|
|
|
|
:::tip
|
|
This approach is recommended over [native build](#native_builds) due to speed of deployment and ease of use.
|
|
:::
|
|
|
|
::: info
|
|
The PX4 build requires [librobotcontrol](http://strawsondesign.com/docs/librobotcontrol/) which is automatically included in the build (but it can be installed and tested independently if required).
|
|
:::
|
|
|
|
### Beaglebone Blue WIFI Setup
|
|
|
|
For easy access to your board, you can connect it to your home network via wifi.
|
|
|
|
The steps are (execute on the board):
|
|
|
|
```sh
|
|
sudo su
|
|
connmanctl
|
|
connmanctl>scan wifi
|
|
connmanctl>services
|
|
#(at this point you should see your network SSID appear.)
|
|
connmanctl>agent on
|
|
connmanctl>connect <SSID>
|
|
Enter Passphrase
|
|
connmanctl>quit
|
|
```
|
|
|
|
::: info
|
|
The format of the `<SSID>` above is normally the text 'wifi' followed by a string of other characters.
|
|
After entering the command you will be prompted to enter the wifi password.
|
|
:::
|
|
|
|
### SSH root Login on Beaglebone
|
|
|
|
Root login can be enabled on the board with:
|
|
|
|
```sh
|
|
sudo su
|
|
echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && systemctl restart sshd
|
|
```
|
|
|
|
### Cross Compiler Setup
|
|
|
|
1. First set up _rsync_ (this is used to transfer files from the development computer to the target board over a network - WiFi or Ethernet).
|
|
For _rsync_ over SSH with key authentication, follow the steps here (on the development machine):
|
|
1. Generate an SSH key if you have not previously done so:
|
|
|
|
```
|
|
ssh-keygen -t rsa
|
|
```
|
|
|
|
1. ENTER //no passphrase
|
|
1. ENTER
|
|
1. ENTER
|
|
|
|
1. Define the BeagleBone Blue board as `beaglebone` in **/etc/hosts** and copy the public SSH key to the board for password-less SSH access:
|
|
|
|
```
|
|
ssh-copy-id debian@beaglebone
|
|
```
|
|
|
|
1. Alternatively you can use the beaglebone's IP directly:
|
|
|
|
```
|
|
ssh-copy-id debian@<IP>
|
|
```
|
|
|
|
1. When prompted if you trust: yes
|
|
1. Enter root password
|
|
|
|
1. Cross Compile Setup
|
|
1. Toolchain download
|
|
1. First install the toolchain into _/opt/bbblue_toolchain/gcc-arm-linux-gnueabihf_.
|
|
Here is an example of using soft link to select which version of the toolchain you want to use:
|
|
|
|
```sh
|
|
mkdir -p /opt/bbblue_toolchain/gcc-arm-linux-gnueabihf
|
|
chmod -R 777 /opt/bbblue_toolchain
|
|
cd /opt/bbblue_toolchain/gcc-arm-linux-gnueabihf
|
|
```
|
|
|
|
The ARM Cross Compiler for _BeagleBone Blue_ can be found at [Linaro Toolchain Binaries site](https://www.linaro.org/downloads/#gnu_and_llvm).
|
|
|
|
:::tip
|
|
GCC in the toolchain should be compatible with kernel in _BeagleBone Blue_.
|
|
General rule of thumb is to choose a toolchain where version of GCC is not higher than version of GCC which comes with the OS image on _BeagleBone Blue_.
|
|
:::
|
|
|
|
Download and unpack [gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz](https://snapshots.linaro.org/gnu-toolchain/13.0-2022.06-1/arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz) to the bbblue_toolchain folder.
|
|
|
|
Different ARM Cross Compiler versions for _BeagleBone Blue_ can be found at [Linaro Toolchain Binaries site](https://www.linaro.org/downloads/).
|
|
|
|
```sh
|
|
wget https://snapshots.linaro.org/gnu-toolchain/13.0-2022.06-1/arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz
|
|
tar -xf gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz
|
|
```
|
|
|
|
:::tip
|
|
The GCC version of the toolchain should be compatible with kernel in _BeagleBone Blue_.
|
|
:::
|
|
|
|
As a general rule of thumb is to choose a toolchain where the version of GCC is not higher than the version of GCC which comes with the OS image on _BeagleBone Blue_.
|
|
|
|
1. Add it to the PATH in ~/.profile as shown below
|
|
|
|
```sh
|
|
export PATH=$PATH:/opt/bbblue_toolchain/gcc-arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf/bin
|
|
```
|
|
|
|
::: info
|
|
Logout and Login to apply the change, or execute the same line on your current shell.
|
|
:::
|
|
|
|
1. Setup other dependencies by downloading the PX4 source code and then running the setup scripts:
|
|
|
|
````
|
|
git clone https://github.com/PX4/PX4-Autopilot.git --recursive
|
|
ols
|
|
```
|
|
|
|
You may have to edit the upload target to match with your setup:
|
|
|
|
```sh
|
|
nano PX4-Autopilot/boards/beaglebone/blue/cmake/upload.cmake
|
|
|
|
# in row 37 change debian@beaglebone.lan TO root@beaglebone (or root@<IP>)
|
|
````
|
|
|
|
See the [Development Environment Setup](../dev_setup/dev_env_linux_ubuntu.md) instructions for additional information.
|
|
|
|
### Cross Compile and Upload
|
|
|
|
Compile and Upload
|
|
|
|
```
|
|
make beaglebone_blue_default upload
|
|
```
|
|
|
|
::: info
|
|
Without upload, files stored local in build folder.
|
|
:::
|
|
|
|
To test the uploaded files, run the following commands on the _BeagleBone Blue_ board:
|
|
|
|
```sh
|
|
cd /home/debian/px4
|
|
sudo ./bin/px4 -s px4.config
|
|
```
|
|
|
|
::: info
|
|
Currently _librobotcontrol_ requires root access.
|
|
:::
|
|
|
|
<a id="native_builds"></a>
|
|
|
|
## Native Builds (optional)
|
|
|
|
You can also natively build PX4 builds directly on the BeagleBone Blue.
|
|
|
|
After acquiring the pre-built library,
|
|
|
|
1. Select the _librobotcontrol_ installation directory, and set it in the `LIBROBOTCONTROL_INSTALL_DIR` environment variable so that other unwanted headers will not be included
|
|
1. Install **robotcontrol.h** and **rc/\*** into `$LIBROBOTCONTROL_INSTALL_DIR/include`
|
|
1. Install pre-built native (ARM) version of librobotcontrol.\* into `$LIBROBOTCONTROL_INSTALL_DIR/lib`
|
|
|
|
Run the following commands on the BeagleBone Blue (i.e. via SSH):
|
|
|
|
1. Install dependencies:
|
|
|
|
```sh
|
|
sudo apt-get update
|
|
sudo apt-get install cmake python3-empy=3.3.4-2
|
|
```
|
|
|
|
1. Clone the PX4 Firmware directly onto the BeagleBone Blue.
|
|
1. Continue with the [standard build system installation](../dev_setup/dev_env_linux.md).
|
|
|
|
## Changes in config
|
|
|
|
All changes can be made in de px4.config file directly on beaglebone.
|
|
For example, you can change the WIFI to wlan.
|
|
|
|
::: info
|
|
If you want to change permanently, you have to change **PX4-Autopilot/posix-configs/bbblue/px4.config** on the Build Machine before build.
|
|
:::
|
|
|
|
## Autostart During Boot
|
|
|
|
Here is an example [/etc/rc.local]:
|
|
|
|
```sh
|
|
#!/bin/sh -e
|
|
#
|
|
# rc.local
|
|
#
|
|
# This script is executed at the end of each multiuser runlevel.
|
|
# Make sure that the script will "exit 0" on success or any other
|
|
# value on error.
|
|
#
|
|
# In order to enable or disable this script just change the execution
|
|
# bits.
|
|
#
|
|
# By default this script does nothing.
|
|
|
|
# wait for services to start up
|
|
/bin/sleep 25
|
|
|
|
cd /home/debian/px4
|
|
|
|
/home/debian/px4/bin/px4 -d -s /home/debian/px4/px4.config > /home/debian/px4/PX4.log &
|
|
|
|
exit 0
|
|
```
|
|
|
|
Below is a _systemd_ service example [/lib/systemd/system/px4-quad-copter.service]:
|
|
|
|
```sh
|
|
[Unit]
|
|
Description=PX4 Quadcopter Service
|
|
After=networking.service network-online.target
|
|
StartLimitIntervalSec=0
|
|
Conflicts=px4-fixed-wing.service
|
|
|
|
[Service]
|
|
WorkingDirectory=/home/debian/px4
|
|
User=root
|
|
ExecStart=/home/debian/px4/bin/px4 -d -s /home/debian/px4/px4.config
|
|
|
|
Restart=on-failure
|
|
RestartSec=1
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|
|
```
|
|
|
|
### Miscellaneous
|
|
|
|
#### Power Servo Rail
|
|
|
|
When PX4 starts, it automatically applies power to servos.
|
|
|
|
#### Unique Features
|
|
|
|
BeagleBone Blue has some unique features such as multiple choices of WiFi interfaces and power sources.
|
|
Refer to comments in **/home/debian/px4/px4.config** for usage of these features.
|
|
|
|
#### SBUS Signal Converter
|
|
|
|
SBUS signal from receiver (e.g., FrSky X8R) is an inverted signal.
|
|
UARTs on BeagleBone Blue can only work with non-inverted 3.3V level signal.
|
|
[This tutorial](../tutorials/linux_sbus.md) contains a SBUS signal inverter circuit.
|
|
|
|
#### Typical Connections
|
|
|
|
For a quadcopter with GPS and an SBUS receiver, here are typical connections:
|
|
|
|
1. Connect the ESC of motor 1, 2, 3 and 4 to channel 1, 2, 3 and 4 of servo outputs on BeagleBone Blue, respectively.
|
|
If your ESC connector contains a power output pin, remove it and do not connect it to the power output pin of the servo channel on the BeagleBone Blue.
|
|
|
|
1. Connect the above mentioned converted SBUS signal to the dsm2 port if you have the matching connector for dsm2, otherwise connect it to any other available UART port and change the corresponding port in **/home/debian/px4/px4.config** accordingly.
|
|
|
|
1. Connect the signals of GPS module to GPS port on the BeagleBone Blue.
|
|
Note that the signal pins of the GPS port on the BeagleBone Blue are only 3.3V tolerant, so choose your GPS module accordingly.
|