Android DFU library

RE: Android DFU library

Hung Bui — Thu, 04 Feb 2021 12:42:58 GMT

@Nathan: This is an old case, please create a new case and describe your issue, you can give a link to this case if needed.

RE: Android DFU library

Nathan — Wed, 03 Feb 2021 15:20:29 GMT

I just ran into this issue myself, using SDK 15.3.0 and a Pixel 3a Android phone using the latest version of the nRF Connect app. After pressing the DFU button and selecting the file, the app would push the board into bootloader and the upgrade would start, but I'd get the "bytes were lost" and "CRC does not match" messages in the log and it would quickly fail. The phone's DFU retry procedure would start, but the board would disconnect and refuse to advertise until it times back out to the originally loaded application.

I noticed that if I allowed the app to push the board into bootloader and then immediately closed and restarted the phone app, when I subsequently reconnected to the board and hit the DFU button again, the procedure would succeed this time. I think there's some kind of timing issue where the bootloader is too busy doing something when it first starts up and it winds up dropping incoming data if the DFU procedure starts too quickly.

For now I've also discovered a temporary workaround where I limit the maximum MTU size in the bootloader via NRF_SDH_BLE_GATT_MAX_MTU_SIZE to 63, instead of the default 247. If I do that, the whole DFU process works perfectly without requiring me to reset the phone app in the middle of the procedure.

I can get full traces of everything once I have the the time (wireshark OTA capture, nRF logger output, video recording of the phone side plus logs), but I'm a little too busy at the moment.

Edit: Scratch the workaround, I just got lucky a couple times. Still trying to find a way to solve.

RE: Android DFU library

Mihua — Wed, 25 Sep 2019 01:59:45 GMT

Hi,

I will write a mail to contact you. If you don't receive it, let me know

RE: Android DFU library

yangamin — Tue, 24 Sep 2019 05:06:25 GMT

If there is a local FAE to help solve it, of course, the best, before giving us technical support is James Xing
We are in Huizhou City, Guangdong Province, China, the distributor is Arrow

RE: Android DFU library

Hung Bui — Fri, 20 Sep 2019 07:49:57 GMT

Hi Yangamin,

I think it's easier if we can have a local FAE help you debug this. Could you let me know who was helping you earlier ? Was him from Nordic ?

Also please let me know your location (city ) and the distributor that working with you so we can allocate an FAE to you.

Regarding the sniffer, you may need to check the content of the snfifer trace to see if you actually can see a connection or not. We have an video here It's for older version of the sniffer but the trace should look similar. It's important that the sniffer catch the connect request.

Please send the whole log, of the CRC issue.

IS_SRVC_CHANGED_CHARACT_PRESENT should only present on the bootloader and the application, not on the DFU library on the phone. Please double check if you have it in your application (the bracelet firmware)

RE: Android DFU library

yangamin — Fri, 20 Sep 2019 00:32:02 GMT

The data we captured you said is not connected, we capture the following:
1. Open wireshark, find sniffer and open
2. Find the bracelet to upgrade
3.APP connects the bracelet and starts capturing data.
4.APP issues an upgrade command
Please tell us how to capture the connection status or the data you need?
The CRC problem and "remote dfu not supported" are a problem. The CRC problem is that the development side reports an error, and "remote dfu not supported" is an error reported by the APP client.

IS_SRVC_CHANGED_CHARACT_PRESENT is enabled in the bootloader and pm_local_database_has_changed() is called. The IS_SRVC_CHANGED_CHARACT_PRESENT field is not found in the DFU library (provided by your company). Please tell us how to handle it

RE: Android DFU library

Hung Bui — Mon, 16 Sep 2019 08:52:43 GMT

No, when the protocol is encrypted you should stil be able to see the connection before it's encrypted (connect request, encryption request etc ). Please try capture more trace.

I don't see the issue DFU getting to 4% in the video ? Are you saying that there are different issues ?

Please try explaining when you receive the "CRC issue" and when you get the "remote dfu not supported" ?

Please have a look at the description of pm_local_database_has_changed() to know how it works. But you need to make sure IS_SRVC_CHANGED_CHARACT_PRESENT is enabled.

Please have a look at the buttonless example at \examples\ble_peripheral\experimental_ble_app_buttonless_dfu to see how it works.

RE: Android DFU library

yangamin — Mon, 16 Sep 2019 03:02:00 GMT

Hi Hung Bui,

The packet sent to you is indeed connected. Is it because the Bluetooth protocol layer is encrypted? Can we only use the sniffer to capture the broadcast packet? So what you see is the unconnected state.We don't have any other methods of capturing packets. If there is a way, please guide us.

In addition, the pm_local_database_has_changed() you are talking about is not called in our program. If this is the case, what does the function do? Where is it called? Please explain.

The CRC check in the original question is also the error reported when the DFU is upgraded to 4%. What is the problem?

Thank you for your reply！

RE: Android DFU library

Hung Bui — Thu, 12 Sep 2019 08:35:52 GMT

Hi Yangamin,

