<?xml-stylesheet type="text/xsl" href="https://test-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/"><channel><title>Thingy:91 Firmware Update using MCUboot</title><link>/guides/cellular-iot-guides/b/getting-started-cellular/posts/thingy91_2d00_fw_2d00_update_2d00_mcuboot</link><description>The nRF Connect Programmer application now also supports MCUboot! Follow these steps to update through the programmer application or the following guide for the command line alternative. 

This guide shows you how to updat...</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><item><title>RE: Thingy:91 Firmware Update using MCUboot</title><link>https://test-devzone.nordicsemi.com/guides/cellular-iot-guides/b/getting-started-cellular/posts/thingy91_2d00_fw_2d00_update_2d00_mcuboot</link><pubDate>Sat, 21 Nov 2020 01:21:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31014bae-3407-4481-950d-2412fc414ff7</guid><dc:creator>user16646</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;When installing mcumgr, it&amp;#39;s a good idea to use the -v verbose. Otherwise, you might get the impression that go has gone off into the weeds.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;go get -v github.com/apache/mynewt-mcumgr-cli/mcumgr&lt;/strong&gt;&lt;/p&gt;&lt;img src="https://test-devzone.nordicsemi.com/aggbug?PostID=1276&amp;AppID=19&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Thingy:91 Firmware Update using MCUboot</title><link>https://test-devzone.nordicsemi.com/guides/cellular-iot-guides/b/getting-started-cellular/posts/thingy91_2d00_fw_2d00_update_2d00_mcuboot</link><pubDate>Wed, 28 Oct 2020 01:37:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31014bae-3407-4481-950d-2412fc414ff7</guid><dc:creator>user93510</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;While running&amp;nbsp;&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;west build -b nrf9160_pca20035ns&lt;/pre&gt;
&lt;/div&gt;
&lt;p&gt;I am getting :&lt;br /&gt;&lt;br /&gt;&amp;nbsp;ERROR: Build directory C:\Users\parva\ncs\v1.3.1\nrf\applications\asset_tracker\build targets board thingy91_nrf9160ns, but board nrf9160_pca20035ns was specified. (Clean the directory, use --pristine, or use --build-dir to specify a different one.)&lt;br /&gt;FATAL ERROR: refusing to proceed without --force due to the above error&lt;br /&gt;&lt;br /&gt;so, I changed the board name to thingy91_nrf9160ns and then I was getting this error:&lt;br /&gt;&lt;br /&gt;FATAL ERROR: command exited with status 1: &amp;#39;C:\Program Files\CMake\bin\cmake.EXE&amp;#39; &amp;#39;-BC:\Users\parva\ncs\v1.3.1\nrf\applications\asset_tracker\build&amp;#39; &amp;#39;-SC:\Users\parva\ncs\v1.3.1\nrf\applications\asset_tracker&amp;#39; -GNinja&lt;br /&gt;&lt;br /&gt;What to do about it?&lt;/p&gt;&lt;img src="https://test-devzone.nordicsemi.com/aggbug?PostID=1276&amp;AppID=19&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Thingy:91 Firmware Update using MCUboot</title><link>https://test-devzone.nordicsemi.com/guides/cellular-iot-guides/b/getting-started-cellular/posts/thingy91_2d00_fw_2d00_update_2d00_mcuboot</link><pubDate>Thu, 27 Aug 2020 15:58:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31014bae-3407-4481-950d-2412fc414ff7</guid><dc:creator>user6610</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Does the same command apply to modem firmware dfu?&lt;/p&gt;
&lt;p&gt;My target is running&amp;nbsp;mfw_nrf9160_1.2.0 and I tried providing&amp;nbsp;mfw_nrf9160_update_from_1.2.0_to_1.2.0-FOTA-TEST.bin as the &amp;lt;image&amp;gt;.&amp;nbsp; It always fail with error 3.&lt;/p&gt;&lt;img src="https://test-devzone.nordicsemi.com/aggbug?PostID=1276&amp;AppID=19&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Thingy:91 Firmware Update using MCUboot</title><link>https://test-devzone.nordicsemi.com/guides/cellular-iot-guides/b/getting-started-cellular/posts/thingy91_2d00_fw_2d00_update_2d00_mcuboot</link><pubDate>Mon, 04 Nov 2019 08:00:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31014bae-3407-4481-950d-2412fc414ff7</guid><dc:creator>user84572</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Hi, it depends on how are you trying to build the SW.&lt;/p&gt;
&lt;p&gt;1. If you build using the command line (power shell in Windows 10) using&lt;/p&gt;
&lt;p&gt;&amp;quot;&lt;strong&gt;west build -b nrf9160_pca20035ns&lt;/strong&gt;&amp;quot; in &amp;quot;cd ncs\nrf\applications\asset_tracker&amp;quot; &lt;br /&gt;you can see &amp;quot;app_update.bin&amp;quot; under the &amp;quot;&lt;strong&gt;build\zephyr\app_update.bin&lt;/strong&gt;&amp;quot;, if your build success.&lt;/p&gt;
&lt;p&gt;If your build was failed, delete the previous build folder in &amp;quot;applications\asset_tracker&amp;quot; and build one more time.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;2. If you are trying to build using SEGGER Embedded Studio, you can see under&lt;/p&gt;
&lt;p&gt;C:\ncs\nrf\applications\asset_tracker\&lt;strong&gt;build_nrf9160_pca20035ns\zephyr\app_update.bin&lt;/strong&gt;&amp;quot;&lt;/p&gt;&lt;img src="https://test-devzone.nordicsemi.com/aggbug?PostID=1276&amp;AppID=19&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Thingy:91 Firmware Update using MCUboot</title><link>https://test-devzone.nordicsemi.com/guides/cellular-iot-guides/b/getting-started-cellular/posts/thingy91_2d00_fw_2d00_update_2d00_mcuboot</link><pubDate>Wed, 30 Oct 2019 00:34:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31014bae-3407-4481-950d-2412fc414ff7</guid><dc:creator>user84523</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;I can&amp;#39;t find the build\zephyr\app_update.bin file.&lt;br /&gt;&lt;br /&gt;Is it called app_update.bin or zephyr.bin ? &lt;/p&gt;&lt;img src="https://test-devzone.nordicsemi.com/aggbug?PostID=1276&amp;AppID=19&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Thingy:91 Firmware Update using MCUboot</title><link>https://test-devzone.nordicsemi.com/guides/cellular-iot-guides/b/getting-started-cellular/posts/thingy91_2d00_fw_2d00_update_2d00_mcuboot</link><pubDate>Tue, 29 Oct 2019 23:54:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31014bae-3407-4481-950d-2412fc414ff7</guid><dc:creator>user84523</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;I can&amp;#39;t find the build\zephyr\app_update.bin file.&lt;br /&gt;&lt;br /&gt;Is it called app_update.bin or zephyr.bin ? &lt;/p&gt;&lt;img src="https://test-devzone.nordicsemi.com/aggbug?PostID=1276&amp;AppID=19&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>