<?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>sysbuild + mcuboot and board specific signature keys</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/124004/sysbuild-mcuboot-and-board-specific-signature-keys</link><description>Hello. 
 I&amp;#39;m currently migrating our existing application code to the NCS 3.1.0 SDK. As far as I have recognized, with sysbuild the child image build has been replaced. We are building our source code together with mcuboot. I managed to add mcuboot by</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 29 Aug 2025 12:57:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/124004/sysbuild-mcuboot-and-board-specific-signature-keys" /><item><title>RE: sysbuild + mcuboot and board specific signature keys</title><link>https://devzone.nordicsemi.com/thread/547199?ContentTypeID=1</link><pubDate>Fri, 29 Aug 2025 12:57:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b161e18-71c1-41ac-a869-2774724a7b75</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Andreas,&amp;nbsp;&lt;br /&gt;For setting up custom key, I would suggest to take a look at our tutorial here:&amp;nbsp;&lt;a href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-9-bootloaders-and-dfu-fota/topic/exercise-2-dfu-over-usb-adding-external-flash/"&gt;https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-9-bootloaders-and-dfu-fota/topic/exercise-2-dfu-over-usb-adding-external-flash/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Regarding your request, for more complex applications, we use different configuration folder for each board. You can take a look at our nRF_Desktop application:&amp;nbsp;&lt;br /&gt;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/applications/nrf_desktop/README.html"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/applications/nrf_desktop/README.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;\nrf\applications\nrf_desktop&lt;br /&gt;&lt;br /&gt;You can find that the configurations including the&amp;nbsp;sysbuild.conf is located in the configuration\{board}\ folder. So each board would has its own sysbuild.conf.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;To do that&amp;nbsp;we have this line in&amp;nbsp;CMakeLists.txt :&lt;br /&gt;set(APPLICATION_CONFIG_DIR &amp;quot;${CMAKE_CURRENT_LIST_DIR}/configuration/\${NORMALIZED_BOARD_TARGET}&amp;quot;)&lt;/p&gt;
&lt;p&gt;and sysbuild\CMakeLists.txt:&lt;br /&gt;&lt;br /&gt;set(SB_APPLICATION_CONFIG_DIR &amp;quot;${CMAKE_CURRENT_LIST_DIR}/../configuration/\${NORMALIZED_BOARD_TARGET}&amp;quot;)&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>