3.3 KiB
Web Bluetooth DFU
Device firmware update with Web Bluetooth
Update device firmware via Web Bluetooth following the protocol here:
Device Configuration
You will need an nRF51 or nRF52 development kit, flashed with the appropriate image:
Web Example
Open this site in a Web Bluetooth enabled browser:
https://thegecko.github.io/web-bluetooth-dfu/
Node Example
Clone this repository, install the npm dependencies and execute.
$ npm install
$ node example_node <device-type>
Where <device-type> is one of nrf51 or nrf52.
Updating the SoftDevice or Bootloader
When updating the application nothing special needs to be done - the only input required is APPLICATION.hex. However it is possible to update the SoftDevice or Bootloader as well. The user will need to specify the image type of the update when transferring a SoftDevice or Bootloader in dfu.provision() (i.e. dfu.provision(device, buffer, dfu.ImageType.SoftDevice);) along with the following:
Softdevice: When updating the SoftDevice we must not rewrite the Master Boot Record (MBR). As the MBR is included in Nordic's SoftDevices at the beggining of FLASH, the end address of the MBR will need to be specified when converting the hex file (i.e. hex2bin(softdevice.hex, 0x1000);). This way when updating the SoftDevice the current MBR already on the device will be preserved, but the SoftDevice will be replaced. User is responsible for determining the end address of the MBR for their specific SoftDevice and specifying this as an input to hex2bin.
Bootloader: When updating the bootloader we must not rewrite the UICR. The UICR is a special page of FLASH located in a different memory region on Nordic Devices. Nordic's DFU protocol does not support transferring data that is located in this memory region, and thus it needs to be trimmed off of our BOOTLOADER.hex file. However hex2bin will take care of this automatically and no special care needs to be taken when doing this type of update.
Note: Currently updating the SoftDevice and Bootloader at the same time is not supported.