<?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>nRF5340 Production DFU</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/104743/nrf5340-production-dfu</link><description>Hi Nordic, We are now in pre-production phase and till now we are MCUBoot serial recovery with slot 0/slot 1 in internal flash to have USB-CDC DFU capability. Due to slotted internal flash (~432KB slot size) we are hitting flash size limitations and now</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 18 Oct 2023 09:12:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/104743/nrf5340-production-dfu" /><item><title>RE: nRF5340 Production DFU</title><link>https://devzone.nordicsemi.com/thread/451003?ContentTypeID=1</link><pubDate>Wed, 18 Oct 2023 09:12:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a4fcbbe0-ab48-4752-a1b1-1c5c996a1f8c</guid><dc:creator>AnujPathak</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote userid="107683" url="~/f/nordic-q-a/104743/nrf5340-production-dfu/450963"]Noted, thank you for clarifying. Then I can with&amp;nbsp;certainty say that simultaneous DFU is production ready for the nRF5340.[/quote]
&lt;p&gt;Thanks for confirming that simultaneous DFU is production ready. SDK Document line&amp;nbsp;&lt;span&gt;&amp;quot;&lt;/span&gt;&lt;span&gt;The simultaneous update of multiple images is available for testing since nRF Connect SDK v1.7.0&amp;quot;&lt;/span&gt; not clear, and give a sense that it is still available for testing only. We suggest to update the document to reflect the production readiness of the feature.&lt;/p&gt;
[quote userid="107683" url="~/f/nordic-q-a/104743/nrf5340-production-dfu/450963"]In general only SPI NOR flashes are supported so mostly out of curiosity could you verify if you&amp;#39;ve successfully implemented a custom driver to perform DFU using the external NAND flash?[/quote]
&lt;p&gt;Yes we are using a custom NAND driver with our bad block management to make sure images are not corrupted. It was working fine as per our internal testing.&lt;/p&gt;
[quote userid="107683" url="~/f/nordic-q-a/104743/nrf5340-production-dfu/450963"]If you&amp;#39;re referring to this part of &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/device_guides/working_with_nrf/nrf53/nrf5340.html#mcuboot-s-serial-recovery-of-the-networking-core-image"&gt;the documentation&lt;/a&gt;, then the answer is yes, and as the documentation states then mcuboot_primary_1 must be used as the RAM partition mediator. MCUboot recovery of the appcore will also work as described in mcuboot recovery of the application, but it will need a secondary slot either on internal or external flash to store the new firmware image[/quote]
&lt;p&gt;Yes we referring to same section and this will add a fallback routine to recover/update devices even if NAND has any issue. But i think secondary slot is not needed to app core recovery process. but it should be defined in partition yaml and dts files. Right?&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/blockquote&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 Production DFU</title><link>https://devzone.nordicsemi.com/thread/450963?ContentTypeID=1</link><pubDate>Wed, 18 Oct 2023 07:38:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:545e6ec1-c218-4d78-b503-5fa68ebfc419</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user="AnujPathak"]1. We just want to confirm that the Simultaneous&amp;nbsp;DFU feature is still experimental or production ready ? Because SDK document still says &lt;span&gt;&amp;quot;&lt;/span&gt;&lt;span&gt;The simultaneous update of multiple images is available for testing since nRF Connect SDK v1.7.0&amp;quot;.&lt;/span&gt;[/quote]
&lt;p&gt;Noted, thank you for clarifying. Then I can with&amp;nbsp;certainty say that simultaneous DFU is production ready for the nRF5340.&lt;/p&gt;
[quote user="AnujPathak"]2. Since secondary slots will be hosted on external NAND (8Gb in our case) with our custom driver.&amp;nbsp;[/quote]
&lt;p&gt;In general only SPI NOR flashes are supported so mostly out of curiosity could you verify if you&amp;#39;ve successfully implemented a custom driver to perform DFU using the external NAND flash?&lt;/p&gt;
[quote user="AnujPathak"]Can&amp;nbsp;we always fallback to&amp;nbsp;&lt;span&gt;&amp;quot;MCUBoot Recovery with netcore&amp;quot; mode to write to app/net core directly bypassing external NAND ?&lt;/span&gt;[/quote]
&lt;p&gt;If you&amp;#39;re referring to this part of &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/device_guides/working_with_nrf/nrf53/nrf5340.html#mcuboot-s-serial-recovery-of-the-networking-core-image"&gt;the documentation&lt;/a&gt;, then the answer is yes, and as the documentation states then mcuboot_primary_1 must be used as the RAM partition mediator. MCUboot recovery of the appcore will also work as described in mcuboot recovery of the application, but it will need a secondary slot either on internal or external flash to store the new firmware image&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/serial_recovery"&gt;https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/serial_recovery&lt;/a&gt;&amp;nbsp;contains&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 Production DFU</title><link>https://devzone.nordicsemi.com/thread/450867?ContentTypeID=1</link><pubDate>Tue, 17 Oct 2023 13:42:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:17a73067-31ef-45c6-9925-32a3bc9bb745</guid><dc:creator>AnujPathak</dc:creator><description>&lt;p&gt;Thanks for reply.&lt;br /&gt;&lt;br /&gt;We have got simultaneous working and are aware the non-simultaneous can leave app core / net core in inconsistent state. &lt;br /&gt;1. We just want to confirm that the Simultaneous&amp;nbsp;DFU feature is still experimental or production ready ? Because SDK document still says &lt;span&gt;&amp;quot;&lt;/span&gt;&lt;span&gt;The simultaneous update of multiple images is available for testing since nRF Connect SDK v1.7.0&amp;quot;.&lt;/span&gt;&lt;br /&gt;Since our devices are completely sealed pack we&amp;#39;ll be relying on robustness of bootloader for device lifetime once that is programmed.&lt;br /&gt;2. Since secondary slots will be hosted on external NAND (8Gb in our case) with our custom driver.&amp;nbsp;Can&amp;nbsp;we always fallback to&amp;nbsp;&lt;span&gt;&amp;quot;MCUBoot Recovery with netcore&amp;quot; mode to write to app/net core directly bypassing external NAND ?&lt;br /&gt;&lt;br /&gt;Regards&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 Production DFU</title><link>https://devzone.nordicsemi.com/thread/450861?ContentTypeID=1</link><pubDate>Tue, 17 Oct 2023 13:20:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c956409-a6e2-412a-8d7b-e5601c3d5d89</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Regarding both questions: To be certain I can answer with 100% confidence, could you elaborate some of your concerns regarding this? In general simultaneous is what we recommend that users do when migrating versions since that ensures that the firmware on the netcore is compatible with the firmware on the appcore. Doing them non-simultaneous can result in communication issues in between the cores since the Softdevice controller&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This case&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/100639/nrf5340-multi-image-dfu-update-over-ble-remote-error-in-value-3"&gt;nrf5340 multi-image DFU update over BLE &amp;#39;Remote Error: In Value(3)&amp;#39; ?&lt;/a&gt;&amp;nbsp;, more specifically&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/100639/nrf5340-multi-image-dfu-update-over-ble-remote-error-in-value-3/431020"&gt;this comment&lt;/a&gt;&amp;nbsp;elaborates some of the incompatibilities you may face if you do nonsimultaneous updates when your migrating in between several major NCS versions&lt;/p&gt;
&lt;p&gt;Let me know about the question I&amp;#39;ve asked and if the other case I&amp;#39;ve linked and supported clarifies things for you&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>