<?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>Kinetis Design StudioのトピックPE suggested fix/addition. DMA request count overflow detection.</title>
    <link>https://community.nxp.com/t5/Kinetis-Design-Studio/PE-suggested-fix-addition-DMA-request-count-overflow-detection/m-p/395427#M2513</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a PE DMA Channel LDD component setup to require 513 bytes, on UARTx Rx. This worked great, until I enabled minor loop channel linking. Then I started getting an on complete event after receiving only 1 byte.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Turns out this was because when you enable minor loop linking, the BITER and CITER fields in the BITER and CITER registers go from 15 bit to 9 bit. Since I had 513 bits set, this actually got written as 0x01, hence my issue.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be nice if PE warned you that the request count field was out of bounds. It doesn't do this in either of the 9 or 15 bit cases ATM.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately I wasted around 10 hours on this, and that could have been solved by a quick warning or comment on this field.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm sorted now, so no hurry, but thought it might be of interest to others.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 May 2015 14:35:17 GMT</pubDate>
    <dc:creator>andrewparlane</dc:creator>
    <dc:date>2015-05-01T14:35:17Z</dc:date>
    <item>
      <title>PE suggested fix/addition. DMA request count overflow detection.</title>
      <link>https://community.nxp.com/t5/Kinetis-Design-Studio/PE-suggested-fix-addition-DMA-request-count-overflow-detection/m-p/395427#M2513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a PE DMA Channel LDD component setup to require 513 bytes, on UARTx Rx. This worked great, until I enabled minor loop channel linking. Then I started getting an on complete event after receiving only 1 byte.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Turns out this was because when you enable minor loop linking, the BITER and CITER fields in the BITER and CITER registers go from 15 bit to 9 bit. Since I had 513 bits set, this actually got written as 0x01, hence my issue.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be nice if PE warned you that the request count field was out of bounds. It doesn't do this in either of the 9 or 15 bit cases ATM.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately I wasted around 10 hours on this, and that could have been solved by a quick warning or comment on this field.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm sorted now, so no hurry, but thought it might be of interest to others.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 May 2015 14:35:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Design-Studio/PE-suggested-fix-addition-DMA-request-count-overflow-detection/m-p/395427#M2513</guid>
      <dc:creator>andrewparlane</dc:creator>
      <dc:date>2015-05-01T14:35:17Z</dc:date>
    </item>
  </channel>
</rss>

