BLE DFU fails after a certain time

RE: BLE DFU fails after a certain time

bscdb — Wed, 28 Aug 2019 23:58:08 GMT

Now it works! I had placed 04 command at the wrong location. Thanks.

RE: BLE DFU fails after a certain time

Hung Bui — Mon, 26 Aug 2019 08:48:12 GMT

Hi Sonal,

How big is your image ? It's seems in the sniffer that it was very small image.

Which DFU master device did you use in the original log/trace ?

It seems that the logs (.txt files) didn't capture the whole DFU process ? Do you have better trace that you have the whole process ?

Do you see the 90 seconds issue when you test using the nRF Toolbox app /nrfConnect app on PC ?

RE: BLE DFU fails after a certain time

bscdb — Fri, 23 Aug 2019 20:58:26 GMT

Hi,

I see some differences in sniffer traces but I'm not getting what is exactly missing? Here are the sniffer traces & rtt logs.

devzone.nordicsemi.com/.../original.pcapng

devzone.nordicsemi.com/.../modified.pcapng

devzone.nordicsemi.com/.../rtt_5F00_original.txt

devzone.nordicsemi.com/.../rtt_5F00_modified.txt

RE: BLE DFU fails after a certain time

Hung Bui — Fri, 23 Aug 2019 08:20:13 GMT

Hi Sonal,

Since you are making a DFU master, it's important that you would know what happens on the bootloader. I strongly suggest you to build the bootloader in debug mode and enable logging.
After execute command I believe you don't need to do anything else. After you receive execute response, you can just terminate the connection.

Please record a sniffer trace of a success DFU update then you can compare the behavior of the bootloader when you do DFU from your master.

RE: BLE DFU fails after a certain time

bscdb — Fri, 23 Aug 2019 03:55:12 GMT

Ok, now I'm able to get the success response for execute command. My computation for creating data objects of 4096 bytes and then again dividing those into 244-byte packets was wrong.

But even after that why is the nrf52 getting stuck in the bootloader? Is there any step after that? I'm using secure bootloader with buttonless app code, works fine on nrfconnect. Please guide.

RE: BLE DFU fails after a certain time

bscdb — Thu, 22 Aug 2019 15:22:13 GMT

Thanks! I'll capture the sniffer trace & post it here in some time.

I dont know but the whole DFU process should be completed within 90 sec. If I send 20 bytes at a time then it takes a long time & the BLE device stops giving responses to the CRC commands. But if I make it 244 bytes at a time, then responses are received at every step.

Please tell me where can I find the stock bootloader example? I was using secure bootloader example. I just modified it to increase the size to 244.

Master is sending the init & firmware files to the nrf52 & in the RTT logs I see nrf52 accepting that data. But for the last execute command I get a wrong response.

RE: BLE DFU fails after a certain time

Hung Bui — Thu, 22 Aug 2019 15:10:36 GMT

Hi Sonal,

We do have a timer to reset the bootloader if there is no activity. NRF_BL_DFU_INACTIVITY_TIMEOUT_MS = 120 seconds. But it won't be triggered if you are receiving image.

Did you modify the bootloader ? Do you see the same issue with the stock bootloader example ?

Could you capture a sniffer trace ? What do you see on the master side when you do DFU ?

I can see in the log you already have the MTU = 244 bytes.