Upgrade failed by using the nRF Connect tool

RE: Upgrade failed by using the nRF Connect tool

lirongqing — Fri, 16 Mar 2018 10:25:43 GMT

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.

RE: Upgrade failed by using the nRF Connect tool

Bjørn Kvaale — Fri, 16 Mar 2018 09:07:51 GMT

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.

RE: Upgrade failed by using the nRF Connect tool

Linxi — Thu, 15 Mar 2018 10:19:23 GMT

如果有时间，可以升级SDK 到 13以上，然后DFU 用 SDK 下的secure DFU 示例工程。

要研究的东西可能会多一些，我们目前 52832搭配 SDK13.1，协议栈 S332 V4.0.5
三款产品在出货

不一定是为了解决你的问题，可以做技术储备

RE: Upgrade failed by using the nRF Connect tool

lirongqing — Thu, 15 Mar 2018 10:13:07 GMT

我们的51平台用魅族升级也是正常的。只有52平台在魅族上升级有问题，魅族和魅蓝的几款机型都测了，都有同样的问题。另外，我手上有的安卓机vivo,华为,小米,锤子都正常。呵呵，可能这个问题暂时列为无解了。只是，如果有新发现，有时间也会去琢磨下。

RE: Upgrade failed by using the nRF Connect tool

Linxi — Thu, 15 Mar 2018 09:11:37 GMT

你要是说其他手机没出现这个问题，那我觉得这个问题无解了。让Nordic 去大量兼容国内那些非原生态的Android系统不现实的。我建议是只要 iPhone 和大部分主流 Android 确保升级稳定就可以了。还有一点，我保持怀疑态度，如果三星和魅族，在升级的时候，DFU工程的LOG显示升级流程完全一样，我不认为下位机会有两种不同的现象。
我们之前有款产品，51平台，SDK 11.0，我开发的时候升级用的是魅蓝，Toolbox 一直正常工作，但是我不确定搭配 52 是不是确实有问题，仅做参考。

RE: Upgrade failed by using the nRF Connect tool

lirongqing — Thu, 15 Mar 2018 08:59:58 GMT

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.

RE: Upgrade failed by using the nRF Connect tool

Bjørn Kvaale — Thu, 15 Mar 2018 08:18:44 GMT

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

RE: Upgrade failed by using the nRF Connect tool

lirongqing — Wed, 14 Mar 2018 10:41:47 GMT

nRF5_SDK_11.0.0_89a8197

现在是普通DFU，我找时间试下secure DFU。

已经联系供应商了，供应商那边的答复还是不能解决，所以到论坛来问的。

谢谢你的建议。如果暂时不能从根源上解决，我们也会把这个问题放在后面处理的。目前通过循环升级来处理，大概升级3、4次就可以成功，只是体验不好。其他手机没出现这个问题。

RE: Upgrade failed by using the nRF Connect tool

Linxi — Wed, 14 Mar 2018 10:28:05 GMT

不知道你SDK 用的哪个版本

DFU 是不是用的 sercure DFU ，区别于之前51 SDK 11 之前的普通DFU

比较快捷的方式是，联系你的芯片供应商，寻求技术支持，能比较快的解决问题

核心技术在Nordic ，研究的意义不是很大，快速解决问题我觉得比较重要

不是不建议研究，只是觉得获得有效核心信息太难

RE: Upgrade failed by using the nRF Connect tool

lirongqing — Wed, 14 Mar 2018 10:24:16 GMT

NRF Toolbox的DFU（library version1.6.1）试了，相同的问题。

Google Play 上，介绍该APP只测试了三星的手机，呵呵，在意料之中。

查看了LOG信息，对比三星手机的LOG，是一样的，传输文件，校正，到完成并断开，都正常。

[DFU] Firmware file opened successfully

...(省略)

[DFU] DFU Start sent (Op Code = 1, Upload Mode = 4)

[DFU] Firmware image size sent (0b, 0b, 58596b)

[DFU] Initialize DFU Parameters completed

[DFU] Uploading firmware...

[DFU] Upload completed in 24131 ms

[DFU] Validate request sent

[DFU] Activate and Reset request sent

[Callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)

如果还有好方法，欢迎继续探讨，

真心很感谢你的热情帮助。

RE: Upgrade failed by using the nRF Connect tool

lirongqing — Wed, 14 Mar 2018 06:14:38 GMT

好的，我测试看下效果再回复

RE: Upgrade failed by using the nRF Connect tool

Linxi — Wed, 14 Mar 2018 06:09:36 GMT

把52的DFU 工程Log打开，升级的时候关注一下Log或许会有发现。

升级过程中，代码会跑DFU的工程流程，熟悉一下工程，把传输、存储、验证新固件的过程通过Log确认一下。

RE: Upgrade failed by using the nRF Connect tool

lirongqing — Wed, 14 Mar 2018 06:05:49 GMT

谢谢，忘记说明了，51是正常的，52不正常。

RE: Upgrade failed by using the nRF Connect tool

Linxi — Wed, 14 Mar 2018 06:02:27 GMT

一看魅族就知道是咱中国人

下位机是51 还是 52？

用Nrf Toolbox 的DFU也试一下

翻墙去Google Play上搜Nrf_connect，看看更新信息中手机的支持。