https://test-devzone.nordicsemi.com/f/nordic-q-a/88933/mcuboot-logsHI, Am using west tool to build and flash .and am following this link. https://docs.zephyrproject.org/3.0.0/guides/west/sign.html . they mentioned in that link after the cmd west flash -d build-hello-signed , it supposed to give the mcuboot logs asen-USTelligent Community 13 Non-ProductionTue, 14 Jun 2022 13:04:02 GMThttps://test-devzone.nordicsemi.com/thread/372395?ContentTypeID=1Tue, 14 Jun 2022 13:04:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b84e3fcf-1213-4d6a-977b-f8ff54b68463Hung Bui<p>Hi Shikamaru,&nbsp;<br /><br />I don&#39;t see the relation between&nbsp;<strong><span>west</span>&nbsp;<span>flash</span>&nbsp;<span>-d</span>&nbsp;<span>build-hello-signed</span></strong><span>&nbsp; and the log from MCUBoot.&nbsp;</span></p> <p><span>What make&nbsp;<strong><span>build-hello-signed</span></strong><span>&nbsp;different is the -</span></span><span>DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE which mean a custom signature key is provided and will be used to sign the image. It has nothing to do with logging in MCUBoot.&nbsp;</span></p> <p><span>Which log do you have when you boot ?&nbsp;<br />Have you configured (if you plan to send log to UART):&nbsp;<br /></span></p> <div> <div><span>CONFIG_LOG</span><span>=y</span></div> <div> <div> <div><span>CONFIG_LOG_BACKEND_UART</span><span>=y</span></div> <div><span></span></div> <div><span>In the prj.conf for MCUBoot project or in the overlay mcuboot.conf if you are in your application project.&nbsp;</span></div> <div><span>If you do the overlay you should put it in something like this:<br /><img src="https://test-devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1655211824082v1.png" alt=" " /><br /><br /><br /></span></div> <div><span>mcuboot.conf file , inside child_image folder inside your project.&nbsp;</span></div> <div><span></span></div> </div> </div> </div><div style="clear:both;"></div>