This repository contains firmware images for the Bluefruit LE family of boards from Adafruit Industries.

Current members of this board family include:

• BLEFRIEND Firmware (16KB SRAM parts):
  • Bluefruit LE Friend V1 - Blue PCB
• BLEFRIEND32 Firmware (32KB SRAM parts):
  • Bluefruit LE Friend V2 - Black PCB
  • Bluefruit LE UART Friend
• BLESPIFRIEND Firmware:
  • Bluefruit LE SPI Friend
  • Bluefruit LE Shield
  • Bluefruit LE Micro
  • Feather 32u4 Bluefruit LE
  • Feather M0 Bluefruit LE

The firmware on your Bluefruit LE modules can be updated with the on-board DFU bootloader, using the latest firmare image from this repository for the update.

The Adafruit Bluefruit LE Connect app for Android or iOS also enable over the air firmware updates using the files found in this repo.

For the V1 (blue PCB) Bluefruit LE Friend, which is based on the first generation 16KB SRAM nRF51822 parts, you must use the 0.5.0 or lower series firmware.

The 0.6.0+ series firmware only works with newer boards based on 32KB SRAM nrf51822 parts like the Bluefruit LE UART Friend or V2 of the Bluefruit LE Friend (black PCBs). The 0.6.0+ firmware won't boot on older 16KB SRAM parts.

If you are using the Bluefruit LE Connect apps from Adafruit to manage your firmware updates, it should take care of the version differences automatically.

Each firmware version and board target folder (for example 0.6.7/blespifriend) contains three files:

• filename.hex - The main firmware image, required for any firmware update.
• filename_signature.hex - This file contains the CRC check for the filename.hex file above, and is required when manually flashing firmware with a tool like Adalink. If the _signature.hex file containing the CRC check isn't flashed along with the main firmware image, the bootloader on the nRF51 will reject the firmware image and you will boot into DFU mode. You only need this file when manually flashing firmware updates onto you Bluefruit LE module via AdaLink or a similar SWD debugger tools. The CRC will automatically be calculate and written when doing over-the-air (OTA) updates.
• filename_init.dat - This file contains meta-data about the main firmware image in filename.hex, such as the required SoftDevice version and expected HW. This file is required when performing over-the-air (OTA) updates, which is a two file process.