<?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>Processor Expert Softwareのトピックhow to fix your bugs, Processor Expert?</title>
    <link>https://community.nxp.com/t5/Processor-Expert-Software/how-to-fix-your-bugs-Processor-Expert/m-p/164226#M211</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I found a bug where PE does not set the right registers. Can I fix this issue if I know the correct setting, or does it go into Notes?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;for example, I am using FTM2 on mc9s08pt60. Setting Edge Control to Rising/Falling should reflect in FTM2_C0SC[ELSB:ELSA] but its not, and I have to set it manually after init(). Is it a simple xml file which controls these setting, or is it more complex?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As I understand it, PE is a complex tool, so bugs are bound to happen. What's Freescale's position on this? Is the user left to fend for themselves, or do we have an option other than a TSR? Thanks for your feedback!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 May 2012 01:13:55 GMT</pubDate>
    <dc:creator>AndreiLuchuk</dc:creator>
    <dc:date>2012-05-18T01:13:55Z</dc:date>
    <item>
      <title>how to fix your bugs, Processor Expert?</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/how-to-fix-your-bugs-Processor-Expert/m-p/164226#M211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I found a bug where PE does not set the right registers. Can I fix this issue if I know the correct setting, or does it go into Notes?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;for example, I am using FTM2 on mc9s08pt60. Setting Edge Control to Rising/Falling should reflect in FTM2_C0SC[ELSB:ELSA] but its not, and I have to set it manually after init(). Is it a simple xml file which controls these setting, or is it more complex?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As I understand it, PE is a complex tool, so bugs are bound to happen. What's Freescale's position on this? Is the user left to fend for themselves, or do we have an option other than a TSR? Thanks for your feedback!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 01:13:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/how-to-fix-your-bugs-Processor-Expert/m-p/164226#M211</guid>
      <dc:creator>AndreiLuchuk</dc:creator>
      <dc:date>2012-05-18T01:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: how to fix your bugs, Processor Expert?</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/how-to-fix-your-bugs-Processor-Expert/m-p/164227#M212</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think you will not be able to modify PEx driver directly (the files are encrupted), generaly your step with workaround in inti. was correct. In this case of existing workaround of the issue is the bug fixed in the next release.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However what I am missing in this issue is the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- version you use (CW + PEx) - please note in case you are using some older verison, there is possibility that the bug was already fixed in some newer version&lt;/P&gt;&lt;P&gt;&amp;nbsp;- could you please provide the project that leads you to getting the error&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;best regards&lt;BR /&gt;Vojtech Filip&lt;BR /&gt;Processor Expert Support Team&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 May 2012 14:13:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/how-to-fix-your-bugs-Processor-Expert/m-p/164227#M212</guid>
      <dc:creator>ProcessorExpert</dc:creator>
      <dc:date>2012-05-18T14:13:58Z</dc:date>
    </item>
  </channel>
</rss>

