RE: DFU stuck at 'Sending Enter Bootloader (Op Code = 1)' on random occasions

MartinBL — Tue, 11 Sep 2018 15:12:11 GMT

Ok thanks.

I'll wait for the logs then.

RE: DFU stuck at 'Sending Enter Bootloader (Op Code = 1)' on random occasions

Jagan — Tue, 11 Sep 2018 02:28:15 GMT

Hi Martin

Thanks for getting back. It is roughly (~) 1 out of 7 times. 😃

Bootloader code is mostly Nordic provided code. Application is custom.

I will try to collect the logs and get back to you in a few days.

Thanks

Jagan

RE: DFU stuck at 'Sending Enter Bootloader (Op Code = 1)' on random occasions

MartinBL — Mon, 10 Sep 2018 11:56:54 GMT

Hi,

Do you get any logging information out of the nRF52 device?

Are you using a custom bootloader and application? Is this reproducible with the examples in the SDK?

Can you provide a sniffer log? If you have an extra Nordic dev kit to spare you can use our nRF Bluetooth Sniffer solution. You can also use the HCI snoop log from Android:

Disable Bluetooth on the phone,
Go to Settings -> (System->) Developer Options -> Enable HCI log
Turn on Bluetooth
Perform experiment
On Android 7+ (?):
1. When the bug happened, go to Settings -> (System->) Developer Options -> Take bug report
2. Check the notification and when the bug report is done, click and send the bugreport to email.
3. Open bugreport….zip and got to FS\data\misc\bluetooth\logs where the btsnoop_hci.log file is located.
4. Open it in Wireshark
On older:
1. Check btsnoop_hci.log file on sdcard, copy it to PC and open in Wireshark.

I was wondering about the 1/7 failure rate. That seems oddly specific. Is it every 7th time or just happening ~1 in 7 times?