<?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>nRF51422/51822: what&amp;#39;s the detailed power-on sequence when using softdevice + BootLoader + APP</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8752/nrf51422-51822-what-s-the-detailed-power-on-sequence-when-using-softdevice-bootloader-app</link><description>I&amp;#39;m a newbie for Nordic development. 
 I just noticed that softdevice, app, and bootloader share the same CPU, RAM and Flash at the same time. This three software modules all has its own vector tables . I know that ARM CPU will run into reset vector</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 Aug 2015 11:53:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8752/nrf51422-51822-what-s-the-detailed-power-on-sequence-when-using-softdevice-bootloader-app" /><item><title>RE: nRF51422/51822: what's the detailed power-on sequence when using softdevice + BootLoader + APP</title><link>https://devzone.nordicsemi.com/thread/32091?ContentTypeID=1</link><pubDate>Mon, 17 Aug 2015 11:53:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:726e3317-9531-4798-972b-eb1f7765d8b6</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi xiaozuanzi,&lt;/p&gt;
&lt;p&gt;The MBR&amp;#39;s(comes with the softdevice) vector table will be accessed first.&lt;/p&gt;
&lt;p&gt;You can have a look at section B in &lt;a href="https://devzone.nordicsemi.com/blogs/685/common-faq-on-dfu/"&gt;this FAQ&lt;/a&gt;, to know more about the start-up sequence.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>