<?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>unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/29937/unable-to-download-larger-bootloader</link><description>Hello, 
 Is there any DFU package that can be created that would enable downloading a larger bootloader? In this case, we have the non-debug bootloader loaded and want to switch to the debug version of the bootloader via a DFU download. These are &amp;quot;sealed</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 16 Feb 2018 22:57:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/29937/unable-to-download-larger-bootloader" /><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/121141?ContentTypeID=1</link><pubDate>Fri, 16 Feb 2018 22:57:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:83ec9cd9-d047-402a-a4f7-6b78ed56385a</guid><dc:creator>Allen</dc:creator><description>&lt;p&gt;The theory about the UICR changing when entering NRFgo is incorrect. There is no difference. The only solution (kludge) that I have found is to assert reset about 4 times after the programming is completed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/119822?ContentTypeID=1</link><pubDate>Mon, 05 Feb 2018 18:30:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef504c85-6a07-4851-96fc-b804b567ed7f</guid><dc:creator>Allen</dc:creator><description>&lt;p&gt;This procedure will only be run during manufacturing. They will not be sealed at this time.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/119821?ContentTypeID=1</link><pubDate>Mon, 05 Feb 2018 18:29:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9340de85-346d-4720-8942-b52f7dce19db</guid><dc:creator>Allen</dc:creator><description>&lt;p&gt;Yes, the run command did not fix the problem. Looking at my previous post, it looks like I had tried that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/119687?ContentTypeID=1</link><pubDate>Mon, 05 Feb 2018 09:22:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:577370d3-8c65-4f8d-a9b0-59bc202ff446</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/members/ajc"&gt;ajc&lt;/a&gt;Did you try running the command that Turbo J mentioned in the comment?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/119625?ContentTypeID=1</link><pubDate>Sat, 03 Feb 2018 14:18:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2c1c285-c108-4671-ac20-f343d62108ea</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;How do you intend to read the debugging data from your &amp;quot;sealed&amp;quot; units?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/119624?ContentTypeID=1</link><pubDate>Sat, 03 Feb 2018 14:17:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:00a090c8-0049-4925-85f6-5c8f4c9f7861</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;I am missing a `nrfjprog.exe --family NRF52 --run` at the end of the sequence. Looks like you just kept the MCU in reset.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/119597?ContentTypeID=1</link><pubDate>Fri, 02 Feb 2018 21:37:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:52625497-db53-4fa2-881d-449cc40c19ae</guid><dc:creator>Allen</dc:creator><description>&lt;p&gt;You must be using a different version of &amp;quot;NRFgo Studio&amp;quot;. I am using version 1.21.2.10.&lt;/p&gt;
&lt;p&gt;Yes, the JLink ID is returned when you run &amp;quot;nrfjproj -i&amp;quot;&lt;/p&gt;
&lt;p&gt;Attached is a file which contains all the commands executed to erase, reprogram and hopefully bring the process back to life. The processor does not boot after the reload. However going into &amp;quot;NRFgo Studio&amp;quot; as previously described does cause the processor to boot and run the application. The application must be doing something more than just reading the flash.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/download_5F00_notes.txt"&gt;devzone.nordicsemi.com/.../download_5F00_notes.txt&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/119496?ContentTypeID=1</link><pubDate>Fri, 02 Feb 2018 10:10:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf39edea-0271-4ec9-96cf-162062fc7877</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Can you see your device in Windows File Explorer as a JLINK external disk after you run your eraseall script? What happens when you type nrfjrpog -i in a windows command window? Can you see the Segger ID of your device?&amp;nbsp;I am slightly unsure what exactly happens when you press nrf5x Programming because I am not able to click it myself. But when I click the Segger ID under &amp;quot;nrf52 development boards&amp;quot;, I am&amp;nbsp; sure the device flash is read, as you can see the different regions (application, softdevice, bootloader) in the graphic in the middle. Something similar like this can be done by using &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.tools/dita/tools/nrf5x_command_line_tools/nrf5x_nrfjprogexe.html?cp=5_1_3" rel="noopener noreferrer" target="_blank"&gt;nrfjprog commands&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/119062?ContentTypeID=1</link><pubDate>Tue, 30 Jan 2018 16:35:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7959f4ef-e836-49ff-8455-cd573bcc631b</guid><dc:creator>Allen</dc:creator><description>&lt;p&gt;Speaking of updating the UICR, there seems to be some magic there I am missing when reflashing the entire chip. I have a script that does an eraseall, then reloads all the software components. When the script completes it will not boot. If I then open NRFgo and select &amp;quot;nRF5x Programming&amp;quot; it suddenly comes to life. What is happening and how can I incorporate that in a script? I have a feeling it has something to do with the UICR registers.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to download larger bootloader</title><link>https://devzone.nordicsemi.com/thread/119061?ContentTypeID=1</link><pubDate>Tue, 30 Jan 2018 10:14:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8c77d9d-3eaa-4fa1-b27a-6fd142762db3</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Unfortunately not. Although it is possible to change the UICR value of the bootloader start address (see the &lt;code&gt;NRF_UICR_BOOTLOADER_START_ADDRESS&lt;/code&gt; macro in &lt;code&gt;nrf_bootloader_info.h&lt;/code&gt; &amp;amp; &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v14.2.0%2Fgroup__sdk__bootloader__info.html&amp;amp;anchor=ga2bf97cf1e3069ab5cbb861a749a206d3"&gt;this link&lt;/a&gt;), this is not advisable because if you make a mistake, you could brick the whole device. From talking with other colleagues at work, it seems this process is very tricky &amp;amp; complicated. Therefore, there is a high chance that you could brick the device. I would recommend debugging via a cabled connection if that is a possibility (depending on how &amp;quot;sealed&amp;quot; the devices are).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>