Intel® Aero Platform for UAVs Installation Files



Build files for Intel® Aero Compute Board.

Available Downloads

  • OS Independent
  • Size: 1.3 GB
  • SHA1: 771D78FB1B9623829CDDE8308DBACCE2B72585B9
  • OS Independent
  • Size: 139.3 MB
  • SHA1: DBD845F77CE218E29BFE8A81DAABC7AC2751CB3F
  • OS Independent
  • Size: 3.3 MB
  • SHA1: C043C7A887CAF7286C9EF60791B67291C625212F

Detailed Description

The Intel® Aero Compute Board is a purpose-built, unmanned aerial vehicle (UAV) developer kit powered by a quad-core Intel® Atom™ processor and geared toward UAV developers, researchers, and enthusiasts. While only the size of a standard playing card, it features abundant storage capabilities, 802.11ac Wi-Fi*, support for multiple cameras including the Intel® RealSense™ Camera R200, which is part of the optional Vision Accessory Kit, industry standard interfaces, and reconfigurable I/O to facilitate connecting to a broad variety of drone hardware subsystems. The Compute Board ships with the open-source Yocto Linux* operating system, and offers sample applications and APIs for flight and vision interfaces, reducing hurdles for developers of sophisticated drone applications.


Release Notes:

OS image:intel-aero-image-intel-aero-v01.00.03.iso

Here are instructions for getting started:

File size: 1.4GB

File Description: OS image for Intel Aero Compute Board v01.00.03

md5sum: 597997fc1a2d4b6d3ae410ca060c87ec

Capsule/BIOS: capsule-01.00.11-r0.core2_64.rpm

Here are the instructions for updating the BIOS:

File size: 3.5MB

File Description: BIOS binary for Intel Aero Compute Board v01.00.11

md5sum: f442b3cdfc06fb486a6bfc625ebb05b6

Kernel Source: kernel-source-v01.00.03.tar.gz

File size: 140MB

File Description: Kernel source for release v01.00.03

md5sum: 484926a18cdde63eaeda3d7fe165d4af

This download is valid for the product(s) listed below.

Product and Performance Information


Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.