<?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>LPC MicrocontrollersのトピックRe: LPC8N04 match register size</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1173836#M42713</link>
    <description>&lt;P&gt;Hi Jun Zhang,&lt;/P&gt;&lt;P&gt;Ok, I understand my mistake. Thanks a lot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 27 Oct 2020 12:13:43 GMT</pubDate>
    <dc:creator>ppaw</dc:creator>
    <dc:date>2020-10-27T12:13:43Z</dc:date>
    <item>
      <title>LPC8N04 match register size</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1169180#M42602</link>
      <description>&lt;P&gt;I recently started working with LPC8N04 and as I'm quite new to this, I just lost a ton of time with CTIMER match register size. Variable used in the driver code for it has size of 32 bits (uint32_t), which in theory is the same in the microcontroller documentation, but after reading into it, only first 16 bits are used and the rest is reserved. I didn't know that at the beginning and only after a long time I found out that it is not the fault of my code, but the value that I assigned gets later cut down to 16 bits.&lt;/P&gt;&lt;P&gt;So my question is why do they use uint32_t, with no warning about it (except for one place in the MCU documentation), if they could easily use uint16_t instead?&lt;/P&gt;</description>
      <pubDate>Sun, 18 Oct 2020 10:56:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1169180#M42602</guid>
      <dc:creator>ppaw</dc:creator>
      <dc:date>2020-10-18T10:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: LPC8N04 match register size</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1169438#M42615</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;SPAN&gt;ppaw&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Which demo code do you work with, any link?&lt;/P&gt;
&lt;P&gt;if SDK, which version of it?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Jun Zhang&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2020 07:52:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1169438#M42615</guid>
      <dc:creator>ZhangJennie</dc:creator>
      <dc:date>2020-10-19T07:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: LPC8N04 match register size</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1169533#M42620</link>
      <description>&lt;P&gt;Hi ZhangJennie,&lt;/P&gt;&lt;P&gt;I'm using SDK: SDK_2.x_LPC8N04DevBoard. I based my code on demo ctimer_match_example, but I'm not sure how can I find a direct link to it.&lt;/P&gt;&lt;P&gt;In the base version of the example, it works because the value assigned to the matchValue: "matchConfig.matchValue = EXAMPLE_CTIMER_CLK_FREQ / 10;" can fit into 16 bits. If you switch it eg: "matchConfig.matchValue = EXAMPLE_CTIMER_CLK_FREQ;" and in debug mode compare the value of matchConfig.matchValue and EXAMPLE_CTIMER.MR[0], you will see that:&lt;/P&gt;&lt;P&gt;matchConfig.matchValue = 500000 (binary 1111010000100100000)&lt;/P&gt;&lt;P&gt;EXAMPLE_CTIMER.MR[0] = 41248 (binary&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1010000100100000) - cut down to 16 bits&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;ppaw&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2020 09:08:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1169533#M42620</guid>
      <dc:creator>ppaw</dc:creator>
      <dc:date>2020-10-19T09:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: LPC8N04 match register size</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1170007#M42629</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A id="link_12" class="lia-link-navigation lia-page-link lia-user-name-link" href="https://community.nxp.com/t5/user/viewprofilepage/user-id/179223" target="_self"&gt;&lt;SPAN class=""&gt;ppaw&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I understand your questions. LPC8N04 has two CTIMERs 16bit timer(CT16B) and 32bit timer(CT32B).&lt;/P&gt;
&lt;P&gt;Accordingly, MR is 16bit for CT18B and 32bit for CT32B.&lt;/P&gt;
&lt;P&gt;both of CTIMERs use&amp;nbsp;CTIMER_SetupMatch to setup match register.&lt;/P&gt;
&lt;P&gt;I checked, its indeed no judgement in this function for CT16B. It will be good to add a warning&amp;nbsp; inside this function for CT16B if MR over 16bit.&lt;/P&gt;
&lt;P&gt;I will suggest it to SDK development team. Thanks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;Jun Zhang&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Oct 2020 04:02:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1170007#M42629</guid>
      <dc:creator>ZhangJennie</dc:creator>
      <dc:date>2020-10-20T04:02:58Z</dc:date>
    </item>
    <item>
      <title>Re: LPC8N04 match register size</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1173836#M42713</link>
      <description>&lt;P&gt;Hi Jun Zhang,&lt;/P&gt;&lt;P&gt;Ok, I understand my mistake. Thanks a lot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Oct 2020 12:13:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC8N04-match-register-size/m-p/1173836#M42713</guid>
      <dc:creator>ppaw</dc:creator>
      <dc:date>2020-10-27T12:13:43Z</dc:date>
    </item>
  </channel>
</rss>

