<?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 Coldfire interrupt priorities in uClinux in ColdFire/68K Microcontrollers and Processors</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Coldfire-interrupt-priorities-in-uClinux/m-p/130983#M829</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #ff0000;"&gt;This message contains an entire topic ported&amp;nbsp;from the WildRice - Coldfire forum.&amp;nbsp; Freescale has received the approval from the WildRice administrator on seeding the Freescale forum with messages.&amp;nbsp; The original message and all replies are in this single message. We have seeded this new forum with selected information that we expect will be of value as you search for answers to your questions.&amp;nbsp; Freescale assumes no responsibility whatsoever with respect to Posted Material.&amp;nbsp; For additional information, please see the&lt;/SPAN&gt; &lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.freescale.com%2Ffiles%2Fabstract%2Fhelp_page%2FTERMSOFUSE.html" rel="nofollow" target="_blank"&gt;&lt;SPAN style=": ; color: #000000;"&gt;Terms of Use - Message Boards and Community Forums&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN style=";"&gt;.&amp;nbsp; Thank You and Enjoy the Forum!&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;HR /&gt;Nov 3, 2005, 8:46 AM&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Post #1 of 2 (19 views)&lt;BR /&gt;Copy Shortcut&lt;BR /&gt;&amp;nbsp;[ColdFire] Coldfire interrupt priorities in uClinux&amp;nbsp; Can't Post&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;--------------------------------------------------------------------------------&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;I'm building a counter driver utilizing the GPT ports of the mcf5282.&lt;BR /&gt;As part of the driver, I'm assigning an interrupt for every IC, so the user&lt;BR /&gt;has the option of doing a slow, soft counter on all 4 channels.&lt;/DIV&gt;&lt;DIV&gt;It works fine, unless I get 2 of these interrupts simultaneously.&lt;BR /&gt;When this happens the processor starts generating an interrupt 127, which is&lt;BR /&gt;actually listed as "unused" in the manual, which is never cleared, so just&lt;BR /&gt;constantly loops the default interrupt handler routine.&lt;/DIV&gt;&lt;DIV&gt;The manual goes on to say that I should not be assigning the same interrupt&lt;BR /&gt;level,priority combo to more than one vector (which I am).&lt;/DIV&gt;&lt;DIV&gt;Is there any type of organization in the current tree that is supposed to&lt;BR /&gt;protect this from happening with drivers? Or are we just playing the odds&lt;BR /&gt;that in most cases 2 interrupts won't happen at exactly the same time?&lt;/DIV&gt;&lt;DIV&gt;Interestingly enough IRQMRH = 0xff7f0ff0, so vector 127 should be masked, yet&lt;BR /&gt;it is still fireing.&lt;BR /&gt;I suspect the processor really doesn't like 2 interrupts with the&lt;BR /&gt;samelevel,priority happening simultaneously.&lt;/DIV&gt;&lt;DIV&gt;thx,&lt;BR /&gt;NZG.&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;--------------------------------------------------------------------&lt;/DIV&gt;&lt;DIV&gt;Nov 3, 2005, 9:03 AM&lt;/DIV&gt;&lt;DIV&gt;Post #2 of 2 (19 views)&lt;BR /&gt;Copy Shortcut&lt;BR /&gt;&amp;nbsp;Re: [ColdFire] Coldfire interrupt priorities in uClinux [In reply to]&amp;nbsp; Can't Post&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;--------------------------------------------------------------------------------&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;Hi NZG. You are right, don't do that! It is your responsability to make&lt;BR /&gt;sure no two interrupt sources have the same IL/IP.&lt;/DIV&gt;&lt;DIV&gt;Marc&lt;/DIV&gt;&lt;DIV&gt;NZG wrote:&lt;/DIV&gt;&lt;DIV&gt;&amp;gt;I suspect the processor really doesn't like 2 interrupts with the&lt;BR /&gt;&amp;gt;samelevel,priority happening simultaneously.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;/DIV&gt;&lt;P&gt;Message Edited by Dietrich on &lt;SPAN class="date_text"&gt;04-03-2006&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;11:02 AM&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Message Edited by Dietrich on &lt;SPAN class="date_text"&gt;04-04-2006&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;09:15 PM&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 01 Apr 2006 07:38:36 GMT</pubDate>
    <dc:creator>Dietrich</dc:creator>
    <dc:date>2006-04-01T07:38:36Z</dc:date>
    <item>
      <title>Coldfire interrupt priorities in uClinux</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Coldfire-interrupt-priorities-in-uClinux/m-p/130983#M829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #ff0000;"&gt;This message contains an entire topic ported&amp;nbsp;from the WildRice - Coldfire forum.&amp;nbsp; Freescale has received the approval from the WildRice administrator on seeding the Freescale forum with messages.&amp;nbsp; The original message and all replies are in this single message. We have seeded this new forum with selected information that we expect will be of value as you search for answers to your questions.&amp;nbsp; Freescale assumes no responsibility whatsoever with respect to Posted Material.&amp;nbsp; For additional information, please see the&lt;/SPAN&gt; &lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.freescale.com%2Ffiles%2Fabstract%2Fhelp_page%2FTERMSOFUSE.html" rel="nofollow" target="_blank"&gt;&lt;SPAN style=": ; color: #000000;"&gt;Terms of Use - Message Boards and Community Forums&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN style=";"&gt;.&amp;nbsp; Thank You and Enjoy the Forum!&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;HR /&gt;Nov 3, 2005, 8:46 AM&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Post #1 of 2 (19 views)&lt;BR /&gt;Copy Shortcut&lt;BR /&gt;&amp;nbsp;[ColdFire] Coldfire interrupt priorities in uClinux&amp;nbsp; Can't Post&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;--------------------------------------------------------------------------------&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;I'm building a counter driver utilizing the GPT ports of the mcf5282.&lt;BR /&gt;As part of the driver, I'm assigning an interrupt for every IC, so the user&lt;BR /&gt;has the option of doing a slow, soft counter on all 4 channels.&lt;/DIV&gt;&lt;DIV&gt;It works fine, unless I get 2 of these interrupts simultaneously.&lt;BR /&gt;When this happens the processor starts generating an interrupt 127, which is&lt;BR /&gt;actually listed as "unused" in the manual, which is never cleared, so just&lt;BR /&gt;constantly loops the default interrupt handler routine.&lt;/DIV&gt;&lt;DIV&gt;The manual goes on to say that I should not be assigning the same interrupt&lt;BR /&gt;level,priority combo to more than one vector (which I am).&lt;/DIV&gt;&lt;DIV&gt;Is there any type of organization in the current tree that is supposed to&lt;BR /&gt;protect this from happening with drivers? Or are we just playing the odds&lt;BR /&gt;that in most cases 2 interrupts won't happen at exactly the same time?&lt;/DIV&gt;&lt;DIV&gt;Interestingly enough IRQMRH = 0xff7f0ff0, so vector 127 should be masked, yet&lt;BR /&gt;it is still fireing.&lt;BR /&gt;I suspect the processor really doesn't like 2 interrupts with the&lt;BR /&gt;samelevel,priority happening simultaneously.&lt;/DIV&gt;&lt;DIV&gt;thx,&lt;BR /&gt;NZG.&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;--------------------------------------------------------------------&lt;/DIV&gt;&lt;DIV&gt;Nov 3, 2005, 9:03 AM&lt;/DIV&gt;&lt;DIV&gt;Post #2 of 2 (19 views)&lt;BR /&gt;Copy Shortcut&lt;BR /&gt;&amp;nbsp;Re: [ColdFire] Coldfire interrupt priorities in uClinux [In reply to]&amp;nbsp; Can't Post&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;--------------------------------------------------------------------------------&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;Hi NZG. You are right, don't do that! It is your responsability to make&lt;BR /&gt;sure no two interrupt sources have the same IL/IP.&lt;/DIV&gt;&lt;DIV&gt;Marc&lt;/DIV&gt;&lt;DIV&gt;NZG wrote:&lt;/DIV&gt;&lt;DIV&gt;&amp;gt;I suspect the processor really doesn't like 2 interrupts with the&lt;BR /&gt;&amp;gt;samelevel,priority happening simultaneously.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;/DIV&gt;&lt;P&gt;Message Edited by Dietrich on &lt;SPAN class="date_text"&gt;04-03-2006&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;11:02 AM&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Message Edited by Dietrich on &lt;SPAN class="date_text"&gt;04-04-2006&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;09:15 PM&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Apr 2006 07:38:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Coldfire-interrupt-priorities-in-uClinux/m-p/130983#M829</guid>
      <dc:creator>Dietrich</dc:creator>
      <dc:date>2006-04-01T07:38:36Z</dc:date>
    </item>
  </channel>
</rss>

