<?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: Anybody using ip-ip tunnels on MQX? in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Anybody-using-ip-ip-tunnels-on-MQX/m-p/229554#M4855</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gary,&lt;/P&gt;&lt;P&gt;Are you asking about the MQX IPC (Inter Processor Communication)?&lt;/P&gt;&lt;P&gt;If yes the MQXUG.pdf in the MQX4.0/docs/mqx folder section 3.8 discusses IPC.&lt;/P&gt;&lt;P&gt;Section 3.8.4.5.4 references the example we have in MQX4.0/examples/ipc folder.&lt;/P&gt;&lt;P&gt;I've just tested this demo using two Tower kits with a NULL modem (Null modem cables have the Tx (&lt;EM&gt;transmit&lt;/EM&gt;) and Rx (&lt;EM&gt;Recieve&lt;/EM&gt;) lines crossed over, thereby allowing data to be sent from one device to the other: &lt;A href="http://www.webopedia.com/TERM/N/null_modem_cable.html"&gt;reference&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;Note that the IPC is using a UARTin the interrupt mode as the IPC communication link&amp;nbsp; so in your user_config.h header you need something like the following:&lt;/P&gt;&lt;P&gt;#define BSPCFG_ENABLE_TTYF 0&amp;nbsp;&amp;nbsp;&amp;nbsp; // &amp;lt;---polled mode disabled&lt;/P&gt;&lt;P&gt;#define BSPCFG_ENABLE_ITTYF 1&amp;nbsp;&amp;nbsp; //&amp;nbsp; &amp;lt;--Interrupt mode enabled&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Other #defines you need&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;#define MQX_IS_MULTI_PROCESSOR&amp;nbsp;&amp;nbsp; 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;#define MQX_USE_IPC&amp;nbsp; 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;SPAN class="mce_paste_marker"&gt;Since there is only one UART interface for each tower kit, you can either use the OSBDM debugger interface as a COM port or define the default for "iodebug:".&amp;nbsp; My example uses iodebug: for the TWR-K60F120M kit and the OSJTAG-COM via the OSBDM interface for the TWR-K60D100M kit.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;SPAN class="mce_paste_marker"&gt;I've attached ZIP with the modified file for CPU1 and CPU2 and the respective user_config.h and twrk60xxxx.h headers.&amp;nbsp; Again using MQX4.0.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must run the CPU2 project first, then boot/run the CPU1 project.&lt;/P&gt;&lt;P&gt;CPU2 project is then waiting for a message from CPU2 and once it receives it, will increment a variable and return it to thr sender/CPU1.&amp;nbsp; CPU2 is basically modifying the message and returning the message to CPU1.&lt;/P&gt;&lt;P&gt;CPU1 will send a message to CPU2.&amp;nbsp; Above explains what CPU2 does.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I added LED blinking to the CPU2 example so there is a visual indication the system is working.&lt;/P&gt;&lt;P&gt;For CPU1 I used the OSBDM COM port to watch the terminal output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the CPU1 has received 1000 messages, it terminate.&amp;nbsp; You can just press reset button on CPU1 and the communication starts again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 May 2013 14:38:28 GMT</pubDate>
    <dc:creator>DavidS</dc:creator>
    <dc:date>2013-05-09T14:38:28Z</dc:date>
    <item>
      <title>Anybody using ip-ip tunnels on MQX?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Anybody-using-ip-ip-tunnels-on-MQX/m-p/229553#M4854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is anybody using ip-ip tunnels on MQX? I am trying with MQX version 3.8.1 (with a Kinetis K60) but not having much success as there is very little documentation/sample code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Gary&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 May 2013 08:34:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Anybody-using-ip-ip-tunnels-on-MQX/m-p/229553#M4854</guid>
      <dc:creator>grixk60n512</dc:creator>
      <dc:date>2013-05-08T08:34:54Z</dc:date>
    </item>
    <item>
      <title>Re: Anybody using ip-ip tunnels on MQX?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Anybody-using-ip-ip-tunnels-on-MQX/m-p/229554#M4855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gary,&lt;/P&gt;&lt;P&gt;Are you asking about the MQX IPC (Inter Processor Communication)?&lt;/P&gt;&lt;P&gt;If yes the MQXUG.pdf in the MQX4.0/docs/mqx folder section 3.8 discusses IPC.&lt;/P&gt;&lt;P&gt;Section 3.8.4.5.4 references the example we have in MQX4.0/examples/ipc folder.&lt;/P&gt;&lt;P&gt;I've just tested this demo using two Tower kits with a NULL modem (Null modem cables have the Tx (&lt;EM&gt;transmit&lt;/EM&gt;) and Rx (&lt;EM&gt;Recieve&lt;/EM&gt;) lines crossed over, thereby allowing data to be sent from one device to the other: &lt;A href="http://www.webopedia.com/TERM/N/null_modem_cable.html"&gt;reference&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;Note that the IPC is using a UARTin the interrupt mode as the IPC communication link&amp;nbsp; so in your user_config.h header you need something like the following:&lt;/P&gt;&lt;P&gt;#define BSPCFG_ENABLE_TTYF 0&amp;nbsp;&amp;nbsp;&amp;nbsp; // &amp;lt;---polled mode disabled&lt;/P&gt;&lt;P&gt;#define BSPCFG_ENABLE_ITTYF 1&amp;nbsp;&amp;nbsp; //&amp;nbsp; &amp;lt;--Interrupt mode enabled&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Other #defines you need&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;#define MQX_IS_MULTI_PROCESSOR&amp;nbsp;&amp;nbsp; 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;#define MQX_USE_IPC&amp;nbsp; 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;SPAN class="mce_paste_marker"&gt;Since there is only one UART interface for each tower kit, you can either use the OSBDM debugger interface as a COM port or define the default for "iodebug:".&amp;nbsp; My example uses iodebug: for the TWR-K60F120M kit and the OSJTAG-COM via the OSBDM interface for the TWR-K60D100M kit.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;SPAN class="mce_paste_marker"&gt;I've attached ZIP with the modified file for CPU1 and CPU2 and the respective user_config.h and twrk60xxxx.h headers.&amp;nbsp; Again using MQX4.0.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must run the CPU2 project first, then boot/run the CPU1 project.&lt;/P&gt;&lt;P&gt;CPU2 project is then waiting for a message from CPU2 and once it receives it, will increment a variable and return it to thr sender/CPU1.&amp;nbsp; CPU2 is basically modifying the message and returning the message to CPU1.&lt;/P&gt;&lt;P&gt;CPU1 will send a message to CPU2.&amp;nbsp; Above explains what CPU2 does.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I added LED blinking to the CPU2 example so there is a visual indication the system is working.&lt;/P&gt;&lt;P&gt;For CPU1 I used the OSBDM COM port to watch the terminal output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the CPU1 has received 1000 messages, it terminate.&amp;nbsp; You can just press reset button on CPU1 and the communication starts again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 May 2013 14:38:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Anybody-using-ip-ip-tunnels-on-MQX/m-p/229554#M4855</guid>
      <dc:creator>DavidS</dc:creator>
      <dc:date>2013-05-09T14:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: Anybody using ip-ip tunnels on MQX?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Anybody-using-ip-ip-tunnels-on-MQX/m-p/229555#M4856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi David&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for all the info, not quite what I had in mind. But I have managed to come up with a solution. I think that I need to switch to MQX 4.0 quite soon.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Gary&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 May 2013 06:50:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Anybody-using-ip-ip-tunnels-on-MQX/m-p/229555#M4856</guid>
      <dc:creator>grixk60n512</dc:creator>
      <dc:date>2013-05-10T06:50:15Z</dc:date>
    </item>
  </channel>
</rss>

