Hello I found example for dual bank bootloader ("examples\dfu\bootloader\pca10040\dual_bank_ble_s132"). And it works well. Do you plan also to add a SINGLE bank boot-loader example over BLE (not serial) for S132 stack?
Hello I found example for dual bank bootloader ("examples\dfu\bootloader\pca10040\dual_bank_ble_s132"). And it works well. Do you plan also to add a SINGLE bank boot-loader example over BLE (not serial) for S132 stack?
Thanks for tip but it seems to be ok: NRF_LOG_PRINTF("%d\r\n",DFU_IMAGE_MAX_SIZE_FULL);
returns 368640
and my bin has 348320. Also I would expect that if error is with size, then MCP shall not tell that problem is "timeout" but "not enough application size"
So the issue was with MCP. I can program same file by using tool nRF connect 4.3.2 on Android K. See question. BTW if you are going to upload big files and you do have enough current you can increase bootlader speed 2 times by changing file dfu_transport_ble.c
setting MIN_CONN_INTERVAL (uint16_t)(MSEC_TO_UNITS(7.5, UNIT_1_25_MS))
Hi Vit, My test here show inconsistency result that most of the time MCP worked fine but sometimes it rejected by the slave or it was timed out because the slave took to much time to erase the flash to prepare for receiving the image. I would need to do further investigation on this.
You can increase the min connection interval to 7.5 ms, but please be aware that on some phones if the phones can send 6 packets per connection interval, there could be an issue that you will have buffer overflow (if you don't use packet notification to control the speed) because data sending from BLE could be too fast to store.