<?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>Logging/Printing issues in the nRF 9160 DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/105678/logging-printing-issues-in-the-nrf-9160-dk</link><description>I am using the nrf9060dk device with the nrf connect software (V2.5.0), but I am facing some logging issues that I did not encounter in the previous versions of zephyr. 
 One issue is that when I use the printk() function, I get —dropped messages— and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Nov 2023 14:34:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/105678/logging-printing-issues-in-the-nrf-9160-dk" /><item><title>RE: Logging/Printing issues in the nRF 9160 DK</title><link>https://devzone.nordicsemi.com/thread/457602?ContentTypeID=1</link><pubDate>Mon, 27 Nov 2023 14:34:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:feca7d19-0a3d-485b-b459-54cd02f7789e</guid><dc:creator>Kazi Afroza Sultana</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;It might be a secure fault; therefore, it is caught by TF-M, not the application. You can try to add the following configurations as well that should make TF-M use the same UART as the application for crash dumps.:&lt;/p&gt;
&lt;p&gt;CONFIG_TFM_LOG_LEVEL_SILENCE=n&lt;/p&gt;
&lt;p&gt;CONFIG_TFM_EXCEPTION_INFO_DUMP=y&lt;/p&gt;
&lt;p&gt;CONFIG_TFM_SECURE_UART_SHARE_INSTANCE=y&lt;/p&gt;
&lt;p&gt;CONFIG_TFM_SECURE_UART0=y&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging/Printing issues in the nRF 9160 DK</title><link>https://devzone.nordicsemi.com/thread/457347?ContentTypeID=1</link><pubDate>Fri, 24 Nov 2023 13:56:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2615671b-d904-4f0a-8d32-6f76d2ab99be</guid><dc:creator>Omar</dc:creator><description>&lt;p&gt;now it stops instead of rebooting, but i can&amp;#39;t see the fatal error message&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging/Printing issues in the nRF 9160 DK</title><link>https://devzone.nordicsemi.com/thread/456885?ContentTypeID=1</link><pubDate>Wed, 22 Nov 2023 11:10:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fc5bcc1d-2200-425d-852c-d23cb081203a</guid><dc:creator>Kazi Afroza Sultana</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You can disable CONFIG_RESET_ON_FATAL_ERROR in the config file. This enables the fatal error handler defined for Nordic DKs. When it is used, the system restarts after a fatal error. You also mentioned &amp;#39;&amp;#39;&lt;span&gt;Restart problem occurs when I use MQTT publish function mqtt_publish()&amp;#39;&amp;#39;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;So, CONFIG_RESET_ON_FATAL_ERROR=n might give you details on the crash.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging/Printing issues in the nRF 9160 DK</title><link>https://devzone.nordicsemi.com/thread/456293?ContentTypeID=1</link><pubDate>Sun, 19 Nov 2023 20:55:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0f2f89e-3e4a-42bc-9614-718332e14b59</guid><dc:creator>Omar</dc:creator><description>&lt;p&gt;The first issue is solved by increasing the&amp;nbsp;CONFIG_LOG_BUFFER_SIZE.&lt;br /&gt;&lt;br /&gt;Restart problem occurs when I use MQTT publish function mqtt_publish()&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Logging/Printing issues in the nRF 9160 DK</title><link>https://devzone.nordicsemi.com/thread/455993?ContentTypeID=1</link><pubDate>Thu, 16 Nov 2023 13:49:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:748b1c26-3520-40a7-9bf3-6ce23034a330</guid><dc:creator>Kazi Afroza Sultana</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&amp;#39;&amp;#39;&lt;span&gt;One issue is that when I use the printk() function, I get —dropped messages— and changing the baudrate does not help, even though priniting this data works fine in the nrf52840dk device.&amp;#39;&amp;#39;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Can you please show the code snippet of prinktk() part and the output you are seeing on the terminal?&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It seems like you are using putty as serial terminal. Can you please try to use another terminal like Termite?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;#39;&amp;#39;Another issue is that the dk device restarts unexpectedly when -I assume- a fatal error happens, and I do not see any FATAL ERROR message in the logs as I did in the nrf52840 device&amp;#39;&amp;#39;. It happens for which application on the DK and what is the error log you got after building the application?&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;BR&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kazi&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>