This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Any other requirement for HEX on DFU in Android OS?

image descriptionHi guys, I install V1.6 nRF ToolBox apk in my Android phone, and want to do the DFU operation. When the device in DFU status, I select the target HEX file but it shows me INVALID file so that the Android phone could not connect to the device. I found the 'ble_app_hrs.v7_1_0.hex' in the SDK folder should be OK with 'Init file selected' displayed. So, is there any other file needed exclude app hex? Or other setting ? The SD version is 7.0 and SDK is 6.0.

Thanks a lot.

  • @Jimlin: nRF Toolbox current version is 1.12. Could you update with latest version ?

    If you use bootloader from SDK v6.x you wouldn't need to select the init file. If you use bootloader from SDK v7.x and up, you would need to select the init file.

    You would need to match the softdevice with the softdevice required for the application image.

    I would suggest you to use bootloader from newer SDK, SDK v6.0 is pretty old.

  • @Hung Bui Thanks for remind. But I could not find the download link of nRF Toolbox for BLE V1.12 on the nodicsemi .com. It's so sad that it could not login in the google play in China for some reasons. Is there any link to download the latest APK in your website? Or could you send me? I prefer the first and could update it in the future in time.

  • Could not access. I update to V1.12 from another market but found it was the same as before, HEX file invalid, like the attached picture. Bootloader and the application both based on SDK 6.0 with softdevice 7.0. No such appearence on the windows PC side with pca10001 dongle.

  • @Jimlin: please make sure you select Application instead of Distribution packet (ZIP) when you click Select File. Also after you select the file, please select NO when asked for Init packet.

    The bootloader from SDK v6.0 doesn't require init packet.

    If the issue remain, please upload your application hex file (by editting the answer)

Related