The error " Remote DFU not supported" usually happens when the phone caches the attribute table of the device when running in normal operation mode. Then when the device switching to bootloader mode the phone doesn't do a new service discovery. This results that the phone couldn't find the DFU service to do DFU and report that "Remote DFU not supported".

If we can have a sniffer trace of the process it could be more clear if it's the case.

The way to fix this is to make sure you have service changed characteristic on both the application and the bootloader. And send a service changed indication when you switch. Please look for IS_SRVC_CHANGED_CHARACT_PRESENT in your code and check if you call pm_local_database_has_changed() or not

However, this issue should not be related to what you described in the original question, where the CRC error happens. Please try to get another log and sniffer trace.

RE: Android DFU library

yangamin — Thu, 12 Sep 2019 02:29:40 GMT

Hi Hung Bui，

Thank you very much for your reply. The FAE in China does not know how to solve this problem, so we will contact you directly. Please help me solve it.

I will describe to you the process of upgrading with the app.First bind the bracelet to the APP and log in, then use the APP to send an upgrade command to the bracelet and wait for the upgrade.“升级” means upgrade at video 48s， after the data may be what you need

The app obtains the interface at github.com/.../documentation. The code related to the data sent by the mobile phone in the firmware upgrade is in the DFU library, so the mobile phone sends and receives during the upgrade process. What, our APP is unable to find out.

The bootloader is yours.Is it buttonless update.

Using the nrfConnect official app to upgrade with the same offline package can be successful (including Huawei mobile phones)

RE: Android DFU library

Hung Bui — Wed, 11 Sep 2019 14:08:49 GMT

I'm not familiar with the app you showed. I'm not sure what exactly the app doing.

You would need to describe me:

- How does the DFU process should work ? Could you describe a normal DFU update process as you know ?

- Do you use our bootloader or use your own bootloader ?

- Is it buttonless update or it requires switching to bootloader via a button press ?

- We can't really read Chinese so it's harder for us to understand what you show. I would suggest you to contact our local FAE to get more help. Do you have contact to our local support in china ?

- The sniffer trace d0.pcapng doesn't contain any data about a connection, it only has the advertising packets which don't help much.

- Please try to test using nRFToolbox/nRFConnect and record the screen.

RE: Android DFU library

yangamin — Wed, 11 Sep 2019 11:18:25 GMT

Hi Hung Bui,

The following models of HUAWEI mobile phone upgrades have failed:
Hai Si Kirin 970: Glory V10\Note 10\Play, Huawei P20 Pro\nova 3\Mate 10

Kirin 659: Glory 9 Youth Edition \ Play 7X \ Mai Mang 6 \nova 2 \nova 3e \ Enjoy 7s

Kirin 960:nova 2S, glory 9

You said that the nRFToolbox DFU tool upgrade package failed to upload. I checked it. This tool is only suitable for Q8 smart bracelet upgrade.

The data packet we obtained with nrf sniffer d0:77:21:0c:14:cd should be the data of the upgrade process, please answer this question, if my way is wrong, please guide.Attachment is the upgrade process video, please check.Thank you!devzone.nordicsemi.com/.../dfu-upload--fail.mp4

RE: Android DFU library

Hung Bui — Tue, 10 Sep 2019 11:42:13 GMT

Hi Yangamin,

By "image" I meant the DFU image/firmware you use to update. The firmware inside the .zip file.

So what you meant was that if you use non- Huawei phone, you can do DFU update on the ring , but if do DFU update on the Huawei phone, you can't do DFU update ?

Have you tried DFU using the nRFToolbox DFU app ? In the sniffer trace you provided (d0.pcapng) there was no connection. Only advertising packets. Please make sure you capture the connection.

Please try to record the phone's screen when you do DFU, also please try capture a new sniffer trace.

RE: Android DFU library

yangamin — Tue, 10 Sep 2019 05:38:31 GMT

Hi Hung Bui,

In short, the wristband APP on Huawei mobile phones cannot be remotely upgraded by the ring, Is it a problem with DFU lib?

Answer your questions:

1.Attachment 1 is to use nrf sniffer to obtain data for non-Huawei mobile phone opponent ring upgrade, the MAC address is c8:d4:1d:72:1d:ac;
Attachment 2 is the data of Huawei mobile phone opponent ring upgrade, the MAC address is d0:77:21:0c:14:cc, the data transmission process fails and the error is "remote dfu not supported".

2.What is mean "image"?The SDK we use is 12.3, the bootloader data mainly changes the display and timeout restart part.

devzone.nordicsemi.com/.../c8.pcapng devzone.nordicsemi.com/.../d0.pcapng

RE: Android DFU library

Hung Bui — Mon, 09 Sep 2019 14:38:35 GMT

Hi Yangamin,

It's quite hard to understand what you describing.

From the log it seems that the CRC was incorrect.

Could you provide the whole logging data ?

Which image did you use to test ? Which SDK did you use ? Do you have any modification to the bootloader ?

Could you provide the sniffer trace ?