<?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>SD+BL OTAU form SD132 ver 3.1.0 to SD112 ver 5.1.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/32758/sd-bl-otau-form-sd132-ver-3-1-0-to-sd112-ver-5-1-0</link><description>Hi, 
 During SD+BL OTAU form SD132 ver 3.1.0 to SD112 ver 5.1.0, Old bootloader copied new one using function nrf_dfu_mbr_copy_bl(uint32_t * p_src, uint32_t len); to bad address 0x79888 instead of 0x74000 proper BL address. 
 How to do OTAU from SD132</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 27 Mar 2018 07:19:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/32758/sd-bl-otau-form-sd132-ver-3-1-0-to-sd112-ver-5-1-0" /><item><title>RE: SD+BL OTAU form SD132 ver 3.1.0 to SD112 ver 5.1.0</title><link>https://devzone.nordicsemi.com/thread/126058?ContentTypeID=1</link><pubDate>Tue, 27 Mar 2018 07:19:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0032362d-4a7f-4f6c-b635-eca40fbb6f77</guid><dc:creator>chris222</dc:creator><description>&lt;p&gt;I solve problem by using module nrf_dfu_util.c from new SDK (&lt;span&gt;SD112 ver 5.1.0&lt;/span&gt;) to compile&amp;nbsp;BL SD132&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>