Hello,
There's any known issue realated with DFU and Android 7.0? When we try to update firmware with nRF Connect or our APP we get an error (hex file error), but when we try the same hex file with the same apps on Android 6 there's no problem.
Hello,
There's any known issue realated with DFU and Android 7.0? When we try to update firmware with nRF Connect or our APP we get an error (hex file error), but when we try the same hex file with the same apps on Android 6 there's no problem.
@abosch: Could you provide the nRF Connect log ?
@Bjørn Spockeli We detect this issue due to feedback from users of our application that have Android 7.0, so we invite them to use "nRF Connect" and they obtained the same result. We have not a device with Android 7.0 so I can't provide you a log. Could you ensure that DFU works on Android 7 with the same hex files used for Android 6?
As far as I know there are no issues with Android v7.0 and DFU. Which SDK and SoftDevice versions are you using? The format of the distribution zip (i.e. the firmware image zips) has not changed between Android v6.0 and v7.0, and our DFU library should be compatible with both. Would it be possible for you to share the distribution zip so that I can try to reproduce the issue here? Are you using the bootloader from the SDK or have you modified it?
We are using softdevice s110_nrf51822_7.1.0 and SDK 6.1.0. I'm sorry but I can't share with you the application, we are using a modified bootloader. The error appears when we try to send the Application from an ".hex" file, we don't use the zip image. The upload never starts because appears the "DFU file error". I hope we can test it soon with an Android 7 device and I will provide you the log. Thanks.
@abosh : I just discussed this with a colleague and it appears that there is a bug in the nRF Connect App that was introduced after v4.3.0 related to DFU without the distribution zip. Which version are you using on your Android v6.0.0 device? If the customer is using a newer version than v4.3.0, then you can suggest that he downgrades to v4.3.0 as a temporary solution untill we have found the cause and a fix. You can find the APK for older releases here.