Upgrade failed by using the nRF Connect tool

[lirongqing]

By using the DFU to transfer an updated version of the application, The nRF Connect tool pop-up tip:"upgrade succesfully". But the version of application mostly is still older.

Sometime it's OK.

Mobile phone models:  Meizu M3s, Meizu note2
The android 5.1 system
nRF Connect tool: Version 4.12 and above

I had tried to change the value:  nRF Connect tool->settings->dfu options->number of packets: from 10 to 1.  It doesn't work.
Everytime it will upgrade succesfully by using the samsung,huawei, or google mobile phone.

What could I do that can match all kind of android mobile phone?

---

According to the reply, add the following content:

The device is nrf52x

The SDK is nRF5_SDK_11.0.0_89a8197

The DFU（library version1.6.1) in NRF Toolbox has the same problem.

There is no problem during the upgrade process. I had checked the log.txt.

 

Thank you.

[Bjørn Kvaale]

lirongqing If you need any more help, would you mind adding a comment in English. 

[lirongqing]

LIN told me several test methods (eg. using the DFU in NRF Toolbox,  check the LOG). I've tried, but  the problem still can't be solved. If you have other Suggestions, please let me know. Thank you.

[Bjørn Kvaale]

You wrote above that the DFU is sometimes successful, right? How often is it successful?

You could try to use the debug bootloader instead to debug using an rtt viewer for example. If you are using rtt, remember to set the optimization level to 0 (Options for Target -> C/C++ tab -> Optimization: field in Keil). Also, make sure to set NRF_LOG_BACKEND_SERIAL_USES_RTT 1, NRF_LOG_ENABLED 1 & NRF_LOG_BACKEND_SERIAL_USES_UART 0 in the sdk_config.h header file.

That way, you can open a J-Link RTT viewer application & see what is happening in the dfu target nrf52 device & see what is going wrong.

[lirongqing]

Test three times or more, it will be successful.

I will try to use your method to test. Your description is very detailed.

Thank you.