This repository has been archived by the owner on Jan 3, 2023. It is now read-only.
v1.2
Intel Aero v1.2 release
- New update procedure that does not require USB hub and monitor connected. Update is still done with a USB drive connected, but the update can be triggered by just connecting the board via WiFi or usb-ethernet. LEDs are used for monitoring the update.
- New packages added: RealSense ROS node, libavahi-client, efibootmgr, rng-tools
- tar, ps and top are no longer provided by busybox
- ssh daemon is now provided by OpenSSH, also providing sftp for easy file transfer
- Updated iwlwifi driver, wpa-supplicant and hostapd to help fix connection drops
- Wi-Fi Access Point starts 5 seconds faster and no longer requires the password several times
- Wi-Fi default network is now on 192.168.8.x to avoid conflicts with default IP ranges used by home routers
- mavlink-router updated providing:
- Configuration file with endpoints, being easier to change
- Default baudrate to talk to flight stack changed to 460800, which is the advised baudrate to avoid packet loss
- Flight stack logging for both PX4 and ArduPilot, which are now kept in /var/lib/mavlink-router/logs
- Bug fixes in general
- Updated binary for PX4: close to release 1.6 of PX4 upstream, providing:
- Improved flight stabilization with much better tunning (This needs a frame reset and complete sensor calibration with QGroundControl)
- Support to save waypoints
- Logging
- FPGA firmware changes:
- Version information
- Recovery FPGA firmware for RTF that allows instructing the flight controller to stop on bootloader
- All firmwares are now available on /etc/fpga
- Firmwares are built from open source repository at https://github.com/intel-aero/intel-aero-fpga
- The jam tool to flash FPGA firmware now accepts absolute paths
- All tools related to Aero board have now being renamed and prefixed with "aero-", which makes them easier to find. Symbolic links are kept to ensure backwards compatibility, but these are going to be removed in future. Anyone relying on them are advised to update their scripts
- Remove Linux console from ttyS1 as it conflicts with the flight stack during updates