<?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: Using PE code in a MQX project</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/Using-PE-code-in-a-MQX-project/m-p/147194#M174</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is because Processor Expert for ColdFireV1 is not fully integrated with MQX yet. In your case, you can try to include PE_Types.h file generated from Processor Expert. This file contains appropriate register access macros like getRegxx. You can also extract only necessary macros from this file directly into your .c/.h file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;See also this topic. It might help.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.freescale.com/message/87924#87924" title="https://community.freescale.com/message/87924#87924"&gt;https://community.freescale.com/message/87924#87924&lt;/A&gt;﻿&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Marek V.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Jul 2011 14:09:32 GMT</pubDate>
    <dc:creator>marek_vinkler</dc:creator>
    <dc:date>2011-07-08T14:09:32Z</dc:date>
    <item>
      <title>Using PE code in a MQX project</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Using-PE-code-in-a-MQX-project/m-p/147193#M173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a MCF51JM processor project that needs a high speed timer. I used PE to generate code to setup and run TMP2. The code works but the PE generated non mqx code ( &lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN style="color: #800080;"&gt;void&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;SPAN style="font-weight: bolder;"&gt;getReg8&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN&gt;TPM2C1SC_CH1F&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt; &lt;SPAN&gt;) which MQX would compile. I ended up moving the code into a sperate module, but it is real ugly. I am new to Freescale , is there clean way&amp;nbsp; to rewrite the code PE generated?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;﻿&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jul 2011 22:15:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Using-PE-code-in-a-MQX-project/m-p/147193#M173</guid>
      <dc:creator>barbercolman</dc:creator>
      <dc:date>2011-07-07T22:15:07Z</dc:date>
    </item>
    <item>
      <title>Re: Using PE code in a MQX project</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Using-PE-code-in-a-MQX-project/m-p/147194#M174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is because Processor Expert for ColdFireV1 is not fully integrated with MQX yet. In your case, you can try to include PE_Types.h file generated from Processor Expert. This file contains appropriate register access macros like getRegxx. You can also extract only necessary macros from this file directly into your .c/.h file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;See also this topic. It might help.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.freescale.com/message/87924#87924" title="https://community.freescale.com/message/87924#87924"&gt;https://community.freescale.com/message/87924#87924&lt;/A&gt;﻿&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Marek V.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Jul 2011 14:09:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Using-PE-code-in-a-MQX-project/m-p/147194#M174</guid>
      <dc:creator>marek_vinkler</dc:creator>
      <dc:date>2011-07-08T14:09:32Z</dc:date>
    </item>
  </channel>
</rss>

