<?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>SDK Migration - nrf_log back to experimental in SDK14.2</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/29230/sdk-migration---nrf_log-back-to-experimental-in-sdk14-2</link><description>I&amp;#39;m using SDK 12.2 with Softdevice S132 V3.0.
I try now the migration to the most resent SDK 14.2 with its Softdevice, because it seams there were several bugs fixed in between. 
 Despite of the migration guides, the migration is quite a hard work and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 17 Jan 2018 14:22:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/29230/sdk-migration---nrf_log-back-to-experimental-in-sdk14-2" /><item><title>RE: SDK Migration - nrf_log back to experimental in SDK14.2</title><link>https://devzone.nordicsemi.com/thread/116270?ContentTypeID=1</link><pubDate>Wed, 17 Jan 2018 14:22:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7576a343-8c53-4ac4-b483-fb38b8da3147</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Strange, don&amp;#39;t know  how I missed that one.&lt;/p&gt;
&lt;p&gt;Anyway, I found internal reports for both of the bugs. They are different. The one fixed in Sdk 12.3.0 relates to an issue where peer manager under certain circumstances decides to fill up the entire flash with garbage data. The other one relates to a case where pds_peer_data_store() corrupts FDS page offsets.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK Migration - nrf_log back to experimental in SDK14.2</title><link>https://devzone.nordicsemi.com/thread/116272?ContentTypeID=1</link><pubDate>Tue, 16 Jan 2018 06:53:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6cef20b6-5500-4aba-a140-e3c676ce262b</guid><dc:creator>Roman</dc:creator><description>&lt;p&gt;nRF5 SDK v12.3.0:
Release Date: Week 19, 2017 - Bugfixes - Drivers and libraries - &amp;quot;Fixed a bug in Peer Manager which made it possible for Peer Manager to corrupt the flash memory under certain circumstances.&amp;quot;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK Migration - nrf_log back to experimental in SDK14.2</title><link>https://devzone.nordicsemi.com/thread/116271?ContentTypeID=1</link><pubDate>Mon, 15 Jan 2018 15:56:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59f2337f-b132-410b-ba04-fe6160dc5831</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;I&amp;#39;m unable to find a mention of any FDS vs Peer manager bug in the SDK 12.3 release notes. Can you point me to where it is mentioned?&lt;/p&gt;
&lt;p&gt;I found the internal report of the bug fix in SDK 13.0. It lists SDK 13.0.0-1.alpha and SDK 12.2. as affected versions, so it is plausible that it is the same bug.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK Migration - nrf_log back to experimental in SDK14.2</title><link>https://devzone.nordicsemi.com/thread/116268?ContentTypeID=1</link><pubDate>Tue, 09 Jan 2018 09:18:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f313caec-5abc-49e4-8596-8c7e4dfded40</guid><dc:creator>Roman</dc:creator><description>&lt;p&gt;Hi Martin,&lt;/p&gt;
&lt;p&gt;Thanks for your answer.
I think, there is no reason to go to 14.x unless I need one of the new features. So far, I only have to decide whether to go to 12.3 or 13.1.&lt;/p&gt;
&lt;p&gt;SDK v12.3.0 Release notes say that there has been «Fixed a bug in Peer Manager which made it possible for Peer Manager to corrupt the flash memory under certain circumstances».
SDK v13.0.0 Release notes say that there has been « Fixed a bug where Peer Manager corrupted FDS data in flash». Is this a different description of the same bug? Or is this bug not relevant when using “fstorage” instead of “FDS”?&lt;/p&gt;
&lt;p&gt;Hmm, I have realized now that there is an other aspect as well:
According the release notes of Softdevice S132 v4.0.2, I don’t see a reason for an update. But according nRF52832 Errata Rev 1, SoftDevice S132 v4.0.2 includes workarounds for two anomalies ([102], [106]).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK Migration - nrf_log back to experimental in SDK14.2</title><link>https://devzone.nordicsemi.com/thread/116269?ContentTypeID=1</link><pubDate>Tue, 09 Jan 2018 07:43:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:469cccf0-00d8-4bde-979f-03a681d1ee4d</guid><dc:creator>Austin</dc:creator><description>&lt;p&gt;Also see &lt;a href="https://devzone.nordicsemi.com/question/174119/nrf_log-fixes-in-sdk1410/?answer=186670#post-id-186670"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK Migration - nrf_log back to experimental in SDK14.2</title><link>https://devzone.nordicsemi.com/thread/116267?ContentTypeID=1</link><pubDate>Tue, 09 Jan 2018 07:25:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1ca1ea3e-0391-42a7-94c1-71c5717c3838</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Between SDK 13 and 14 the logger was significantly refactored and extended. It had some stability issues, but most of them are fixed in 14.2. It is also not properly documented yet. Especially with regards to some of the new modules that it is using, like ring buffers and memory handling. That is why we moved it back into experimental.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>