<?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: Cyclone Pro + QGx programming in CodeWarrior for MCU</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Cyclone-Pro-QGx-programming/m-p/143714#M3115</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I agree Mark. Is it possible that my Cyclone Pro isn't programmed for HCS08 parts?&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Feb 2007 23:52:50 GMT</pubDate>
    <dc:creator>irob</dc:creator>
    <dc:date>2007-02-05T23:52:50Z</dc:date>
    <item>
      <title>Cyclone Pro + QGx programming</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Cyclone-Pro-QGx-programming/m-p/143712#M3113</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm using a Cyclone Pro for programming my MON08 QT4s, and would now like to use it to program my newer QGx targets.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For some reason, I'm unable to get the target boards into background mode. I get the "ERROR - SYNC returned no result" message.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The strange part is that with this same cable and same target board, I'm able to enter background mode, erase, program all day long with my P&amp;amp;E Multilink programmer. Same company, what's the difference?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have this vague feeling that it's somehow related to &lt;/SPAN&gt;&lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fforums.freescale.com%2Ffreescale%2Fboard%2Fmessage%3Fboard.id%3DOSBDM08%26message.id%3D136%23M136" rel="nofollow" target="_blank"&gt;this thread about blank QGx parts and background mode&lt;/A&gt;&lt;SPAN&gt;, but I'm not sure.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any thoughts?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Jan 2007 07:49:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Cyclone-Pro-QGx-programming/m-p/143712#M3113</guid>
      <dc:creator>irob</dc:creator>
      <dc:date>2007-01-27T07:49:01Z</dc:date>
    </item>
    <item>
      <title>Re: Cyclone Pro + QGx programming</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Cyclone-Pro-QGx-programming/m-p/143713#M3114</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;irob:&lt;BR /&gt;&lt;BR /&gt;The Cyclone Pro and the multilink should function nearly identically in this situation. The thread you referenced is indeed the culprit-- however, as that threat states, you should be able to communicate with the QG by cycling power on the device (while keeping the Cyclone Pro plugged in) after the initial attempt to communicate fails.&lt;BR /&gt;&lt;BR /&gt;One of the main differences between the two interfaces, however, is that the Cyclone Pro has the ability to cycle the power for you if you've configured it to provide power to your target system.&lt;BR /&gt;&lt;BR /&gt;So, technically this issue should be alleviated rather than exacerbated by the Cyclone...&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Mark&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Feb 2007 22:54:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Cyclone-Pro-QGx-programming/m-p/143713#M3114</guid>
      <dc:creator>P_EMark</dc:creator>
      <dc:date>2007-02-05T22:54:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cyclone Pro + QGx programming</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Cyclone-Pro-QGx-programming/m-p/143714#M3115</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I agree Mark. Is it possible that my Cyclone Pro isn't programmed for HCS08 parts?&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Feb 2007 23:52:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Cyclone-Pro-QGx-programming/m-p/143714#M3115</guid>
      <dc:creator>irob</dc:creator>
      <dc:date>2007-02-05T23:52:50Z</dc:date>
    </item>
    <item>
      <title>Re: Cyclone Pro + QGx programming</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Cyclone-Pro-QGx-programming/m-p/143715#M3116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;irob:&lt;BR /&gt;&lt;BR /&gt;All Cyclones are programmed identically-- so this would not be a possibility. Basically, if the Cyclone works at all, then there's no firmware programming issue there :smileyhappy:&lt;BR /&gt;&lt;BR /&gt;Have you checked your power jumper settings to make sure that you're using an appropriate power configuration for your HCS08 target?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Mark&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Feb 2007 23:52:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Cyclone-Pro-QGx-programming/m-p/143715#M3116</guid>
      <dc:creator>P_EMark</dc:creator>
      <dc:date>2007-02-06T23:52:15Z</dc:date>
    </item>
  </channel>
</rss>

