<?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>nRF52840 UART DFU fault</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69031/nrf52840-uart-dfu-fault</link><description>Hi, 
 We are attempting to update the nRF52840 on our Thingy91 over the UART connection from the 9160. All development on the nRF52 is done in the nRF5 SDK 17.0.2. I have flashed the secure uart debug bootloader. I can enter it from the application, and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 07 Dec 2020 18:46:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69031/nrf52840-uart-dfu-fault" /><item><title>RE: nRF52840 UART DFU fault</title><link>https://devzone.nordicsemi.com/thread/283662?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2020 18:46:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:568a722b-863e-472f-b9f5-bdd34649bd58</guid><dc:creator>coreyD</dc:creator><description>&lt;p&gt;It turns out the problem was my data packet size. I read a post somewhere saying that the data packets needed to be in 32 bit increments. I played with the size and found out that setting the packets to 16 bytes allows the DFU process to work. I have successfully updated the nRF52 firmware from the nRF9160!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 UART DFU fault</title><link>https://devzone.nordicsemi.com/thread/283653?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2020 17:51:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1843240b-5064-450e-aef2-c771e82f9aa6</guid><dc:creator>coreyD</dc:creator><description>&lt;p&gt;I am using RTT to view the logs, so I have NRF_LOG_BACKEND_RTT_ENABLED. Adding the UART backend seems to reduce the amount of logs shown to just &amp;quot;app: Inside main.&amp;quot; I already had the Log enabled at level 4. Do you have any other ideas?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Corey&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 UART DFU fault</title><link>https://devzone.nordicsemi.com/thread/283476?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2020 08:51:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aafdeac7-e3bd-44d8-ad5d-3a3b0df1d028</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;In sdk_config.h you should be able to enable log output by configuring the following:&lt;br /&gt;&lt;br /&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;// &amp;lt;e&amp;gt; NRF_LOG_BACKEND_UART_ENABLED - nrf_log_backend_uart - Log UART backend
//==========================================================
#ifndef NRF_LOG_BACKEND_UART_ENABLED
#define NRF_LOG_BACKEND_UART_ENABLED 1
#endif

// &amp;lt;e&amp;gt; NRF_LOG_ENABLED - nrf_log - Logger
//==========================================================
#ifndef NRF_LOG_ENABLED
#define NRF_LOG_ENABLED 1
#endif

// &amp;lt;o&amp;gt; NRF_LOG_DEFAULT_LEVEL  - Default Severity level
 
// &amp;lt;0=&amp;gt; Off 
// &amp;lt;1=&amp;gt; Error 
// &amp;lt;2=&amp;gt; Warning 
// &amp;lt;3=&amp;gt; Info 
// &amp;lt;4=&amp;gt; Debug 

#ifndef NRF_LOG_DEFAULT_LEVEL
#define NRF_LOG_DEFAULT_LEVEL 4
#endif&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I have not used the nRF5 SDK in a while, so have not confirmed this functionality.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Let me know how this works for you.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;-Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 UART DFU fault</title><link>https://devzone.nordicsemi.com/thread/283387?ContentTypeID=1</link><pubDate>Fri, 04 Dec 2020 18:14:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d95dab5d-3720-42b5-a21d-4719237bc803</guid><dc:creator>coreyD</dc:creator><description>&lt;p&gt;Hello&amp;nbsp;&lt;span&gt;&amp;Oslash;yvind,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank you for your response. I have tried adding the DEBUG define to the preprocessor definitions in Segger, however, the log does not display any additional information. Could there be any other settings, maybe in sdk_config that I need to change to see the assert information? I have not changed anything about the UART debug bootloader other than allowing it to enter from the application (using GPREGRET).&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Corey&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 UART DFU fault</title><link>https://devzone.nordicsemi.com/thread/283133?ContentTypeID=1</link><pubDate>Thu, 03 Dec 2020 14:22:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba38df34-ef2a-4096-97eb-5aa0231d4096</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;A fault ID of 0x4002 matches &amp;quot;&lt;span&gt;NRF_FAULT_ID_SDK_ASSERT&amp;quot; (&lt;/span&gt;&lt;span&gt;An&amp;nbsp;error&amp;nbsp;stemming&amp;nbsp;from&amp;nbsp;a&amp;nbsp;call&amp;nbsp;to&amp;nbsp;ASSERT&amp;nbsp;(nrf_assert.h).&amp;nbsp;The&amp;nbsp;info&amp;nbsp;parameter&amp;nbsp;is&amp;nbsp;a&amp;nbsp;pointer&amp;nbsp;to&amp;nbsp;an&amp;nbsp;@ref&amp;nbsp;assert_info_t&amp;nbsp;variable.)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Can you please add the DEBUG define to the preprocessor. This would give more information about the error printed in the output log. E.g. if GCC is used, update the Makefile:&amp;nbsp;&lt;span&gt;CFLAGS&lt;/span&gt;&lt;span&gt;&amp;nbsp;+=&amp;nbsp;-DDEBUG&lt;/span&gt;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;​With the DEBUG define set, the output log should specify which line in which file that triggered this assert.&amp;nbsp;&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;Kind regards,&lt;/div&gt;
&lt;div&gt;Øyvind&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>