<?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>NRF52832 DFU s132 7.2.0 to s332 7.0.1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125867/nrf52832-dfu-s132-7-2-0-to-s332-7-0-1</link><description>Hi, I am trying to migrate my device from s132 7.2.0 to s332 7.0.1, for adding ANT. I have no more access to the SWD. I know it is not tested : docs.nordicsemi.com/.../lib_bootloader_dfu_validation.html &amp;quot;Updating between different SoftDevice families</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 27 Nov 2025 14:40:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125867/nrf52832-dfu-s132-7-2-0-to-s332-7-0-1" /><item><title>RE: NRF52832 DFU s132 7.2.0 to s332 7.0.1</title><link>https://devzone.nordicsemi.com/thread/555640?ContentTypeID=1</link><pubDate>Thu, 27 Nov 2025 14:40:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a9ba929-1ab4-449f-b8cf-85a4579a8bb7</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Good to hear you found the problem! Changing the bootloader address is not possible through DFU. it can only be done when programming the device through the debug interface. One thing to note however is that both 0xFF8 and 0xFFC are populated at runtime by the bootloader during the initial boot with the UICR register values at 0x10001014 and 0x10001018. &amp;nbsp;As a result, it&amp;rsquo;s possible to reprogram the device with another bootloader at a different start address and end up with the value at 0xFF8 not being updated.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 DFU s132 7.2.0 to s332 7.0.1</title><link>https://devzone.nordicsemi.com/thread/555636?ContentTypeID=1</link><pubDate>Thu, 27 Nov 2025 14:33:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:84f79f17-54cd-4b59-9f60-5166cc837574</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;I don&amp;#39;t think its spelled out explicitly, but if you look at how the bootloader is supposed to work its very clear that you can&amp;#39;t change the address via an update - you need to flash with debugger for that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 DFU s132 7.2.0 to s332 7.0.1</title><link>https://devzone.nordicsemi.com/thread/555626?ContentTypeID=1</link><pubDate>Thu, 27 Nov 2025 13:49:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ea148757-07be-4f48-99c8-0b97bcceff43</guid><dc:creator>Salmat</dc:creator><description>&lt;p&gt;I have find why it did not work !&lt;br /&gt;&lt;br /&gt;nrfjprog --memrd 0x000FF8 --n 4&lt;br /&gt;&lt;br /&gt;showed me the MBR pointed at the wrong place for bootloader !&lt;br /&gt;Because of activating LOGs for debug, I changed the start add for the bootloader (to increase it size)&lt;br /&gt;&lt;br /&gt;So I disactivated LOGs to have the same add as the pkg for the bootloader, and it works !&lt;br /&gt;I think there is missing test to verify the bootloader has not changed of address ? It could have even if the same SDK, the same App ...&lt;/p&gt;
&lt;p&gt;Or maybe it is documented someware ?&lt;br /&gt;&lt;br /&gt;I will wait for a Nordic response regarding the bootloader address change.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 DFU s132 7.2.0 to s332 7.0.1</title><link>https://devzone.nordicsemi.com/thread/555596?ContentTypeID=1</link><pubDate>Thu, 27 Nov 2025 11:09:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ee9d7cfd-2549-4842-b5ce-68d15076b50a</guid><dc:creator>Salmat</dc:creator><description>&lt;p&gt;Yes the pkg has the 3 !&lt;br /&gt;It seems to be writing on the old app : the new SDK + bootloader&lt;br /&gt;and then copy the SDK to the&amp;nbsp;0x1000&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 DFU s132 7.2.0 to s332 7.0.1</title><link>https://devzone.nordicsemi.com/thread/555593?ContentTypeID=1</link><pubDate>Thu, 27 Nov 2025 10:40:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:260ed038-0de8-4078-917c-eeac9f2b2fa9</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Replacing SD here would also requires replacing the bootloader. Bootloader should support the combined SD+BL upgrade out-of-the-box if there is enough free flash space.&lt;/p&gt;
&lt;p&gt;You can&amp;#39;t overwrite the first sector with the MBR, hence it will only write the actual SD starting at 0x1000 address.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>