<?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>Delay in executing main application after migrating from child/parent build to sysbuild</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/117167/delay-in-executing-main-application-after-migrating-from-child-parent-build-to-sysbuild</link><description>Hi 
 We have a project previously built on NCS v2.6.0 and now we need to migrate it to v2.8.0 
 I see from v2.9.0 child/parent build setup is not supported and so we are planning to migrate to sysbuild from v2.8.0. 
 After looking into many references</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 10 Dec 2024 15:22:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/117167/delay-in-executing-main-application-after-migrating-from-child-parent-build-to-sysbuild" /><item><title>RE: Delay in executing main application after migrating from child/parent build to sysbuild</title><link>https://devzone.nordicsemi.com/thread/514321?ContentTypeID=1</link><pubDate>Tue, 10 Dec 2024 15:22:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:412180f5-7c4b-43b8-9b8a-395c159bb381</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]I see from v2.9.0 child/parent build setup is not supported and so we are planning to migrate to sysbuild from v2.8.0.[/quote]
&lt;p&gt;This is correct, instead it will migrate to a similar setup with &amp;quot;companion images&amp;quot; instead of child images. This means that configurations that you&amp;#39;ve previously added to your child_image/mcuboot.conf and child_image/mcuboot.overlay needs to be present in a similar structure with sysbuild configurations. This can be organized as sysbuild/mcuboot.conf and .overlay.&lt;/p&gt;
&lt;p&gt;Do you have this structure in your folder? If not, I believe whats happening is that MCUboot has no information about using&amp;nbsp;CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y, and adding that to sysbuild/mcuboot.conf with something like SB_CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y (I&amp;#39;m not 100% sure about the SB_ prefix, but it might be required).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You might also have to set the rc oscillator up in your devicetree as a device that can be used. Could you verify if you&amp;#39;ve done this?&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>