<?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 Re: MKE14F: TRGMUX complain in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKE14F-TRGMUX-complain/m-p/690154#M42499</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the feedback.&lt;/P&gt;&lt;P&gt;About using UART communication error as trigger source, I think that still need be discussed. When UART communication with error, the better handle way to generate a UART interrupt to handle related error issue.&lt;/P&gt;&lt;P&gt;Thank you for the attention.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Ma Hui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Jul 2017 08:50:05 GMT</pubDate>
    <dc:creator>Hui_Ma</dc:creator>
    <dc:date>2017-07-11T08:50:05Z</dc:date>
    <item>
      <title>MKE14F: TRGMUX complain</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKE14F-TRGMUX-complain/m-p/690153#M42498</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The TRGMUX is a really good advantage for programming MCUs. But why the heck only 23 channels out of 128 are assigned? Why are not all channels routed to the trgmux? Example Uart communication error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The idea is really good, but implementation could be advanced.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jul 2017 16:23:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKE14F-TRGMUX-complain/m-p/690153#M42498</guid>
      <dc:creator>michaelheidinge</dc:creator>
      <dc:date>2017-07-10T16:23:21Z</dc:date>
    </item>
    <item>
      <title>Re: MKE14F: TRGMUX complain</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKE14F-TRGMUX-complain/m-p/690154#M42499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the feedback.&lt;/P&gt;&lt;P&gt;About using UART communication error as trigger source, I think that still need be discussed. When UART communication with error, the better handle way to generate a UART interrupt to handle related error issue.&lt;/P&gt;&lt;P&gt;Thank you for the attention.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Ma Hui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jul 2017 08:50:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKE14F-TRGMUX-complain/m-p/690154#M42499</guid>
      <dc:creator>Hui_Ma</dc:creator>
      <dc:date>2017-07-11T08:50:05Z</dc:date>
    </item>
  </channel>
</rss>

