<?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>Getting FLASH_MAP dependency warning when trying to migrate build systems to sysbuild</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/117643/getting-flash_map-dependency-warning-when-trying-to-migrate-build-systems-to-sysbuild</link><description>Hello, 
 I am trying to migrate a project nRF Connect SDK v2.6.2 to v2.7.0 for the nrf5340dk target board, particularly to update to the new hw model v2 and sysbuild. I am particularly having issues when building with MCUBoot + sysbuild. I am essentially</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 02 Jan 2025 14:56:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/117643/getting-flash_map-dependency-warning-when-trying-to-migrate-build-systems-to-sysbuild" /><item><title>RE: Getting FLASH_MAP dependency warning when trying to migrate build systems to sysbuild</title><link>https://devzone.nordicsemi.com/thread/516665?ContentTypeID=1</link><pubDate>Thu, 02 Jan 2025 14:56:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1e25519-3404-4f7c-86f7-ab7f640de8a1</guid><dc:creator>Alfredo Antolinez</dc:creator><description>&lt;p&gt;Excellent! Thank you for the clarification. Now I feel I have a better understanding of how sysbuild works.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting FLASH_MAP dependency warning when trying to migrate build systems to sysbuild</title><link>https://devzone.nordicsemi.com/thread/516655?ContentTypeID=1</link><pubDate>Thu, 02 Jan 2025 14:27:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e20b7dc2-e3c5-4e79-bb95-82c9a25ae8c8</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>[quote user="Alfredo Antolinez"]If I was to go with the approach of just using mcuboot.conf to overlay (A), what is the recommended method of adding device tree overlays into the sysbuild structure?[/quote]
&lt;p&gt;If you are good with generic dts overlays for all boards, that would be mcuboot.overlay.&lt;/p&gt;
[quote user="Alfredo Antolinez"]My understanding is that you would add your overlays into sysbuild/mcuboot/boards and the build would automatically detect the dts overlay for multiple boards. But whenever I add a mcuboot directory, the build requires a prj.conf. Since I just want to overlay both dts and (A), what is the correct approach? OR would I be obligated to copy (A) into sysbuild/mcuboot/prj.conf and then I would be able to add the dts overlay?[/quote]
&lt;p&gt;Yea, board specific overlays require prj.conf. In this case you must define the full prj.conf.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting FLASH_MAP dependency warning when trying to migrate build systems to sysbuild</title><link>https://devzone.nordicsemi.com/thread/516651?ContentTypeID=1</link><pubDate>Thu, 02 Jan 2025 13:57:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:387c5c9d-f46f-485e-b04d-5f9cda63327a</guid><dc:creator>Alfredo Antolinez</dc:creator><description>&lt;p&gt;Hello Sigurd,&lt;/p&gt;
&lt;p&gt;Thank you for the reply. I think your clarification really helped me understand how the mcuboot configuration works.&lt;/p&gt;
&lt;p&gt;If I was to go with the approach of just using mcuboot.conf to overlay (A), what is the recommended method of adding device tree overlays into the sysbuild structure?&lt;/p&gt;
&lt;p&gt;My understanding is that you would add your overlays into sysbuild/mcuboot/boards and the build would automatically detect the dts overlay for multiple boards. But whenever I add a mcuboot directory, the build requires a prj.conf. Since I just want to overlay both dts and (A), what is the correct approach? OR would I be obligated to copy (A) into sysbuild/mcuboot/prj.conf and then I would be able to add the dts overlay?&lt;/p&gt;
&lt;p&gt;I am looking for the correct way to add mcuboot dts overlay without having to use build command arguments.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Getting FLASH_MAP dependency warning when trying to migrate build systems to sysbuild</title><link>https://devzone.nordicsemi.com/thread/516638?ContentTypeID=1</link><pubDate>Thu, 02 Jan 2025 12:22:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2521591-886a-4030-a063-7bfe40c1ac73</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;MCUboot has a base &lt;a href="https://github.com/nrfconnect/sdk-mcuboot/blob/main/boot/zephyr/prj.conf"&gt;prj,conf&lt;/a&gt; file. Let&amp;#39;s call this (A).&lt;/p&gt;
&lt;p&gt;sysbuild/mcuboot/prj.conf OVERWRITES (A). This means mcuboot configueation becomes only sysbuild/mcuboot/prj.conf.&lt;/p&gt;
&lt;p&gt;sysbuild/mcuboot.conf OVERLAYS (A). This means mcuboot configueation becomes (A) plus sysbuild/mcuboot.conf .&lt;/p&gt;
&lt;p&gt;If you want sysbuild/mcuboot/prj.conf to behave the same, you must copy the content from (A) into your project configuration.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Sigurd Hellesvik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>