<?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>AWS FOTA Failure on nRF9160</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/96416/aws-fota-failure-on-nrf9160</link><description>We have deployed a fleet of nRF9160 based devices communicating with AWS. The production code currently deployed is based on SDK 1.9.1. Previously we have pushed out firmware and modem FOTA updates without issue using AWS. 
 We have now upgraded to nRFConnect</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Feb 2023 12:03:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/96416/aws-fota-failure-on-nrf9160" /><item><title>RE: AWS FOTA Failure on nRF9160</title><link>https://devzone.nordicsemi.com/thread/408848?ContentTypeID=1</link><pubDate>Wed, 08 Feb 2023 12:03:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59d453b4-80e1-4cf4-9bbb-c38ef3c31caf</guid><dc:creator>Craig12</dc:creator><description>&lt;p&gt;Thanks Oyvind. That makes perfect sense.&lt;/p&gt;
&lt;p&gt;It has got us closer, but I suspect we now have a memory map allocation issue we have to work through.&lt;/p&gt;
&lt;p&gt;If I copied the partitions.yml over verbatim to pm_static.yml, it failed to build with &amp;quot;Shared data area and non-secure data area is overlapping&amp;quot;&lt;br /&gt;&lt;br /&gt;So instead, I statically assigned just the mcuboot_secondary address and size. I could now get FOTA to work and mcuboot to pick up the image and swap them. So it verifies the change of mcuboot_secondary address was indeed the problem.&lt;br /&gt;&lt;br /&gt;However, it then got in a loop and would reboot and download the image again with MCUboot sometimes doing a revert.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: revert
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Bootloader chainload address offset: 0x10000
I: Jumping to the first image slot
*** Booting Zephyr OS build v3.2.99-ncs1 ***&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;Looking at MCUboot documentation it appears there is an image trailer at the end of each slot to determine the current state. So I suspect the mcuboot_primary end_address may in incorrect as well and the image is never being set as OK.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll continue to work through the problem for now. Thanks for your help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AWS FOTA Failure on nRF9160</title><link>https://devzone.nordicsemi.com/thread/408581?ContentTypeID=1</link><pubDate>Tue, 07 Feb 2023 13:53:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf64c03f-0aac-4c0e-b522-a7b25c74fa79</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Have you remembered to &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.2.0/nrf/scripts/partition_manager/partition_manager.html#static-configuration"&gt;configure a static configuration of your project?&lt;/a&gt; This ensures that the flash partitions stays the same between upgrades using a pm_static.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;span&gt;The current partition configuration for a build can be found in&amp;nbsp;&lt;/span&gt;&lt;code&gt;&lt;span&gt;$&lt;/span&gt;&lt;em&gt;&lt;span&gt;BUILD_DIR&lt;/span&gt;&lt;/em&gt;&lt;span&gt;/partitions.yml&lt;/span&gt;&lt;/code&gt;&lt;span&gt;. To apply the current configuration as a static configuration, copy this file to&amp;nbsp;&lt;/span&gt;&lt;code&gt;&lt;span&gt;$&lt;/span&gt;&lt;em&gt;&lt;span&gt;APPLICATION_CONFIG_DIR&lt;/span&gt;&lt;/em&gt;&lt;span&gt;/pm_static.yml&lt;/span&gt;&lt;/code&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;span&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: AWS FOTA Failure on nRF9160</title><link>https://devzone.nordicsemi.com/thread/408500?ContentTypeID=1</link><pubDate>Tue, 07 Feb 2023 10:43:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d03d86c-4fa8-4055-b9d8-ce355ff4e7ae</guid><dc:creator>Craig12</dc:creator><description>&lt;p&gt;I just had a look at the partitions.yml left behind in the build directory from the two projects.&lt;br /&gt;&lt;br /&gt;The project built with SDK 1.8.1 has &lt;br /&gt;&lt;br /&gt;mcuboot_secondary:&lt;br /&gt;&amp;nbsp; address: 0x88000&lt;br /&gt;&lt;br /&gt;SDK 2.2.0 has &lt;br /&gt;mcuboot_secondary:&lt;br /&gt;&amp;nbsp; address: 0x80000&lt;/p&gt;
&lt;p&gt;I think I&amp;#39;ll do a little more digging on flash partitions.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>