This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Where is ble_dfu.py?

I found ble_dfu.py referenced in some posts to help automate the generation of an application.dat metadata file used (along with the application.hex file) to create the input to the DFU bootloader can use.

I can't seem to find it any more, however. Is there a place I can go to download it? GitHub? nordicsemi.com?

Parents
  • Really ? I can find it in all the SDKs I have on my machine

    find . -name ble_dfu.py -print
    ./nRF51_SDK_7.0.1/examples/dfu/ble_dfu_send_hex/dfu/ble_dfu.py
    ./nRF51_SDK_7.1.0/examples/dfu/ble_dfu_send_hex/dfu/ble_dfu.py  
    ./nRF51_SDK_7.2.0/examples/dfu/ble_dfu_send_hex/dfu/ble_dfu.py
    ./nrf51_sdk_v6_1_0_b2ec2e6/nrf51822/Board/nrf6310/device_firmware_updates/ble_dfu_send_hex/dfu/ble_dfu.py
    
  • It was in 7.1.0, but was removed in SDK 8.0.0.

    I hacked up the 7.1.0 version to add .zip file support, but was too lazy to add bonding support to it so it could do buttonless upgrades. I would have to manually put the device in bootloader and then use the python script to upload the firmware.

    The nice thing about ble_dfu_send_hex was with a few hacks it is significantly faster then the Android or iOS apps and would happily work with a 7.5ms connection interval.

Reply
  • It was in 7.1.0, but was removed in SDK 8.0.0.

    I hacked up the 7.1.0 version to add .zip file support, but was too lazy to add bonding support to it so it could do buttonless upgrades. I would have to manually put the device in bootloader and then use the python script to upload the firmware.

    The nice thing about ble_dfu_send_hex was with a few hacks it is significantly faster then the Android or iOS apps and would happily work with a 7.5ms connection interval.

Children
No Data
Related