<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/75135/can-not-reprogram-board-after-attempting-to-use-dfu</link><description>I was attempting to implement the secure bootloader example on my custom board (nrf52832) and it failed, so I have been trying to reprogram the board with our normal application using j-link and SES ver 5.42b. It fails when it attempts to flash the softdevice</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 02 Jun 2021 08:30:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/75135/can-not-reprogram-board-after-attempting-to-use-dfu" /><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/313035?ContentTypeID=1</link><pubDate>Wed, 02 Jun 2021 08:30:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fed2ad72-faee-424b-80a7-d041513eb6a0</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p lang="en-GB"&gt;Thanks a lot for the feedback, Mike! Would you mind sharing with me what the root cause was? I’m a little curious :-)&lt;/p&gt;
&lt;p lang="en-GB"&gt;Regards,&lt;/p&gt;
&lt;p lang="en-GB"&gt;Markus&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/313011?ContentTypeID=1</link><pubDate>Wed, 02 Jun 2021 06:34:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3e9f46c1-ffe5-47b7-8d07-10953a6d3a25</guid><dc:creator>BigMike</dc:creator><description>&lt;p&gt;Marcus,&lt;/p&gt;
&lt;p&gt;We can definitely close this ticket out as I figured out what was wrong with the bootloader not working&lt;/p&gt;
&lt;p&gt;Thanks for everything&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/313010?ContentTypeID=1</link><pubDate>Wed, 02 Jun 2021 06:33:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4606f89d-d5a6-44eb-a3fe-42c754e98eb4</guid><dc:creator>BigMike</dc:creator><description>&lt;p&gt;Marcus,&lt;/p&gt;
&lt;p&gt;Not sure if this will help but here is the debug output from the board during the upgrade process&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;pre&gt;debug&amp;gt; app: timer_stop (0x20005984)
 app:  nrf_dfu_ble: Configuring BLE stack.
 nrf_dfu_ble: Enabling the BLE stack.
 nrf_dfu_ble: No advertising name found
 nrf_dfu_ble: Using default advertising name
 nrf_dfu_ble: Advertising...
 nrf_dfu_ble: BLE DFU transport initialized.
 nrf_dfu_flash: Initializing nrf_fstorage_sd backend.
 nrf_dfu_validation: PB: Init packet data len: 73
 app: Enter main loop
 nrf_dfu_ble: Connected
 nrf_dfu_ble: Received BLE_GAP_EVT_CONN_PARAM_UPDATE
 nrf_dfu_ble: max_conn_interval: 12
 nrf_dfu_ble: min_conn_interval: 12
 nrf_dfu_ble: slave_latency: 0
 nrf_dfu_ble: conn_sup_timeout: 600
 nrf_dfu_ble: Received BLE_GAP_EVT_PHY_UPDATE_REQUEST.
 nrf_dfu_ble: Received BLE_GAP_EVT_PHY_UPDATE (RX:2, TX:2, status:0)
 nrf_dfu_ble: Received BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST.
 nrf_dfu_ble: Received BLE_GAP_EVT_DATA_LENGTH_UPDATE (27, max_rx_time 2120).
 nrf_dfu_ble: Received BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST (request: 293, reply: 23).
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_SELECT (command)
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_EXECUTE (command)
 nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
 nrf_dfu_settings: Backing up settings page to address 0x7E000.
 nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
 nrf_dfu_req_handler: Writing valid init command to flash.
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_ble: Set receipt notif
 nrf_dfu_req_handler: Handle NRF_DFU_OP_RECEIPT_NOTIF_SET
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_SELECT (data)
 nrf_dfu_req_handler: crc = 0x0, offset = 0x0, max_size = 0x1000
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_CREATE (data)
 nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x00026000, len=1 pages), queue usage: 0
 nrf_dfu_req_handler: Creating object with size: 4096. Offset: 0x00000000, CRC: 0x00000000
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_flash: Flash erase success: addr=0x00026000, pending 0
 nrf_dfu_ble: Buffer 0x2000675C acquired, len 20 (20)
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_ble: Buffer 0x20006770 acquired, len 20 (20)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x00026000, src=0x2000675C, len=20 bytes), queue usage: 0
 nrf_dfu_ble: Buffer 0x20006784 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006798 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006798 acquired, len 20 (20)
