<?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>MCUBOOT UART pin numbers</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/92937/mcuboot-uart-pin-numbers</link><description>I have MCUBOOT working using the default UART pin numbers. I need to change the UART RX and TX pin numbers used by MCUBOOT for a custom application. I am able to change the UART pin numbers used in the application firmware by creating an overlay file</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 19 Oct 2022 01:57:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/92937/mcuboot-uart-pin-numbers" /><item><title>RE: MCUBOOT UART pin numbers</title><link>https://devzone.nordicsemi.com/thread/391310?ContentTypeID=1</link><pubDate>Wed, 19 Oct 2022 01:57:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2f0d301f-0355-4aee-a7d0-7ea452b33cc6</guid><dc:creator>rdolejs</dc:creator><description>&lt;p&gt;Hi Vidar,&lt;/p&gt;
&lt;p&gt;I tried the second approach and it worked. I left the mcuboot.conf file in the child_image directory and renamed mcuboot_dtc.overlay as nrf52840dk_nrf52840.overlay and placed it in the boards directory. The mcuboot uart pin numbers are now assigned correctly.&lt;/p&gt;
&lt;p&gt;Thanks for your help,&lt;/p&gt;
&lt;p&gt;Ray&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MCUBOOT UART pin numbers</title><link>https://devzone.nordicsemi.com/thread/391107?ContentTypeID=1</link><pubDate>Tue, 18 Oct 2022 08:23:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:94439951-09e3-43e7-b064-4495a632a7db</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello Ray,&lt;/p&gt;
&lt;p&gt;mcuboot_DTC_OVERLAY_FILE and mcuboot_CONF_FILE must be set before find_package() and project() to be applied to the build. So, it should work if you move set() functions just below cmake_minimum_required(VERSION 3.20.0) line.&lt;/p&gt;
&lt;p&gt;Another approach that does not involve changing cmakelist.txt is to use the naming convention described here: &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_multi_image.html#image-specific-variables"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_multi_image.html#image-specific-variables&lt;/a&gt;. This will make the build system apply the configs and overlays to the mcuboot child image automatically.&lt;/p&gt;
&lt;p&gt;Example of how you can apply board specific configurations to the mcuboot build:&lt;/p&gt;
&lt;p&gt;├── child_image&lt;br /&gt;│&amp;nbsp;&amp;nbsp; └── mcuboot&lt;br /&gt;│&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; └── boards&lt;br /&gt;│&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ├── nrf52840dk_nrf52840.conf&lt;br /&gt;│&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; └── nrf52840dk_nrf52840.overlay&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>