https://devzone.nordicsemi.com/f/nordic-q-a/11645/dfu-on-nrf51822-error-during-firmware-upload-with-mcp-3-10Dear Sirs, We compile the bootloader in dfu folder, sdk 10.0.0, with IAR, and download on 51822 QFAA chip. When trying the DFU function with MCP tool with version 3.10.0.14, we always receive the error &quot;Error during firmware upload. Disconnected fromen-USTelligent Community 13Tue, 16 Feb 2016 17:23:35 GMThttps://devzone.nordicsemi.com/thread/44008?ContentTypeID=1Tue, 16 Feb 2016 17:23:35 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2d034576-3474-493b-a2a2-06f6d0484ee0phate<p>Hi Einar, thanks for reply. My configuration in bootloader is RAM: 0x20002c00 - 0x20003f7f/ ROM: 0x3c000 - 0x3fbff and in application is RAM: 0x20002000 - 0x20003fff/ ROM: 0x18000 - 0x3bfff (<a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk51.v10.0.0/bledfu_memory.html?cp=4_0_1_4_3_1_3)">infocenter.nordicsemi.com/.../bledfu_memory.html</a> By the way, I generate the zip package with this command: C:\Program Files (x86)\Nordic Semiconductor\Master Control Panel\3.10.0.14\nrf&gt;nrfutil.exe dfu genpkg --application application.hex --application-version 0xffffffff --dev-type 0xffff --dev-revision 0xffff --sd-req 0xffff application.zip. Is it possible that the zip package is wrong? Thank you.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/44007?ContentTypeID=1Mon, 15 Feb 2016 13:04:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:91b85384-88e2-45ab-a0b0-414ac6cc751bEinar Thorsrud<p>Have you configured the RAM areas correctly in the bootloader as well at the application?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/44006?ContentTypeID=1Fri, 12 Feb 2016 04:01:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fa2c1edc-8623-47f1-a396-501a3db5b353phate<p>Hi Einar, no. I try to upload with both MCP and nrf toolbox in iOS, but all failed to upload. The notification dialog always shown fail when 0%. I also try to zip the hex file with this link: <a href="https://github.com/NordicSemiconductor/nRF-Master-Control-Panel/tree/master/init%20packet%20handling">github.com/.../init packet handling</a>, but still failed. Thank you.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/44005?ContentTypeID=1Thu, 11 Feb 2016 09:51:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:503305c6-8cb4-4f58-9b54-17ed60b2a0d2Einar Thorsrud<p>Have you had any progress? If not, in what way is it failing when you attempt to upload firmware?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/44004?ContentTypeID=1Tue, 02 Feb 2016 12:35:29 GMT137ad170-7792-4731-bb38-c0d22fbe4515:07939ee8-f09c-43ec-9def-68a64cac0db1phate<p>Thanks for reply, I had modified the default setting from SDK. My setting is RAM: 0x20002c00 - 0x20003f7f/ ROM: 0x3c000 - 0x3fbff. But it still fail to uploading firmware.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/44003?ContentTypeID=1Tue, 02 Feb 2016 11:51:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2702ddd4-2bc3-4373-b721-ef7edab1b823Einar Thorsrud<p>The nRF51 DFU examples in the SDK assume a device that has 32 kB of RAM, but the QFAA only has 16 kB. This is no problem as long as you adapt the linker settings accordingly. Have you done that? <a href="https://devzone.nordicsemi.com/question/56218/how-can-i-compile-dfu-bootloader-examples-for-pca10031other-16k-ram-boardsdongles/?answer=56281#post-id-56281">This post</a> describes it for Keil and GCC, but it should be the same for IAR.</p><div style="clear:both;"></div>