<?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>DFU in nrf52840 using UART.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/96137/dfu-in-nrf52840-using-uart</link><description>Hello Everyone, 
 I developed a ZigBee gateway using nrf52840, 
 SDK: nrf5_sdk_for_thread_and_zigbee_v4.2.0_af27f76 
 Chip: NRF52840 
 IDE: Segger embedded studio 
 now we are planning to integrate a DFU functionality. 
 Our plan is, NRF52840 is connected</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 30 Jan 2023 13:43:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/96137/dfu-in-nrf52840-using-uart" /><item><title>RE: DFU in nrf52840 using UART.</title><link>https://devzone.nordicsemi.com/thread/407121?ContentTypeID=1</link><pubDate>Mon, 30 Jan 2023 13:43:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:74cf7fcc-7ee2-4d4a-b6b8-cb12bb02f44a</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi Bose,&lt;/p&gt;
&lt;p&gt;I think&amp;nbsp;you will find it&amp;nbsp;easier to&amp;nbsp;rely on the existing DFU protocol rather than making a new protocol from scratch (even if the new one is less complex). If you decide to create a new protocol, you will&amp;nbsp;not only&amp;nbsp;have&amp;nbsp;to&amp;nbsp;implement it on the ESP, but also make adaptations to the existing bootloader on the nRF.&lt;/p&gt;
&lt;p&gt;Maybe you have seen them already, but the message sequence charts for our serial DFU transport here:&amp;nbsp;&lt;a title="Serial" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_dfu_transport_serial.html?cp=8_1_3_5_2_3"&gt;Serial&lt;/a&gt;&amp;nbsp;should give&amp;nbsp;a good overview of what packets the ESP would need to send to complete a DFU process.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The ESP&amp;nbsp;will not need worry about the content of the .bin and .dat file, it just&amp;nbsp;have to forward them to the nRF. The .dat file contains the init command (&lt;a title="Init packet" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_bootloader_dfu_validation.html?cp=8_1_3_5_1_1_0#lib_bootloader_dfu_init"&gt;Init packet&lt;/a&gt;) which includes various metadata such as checksum values and version numbers along with the update request, and the .bin contains the FW image.&lt;/p&gt;
&lt;p&gt;However, if you still prefer to handle storage of the update image yourself, you may have a look at the discussion in this post:&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/94234/nrf52840-update-from-a-ltem-modem"&gt;nRF52840 : update from a LTEM modem&lt;/a&gt;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>