=0x2000675C, len=20 bytes), queue usage: 0
 nrf_dfu_ble: Buffer 0x20006784 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006798 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067AC acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067C0 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067D4 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067E8 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067FC acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006810 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006824 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006838 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006784 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006798 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067AC acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067C0 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067D4 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067E8 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x200067FC acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006810 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006824 acquired, len 20 (20)
 nrf_dfu_ble: Buffer 0x20006838 acquired, len 20 (20)
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: Flash write success: addr=0x00026000, pending 0
 nrf_dfu_ble: Freeing buffer 0x2000675C
 nrf_dfu_flash: Flash write success: addr=0x00026000, pending 0
 nrf_dfu_ble: Freeing buffer 0x2000675C
 nrf_dfu_flash: nrf_fstorage_write(addr=0x00026014, src=0x20006770, len=20 bytes), queue usage: 0
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x00026028, src=0x20006784, len=20 bytes), queue usage: 1
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x0002603C, src=0x20006798, len=20 bytes), queue usage: 2
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x00026050, src=0x200067AC, len=20 bytes), queue usage: 3
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x00026064, src=0x200067C0, len=20 bytes), queue usage: 4
 nrf_dfu_flash: nrf_fstorage_write() failed with error 0x4.
 nrf_dfu_ble: Freeing buffer 0x200067C0
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x00026064, src=0x200067D4, len=20 bytes), queue usage: 4
 nrf_dfu_flash: nrf_fstorage_write() failed with error 0x4.
 nrf_dfu_ble: Freeing buffer 0x200067D4
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: Flash write success: addr=0x00026014, pending 3
 nrf_dfu_ble: Freeing buffer 0x20006770
 nrf_dfu_flash: Flash write success: addr=0x00026028, pending 2
 nrf_dfu_ble: Freeing buffer 0x20006784
 nrf_dfu_flash: Flash write success: addr=0x0002603C, pending 1
 nrf_dfu_ble: Freeing buffer 0x20006798
 nrf_dfu_ble: Freeing buffer 0x20006798
=0x0002603C, pen nrf_dfu_flash: Flash write success: addr=0x00026050, pending 0
 nrf_dfu_ble: Freeing buffer 0x200067AC
 nrf_dfu_flash: Flash write success: addr=0x00026014, pending 3
 nrf_dfu_ble: Freeing buffer 0x20006770
 nrf_dfu_flash: Flash write success: addr=0x00026028, pending 2
 nrf_dfu_ble: Freeing buffer 0x20006784
 nrf_dfu_flash: Flash write success: addr=0x0002603C, pending 1
 nrf_dfu_ble: Freeing buffer 0x20006798
 nrf_dfu_flash: Flash write success: addr=0x00026050, pending 0
 nrf_dfu_ble: Freeing buffer 0x200067AC
 nrf_dfu_flash: nrf_fstorage_write(addr=0x00026064, src=0x200067E8, len=20 bytes), queue usage: 0
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x00026078, src=0x200067FC, len=20 bytes), queue usage: 1
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x0002608C, src=0x20006810, len=20 bytes), queue usage: 2
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x000260A0, src=0x20006824, len=20 bytes), queue usage: 3
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
 nrf_dfu_flash: nrf_fstorage_write(addr=0x000260B4, src=0x20006838, len=20 bytes), queue usage: 4
 nrf_dfu_flash: nrf_fstorage_write() failed with error 0x4.
 nrf_dfu_ble: Freeing buffer 0x20006838
 nrf_dfu_req_handler: Request handling complete. Result: 0x1
 nrf_dfu_flash: Flash write success: addr=0x00026064, pending 3
 nrf_dfu_ble: Freeing buffer 0x200067E8
 nrf_dfu_flash: Flash write success: addr=0x00026078, pending 2
 nrf_dfu_ble: Freeing buffer 0x200067FC
 nrf_dfu_flash: Flash write success: addr=0x0002608C, pending 1
 nrf_dfu_ble: Freeing buffer 0x20006810
 nrf_dfu_flash: Flash write success: addr=0x000260A0, pending 0
 nrf_dfu_ble: Freeing buffer 0x20006824
 app: timer_stop (0x20005984)
 app: timer_fire (0x20005984)
 app: Inactivity timeout.
 nrf_dfu_ble: Enabling SoftDevice.
 nrf_dfu_ble: Configuring BLE stack.
 nrf_dfu_ble: Enabling the BLE stack.
 nrf_dfu_ble: No advertising name found
 nrf_dfu_ble: Using default advertising name
 nrf_dfu_ble: Advertising...
 nrf_dfu_ble: BLE DFU transport initialized.
 nrf_dfu_flash: Initializing nrf_fstorage_sd backend.
 nrf_dfu_validation: PB: Init packet data len: 73
 app: Enter main loop
 app: timer_stop (0x20005984)
 nrf_dfu_ble: BLE DFU transport initialized.
 nrf_dfu_flash: Initializing nrf_fstorage_sd backend.
 nrf_dfu_validation: PB: Init packet data len: 73
 app: Enter main loop&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/312984?ContentTypeID=1</link><pubDate>Tue, 01 Jun 2021 22:01:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e30d0a6a-349c-48bb-a5d4-1df6c825027f</guid><dc:creator>BigMike</dc:creator><description>&lt;p&gt;Hi Marcus,&lt;/p&gt;
