DFU BLE Connect and NRF Connect

RE: DFU BLE Connect and NRF Connect

Elfving — Tue, 04 Jan 2022 12:37:10 GMT

Hello again!

That sounds great! Thanks for sharing your solution here.

Best regards,

Elfving

RE: DFU BLE Connect and NRF Connect

Andreas48752 — Sun, 02 Jan 2022 19:31:35 GMT

Hello Elfving,

thank you for your reply.

I searched a little bit more and found some threads where it says that the change of the MAC address (+1) while booting in bootloader may cause connection problems on android as there will be no ble scan when starting dfu library update.

I have to verify this but I changed my android app to start a 10 second ble scan right before starting dfu update and until now connection can be made!

Andreas!

RE: DFU BLE Connect and NRF Connect

Elfving — Tue, 28 Dec 2021 15:48:10 GMT

Hello Andreas

Error code 133 is very famous for being undocumented by Android itself. It is kind of a generic GATT/GAP error, usually related to a timeout where the phone is trying to do something when it is disconnected. This error happens very rarely from Android 8.0 onwards (it sometimes may be on Samsung devices and we almost never see this on Pixels). If the phone is older or has a worse BLE implementation there is a larger chance of this occuring.

[quote user=""]What does nrf connect at startup to "heal" ble in my app?[/quote]

So my guess is that it doesn't do anything in particular to heal it. It just restarts it. Solutions to other run-ins with error code 133 includes increasing the connection retries or even increase the delay between each retry, so it would make sense that another attempt would make it work for you.

Could you tell me how often this happens per DFU attempt? And what phone are you using?

Best regards,

Elfving

RE: DFU BLE Connect and NRF Connect

Elfving — Tue, 21 Dec 2021 16:03:14 GMT

Hey Andreas!

I will have to get back to you on this. Due to the holidays you might have to expect both limited help and slower responses on DevZone.

Best regards,

Elfving