<?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>Flashlog Backend - not all logs available afte reset</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/55821/flashlog-backend---not-all-logs-available-afte-reset</link><description>I am able to log information to the flashlog backend. When I use the cli interface &amp;quot;flashlog read&amp;quot; I see my information stored (e.g. &amp;quot;operation took %s seconds to complete&amp;quot;, seconds) 
 After a reset this information does not appear in &amp;quot;flashlog read&amp;quot;</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 20 Dec 2019 08:28:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/55821/flashlog-backend---not-all-logs-available-afte-reset" /><item><title>RE: Flashlog Backend - not all logs available afte reset</title><link>https://devzone.nordicsemi.com/thread/226495?ContentTypeID=1</link><pubDate>Fri, 20 Dec 2019 08:28:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad080800-5f30-48b7-94ad-0f675a131265</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Thank you for sharing your solution, Stefan!&lt;/p&gt;
&lt;p&gt;Best regards and Happy Holidays,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flashlog Backend - not all logs available afte reset</title><link>https://devzone.nordicsemi.com/thread/226483?ContentTypeID=1</link><pubDate>Fri, 20 Dec 2019 07:48:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f680a1b1-291b-49a0-82b9-a28d26d54530</guid><dc:creator>stes</dc:creator><description>&lt;p&gt;Hi Simon,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;me again. It works now, but using NRF_LOG_WARNING. I removed all NRF_LOG_PUSH and NRF_LOG_FINAL_FLUSH which I added before as only my logs did not appear in the flashlog...&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Sorry for wasting your time...&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Stefan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flashlog Backend - not all logs available afte reset</title><link>https://devzone.nordicsemi.com/thread/226401?ContentTypeID=1</link><pubDate>Thu, 19 Dec 2019 14:10:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:541323d3-4499-4016-ba7d-56493e0fe872</guid><dc:creator>stes</dc:creator><description>&lt;p&gt;Hi Simon,&lt;/p&gt;
&lt;p&gt;thanks for the fast response. I just wanted to make sure that if I have seen a log by calling &amp;quot;flashlog read&amp;quot; I should be able to see it also after a reset of the firmware.&lt;/p&gt;
&lt;p&gt;So I do not have to call any other function in order to write the stuff to flash?&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Stefan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flashlog Backend - not all logs available afte reset</title><link>https://devzone.nordicsemi.com/thread/226393?ContentTypeID=1</link><pubDate>Thu, 19 Dec 2019 13:53:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5847b9f1-59e0-4aee-9666-17154a743dd3</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;If the flashlog is initialized and enabled the logs should be stored until the flash memory is erased. What pages of the flash is the flashlog supposed to write to in your application? Can you show me how you initialize, configure and enable the flashlog module in your application? Also, are you able to provide an error code of some kind?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;
&lt;p&gt;PS: The Holiday season is upon us, which will leave us understaffed until January 6th, 2020. This means that delayed replies will occur during this time. Sorry about the inconvenience and happy Holidays!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>