philips77
commented
3 months ago Hello, I can see that the disconnection happens after sending the image size:
A 16:36:33.281 [DFU] Firmware image size sent (0b, 0b, 58628b)
E 16:36:38.142 [DFU] Device has disconnectedThere's a 5 second delay between these two messages, suggesting that the device started erasing memory and does not reply when doing so. The connection parameters may have a Supervision Timeout set to 5 seconds, so after that time the phone disconnects. I suggest requesting a different supervision timeout from the device side before DFU or checking why the device does not reply. Some phones request 20 second timeout instead of 5, perhaps that's why it works on other phones. Check the time that it takes for the device to reply to firmware image size sent command on phones that are working.
amineKhik
gte1
Where do you suspect the issue?
Issue related to Android version or specific device
Version
2.4.0
Describe the issue
I am using DFU Bootloader v8.1.0 for my application and trying to perform a DFU using the DFU app version 2.4.0. I am using a Redmi 9C running Android 10 for the process. The issue is that whenever I start the DFU, it always returns an error during the initialization. The logs can be found below. I tried debugging the bootloader during the process and discovered that the issue stems from the
pstorage_callback_handlerfunction, specifically in the case where the callback code isPSTORAGE_CLEAR_OP_CODE. In this case,m_data_pkt_cbreturns the error codeNRF_ERROR_TIMEOUT. However, when I tried with another phone, a Pixel 5, the process worked without any issues. This suggests that the issue may be reproducible on specific phones. Can anyone help me solve this issue? Note: I tried increasing the BLE connection parameters, but this did not resolve the problem.Relevant log output