<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SCT MATCHMEM Problem/Question in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/SCT-MATCHMEM-Problem-Question/m-p/525309#M7945</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by rlund on Wed Dec 02 15:55:57 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Setting the MATCHMEM bit in the SCT peripheral isn't acting quite as expected.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There is a case with a match event, where we are interested in knowing if the match has already occurred prior to entering the state where it is activated.&amp;nbsp; Basically, if the count is equal or greater than the match value, we want&amp;nbsp; the event to be triggered.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The thought was that the MATCHMEM bit would achieve this result for us.&amp;nbsp; However, when the MATCHMEM bit is enabled, the event is being triggered upon entering the state, BEFORE the match value is reached.&amp;nbsp; In other words the count is still less than the match and yet the event is triggered.&amp;nbsp; This is not what the documentation states should happen.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, the counter is counting up (not down), and isn't setup to be bidirectional.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any thoughts, are we missing something?&amp;nbsp; Tried doing a capture on the count for the event in question, and found that the capture value from the count was indeed less than the match value that was setup.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 18:13:20 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T18:13:20Z</dc:date>
    <item>
      <title>SCT MATCHMEM Problem/Question</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/SCT-MATCHMEM-Problem-Question/m-p/525309#M7945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by rlund on Wed Dec 02 15:55:57 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Setting the MATCHMEM bit in the SCT peripheral isn't acting quite as expected.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There is a case with a match event, where we are interested in knowing if the match has already occurred prior to entering the state where it is activated.&amp;nbsp; Basically, if the count is equal or greater than the match value, we want&amp;nbsp; the event to be triggered.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The thought was that the MATCHMEM bit would achieve this result for us.&amp;nbsp; However, when the MATCHMEM bit is enabled, the event is being triggered upon entering the state, BEFORE the match value is reached.&amp;nbsp; In other words the count is still less than the match and yet the event is triggered.&amp;nbsp; This is not what the documentation states should happen.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, the counter is counting up (not down), and isn't setup to be bidirectional.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any thoughts, are we missing something?&amp;nbsp; Tried doing a capture on the count for the event in question, and found that the capture value from the count was indeed less than the match value that was setup.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 18:13:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/SCT-MATCHMEM-Problem-Question/m-p/525309#M7945</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T18:13:20Z</dc:date>
    </item>
  </channel>
</rss>