&lt;p&gt;Yes the new link works but the still the same problem... anyway I am going to close this ticket out and set this board aside and just chalk it up as a anomaly. I&amp;#39;ve grabbed another board and I am able to successfully program the secure bootloader, though I modified by using my own public_key.c. But when I use the nRFConnect App to program the Application, i get an error on the nRFConnect saying &amp;quot;240 bytes were sent but only 200 bytes were received&amp;quot; and it seems like it quits. Should i open another ticket or still use this one.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/311989?ContentTypeID=1</link><pubDate>Thu, 27 May 2021 08:17:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:675dad02-b59a-4dbd-a0d6-ce2cbd4e91b6</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p lang="en-GB"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;Hello again Mike,&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p lang="en-GB"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;it should work now! Can you confirm?&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p lang="en-GB"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;Regards,&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p lang="en-GB"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;Markus&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/311850?ContentTypeID=1</link><pubDate>Wed, 26 May 2021 14:18:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c192d6a0-353b-4eb1-b573-077d395e8d2a</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;&lt;span lang="en-GB"&gt;Hello Mike,&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;&lt;span lang="en-GB"&gt;you are right, the link does not work. I’m sorry for that. I will check this internally and come back to you!&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;&lt;span lang="en-GB"&gt;Regards,&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;&lt;span lang="en-GB"&gt;Markus&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/311837?ContentTypeID=1</link><pubDate>Wed, 26 May 2021 13:49:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aef630f6-a8ca-439f-9d81-a6a0bcaacc10</guid><dc:creator>BigMike</dc:creator><description>&lt;p&gt;Hi Markus,&lt;/p&gt;
&lt;p&gt;It seems that the link for the latest tools for MacOS is broken, I tried several times and I get a 404 error&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/311679?ContentTypeID=1</link><pubDate>Wed, 26 May 2021 08:28:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:476d6db1-f429-4c3c-b061-a31c474c832c</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p lang="en-GB"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;Hello Mike,&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p lang="en-GB"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;could you please upgrade your &lt;a href="https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download#infotabs"&gt;command line tools&lt;/a&gt; to the latest version 10.12.1 and try to erase the flash one more time? Does that make any difference?&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p lang="en-GB"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;Regards,&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p lang="en-GB"&gt;&lt;span&gt;&lt;span&gt;&lt;span&gt;Markus&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/311365?ContentTypeID=1</link><pubDate>Tue, 25 May 2021 08:55:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bf894c07-2c16-459c-9763-35ea17202665</guid><dc:creator>BigMike</dc:creator><description>&lt;p&gt;Hello Marcus,&lt;/p&gt;
&lt;p&gt;Sorry I didn&amp;#39;t see your response till today...&lt;/p&gt;
&lt;p&gt;1. How old is the board - My custom board is fairly new (less than 3 weeks old)&lt;/p&gt;
&lt;p&gt;2. Does my application perform many read/writes operations normally - No we don&amp;#39;t store much data and most of the reading or writing is uploading new code for debugging&lt;/p&gt;
&lt;p&gt;3. What version of nrfjprog -&amp;nbsp;&amp;nbsp;&lt;span class="s1"&gt;nrfjprog version: 10.3.0&amp;nbsp;&lt;/span&gt;&lt;span class="s1"&gt;JLinkARM.dll version: 6.70g&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/310930?ContentTypeID=1</link><pubDate>Fri, 21 May 2021 07:43:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9abe944b-a9c9-4da5-934c-1be6f7f2d6b0</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p lang="en-GB"&gt;Hello Mike,&lt;/p&gt;
&lt;p lang="en-GB"&gt;normally, an --eraseall / --recover should erase all memory areas. What kind of error do you get during flashing of the SoftDevice area?&lt;/p&gt;
&lt;p lang="en-GB"&gt;How old is the board you are using? Does your applications perform many read/write operations normally?&lt;/p&gt;
&lt;p lang="en-GB"&gt;What version of nrfjprog are you using?&lt;/p&gt;
&lt;p lang="en-GB"&gt;Regards,&lt;/p&gt;
&lt;p lang="en-GB"&gt;Markus&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/310787?ContentTypeID=1</link><pubDate>Thu, 20 May 2021 13:42:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4db2f9f3-0023-4391-8282-3b53beeedc03</guid><dc:creator>BigMike</dc:creator><description>&lt;p&gt;Hello Marcus,&lt;/p&gt;
&lt;p&gt;I have tried your suggestion but still no luck... but let me share some more insight. It seems that I am able to reprogram the main section of the flash where the application code resides but I get an error when I try to flash the softdevice area even though I erase all the chip&amp;#39;s flash area. I have tried using nrfjprog and SES IDe commands. Any suggestions&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/310139?ContentTypeID=1</link><pubDate>Tue, 18 May 2021 12:10:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d6e972a6-05bb-404a-973f-3cba4ef4774d</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p lang="en-GB"&gt;Hello Mike,&lt;/p&gt;
&lt;p lang="en-GB"&gt;again, my apologies for the late reply.&lt;/p&gt;
&lt;p lang="en-GB"&gt;I’m actually a little surprised that you are not able to reprogram your board, because that should work anyway.&lt;/p&gt;
&lt;p lang="en-GB"&gt;One thing you could try though is to reduce the clock speed and run the recover command again.&lt;/p&gt;
&lt;p lang="en-GB"&gt;&lt;pre class="ui-code" data-mode="text"&gt; -c  --clockspeed &amp;lt;speed&amp;gt;    Sets the debugger SWD clock speed in kHz                                                                     │
                             resolution for the operation. The valid clockspeed                                                           │
                             arguments go from 125 kHz to 50000 kHz. If given                                                             │
                             clockspeed is above the maxiumum clockspeed                                                                  │
                             supported by the emulator, its maximum will be                                                               │
                             used instead. If --clockspeed option is not given,                                                           │
                             the default is taken from nrfjprog.ini. Must be                                                              │
                             combined with another command.  &lt;/pre&gt;&lt;/p&gt;
&lt;p lang="en-GB"&gt;I hope this will help you!&lt;/p&gt;
&lt;p lang="en-GB"&gt;Regards,&lt;/p&gt;
&lt;p lang="en-GB"&gt;Markus&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can not reprogram board after attempting to use DFU</title><link>https://devzone.nordicsemi.com/thread/309828?ContentTypeID=1</link><pubDate>Fri, 14 May 2021 14:25:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3c472b50-b240-48dd-8ffc-e906f9f25e5d</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p&gt;Hello Mike,&lt;/p&gt;
&lt;p&gt;Due to public holidays in Norway, we are short on staff at the moment. I might need some time to analyse your case, but I will come back to you as soon as possible.&lt;/p&gt;
&lt;p&gt;I apologise for any inconvenience caused.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Markus&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>