<?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>building APP with no SD but with secure bootloader</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/89488/building-app-with-no-sd-but-with-secure-bootloader</link><description>we currently have a product which use nrf52832 as processor using SD132 for BLE capability with DFU capability 
 we want to build a sister product with nrf552810 with no SD (no BLE functionality) but with DFU capability. We build the APP with flash map</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 01 Jul 2022 07:36:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/89488/building-app-with-no-sd-but-with-secure-bootloader" /><item><title>RE: building APP with no SD but with secure bootloader</title><link>https://devzone.nordicsemi.com/thread/375012?ContentTypeID=1</link><pubDate>Fri, 01 Jul 2022 07:36:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ee7c73b-0c68-4949-862f-fd91aa5ce0c6</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;1)&lt;/p&gt;
&lt;p&gt;Do your memory configuration look something like this? (for nRF52810):&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;FLASH_PH_START=0x0
FLASH_PH_SIZE=0x30000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x6000
FLASH_START=0x1000
FLASH_SIZE=0x2f000
RAM_START=0x20000008
RAM_SIZE=0x5ff8&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;nRF52832:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;FLASH_PH_START=0x0
FLASH_PH_SIZE=0x80000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x10000
FLASH_START=0x1000
FLASH_SIZE=0x7f000
RAM_START=0x20000008
RAM_SIZE=0xfff8&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;2) Check out the MBR variant of the Blinky peripheral example, and see if you can recreate the issue based on that.&lt;br /&gt;nRF5-SDK\examples\peripheral\blinky\pca10040e\mbr\ses&lt;/p&gt;
&lt;p&gt;3) To debug a hardfault, you can add the hardfault library to your project&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_hardfault.html"&gt;https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_hardfault.html&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: building APP with no SD but with secure bootloader</title><link>https://devzone.nordicsemi.com/thread/374981?ContentTypeID=1</link><pubDate>Thu, 30 Jun 2022 21:05:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93aaff1f-9dee-4ad4-ac6d-3e59c92648c0</guid><dc:creator>tnguyen</dc:creator><description>&lt;p&gt;Thanks Sigurd.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;I am using SES to build my solution.I built my own BL image and APP image separately. When I want to debug my APP, I told SES to also load MBR.hex (in softdevice folder), and BL.elf that I build earlier. Everything looks good. I can step through the code and I can see that MBR&amp;#39;s Reset Handler, the BL&amp;#39;s Reset Handler and the APP&amp;#39;s Reset Handler is getting call and I am in my APP. However after stepping through several functions, strange thing happened. In one of the function call, if I step through it using assembly then it is working fine but if I step through it using C or step over in assembly, I got a bus fault (0xa60). Note that if I reallocated the APP to start at 0 and step through using C, then I don&amp;#39;t see the same issue. What is going on ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: building APP with no SD but with secure bootloader</title><link>https://devzone.nordicsemi.com/thread/374979?ContentTypeID=1</link><pubDate>Thu, 30 Jun 2022 20:00:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9e24fc6-5c40-409a-80c2-2dfe9a8f19bc</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]Can someone explain what the MBR does (ie API, significant flash location, etc) ?&amp;nbsp;[/quote]
&lt;p&gt;&lt;span&gt;The main functionality of the MBR is to provide an interface to allow in-system updates of the application, the SoftDevice, and bootloader firmware. It&amp;#39;s located at the start of flash, and is the first thing that runs when the you power the chip. The MBR can then boot the Bootloader(if present), if not present, it will boot the Application. See these links for more info:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/sds_s112/SDS/s1xx/mbr_bootloader/mbr_bootloader.html"&gt;https://infocenter.nordicsemi.com/topic/sds_s112/SDS/s1xx/mbr_bootloader/mbr_bootloader.html&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_bootloader.html"&gt;https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_bootloader.html&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/guides/short-range-guides/b/software-development-kit/posts/getting-started-with-nordics-secure-dfu-bootloader"&gt;Getting started with Nordic&amp;#39;s Secure DFU bootloader, a step by step guide&lt;/a&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>