<?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>About the secure serial DFU for nRF52840 and  nRF52832</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/26791/about-the-secure-serial-dfu-for-nrf52840-and-nrf52832</link><description>Hi, 
 I&amp;#39;m using SDK13.0 with nRF52840. Now I&amp;#39;m doing the DFU by the UART through MCU. But we meet a big problem, MCU is hard to read the infomation in the .dat and .json file, so we want to just use the .bin file to do DFU. 
 I have seen the data on</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 16 Nov 2017 01:44:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/26791/about-the-secure-serial-dfu-for-nrf52840-and-nrf52832" /><item><title>RE: About the secure serial DFU for nRF52840 and  nRF52832</title><link>https://devzone.nordicsemi.com/thread/105314?ContentTypeID=1</link><pubDate>Thu, 16 Nov 2017 01:44:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:61b3ffe2-6ca3-4cbf-99f5-85a9d5428b16</guid><dc:creator>Alice</dc:creator><description>&lt;p&gt;Sorry, I forgot to mention we have another WIFI module, which would be used more, so we also should think about it. We would think about your suggestion carefully and decide how to do. Thanks so much.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: About the secure serial DFU for nRF52840 and  nRF52832</title><link>https://devzone.nordicsemi.com/thread/105313?ContentTypeID=1</link><pubDate>Wed, 15 Nov 2017 12:38:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ddb74ec-f83d-4473-9bfd-5d9a4ca2bdea</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;If there isn&amp;#39;t any MCU on the Wifi module, how would you plan to interface the bootloader with the Wifi module ? At the beginning you mentioned &amp;quot;I&amp;#39;m doing the DFU by the UART through MCU&amp;quot;, where does the MCU sit in your set up ?&lt;/p&gt;
&lt;p&gt;There are several steps you need to do with the bootloader, first step would be to make it work with the new Softdevice, after that you need to adapt the flash size to match with nRF52840. There are some difference in the SDK library as well. It&amp;#39;s not a quick task but would require some work here. My comment above on &amp;quot;just some change in the flash size and softdevice API&amp;quot; was not really correct. Sorry about that. My idea here is to follow what we do in SDK v6 and make your own bootloader. Because the bootloader in that SDK was much more simpler.&lt;/p&gt;
&lt;p&gt;With further consideration, I think it&amp;#39;s easier just to make the MCU to send the init packet and use the stock SDK v13+ bootloader.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: About the secure serial DFU for nRF52840 and  nRF52832</title><link>https://devzone.nordicsemi.com/thread/105312?ContentTypeID=1</link><pubDate>Wed, 15 Nov 2017 09:59:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:27063c26-93d7-4597-a465-e6428b69b896</guid><dc:creator>Alice</dc:creator><description>&lt;p&gt;No, the WIFI module just work as a reply to send data to cloud and couldn&amp;#39;t be proramed.&lt;/p&gt;
&lt;p&gt;Could you tell me more about how to modify the bootloader in SDK v6.x? Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: About the secure serial DFU for nRF52840 and  nRF52832</title><link>https://devzone.nordicsemi.com/thread/105311?ContentTypeID=1</link><pubDate>Tue, 14 Nov 2017 13:25:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88bc56b7-e5a8-4bae-b330-28cbb58a6246</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;You would need to modify the bootloader in SDK v6.x to meet your need. I think it shouldn&amp;#39;t be too difficult just some change in the flash size and softdevice API.&lt;/p&gt;
&lt;p&gt;Do you have full control over the WIFI module, is there any MCU on it ? If there is, you should be able to program the chip to send init packet first and then send firmware image .&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: About the secure serial DFU for nRF52840 and  nRF52832</title><link>https://devzone.nordicsemi.com/thread/105310?ContentTypeID=1</link><pubDate>Tue, 14 Nov 2017 03:16:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aca8ba15-9e95-4317-afa7-a884a463e912</guid><dc:creator>Alice</dc:creator><description>&lt;p&gt;But the SDK v6.x couldn&amp;#39;t work with nRF52840. We would put the zip file on the &amp;quot;Cloud&amp;quot; then send the file to WIFI module through WIFI, the WIFI module would do DFU via UART interface.We have many other MCU use the same protocol to update fireware. They wouldn&amp;#39;t have the init packet, so how to let the WIFI module know the packet is the init packet? Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: About the secure serial DFU for nRF52840 and  nRF52832</title><link>https://devzone.nordicsemi.com/thread/105309?ContentTypeID=1</link><pubDate>Mon, 13 Nov 2017 10:24:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fcf8e6b8-f124-44fd-bd1c-6af6750099dd</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Alice,&lt;/p&gt;
&lt;p&gt;The MCU doesn&amp;#39;t need to read the .json file. It just need to send the .dat (which is the binary of the init packet) and the .bin.&lt;/p&gt;
&lt;p&gt;If you don&amp;#39;t plan to send init packet, you will not be able to check for image size, CRC and signature when you receiving the image.&lt;/p&gt;
&lt;p&gt;I would suggest you to try sending init packet, instead of modifying the bootloader to skip it.&lt;/p&gt;
&lt;p&gt;If you want a very simple bootloader, you can go back to SDK v6.x where we don&amp;#39;t require init packet, and the bootloader was pretty simpler.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>