<?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>SENSE Value Mismatch?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/633/sense-value-mismatch</link><description>Over the past few months I have worked extensively on a few different projects that all utilize the nRF51422. In some recent debugging of GPIO issues (both relating to SENSE mechanism and GPIOTE module) I have discovered an inconsistency between the </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 14 Oct 2013 11:35:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/633/sense-value-mismatch" /><item><title>RE: SENSE Value Mismatch?</title><link>https://devzone.nordicsemi.com/thread/3247?ContentTypeID=1</link><pubDate>Mon, 14 Oct 2013 11:35:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fbfd3d6b-3115-4bc4-a251-14d0022b2de2</guid><dc:creator>Ole Morten</dc:creator><description>&lt;p&gt;Accepting an answer is only available to the original poster, but the question was posted anonymously, there is no way for you to do this. I can however do it for you. :-)&lt;/p&gt;
&lt;p&gt;What I meant with my &amp;quot;shouldn&amp;#39;t rely on that&amp;quot; comment was that when you read the reference manual, you should only rely on things that are explicitly spelled out. Even though you can work out the meaning of the bits behind the values, this &lt;em&gt;could&lt;/em&gt; in principle change with a future revision, and if it does, we won&amp;#39;t necessarily document that change very clearly, since the exact meaning wasn&amp;#39;t spelled out in the first place. However, for the same version of the chip, this shouldn&amp;#39;t really be a problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SENSE Value Mismatch?</title><link>https://devzone.nordicsemi.com/thread/3246?ContentTypeID=1</link><pubDate>Fri, 11 Oct 2013 13:19:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fb9307a9-ce93-4221-b4c6-9d17c8d71ba2</guid><dc:creator>Brian Acock</dc:creator><description>&lt;p&gt;Thanks for the quick response Ole! This is the 3rd time you have answered a question for me and I have neglected to &amp;quot;Accept as Answer&amp;quot; all 3 times - not because it wasn&amp;#39;t helpful, but because I did not see any option in my browser to &amp;quot;accept as answer&amp;quot;.&lt;/p&gt;
&lt;p&gt;Perhaps this is because I posted as a guest? I have created an account as it seems I&amp;#39;ll be frequenting this website for the foreseeable future :)&lt;/p&gt;
&lt;p&gt;One last thing, can you clarify what you mean that I &amp;quot;shouldn&amp;#39;t rely on that&amp;quot;? Just that I should not rely on the bit meanings until they are officially corrected/published in the reference manual?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SENSE Value Mismatch?</title><link>https://devzone.nordicsemi.com/thread/3245?ContentTypeID=1</link><pubDate>Fri, 11 Oct 2013 12:31:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b478249b-d622-44b9-889e-49faf9eed6d5</guid><dc:creator>Ole Morten</dc:creator><description>&lt;p&gt;Unfortunately, this is a know typo in the reference manual, that will be fixed in the next release. You&amp;#39;re quite correct that the value in nrf51_bitfields is correct, and also on the bit meanings, although you shouldn&amp;#39;t rely on that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>