<?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>Zephyr nRF52832 FLASH overflow when MCUBOOT enable</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/89290/zephyr-nrf52832-flash-overflow-when-mcuboot-enable</link><description>Hello everyone, 
 
 I&amp;#39;m developing an application on the nRF52832 development kit. It is nrf52dk_nrf52832(PCA10040). It is based on Zephyr. 
 Zephyr version: 3.0.99 Zephyr SDK version: zephyr-sdk-0.13.2 This project is based on the example of Bluetooth</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 28 Jun 2022 14:46:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/89290/zephyr-nrf52832-flash-overflow-when-mcuboot-enable" /><item><title>RE: Zephyr nRF52832 FLASH overflow when MCUBOOT enable</title><link>https://devzone.nordicsemi.com/thread/374590?ContentTypeID=1</link><pubDate>Tue, 28 Jun 2022 14:46:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:75fb3fea-d124-47ca-a1c8-50f7114b35e9</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;Are you uising Zephyr upstream or the nRF Connect SDK? I would recommend you to use the latter. If you use Zephyr upstream, you might get better help if you ask the Zephyr community, see&amp;nbsp;&lt;a href="https://www.zephyrproject.org/developer-resources/#:~:text=Members%20contribute%20and,Technical%20Steering%20Committee"&gt;https://www.zephyrproject.org/developer-resources/#:~:text=Members%20contribute%20and,Technical%20Steering%20Committee&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zephyr nRF52832 FLASH overflow when MCUBOOT enable</title><link>https://devzone.nordicsemi.com/thread/374396?ContentTypeID=1</link><pubDate>Mon, 27 Jun 2022 16:37:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8bc82da-f729-4092-8e4a-8396bf4b067b</guid><dc:creator>Neel Oza</dc:creator><description>&lt;p&gt;Hi Simon,&lt;/p&gt;
&lt;p&gt;Thank you for you quick response. We are able to reduce the size of mcuboot and application size to the minimum configurations as you have suggested.&lt;/p&gt;
&lt;p&gt;We are facing an issue with the rollover image when DFU is completed. I think it is related to the DTS flash partition. Here is the flash partition table with a 30 KB mcuboot partition.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;&amp;amp;flash0 {

partitions {
compatible = &amp;quot;fixed-partitions&amp;quot;;
#address-cells = &amp;lt;1&amp;gt;;
#size-cells = &amp;lt;1&amp;gt;;

boot_partition: partition@0 {
label = &amp;quot;mcuboot&amp;quot;;
reg = &amp;lt;0x00000000 0x7800&amp;gt;;
};
slot0_partition: partition@7800 {
label = &amp;quot;image-0&amp;quot;;
reg = &amp;lt;0x00007800 0x37000&amp;gt;;
};
slot1_partition: partition@3e800 {
label = &amp;quot;image-1&amp;quot;;
reg = &amp;lt;0x0003e800 0x37000&amp;gt;;
};
scratch_partition: partition@75800 {
label = &amp;quot;image-scratch&amp;quot;;
reg = &amp;lt;0x00070000 0x8800&amp;gt;;
};
storage_partition: partition@7e000 {
label = &amp;quot;storage&amp;quot;;
reg = &amp;lt;0x0007e000 0x00002000&amp;gt;;
};
};
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Que-1: Does mcuboot partition have any minimum flash size requirement?&lt;/p&gt;
&lt;p&gt;Que-2: What is the bare minimum flash size for each flash partition? When we tried to reduce the &amp;quot;storage&amp;quot; partition, the Bluetooth stack failed to boot in initialization.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zephyr nRF52832 FLASH overflow when MCUBOOT enable</title><link>https://devzone.nordicsemi.com/thread/374025?ContentTypeID=1</link><pubDate>Thu, 23 Jun 2022 18:22:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:54f5f02f-4f5d-4383-9dc7-ce3b9a380d18</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;What nRF Connect SDK version are you using?&lt;/p&gt;
&lt;p&gt;I think the problem is&amp;nbsp;similar to this issue:&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/89237/nrf52840-dfu-with-external-flash/373673"&gt;RE: nrf52840 DFU with external flash&lt;/a&gt;&amp;nbsp;(three partitions are created, primary slot, secondary slot and mcuboot and they doesn&amp;#39;t all fit into your flash). However, in your case you only have 512 kB available. Try reducing the size of your application. The file&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/v2.0.0/samples/bluetooth/peripheral_uart/prj_minimal.conf"&gt; nrf/samples/belutooth/peripheral_uart/prj_minial.conf&lt;/a&gt;&amp;nbsp;shows you how to reduce the memory usage in a Bluetooth project.&lt;/p&gt;
&lt;p&gt;Also try to to reduce the size of mcuboot by using the file&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-mcuboot/blob/v1.9.99-ncs1/boot/zephyr/prj_minimal.conf"&gt;bootloader/mcuboot/boot/zephyr/prj_minimal.conf&lt;/a&gt;&amp;nbsp;and following the advice given in this ticket:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/85319/how-to-resize-mcuboot-partition-in-zephyr"&gt;How to resize MCUBoot partition in zephyr?&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If you&amp;#39;re not able to reduce the partitions enough to fit into flash, you could use single slot dfu update with serial recovery. If you would like to use two slot for the DFU update, you could put the secondary slot into external flash.&lt;/p&gt;
&lt;p&gt;Please let me know if anything is unclear, and I will go into more details.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>