<?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>Is the mcuboot supposed to be running during application time?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/118264/is-the-mcuboot-supposed-to-be-running-during-application-time</link><description>~Using nrf Connect sdk and toolchain at version V2.9.0 Attached is the app.zip project. 
 
 Basically it consists of a single main funct that prints (&amp;quot;AAAAAAAAAAA&amp;quot;) to the screen. What I&amp;#39;ve discovered is that during app runtime (when AAAAA ...is being</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 24 Jan 2025 10:02:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/118264/is-the-mcuboot-supposed-to-be-running-during-application-time" /><item><title>RE: Is the mcuboot supposed to be running during application time?</title><link>https://devzone.nordicsemi.com/thread/519947?ContentTypeID=1</link><pubDate>Fri, 24 Jan 2025 10:02:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:26c6a23c-8c6b-4e9a-90cb-225bb9bf13ab</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The nRF52811 is quite limited on RAM, but you should have no problem adjusting the RAM usage of this sample. Generally, default buffer sizes etc will not fit all use cases and need adjustment. As MCUboot does not fit in RAM here, you need to look at MCUboot memory usage. There are several tools that can help, but having a quick look in&amp;nbsp;build/mcuboot/zephyr/.config after building the project I notice a very large main stack size. Maybe you can just reduce that? I would test first by setting&amp;nbsp;CONFIG_MAIN_STACK_SIZE=6144 in&amp;nbsp;sysbuild/mcuboot.conf. With that it builds, but you need to test to see if this stack size is actually large enough run time (I have not done that).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is the mcuboot supposed to be running during application time?</title><link>https://devzone.nordicsemi.com/thread/519917?ContentTypeID=1</link><pubDate>Fri, 24 Jan 2025 07:21:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:86a5b0ce-e1b7-4a14-a5e5-c343a2784c7c</guid><dc:creator>Spector</dc:creator><description>&lt;p&gt;Okay, I can see that. -___-&lt;br /&gt;&lt;br /&gt;Do you have any suggestions on how to reduce RAM usage.&lt;br /&gt;&lt;br /&gt;We can&amp;#39;t use nordic chips if it&amp;#39;s impossible to have a serial bootloader and a simple app that just prints A to the screen.&lt;br /&gt;There must be a trick that we&amp;#39;ve missed.&lt;br /&gt;&lt;br /&gt;I&amp;#39;m sitting on commit #e9457f6576 of &lt;a id="" href="https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk.git"&gt;https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk.git&lt;/a&gt;&lt;br /&gt;working on the &lt;/p&gt;
&lt;p&gt;mcuboot_serial_recovery_uart_sysbuild&lt;br /&gt;&lt;br /&gt;and the only change was to create a build configuration with the board &lt;br /&gt;--board ubx_bmd360eval/nrf52811&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is the mcuboot supposed to be running during application time?</title><link>https://devzone.nordicsemi.com/thread/519800?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2025 14:12:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:85895aa5-94f4-4fc2-a05e-b9d3cb86f4c2</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The buildl og here shows that the RAM overflows:&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;arm-zephyr-eabi/bin/ld.bfd:&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;zephyr/zephyr_pre0.elf&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;section&lt;/span&gt;&lt;span&gt; &lt;/span&gt;&lt;span&gt;`&lt;/span&gt;&lt;span&gt;noinit&amp;#39; will not fit in region `RAM&amp;#39;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;/home/wtr/ncs/toolchains/b77d8c1312/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd:&lt;/span&gt;&lt;span&gt; region `&lt;/span&gt;&lt;span&gt;RAM&lt;/span&gt;&lt;span&gt;&amp;#39; overflowed by 3328 bytes&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is the mcuboot supposed to be running during application time?</title><link>https://devzone.nordicsemi.com/thread/519745?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2025 12:19:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:55e220f1-b525-483c-b861-9f80b974b225</guid><dc:creator>Spector</dc:creator><description>&lt;p&gt;Why doesn&amp;#39;t this sysbuild example build? I&amp;#39;ve attached the log.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/build_5F00_config.log"&gt;devzone.nordicsemi.com/.../build_5F00_config.log&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Do i need to change the west build command?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is the mcuboot supposed to be running during application time?</title><link>https://devzone.nordicsemi.com/thread/519731?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2025 11:32:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c26efa4b-bec8-4788-a545-9a708a4b0b2a</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You are right that configs and the build procedure is a bit different with sysbuild. You can refer to the &lt;a href="https://github.com/nrfconnect/sdk-zephyr/blob/b979e73fbf9c8eb07bc142beb3df45aa3574a41c/samples/subsys/mgmt/mcumgr/smp_svr"&gt;smp_svr sample&lt;/a&gt;, which has support for sysbuild.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is the mcuboot supposed to be running during application time?</title><link>https://devzone.nordicsemi.com/thread/519724?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2025 11:03:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:915e3e27-d078-4773-b814-740ce73de9c8</guid><dc:creator>Spector</dc:creator><description>&lt;p&gt;Given that the v2.9.0 has moved away from the parent child setup. Where do i place the .conf info as shown in , does the fact I have config_mcumgr_params etc mean that it puts the smp_svr on the app, rather than in the Bootloader as shown in &lt;a href="https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/serial_recovery"&gt;serial_recovery&lt;br /&gt;&lt;/a&gt;&lt;br /&gt;Are there any examples of the link using v2.9.0? I&amp;#39;m not sure where to put the&amp;nbsp;my_defconfig (mcuboot.conf) file.&lt;br /&gt;&lt;br /&gt;I&amp;#39;m looking into&amp;nbsp;&lt;a href="https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/serial_recovery/mcuboot_serial_recovery_uart_sysbuild"&gt;sysbuild example&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Tak for hj&amp;aelig;lpen&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is the mcuboot supposed to be running during application time?</title><link>https://devzone.nordicsemi.com/thread/519713?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2025 10:04:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b398ae33-679e-499c-9234-aab640659002</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
[quote user=""]Why is mcuboot running during application runtime?[/quote]
&lt;p&gt;MCUboot does not run after starting the application. What is it you are seeing that indicate that it is? What is the initial proglem you are seeing?&lt;/p&gt;
[quote user=""]What I&amp;#39;ve discovered is that during app runtime (when AAAAA ...is being printed to rtt) I can communicate with mcumgr or smpmgr[/quote]
&lt;p&gt;The application includes MCUmgr with UART transport. This means that images can be transfered when in the application (this is normally how it is done, and always if using transprots like BLE). However, serial transports (UART or USB) are supported both in the app and bootloader, so you can choose one or the other (or both).&lt;/p&gt;
[quote user=""]app_update.bin generated. This allowed mcumgr to do a firmware update.[/quote]
&lt;p&gt;Yes, you need the app_udpate.bin or an update zip that incnludes it. Ths includes the trailer used by the bootloaer holding information like hash, version number, etc. I suggest gooing through &lt;a href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/"&gt;Lesson 8 – Bootloaders and DFU/FOTA&lt;/a&gt;. You may also find &lt;a href="https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples"&gt;these unofficial samples&lt;/a&gt; relevant.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>