<?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>MQX Software SolutionsのトピックRe: SPI slave interrupt CRASH problem</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390979#M13078</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Oh No, I'm looking at the MQX RM: I think this means I cannot use the "iodebug:" to view unexpected isr stuff. &lt;/P&gt;&lt;P&gt;Am I correct?&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2.1.49&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; _int_unexpected_isr&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CAUTION&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Since the ISR uses printf() to display information to the default I/O channel,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;default I/O must not be on a channel that uses interrupt-driven I/O or the&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;debugger.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Dec 2014 21:04:52 GMT</pubDate>
    <dc:creator>tjunkans</dc:creator>
    <dc:date>2014-12-04T21:04:52Z</dc:date>
    <item>
      <title>SPI slave interrupt CRASH problem</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390978#M13077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a K20dx256 configured as an SPI slave generating an interrupt. (CW 10.5, MQX 4.1, Freescale tools)&lt;/P&gt;&lt;P&gt;All the SPI ISR does is get the data, set an event and reset the SPI interrupt registers. This has been working for over a year with no issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;-Now,&lt;/STRONG&gt; when I ramp up the SPI interrupts to over a few Khz the system crashes over time, hanging the debugger in the _mqx_idle_task() or in __boot().&lt;/P&gt;&lt;P&gt;-Debugging shows no stack overflow issues and no errors, there are 3 tasks running.&lt;/P&gt;&lt;P&gt;-I have my BSP_DEFAULT_IO_CHANNEL set to "iodebug:" and BSPCFG_ENABLE_IODEBUG set to true. I can see printf()s on my console.&lt;/P&gt;&lt;P&gt;-In the code I run --&amp;gt; _int_install_unexpected_isr(); and _int_install_exception_isr(); which I understand will print some useful information to the console when I crash.&lt;/P&gt;&lt;P&gt;-My problem (besides the crash) is I see nothing printed to the console when I CRASH, no clues as to what is happening. The debugger stops in&amp;nbsp; _mqx_idle_task() or in __boot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help getting CRASH information printed to my console or help figuring out what is causing my CRASH will be much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;TJ&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Dec 2014 16:55:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390978#M13077</guid>
      <dc:creator>tjunkans</dc:creator>
      <dc:date>2014-12-04T16:55:48Z</dc:date>
    </item>
    <item>
      <title>Re: SPI slave interrupt CRASH problem</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390979#M13078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Oh No, I'm looking at the MQX RM: I think this means I cannot use the "iodebug:" to view unexpected isr stuff. &lt;/P&gt;&lt;P&gt;Am I correct?&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2.1.49&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; _int_unexpected_isr&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CAUTION&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Since the ISR uses printf() to display information to the default I/O channel,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;default I/O must not be on a channel that uses interrupt-driven I/O or the&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;debugger.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;----------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Dec 2014 21:04:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390979#M13078</guid>
      <dc:creator>tjunkans</dc:creator>
      <dc:date>2014-12-04T21:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: SPI slave interrupt CRASH problem</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390980#M13079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you using a Freescale board?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sol &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Dec 2014 19:03:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390980#M13079</guid>
      <dc:creator>soledad</dc:creator>
      <dc:date>2014-12-05T19:03:39Z</dc:date>
    </item>
    <item>
      <title>Re: SPI slave interrupt CRASH problem</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390981#M13080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Sol,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No, a custom K20 board acting as SPI slave, while getting interrupt from a couple A/Ds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AHH! Maybe I should try running this stuff on a Kinetis tower board to see if my hardware is having an issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Dec 2014 19:37:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390981#M13080</guid>
      <dc:creator>tjunkans</dc:creator>
      <dc:date>2014-12-06T19:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: SPI slave interrupt CRASH problem</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390982#M13081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, please try using a Freescale board, and please let me know results of this test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sol &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Dec 2014 17:20:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/SPI-slave-interrupt-CRASH-problem/m-p/390982#M13081</guid>
      <dc:creator>soledad</dc:creator>
      <dc:date>2014-12-07T17:20:30Z</dc:date>
    </item>
  </channel>
</rss>

