<?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: Does the 52234 part miss interrupts ? in ColdFire/68K Microcontrollers and Processors</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Does-the-52234-part-miss-interrupts/m-p/214215#M10718</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi Alessandro&lt;BR /&gt;&lt;BR /&gt;I haven't heard of problems with lost rx interrupts after working on a number of projects with&amp;nbsp; the device.&lt;BR /&gt;&lt;BR /&gt;Looking at our code i think that the following three commands are required to clear an interrupt and free the present buffer.&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;DIV class="msg_source_code"&gt;&lt;DIV class="text_smallest"&gt;Code:&lt;/DIV&gt;&lt;PRE&gt;    EIR = RXF;                                                           // reset interrupt flag    ptrRxBd-&amp;gt;usBDControl |= EMPTY_BUFFER;                                // free the buffer    RDAR = 0;                                                            // re-enable buffer operation&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;On the other hand I haven't heard of anyone using just one rx buffer (the overrun chance will be rather high).&lt;BR /&gt;&lt;BR /&gt;There is however a problem with using just one tx buffer - see the device errata - where the buffer descriptor (which wraps from one buffer back to itself) may cause a transmission to be sent twice due to timing difficulties in this case. There may be something similar with using just one rx buffer too - possibly not encountered since this is probably a very rare configuration...&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;Mark&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.uTasker.com" rel="nofollow noopener noreferrer" target="_blank"&gt;www.uTasker.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 10 Jan 2009 01:13:20 GMT</pubDate>
    <dc:creator>mjbcswitzerland</dc:creator>
    <dc:date>2009-01-10T01:13:20Z</dc:date>
    <item>
      <title>Does the 52234 part miss interrupts ?</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Does-the-52234-part-miss-interrupts/m-p/214214#M10717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm facing a problem about the FEC which stops frames receiving in the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;presence of a heavily loaded network. More in detail, I've configured&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;the FEC with only one receive buffer descriptor which is always&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;consumed inside the receive frame interrupt service routine. The&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;strategy I've implemented is the following:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1) RXF interrupt is rised due to a frame receiving. Since I have only one&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; receive buffer descriptor the FEC stops to process incoming frames&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Inside the ISR I consume the buffer descriptor and FEC starts to&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; process incoming frames again because at least one receive buffer is&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; available at this time&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have analysed the problem under different point of views and I suspect&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;that when it occurs the reason is that the CPU misses the RXF interrupt.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;My suspect is based on the fact that the CPU has to handle several other&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;interrupts other than the FEC ones, and the ISR policy I've implemented&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;plans to use nested interrupts using the priority scheme of Coldfire.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is it possible that the CPU miss some interrupts ? For my knowledge every&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;pending interrupt is served during the time. I can accept that someone of the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;same type is missed due to system performance but at least one should be&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;always rised and retriggered from the ISR using the flag clearing mechanism.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Do you have any ideas ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;/Alessandro&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jan 2009 06:04:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Does-the-52234-part-miss-interrupts/m-p/214214#M10717</guid>
      <dc:creator>Alessandro</dc:creator>
      <dc:date>2009-01-08T06:04:32Z</dc:date>
    </item>
    <item>
      <title>Re: Does the 52234 part miss interrupts ?</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Does-the-52234-part-miss-interrupts/m-p/214215#M10718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi Alessandro&lt;BR /&gt;&lt;BR /&gt;I haven't heard of problems with lost rx interrupts after working on a number of projects with&amp;nbsp; the device.&lt;BR /&gt;&lt;BR /&gt;Looking at our code i think that the following three commands are required to clear an interrupt and free the present buffer.&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;DIV class="msg_source_code"&gt;&lt;DIV class="text_smallest"&gt;Code:&lt;/DIV&gt;&lt;PRE&gt;    EIR = RXF;                                                           // reset interrupt flag    ptrRxBd-&amp;gt;usBDControl |= EMPTY_BUFFER;                                // free the buffer    RDAR = 0;                                                            // re-enable buffer operation&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;On the other hand I haven't heard of anyone using just one rx buffer (the overrun chance will be rather high).&lt;BR /&gt;&lt;BR /&gt;There is however a problem with using just one tx buffer - see the device errata - where the buffer descriptor (which wraps from one buffer back to itself) may cause a transmission to be sent twice due to timing difficulties in this case. There may be something similar with using just one rx buffer too - possibly not encountered since this is probably a very rare configuration...&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;Mark&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.uTasker.com" rel="nofollow noopener noreferrer" target="_blank"&gt;www.uTasker.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Jan 2009 01:13:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Does-the-52234-part-miss-interrupts/m-p/214215#M10718</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2009-01-10T01:13:20Z</dc:date>
    </item>
  </channel>
</rss>

