<?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>Custom Bootloader</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23908/custom-bootloader</link><description>Hi all, 
 I&amp;#39;m trying to write a custom bootloader that must works in this way: 
 
 The new image to flash is received by a uBlox GPRS modem that communicates with the nRF52832 using the SPI; 
 Through SPI, I&amp;#39;m able to read the new binary file, validate</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 02 Aug 2017 13:35:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23908/custom-bootloader" /><item><title>RE: Custom Bootloader</title><link>https://devzone.nordicsemi.com/thread/94098?ContentTypeID=1</link><pubDate>Wed, 02 Aug 2017 13:35:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c0a0c4e-313d-42c4-b56c-5f58ca9a6657</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Have you tried what I suggested ? Simply call nrf_bootloader_app_start() at the beginning of the bootloader ? If you still have error when doing so,  you need to compare with the normal bootloader and check why it works there but not on yours.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom Bootloader</title><link>https://devzone.nordicsemi.com/thread/94102?ContentTypeID=1</link><pubDate>Wed, 02 Aug 2017 11:53:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b6d5f05-3929-4d56-b918-40bdf87a03b5</guid><dc:creator>mectronicsinc</dc:creator><description>&lt;p&gt;Hi. I saw the jump after nrf_bootloader_app_start() (NOTE: I DO NOT modified this function: the code I removed/changed is just the boot enter check criterion..). The execution is locked @ 0x1E088 (--&amp;gt; LDR R3, [R3, #0xC]), that is a SD code address. This occours when nrf_bootloader_app_start() calls sd_softdevice_vector_table_base_set().&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom Bootloader</title><link>https://devzone.nordicsemi.com/thread/94097?ContentTypeID=1</link><pubDate>Mon, 31 Jul 2017 14:42:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:16e6bfe4-855f-4c6b-a814-2f746ab0de0b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Do you see the PC jump to the start_addr after nrf_bootloader_app_start_impl() ?&lt;/p&gt;
&lt;p&gt;I agree with Roger, maybe you missed something important. You can test the nrf_bootloader_app_start() function by flashing the application manually using SWD, then call nrf_bootloader_app_start() in the bootloader to jump to the application.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom Bootloader</title><link>https://devzone.nordicsemi.com/thread/94101?ContentTypeID=1</link><pubDate>Sun, 30 Jul 2017 22:32:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b42e220e-9f02-40b0-b7c8-e84666a6a108</guid><dc:creator>Roger Clark</dc:creator><description>&lt;p&gt;Impossible to tell whats going wrong unless you post all your code, and I doubt anyone would have time do debug it for you.&lt;/p&gt;
&lt;p&gt;However one interesting thing you said is &amp;quot;I&amp;#39;ve cut  all the unnecessary code&amp;quot;&lt;/p&gt;
&lt;p&gt;I wonder if you cut something necessary&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom Bootloader</title><link>https://devzone.nordicsemi.com/thread/94099?ContentTypeID=1</link><pubDate>Sun, 30 Jul 2017 10:00:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a0c2dadc-ee22-4bd4-9bf4-6dddc97d4e1b</guid><dc:creator>mectronicsinc</dc:creator><description>&lt;p&gt;Hi Roger,&lt;/p&gt;
&lt;p&gt;Yes, all the steps I&amp;#39;ve described are done in the Bootloader. My starting point has been the secure DFU bootloader, I&amp;#39;ve &amp;quot;cut&amp;quot; all the unnecessary code, keeping, obviusly modified, the enter check.&lt;/p&gt;
&lt;p&gt;Yes, the main app receives a notification by the modem when there&amp;#39;s a new application and then perform a system reset. Of course, this check is done also every time the circuit is powered.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom Bootloader</title><link>https://devzone.nordicsemi.com/thread/94100?ContentTypeID=1</link><pubDate>Sat, 29 Jul 2017 22:16:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ff448e4-5985-443f-9157-ce0bea067b07</guid><dc:creator>Roger Clark</dc:creator><description>&lt;p&gt;Is the all the code you described in your post inside the bootloader?&lt;/p&gt;
&lt;p&gt;I presume you took the UART bootloader as your starting point ???&lt;/p&gt;
&lt;p&gt;So the process, is that first the application receives notification there&amp;#39;s is a new application, and it resets the system onto your custom bootloader, which loads via SPI ?.???&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>