<?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>NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/67510/ncs-recommended-mcuboot-enabled-apps-build-and-flash-methods</link><description>I am testing smp_srv (bluetooth) with NCS 1.3.2. I don&amp;#39;t know how to build and flash related apps for MCU boot in NCS. MCUboot is unable to boot smp_srv even after running as documented. All sample code related to MCUboot will fail to start the application</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 13 Aug 2021 09:38:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/67510/ncs-recommended-mcuboot-enabled-apps-build-and-flash-methods" /><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/324792?ContentTypeID=1</link><pubDate>Fri, 13 Aug 2021 09:38:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89fb5613-90b7-47f5-9b49-00b860207f90</guid><dc:creator>ayavilevich</dc:creator><description>&lt;p&gt;Thanks for the pointers.&lt;/p&gt;
&lt;p&gt;I am on v1.5.1 and ended up with another method of setting a custom key that I though is worth sharing. Not sure if v1.6 changes anything. At least I found not relevant info in the release notes.&lt;/p&gt;
&lt;p&gt;This processes of setting up a custom mcuboot signing key is definitely not polished enough. Took a while to solve. I hope Nordic can improve on that.&lt;/p&gt;
&lt;p&gt;A good implementation for this in the build system will allow to set a relative path to a file. Then it should take effect in the app and in the mcuboot build processes. It should support the file being located in the app folder or in some other out-of-tree folder.&lt;/p&gt;
&lt;p&gt;All of the other solutions I have seen are based on putting the file in mcuboot project folder. That code is shared by several projects, so doesn&amp;#39;t seem to be a proper solution.&lt;/p&gt;
&lt;p&gt;Also, most of the solutions will not accept a relative file path...&lt;/p&gt;
&lt;p&gt;The way I found that addresses these issues is adding the following line in CMakeLists.txt:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;set(mcuboot_CONFIG_BOOT_SIGNATURE_KEY_FILE &amp;quot;\&amp;quot;${CMAKE_CURRENT_LIST_DIR}/mcuboot_key_dev.pem\&amp;quot;&amp;quot;)&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;This works. Makes a different autogen-pubkey.c file and signs the bin file correctly. Make sure you verify with &amp;quot;imgtool.py verify&amp;quot;.&lt;/p&gt;
&lt;p&gt;Specifying this line in cmake allows for variables to be used. This way I can convert a relative path to an absolute one that mcuboot script expects.&lt;/p&gt;
&lt;p&gt;The quotes make sure the values goes correctly to &amp;quot;build_*\mcuboot\zephyr\misc\generated\extra_kconfig_options.conf&amp;quot; file. Otherwise it doesn&amp;#39;t build.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/292788?ContentTypeID=1</link><pubDate>Thu, 04 Feb 2021 00:46:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c87eb66-66d3-44b4-82ea-b01b71e5fc86</guid><dc:creator>n.sakamoto</dc:creator><description>&lt;p&gt;thanks you.&lt;br /&gt;I didn&amp;#39;t notice.&lt;br /&gt;Be careful.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/292768?ContentTypeID=1</link><pubDate>Wed, 03 Feb 2021 20:10:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28b7a0e3-09cf-456d-b6a2-2e2f4215b669</guid><dc:creator>Vitaliy69</dc:creator><description>&lt;p&gt;Thx, this is a working way.&lt;/p&gt;
&lt;p&gt;But I found another one. It&amp;#39;s need to create a directory &lt;strong&gt;child_image &lt;/strong&gt;in directory with prj.conf&amp;nbsp;with file &lt;strong&gt;mcuboot.conf&lt;/strong&gt; with content:&lt;/p&gt;
&lt;p&gt;CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=n&lt;br /&gt;CONFIG_BOOT_SIGNATURE_TYPE_RSA=y&lt;br /&gt;CONFIG_BOOT_SIGNATURE_KEY_FILE=&amp;quot;custom_key_rsa-2048.pem&amp;quot;&lt;/p&gt;
&lt;p&gt;For exaple:&amp;nbsp;&lt;strong&gt;nrf/samples/nrf9160/http_update/application_update/child_image/mcuboot.conf&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;But the scary message doesn&amp;#39;t disappear anyway.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/292760?ContentTypeID=1</link><pubDate>Wed, 03 Feb 2021 19:19:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e00df89c-57f9-42ec-a28d-e212d0987ae2</guid><dc:creator>Cody</dc:creator><description>&lt;p&gt;Is it expected that we still get this scary message even though it appears to be working properly?&lt;br /&gt;&lt;br /&gt; ---------------------------------------------------------&lt;br /&gt; --- WARNING: Using default MCUBoot key, it should not ---&lt;br /&gt; --- be used for production. ---&lt;br /&gt; ---------------------------------------------------------&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/290874?ContentTypeID=1</link><pubDate>Sun, 24 Jan 2021 18:18:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:73c6a148-2e8b-4054-81e9-21bbb39d928f</guid><dc:creator>Dominic</dc:creator><description>&lt;p&gt;On NCS v1.4.0 you no longer need to specify the signature key file in the application, however the default key type has been changed to ECDSA. Thus, the lines you have to add to mcuboot/boot/zephyr/prj.conf to use an RSA key are:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=n
CONFIG_BOOT_SIGNATURE_TYPE_RSA=y
CONFIG_BOOT_SIGNATURE_KEY_FILE=&amp;quot;custom_key_rsa-2048.pem&amp;quot;&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/278365?ContentTypeID=1</link><pubDate>Wed, 04 Nov 2020 07:39:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:055a484d-de6a-43e0-a525-3d05354a0230</guid><dc:creator>n.sakamoto</dc:creator><description>&lt;p&gt;key pair file path is bootloader/mcuboot/root-rsa-2048-new.pem.&lt;br /&gt;However, smp_srv builds with the default root-rsa-2048.pem.&lt;/p&gt;
&lt;p&gt;ncs v1.4.0 seems to have solved this problem.&lt;br /&gt;Use v1.4.0. Thank you for the correction.&lt;/p&gt;
&lt;p&gt;I also understand that NCS does not need to extract the private key (&amp;quot;imgtool.py getpub&amp;quot;).&lt;/p&gt;
&lt;p&gt;[imgtool.py getpub]&lt;br /&gt;./scripts/imgtool.py getpub -k root-rsa-2048-new.pem&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/277980?ContentTypeID=1</link><pubDate>Mon, 02 Nov 2020 08:58:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ba44c9a-5930-48b8-80a4-19973992d720</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;I did some investigation into NCS v1.3.2 and it seems like you have to do the following to use your custom key:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Generate the key&amp;nbsp;&lt;span&gt;&amp;quot;root-rsa-2048&lt;/span&gt;&lt;span&gt;-custom.&lt;/span&gt;&lt;span&gt;pem&amp;quot;&lt;/span&gt; according to&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.3.2/mcuboot/imgtool.html"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.3.2/mcuboot/imgtool.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Put the generated key inside&amp;nbsp;&lt;em&gt;&amp;lt;ncs location&amp;gt;\bootloader\mcuboot&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;
&lt;div&gt;set CONFIG_BOOT_SIGNATURE_KEY_FILE=&amp;quot;root-rsa-2048-custom.pem&amp;quot; in both &lt;em&gt;&amp;lt;ncs location&amp;gt;\bootloader\mcuboot\boot\zephyr\prj.conf&lt;/em&gt; and &lt;em&gt;&amp;lt;application to be signed&amp;gt;\prj.conf&lt;/em&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;div&gt;The reason you have to put it both places is the following: Inside &lt;em&gt;bootloader\mcuboot\boot\zephyr\CMakeLists.tx&lt;/em&gt;t (where the public key autogen-pubkey.c is created), it uses the key from &lt;em&gt;mcuboot\boot\zephyr\prj.conf&lt;/em&gt;. Inside &lt;em&gt;nrf\cmake\mcuboot.cmake&lt;/em&gt; (where the signed image app_update.bin is created), the key from &lt;em&gt;&amp;lt;application to be signed&amp;gt;&lt;/em&gt;&lt;em&gt;\prj.conf&lt;/em&gt; is used.&lt;/div&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Next you simply flash the merged.hex file from the applications build folder. It will contain both the mcuboot and app_update.bin hex. The mcuboot should be able to boot validate and boot the application.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I have not looked into NCS v1.4.0/master, and if this process is simplified to only set the key in one place. I can do some investigation if you would like to.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/277358?ContentTypeID=1</link><pubDate>Wed, 28 Oct 2020 10:56:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:717f7c8d-035a-4cc5-97ba-147c82a49bdc</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;I&amp;#39;m sorry for the delay on this. I have not looked into this topic&amp;nbsp;(singing, keys, etc..)&amp;nbsp; very much and I put off some time yesterday and today to get an overview of how all this works. I&amp;#39;m gradually getting a better understanding of this and will try to&lt;span&gt;&amp;nbsp;&lt;/span&gt;provide you with an answer soon.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/277277?ContentTypeID=1</link><pubDate>Wed, 28 Oct 2020 05:20:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f54a46ee-68f2-4631-918a-094589e66195</guid><dc:creator>n.sakamoto</dc:creator><description>&lt;p&gt;I decided to avoid the problem by using the generated private key without changing the original file name, hoping that the problem that CONFIG_BOOT_SIGNATURE_KEY_FILE is not reflected in MCU boot will be solved by version upgrade.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/277275?ContentTypeID=1</link><pubDate>Wed, 28 Oct 2020 04:18:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af212e2e-d10a-41f5-8622-7df6372856a7</guid><dc:creator>n.sakamoto</dc:creator><description>&lt;p&gt;I found the following post about an issue where MCUboot&amp;#39;s CONFIG_BOOT_SIGNATURE_KEY_FILE is not recognized.&lt;/p&gt;
&lt;p&gt;[CONFIG_BOOT_SIGNATURE_KEY_FILE doesn't correctly get propagated to MCUBoot build]&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/65235/config_boot_signature_key_file-doesn-t-correctly-get-propagated-to-mcuboot-build/267627#267627"&gt;devzone.nordicsemi.com/.../267627&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/277012?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2020 04:54:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90f457d0-3d80-4e0e-a865-c3e50441ddf4</guid><dc:creator>n.sakamoto</dc:creator><description>&lt;p&gt;Reverting CONFIG_BOOT_SIGNATURE_KEY_FILE in prj.conf of MCUboot to the original file name and executing &amp;quot;imgtool.py getpub&amp;quot; to rebuild it solved the problem.&lt;br /&gt;1.edit mcuboot prj.conf&lt;br /&gt;[bootloader/mcuboot/boot/zephyr/prj.conf]&lt;br /&gt;#CONFIG_BOOT_SIGNATURE_KEY_FILE=&amp;quot;root-rsa-2048-new.pem&amp;quot; &amp;lt;-comment&lt;br /&gt;CONFIG_BOOT_SIGNATURE_KEY_FILE=&amp;quot;root-rsa-2048.pem&amp;quot; &amp;lt;-Revert to old code&lt;br /&gt;2.&lt;br /&gt;./scripts/imgtool.py getpub -k root-rsa-2048.pem&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;When I built mcuboot when bootloader / mcuboot / root-rsa-2048.pem did not exist, the build failed.&lt;br /&gt;An error will occur if root-rsa-2048.pem&amp;#39;is missing.&lt;br /&gt;Could not build with the newly generated root-rsa-2048-new.pem.&lt;br /&gt;Is the method of specifying the key pair wrong?&lt;/p&gt;
&lt;p&gt;error:&lt;br /&gt;FileNotFoundError: [Errno 2] No such file or directory: &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/../bootloader/mcuboot/root-rsa-2048.pem&amp;#39;&lt;/p&gt;
&lt;p&gt;1.edit mcuboot prj.conf&lt;br /&gt;[bootloader/mcuboot/boot/zephyr/prj.conf]&lt;br /&gt;CONFIG_BOOT_SIGNATURE_KEY_FILE=&amp;quot;root-rsa-2048-new.pem&amp;quot; &amp;lt;-set new file&lt;br /&gt;#CONFIG_BOOT_SIGNATURE_KEY_FILE=&amp;quot;root-rsa-2048.pem&amp;quot; &amp;lt;-comment&lt;br /&gt;2.&lt;br /&gt;./scripts/imgtool.py getpub -k root-rsa-2048-new.pem&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;[smp_srv build log]&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;ncs@ubuntu:~/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr$ west build -b nrf52dk_nrf52832  -d build_nrf52dk_nrf52832 . -- -DOVERLAY=overlay-bt.conf
-- west build: generating a build system
Including boilerplate (Zephyr base): /home/ncs/ncs/v1.3.2/zephyr/cmake/app/boilerplate.cmake
-- Application: /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr
-- Zephyr version: 2.3.0-rc1 (/home/ncs/ncs/v1.3.2/zephyr)
-- Found Python3: /usr/bin/python3.8 (found suitable exact version &amp;quot;3.8.5&amp;quot;) found components: Interpreter 
-- Board: nrf52dk_nrf52832
-- Found west: /home/ncs/.local/bin/west (found suitable version &amp;quot;0.7.2&amp;quot;, minimum required is &amp;quot;0.7.1&amp;quot;)

-- Found dtc: /usr/bin/dtc (found suitable version &amp;quot;1.5.0&amp;quot;, minimum required is &amp;quot;1.4.6&amp;quot;)
-- Found toolchain: gnuarmemb (/home/ncs/gnuarmemb)
-- Found BOARD.dts: /home/ncs/ncs/v1.3.2/zephyr/boards/arm/nrf52dk_nrf52832/nrf52dk_nrf52832.dts
-- Generated zephyr.dts: /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/include/generated/devicetree_unfixed.h
Parsing /home/ncs/ncs/v1.3.2/zephyr/Kconfig
Loaded configuration &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/boards/arm/nrf52dk_nrf52832/nrf52dk_nrf52832_defconfig&amp;#39;
Merged configuration &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/prj.conf&amp;#39;
Merged configuration &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/boards/nrf52dk_nrf52832.conf&amp;#39;
Configuration saved to &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/.config&amp;#39;
Kconfig header saved to &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/include/generated/autoconf.h&amp;#39;
-- The C compiler identification is GNU 9.3.1
-- The CXX compiler identification is GNU 9.3.1
-- The ASM compiler identification is GNU
-- Found assembler: /home/ncs/gnuarmemb/bin/arm-none-eabi-gcc
-- Cache files will be written to: /home/ncs/.cache/zephyr

=== child image mcuboot - nrf52dk_nrf52832 begin ===
Including boilerplate (Zephyr base): /home/ncs/ncs/v1.3.2/zephyr/cmake/app/boilerplate.cmake
-- Application: /home/ncs/ncs/v1.3.2/bootloader/mcuboot/boot/zephyr
-- Zephyr version: 2.3.0-rc1 (/home/ncs/ncs/v1.3.2/zephyr)
-- Found Python3: /usr/bin/python3.8 (found suitable exact version &amp;quot;3.8.5&amp;quot;) found components: Interpreter 
-- Board: nrf52dk_nrf52832
-- Found west: /home/ncs/.local/bin/west (found suitable version &amp;quot;0.7.2&amp;quot;, minimum required is &amp;quot;0.7.1&amp;quot;)
-- Found dtc: /usr/bin/dtc (found suitable version &amp;quot;1.5.0&amp;quot;, minimum required is &amp;quot;1.4.6&amp;quot;)
-- Found toolchain: gnuarmemb (/home/ncs/gnuarmemb)
-- Found BOARD.dts: /home/ncs/ncs/v1.3.2/zephyr/boards/arm/nrf52dk_nrf52832/nrf52dk_nrf52832.dts
-- Found devicetree overlay: /home/ncs/ncs/v1.3.2/bootloader/mcuboot/boot/zephyr/dts.overlay
-- Generated zephyr.dts: /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/mcuboot/zephyr/include/generated/devicetree_unfixed.h
Parsing /home/ncs/ncs/v1.3.2/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/boards/arm/nrf52dk_nrf52832/nrf52dk_nrf52832_defconfig&amp;#39;
Merged configuration &amp;#39;/home/ncs/ncs/v1.3.2/bootloader/mcuboot/boot/zephyr/prj.conf&amp;#39;
Configuration saved to &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/mcuboot/zephyr/.config&amp;#39;
Kconfig header saved to &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/mcuboot/zephyr/include/generated/autoconf.h&amp;#39;
-- The C compiler identification is GNU 9.3.1
-- The CXX compiler identification is GNU 9.3.1
-- The ASM compiler identification is GNU
-- Found assembler: /home/ncs/gnuarmemb/bin/arm-none-eabi-gcc
-- Cache files will be written to: /home/ncs/.cache/zephyr
-- Configuring done
-- Generating done
-- Build files have been written to: /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/mcuboot
=== child image mcuboot - nrf52dk_nrf52832 end ===

-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

    OVERLAY


-- Build files have been written to: /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832
-- west build: building application
[1/266] Preparing syscall dependency handling

[9/266] Performing build step for &amp;#39;mcuboot_subimage&amp;#39;
[1/239] Preparing syscall dependency handling

[234/239] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       36060 B        48 KB     73.36%
            SRAM:       23608 B        64 KB     36.02%
        IDT_LIST:          72 B         2 KB      3.52%
[239/239] Linking C executable zephyr/zephyr.elf
[255/266] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      177420 B     224768 B     78.93%
            SRAM:       32280 B        64 KB     49.26%
        IDT_LIST:         136 B         2 KB      6.64%
[263/266] Generating ../../zephyr/app_...../../zephyr/app_moved_test_update.hex
FAILED: zephyr/app_update.bin zephyr/app_signed.hex zephyr/app_test_update.hex zephyr/app_moved_test_update.hex 
cd /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/modules/mcuboot &amp;amp;&amp;amp; /usr/bin/python3.8 /home/ncs/ncs/v1.3.2/zephyr/../bootloader/mcuboot/scripts/imgtool.py sign --key /home/ncs/ncs/v1.3.2/zephyr/../bootloader/mcuboot/root-rsa-2048.pem --header-size 0x200 --align 4 --version 0.0.0+0 --slot-size 0x37000 --pad-header /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/mcuboot_primary_app.hex /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/app_signed.hex &amp;amp;&amp;amp; /home/ncs/gnuarmemb/bin/arm-none-eabi-objcopy --input-target=ihex --output-target=binary /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/mcuboot_primary_app.hex /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/app_to_sign.bin &amp;amp;&amp;amp; /usr/bin/python3.8 /home/ncs/ncs/v1.3.2/zephyr/../bootloader/mcuboot/scripts/imgtool.py sign --key /home/ncs/ncs/v1.3.2/zephyr/../bootloader/mcuboot/root-rsa-2048.pem --header-size 0x200 --align 4 --version 0.0.0+0 --slot-size 0x37000 --pad-header /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/app_to_sign.bin /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/app_update.bin &amp;amp;&amp;amp; /usr/bin/python3.8 /home/ncs/ncs/v1.3.2/zephyr/../bootloader/mcuboot/scripts/imgtool.py sign --key /home/ncs/ncs/v1.3.2/zephyr/../bootloader/mcuboot/root-rsa-2048.pem --header-size 0x200 --align 4 --version 0.0.0+0 --slot-size 0x37000 --pad-header --pad /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/mcuboot_primary_app.hex /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/app_test_update.hex &amp;amp;&amp;amp; /home/ncs/gnuarmemb/bin/arm-none-eabi-objcopy --input-target=ihex --output-target=ihex --change-address 0x37000 /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/app_test_update.hex /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832/zephyr/app_moved_test_update.hex
Traceback (most recent call last):
  File &amp;quot;/home/ncs/ncs/v1.3.2/zephyr/../bootloader/mcuboot/scripts/imgtool.py&amp;quot;, line 20, in &amp;lt;module&amp;gt;
    main.imgtool()
  File &amp;quot;/home/ncs/.local/lib/python3.8/site-packages/click/core.py&amp;quot;, line 764, in __call__
    return self.main(*args, **kwargs)
  File &amp;quot;/home/ncs/.local/lib/python3.8/site-packages/click/core.py&amp;quot;, line 717, in main
    rv = self.invoke(ctx)
  File &amp;quot;/home/ncs/.local/lib/python3.8/site-packages/click/core.py&amp;quot;, line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File &amp;quot;/home/ncs/.local/lib/python3.8/site-packages/click/core.py&amp;quot;, line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File &amp;quot;/home/ncs/.local/lib/python3.8/site-packages/click/core.py&amp;quot;, line 555, in invoke
    return callback(*args, **kwargs)
  File &amp;quot;/home/ncs/ncs/v1.3.2/bootloader/mcuboot/scripts/imgtool/main.py&amp;quot;, line 294, in sign
    key = load_key(key) if key else None
  File &amp;quot;/home/ncs/ncs/v1.3.2/bootloader/mcuboot/scripts/imgtool/main.py&amp;quot;, line 72, in load_key
    key = keys.load(keyfile)
  File &amp;quot;/home/ncs/ncs/v1.3.2/bootloader/mcuboot/scripts/imgtool/keys/__init__.py&amp;quot;, line 44, in load
    with open(path, &amp;#39;rb&amp;#39;) as f:
FileNotFoundError: [Errno 2] No such file or directory: &amp;#39;/home/ncs/ncs/v1.3.2/zephyr/../bootloader/mcuboot/root-rsa-2048.pem&amp;#39;
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /usr/bin/cmake --build /home/ncs/ncs/v1.3.2/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build_nrf52dk_nrf52832
&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS recommended MCUboot enabled apps build and flash methods</title><link>https://devzone.nordicsemi.com/thread/276570?ContentTypeID=1</link><pubDate>Fri, 23 Oct 2020 08:38:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0648b1a0-70d7-4d00-8fce-98d083874ece</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;I&amp;#39;m sorry for the delay on this. I&amp;#39;ll try to provide you with an answer&amp;nbsp;within the next upcoming working days.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>