<?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>Update problem with nrf toolbox</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/73625/update-problem-with-nrf-toolbox</link><description>Hi, 
 I&amp;#39;m working with the dfu example. the sdk I use is 15.3.0 and softdevice is s132. I am creating the zip package without any problems. 
 I use the following commands when creating the zip package: 
 N5ftrrfutil pkg generate --hw-version 52 --sd-req</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 07 Apr 2021 07:39:03 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/73625/update-problem-with-nrf-toolbox" /><item><title>RE: Update problem with nrf toolbox</title><link>https://devzone.nordicsemi.com/thread/303368?ContentTypeID=1</link><pubDate>Wed, 07 Apr 2021 07:39:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b8dbd656-02af-4d16-bde8-00d35eaa45cc</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;As you have noticed, the bootloader hex needs to be programmed last. This is unfortunately a known limitation with the SDK 15.3.0 bootloader. In this release we started to use the MBR section (address 0x0 - 0x1000) to hold the bootloader start address and MBR param page address, and this made it easy to inadvertently erase MBR when programming the bootloader image (because the bootloader.hex overlap with the softdevice&amp;#39;s address range)&lt;/p&gt;
&lt;p&gt;Related thread: &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/61707/unable-to-enter-bootloader-after-flashing-new-firmware-with-segger-embedded-studio/251525#251525"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/61707/unable-to-enter-bootloader-after-flashing-new-firmware-with-segger-embedded-studio/251525#251525&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Update problem with nrf toolbox</title><link>https://devzone.nordicsemi.com/thread/303238?ContentTypeID=1</link><pubDate>Tue, 06 Apr 2021 14:50:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4b39f5f7-8ec4-4f2b-8f99-e2dc7b52ac04</guid><dc:creator>cemalb</dc:creator><description>&lt;p&gt;i think the problem is caused by the way it loads softdevice and bootloader hex files.&amp;nbsp;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/qqq.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;At first, I was pressing the &amp;quot;add hex file&amp;quot; button on the right and writing the softdevice and bootloader files at the same time.this was causing the problem.&lt;/p&gt;
&lt;p&gt;but now I add and write the softdevice hex file with &amp;quot;add hex file&amp;quot;. Then I press &amp;quot;clear files&amp;quot;, press &amp;quot;add hex file&amp;quot; again, add the bootloader hex file and write. After doing this, there is no problem during the upload process with the mobile application.&lt;/p&gt;
&lt;p&gt;Does anyone know what the difference is between these two situations? Can anyone confirm what I did second is more correct?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Update problem with nrf toolbox</title><link>https://devzone.nordicsemi.com/thread/303118?ContentTypeID=1</link><pubDate>Tue, 06 Apr 2021 11:50:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d77c047-e30a-43d1-9838-9df25c836a09</guid><dc:creator>cemalb</dc:creator><description>&lt;p&gt;Isn&amp;#39;t there any abnormality in these images?&lt;/p&gt;
&lt;p&gt;I install the softdevice software firstly. after installation, the left part shows in blue.:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/3005.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I want to install the bootolader software later. but the bootloader occupies a place in the softdevice area.:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/7416.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;and after the bootloader software is loaded, the softdevice part turns green. and appears to be the application region.:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/2273.PNG" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>