MCP - Firmware upload - timeout waiting for START

[vit bernatik]

Hello, I tried to do DFU using MCP 3.10.0.14 and I'm getting the error:

"Error during firmware upload. Timeout while waiting for response for START DFU"

How do I increase timeout in MCP??

It seems to happen when I try to upload bigger firmware.

[Susheel Nuguru]

I am not sure if you can increase this timeout, but have you tried with faster connection interval? how big file are you talking about?

[vit bernatik]

Thank you for tip. But I started from standard example (examples\dfu\bootloader\pca10040\dual_bank_ble_s132\arm5_no_packs\dfu_dual_bank_ble_s132_pca10040.uvprojx) and I did not touch the speed. It was set to fairly fast:

MIN_CONN_INTERVAL                    (uint16_t)(MSEC_TO_UNITS(15, UNIT_1_25_MS))           
MAX_CONN_INTERVAL                    (uint16_t)(MSEC_TO_UNITS(30, UNIT_1_25_MS))  

I tried to set 7.5 and 15. And the error is same.

Also it seems the error is before programming starts - so I assume what takes really long is erasing 360KB of Flash.. I think this is the bottle neck on FW side and it is in flash which is fixed...

[Susheel Nuguru]

can you try nRFConnect and see if this is the same case there. If so, then i will take your hex files and talk to the engineer of MCP and nRFConnect.

[vit bernatik]

I tried to upload the same zip file using nRF connect 4.3.2 on android K and it worked :). So the problem seems to be only in MCP. I looked on nRF connect v 1.0 also for PC - but I do not see the button for start DFU.

[vit bernatik]

BTW bin file has 348KB. I did modify bootloader to use dfu_single_bank.c as was advised here. With dual bank I would not be able to update so big application. My programming zip file is here.