<?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>nRF52810 and errata 185</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/83589/nrf52810-and-errata-185</link><description>I am currently evaluating the differences between nRF52811 and nRF52810. I am still using the nRF5 SDK. 
 One difference is in the nRFInitialize function in the startup code at nRF5_SDK_17.1.0_ddde560\modules\nrfx\mdk\ses_startup_nrf52810.s 
 It seems</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 14 Jan 2022 08:31:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/83589/nrf52810-and-errata-185" /><item><title>RE: nRF52810 and errata 185</title><link>https://devzone.nordicsemi.com/thread/347694?ContentTypeID=1</link><pubDate>Fri, 14 Jan 2022 08:31:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:335f215f-93dd-45a8-99df-36f9646aac08</guid><dc:creator>Michael Hunold</dc:creator><description>&lt;p&gt;I understand that not every aspect of the device is disclosed to the public in the datasheet. However:&lt;/p&gt;
[quote userid="7377" url="~/f/nordic-q-a/83589/nrf52810-and-errata-185/347661#347661"]but you can see from how they are used extensively in the MDK (nrf52_erratas.h) that this contains information used to determine if a specific errata workaround applies to the device or not, and this has to do with device type and revision.[/quote]
&lt;p&gt;Exactly because these registers are used to check device type and revision it makes them important registers that are necessary when you want to manually check this information in your own application for example.&lt;/p&gt;
&lt;p&gt;Of course you can argue that this is all handled by the SDK and that customers should not worry, but there are people out there that like to understand and handle these things even at this very low level.&lt;/p&gt;
&lt;p&gt;So if you could raise awareness for this internally this would be great - I would appreciate if these register would be disclosed to the public as well.&lt;/p&gt;
&lt;p&gt;Thanks for your answers, from my side this ticket can be closed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52810 and errata 185</title><link>https://devzone.nordicsemi.com/thread/347661?ContentTypeID=1</link><pubDate>Thu, 13 Jan 2022 18:50:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3e2c228b-6948-4254-9299-3e720dc895e0</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This erratum is not officially documented,&amp;nbsp;so I cannot say much about it. But the workaround is effective, and is only applied to revision 1 devise, which has not been produced for a long time.&lt;/p&gt;
&lt;p&gt;Regarding the magic registers&amp;nbsp;0x10000130 and&amp;nbsp;0x10000134 there are also not documented, but you can see from how they are used extensively in the MDK (nrf52_erratas.h) that this contains information used to determine if a specific errata workaround applies to the device or not, and this has to do with device type and revision.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52810 and errata 185</title><link>https://devzone.nordicsemi.com/thread/347648?ContentTypeID=1</link><pubDate>Thu, 13 Jan 2022 16:23:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ca2b58b7-e283-4a14-8a97-14ab6081ec27</guid><dc:creator>Michael Hunold</dc:creator><description>&lt;p&gt;Thank you very much for your answer. But in any case this information is missing from the list of erratas and for the sake of completeness it would be nice to have that information up-to-date.&lt;/p&gt;
&lt;p&gt;Can you also comment on these &amp;quot;magic&amp;quot; registers that are used in the errata functions for checking if a device is affected or not?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52810 and errata 185</title><link>https://devzone.nordicsemi.com/thread/347415?ContentTypeID=1</link><pubDate>Wed, 12 Jan 2022 14:34:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2995540c-153a-48e3-aff3-674b296225c7</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The code snippet&amp;nbsp; you have found in the MDK is a workaround for an undocumented issue&amp;nbsp;that only exist in revision 1 of the nRF52810. It does not exist in revision 2, nor in any other nRF52 devices.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>