Our BLE Update utility only works with the CC Debugger, which means (unless you are very adventurous) that it can only used with our BLE112/BLE113 modules. What about updating firmware on the BLED112 dongle?
The dongle can be updated using the "/bin/dfutool.exe" application and the "/example/usbcdc/out.hex" file from the latest SDK archive, which you can find under the Software Releases section on our Tech Forum. Note that you can use dfutool to flash any .hex file onto the dongle, but you should only use the one from the usbcdc project because it is guaranteed to keep the dongle in a state where you can still access the API and return it to DFU mode if desired. Other projects can leave the dongle in a state where DFU mode is inaccessible, which means it can't be updated again (unless you break open the physical housing and connect a CC debugger to the test pads).
NOTE: Newer SDK builds (88 or later) contain a GUI interface within the BLEGUI program, so that manually running the "dfutool.exe" command is not necessary. Both upgrade methods are detailed below.
For more information on the precautions necessary when flashing other projects onto the dongle, please see the following article:
In general, this is not something you want to do, but it is possible if you follow the correct guidelines.
All firmware that is build using our BLE SDK newer than v1.1.0-55 requires a valid Bluegiga license key in order to activate the BLE radio. All hardware manufactured after October 2012 has this key present, but some older devices do not contain a valid license key. Although these dongles can be upgraded (or downgraded) using the DFU process at any time, any attempts to use BLE-related functionality will result in a 0x0189 error code indicating that no valid license key could be found. You will also receive the "No License Key" event packet [ 80 00 00 05 ] upon boot/reset, immediately after the system_boot event packet.
The license key on a BLED112 dongle cannot be updated using the DFU method, and the dongle must either be replaced or reprogrammed manually by opening up the housing and attaching the CC debugger to five small test pads on the PCB inside. Please contact us via the support ticketing system for further information concerning replacement.
The basic procedure is this:
..\..\bin\dfutool.exe 2458:fffe out.hex