<?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 Trouble with new design using DSP56F805 in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/Trouble-with-new-design-using-DSP56F805/m-p/141519#M257</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;I created a design using the DSPF805 processor about 5 years ago. It worked fine and never had any problems. I just created a new design using the same DSP (now 5 years later) and neither test board works. When I try to connect to the DSP through the JTAG port I get "Core is not responding" I thought this was going to be a simple thing because I have already used this DSP before. I have triple checked all the connections, VCC, GND levels....everything around the chips seems to be fine. When I hold it in reset I get the crystal oscillator output signal on the CLKO pin...and the oscilator section is working fine. Its just like is is sitting there with some simple stupid reason for not communicating with the software. It is a different chip revision, but I can't hardly imagin that would be the reason...could it? There does not seem to be any major change in the Irrata documentation. Now I am dead in the water with a project that is way overdue. Any input would be appreciated!&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 30 Dec 2006 01:46:04 GMT</pubDate>
    <dc:creator>CCStuart</dc:creator>
    <dc:date>2006-12-30T01:46:04Z</dc:date>
    <item>
      <title>Trouble with new design using DSP56F805</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Trouble-with-new-design-using-DSP56F805/m-p/141519#M257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;I created a design using the DSPF805 processor about 5 years ago. It worked fine and never had any problems. I just created a new design using the same DSP (now 5 years later) and neither test board works. When I try to connect to the DSP through the JTAG port I get "Core is not responding" I thought this was going to be a simple thing because I have already used this DSP before. I have triple checked all the connections, VCC, GND levels....everything around the chips seems to be fine. When I hold it in reset I get the crystal oscillator output signal on the CLKO pin...and the oscilator section is working fine. Its just like is is sitting there with some simple stupid reason for not communicating with the software. It is a different chip revision, but I can't hardly imagin that would be the reason...could it? There does not seem to be any major change in the Irrata documentation. Now I am dead in the water with a project that is way overdue. Any input would be appreciated!&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 30 Dec 2006 01:46:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Trouble-with-new-design-using-DSP56F805/m-p/141519#M257</guid>
      <dc:creator>CCStuart</dc:creator>
      <dc:date>2006-12-30T01:46:04Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble with new design using DSP56F805</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Trouble-with-new-design-using-DSP56F805/m-p/141520#M258</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;DIV&gt;I vaguely remember someone having trouble &lt;SPAN class="801015214-02012007"&gt;&lt;/SPAN&gt;maintaining communication with the JTAG probe on a DSP once.&amp;nbsp;Turned out that there was a "wait" instruction in the code&amp;nbsp;(or something like that) causing the processor not to respond. Could this be the cause&lt;SPAN class="801015214-02012007"&gt;?&lt;/SPAN&gt; Just a shot in the dark.&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 22:53:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Trouble-with-new-design-using-DSP56F805/m-p/141520#M258</guid>
      <dc:creator>marks</dc:creator>
      <dc:date>2007-01-02T22:53:21Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble with new design using DSP56F805</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Trouble-with-new-design-using-DSP56F805/m-p/141521#M259</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Did you ever get this sorted? I had this problem yesterday with a wiggler jtag programmer, &amp;amp; it turned out to be that I didn't have a flash .cfg file set in the M56800E target settings.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Jan 2007 00:07:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Trouble-with-new-design-using-DSP56F805/m-p/141521#M259</guid>
      <dc:creator>AgentK</dc:creator>
      <dc:date>2007-01-20T00:07:15Z</dc:date>
    </item>
    <item>
      <title>Re: Trouble with new design using DSP56F805</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Trouble-with-new-design-using-DSP56F805/m-p/141522#M260</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Yes actually I got it resolved thanks. It turned out that there is a "test" pin on the dsp that needs to be pulled low for "normal chip operation" and I had inadvertantly left it floating. After I tied it to ground the chips woke up. UURRRGGG. Details!&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Jan 2007 00:19:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Trouble-with-new-design-using-DSP56F805/m-p/141522#M260</guid>
      <dc:creator>CCStuart</dc:creator>
      <dc:date>2007-01-20T00:19:19Z</dc:date>
    </item>
  </channel>
</rss>

