Intel® Aero Platform for UAVs Installation Files



Build files for Intel® Aero Compute Board.

Available Downloads

  • OS Independent
  • Size: 1.4 GB
  • SHA1: F0FE2C421AE3AEC9E53DBDCE36436B48B9274F86
  • OS Independent
  • Size: 139.4 MB
  • SHA1: 290D51FDE16D1E3C8C2B0D37BEBFABC707E8A2F8
  • OS Independent
  • Size: 3.3 MB
  • SHA1: EFECC01744523FBEFEC54C26AA1DB03D58A6DF6E

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.iso

Here are instructions for getting started:

File size: 1.5GB

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

md5sum: 7cdb1fb4ac945e204c9ba85eaac1c9fb   

Capsule/BIOS: capsule-01.00.12-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.12

md5sum: 735044e92a51a5ba47093868cf8117f2

Kernel Source: kernel-source.tar.gz

File size: 146.2MB

File Description: Kernel source for release v01.00.04

md5sum: 3d37d760e0cd3be92253f31aa8a7679d


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.