<?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>build and run secure_bootloader example from SDK 15.3.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/53257/build-and-run-secure_bootloader-example-from-sdk-15-3-0</link><description>Hello, 
 I&amp;#39;m trying to build and run &amp;#39;secure_bootloader/pca10040_ble_debug/armgcc/&amp;#39; example and it seams that it stops with some hard fault: 
 Remote debugging using localhost:2331 
 0xfffffffe in ?? () 
 (gdb) continue 
 Continuing. 
 Program received</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 15 Oct 2019 13:37:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/53257/build-and-run-secure_bootloader-example-from-sdk-15-3-0" /><item><title>RE: build and run secure_bootloader example from SDK 15.3.0</title><link>https://devzone.nordicsemi.com/thread/215106?ContentTypeID=1</link><pubDate>Tue, 15 Oct 2019 13:37:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:903e958c-812b-4cab-8c01-11e80cb0b343</guid><dc:creator>Wujas Dongiel</dc:creator><description>&lt;p&gt;Yes, after that I can see DfuTarg running.&lt;/p&gt;
&lt;p&gt;Thank You&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: build and run secure_bootloader example from SDK 15.3.0</title><link>https://devzone.nordicsemi.com/thread/215099?ContentTypeID=1</link><pubDate>Tue, 15 Oct 2019 13:28:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5858df9c-b352-4417-bb7b-7de26acbee5d</guid><dc:creator>Wujas Dongiel</dc:creator><description>&lt;p&gt;My output is:&lt;/p&gt;
&lt;p&gt;$ nrfjprog --memrd 0xff8&lt;br /&gt;0x00000FF8: 00072000 |. ..|&lt;/p&gt;
&lt;p&gt;So it seams ok.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: build and run secure_bootloader example from SDK 15.3.0</title><link>https://devzone.nordicsemi.com/thread/215098?ContentTypeID=1</link><pubDate>Tue, 15 Oct 2019 13:23:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:22489b64-df30-4b1d-982b-43f516d72a50</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Your hex file runs fine on my DK. Maybe the BL start address is not set. Try to read out the bootloader start address which is stored inside the MBR:&lt;/p&gt;
&lt;p&gt;&amp;gt; nrfjprog --memrd 0xff8 // should return 0x72000&lt;/p&gt;
&lt;p&gt;Edit: both flash targets are using the --sectorease option. This will cause the start address to be erased when you run both. Try&amp;nbsp;&lt;em&gt;make flash_softdevice &amp;amp;&amp;amp; make flash&amp;nbsp;&lt;/em&gt;the configuration below.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;# Flash the program
flash: default
	@echo Flashing: $(OUTPUT_DIRECTORY)/nrf52832_xxaa_s132.hex
	nrfjprog -f nrf52 --program $(OUTPUT_DIRECTORY)/nrf52832_xxaa_s132.hex 
	nrfjprog -f nrf52 --reset

# Flash softdevice
flash_softdevice:
	@echo Flashing: s132_nrf52_6.1.1_softdevice.hex
	nrfjprog -f nrf52 --program $(SDK_ROOT)/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex --chiperase
	nrfjprog -f nrf52 --reset&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: build and run secure_bootloader example from SDK 15.3.0</title><link>https://devzone.nordicsemi.com/thread/215093?ContentTypeID=1</link><pubDate>Tue, 15 Oct 2019 13:15:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f51a323b-7d43-4d9e-b1b2-d09824d9404b</guid><dc:creator>Wujas Dongiel</dc:creator><description>&lt;p&gt;Yes, I have done that as well&lt;/p&gt;
&lt;p&gt;And before any building I&amp;#39;ve followed instruction regarding keys generation from here:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/getting-started-with-nordics-secure-dfu-bootloader"&gt;devzone.nordicsemi.com/.../getting-started-with-nordics-secure-dfu-bootloader&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: build and run secure_bootloader example from SDK 15.3.0</title><link>https://devzone.nordicsemi.com/thread/215082?ContentTypeID=1</link><pubDate>Tue, 15 Oct 2019 12:46:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd07a205-e28f-40e0-8ab0-b7112377296d</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Did you remember to flash the Softdevice as well? You can use the flash_softdevice target for that: &lt;em&gt;make flash_softdevice &amp;amp;&amp;amp; make flash&lt;/em&gt;. The pre-compiled hex files have been merged with the Softdevice.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>