<?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: CAN RTR feature in S12 / MagniV Microcontrollers</title>
    <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133424#M1878</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Dear Lundin,&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;You said&lt;/STRONG&gt; &lt;EM&gt;: Think of it... how would the hardware know how to respond to a RTR frame?&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;For example PIC18F2480 says that:&lt;/STRONG&gt; &lt;FONT face="Helvetica" size="2"&gt;&lt;/FONT&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="2"&gt;23.2.3.1 Programmable TX/RX and&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="2"&gt;Auto-RTR Buffers&lt;/FONT&gt;&lt;/P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;/FONT&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;The ECAN module contains 6 message buffers that can be programmed as transmit or receive buffers. Any of&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;these buffers can also be programmed to &lt;FONT color="#FF3300"&gt;automatically&lt;/FONT&gt; handle RTR messages.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="3"&gt;&lt;STRONG&gt;&lt;FONT face="Arial" size="2"&gt;Another example that&amp;nbsp; Daniel says that&lt;/FONT&gt; :&lt;/STRONG&gt;&lt;/FONT&gt; &lt;FONT size="2"&gt;&lt;EM&gt;automatic RTR reply is supported by FlexCAN modules (e.g. on power PC or new DSC devices) but not by the simpler MSCAN module&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="2"&gt;&lt;STRONG&gt;So these means that hardware RTR is possible but not in MSCAN (that was the right answer!)&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="2"&gt;&lt;STRONG&gt;You said :&lt;/STRONG&gt; &lt;EM&gt;Are you suggesting that there should be an 8 byte hardware data buffer for every&lt;BR /&gt;possible identifier on the bus...?&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="2"&gt;&lt;EM&gt;&lt;STRONG&gt;&lt;U&gt;Dear Lundin I don't suggest anything. There was a simple question and that was about supporting or not supporting hardware RTR. The answer is also very simple. "No hardware support"&amp;nbsp;,as freescale's technical support said:&lt;/U&gt;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="2"&gt;&lt;BR /&gt;There is no internal HW mechanism which recognize data/remote frame. It has to be done by user SW. by Ladislav&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="2"&gt;My Problem was not in receiving these remote frames but in interrupting the CPU by these frames. However, thanks for your interest and trying to help with this question.&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 May 2007 20:37:51 GMT</pubDate>
    <dc:creator>BFS</dc:creator>
    <dc:date>2007-05-23T20:37:51Z</dc:date>
    <item>
      <title>CAN RTR feature</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133421#M1875</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Hi,&lt;/DIV&gt;&lt;DIV&gt;We tried to use RTR feature. Sending RTR frames is OK, but I can't send RTR answer frame automatically (by hardware support).&lt;/DIV&gt;&lt;DIV&gt;MSCAN user manual says that:&lt;/DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Times New Roman';"&gt;&lt;EM&gt;This flag reflects the status of the Remote Transmission Request bit in the CAN frame. In the case of&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Times New Roman';"&gt;&lt;EM&gt;a receive buffer, it indicates the status of the received frame and supports the transmission of an&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Times New Roman';"&gt;&lt;EM&gt;answering frame in &lt;STRONG style=": ; color: #ff0000; text-decoration: underline;"&gt;software&lt;/STRONG&gt;. In the case of a transmit buffer, this flag defines the setting of the RTR&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Times New Roman';"&gt;&lt;EM&gt;bit to be sent.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style=": ; font-size: 3; font-family: Arial;"&gt;What is the meaning of software? (Does freescale MSCAN not support automatic RTR answering?)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style=": ; font-size: 3; font-family: Arial;"&gt;Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 May 2007 22:20:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133421#M1875</guid>
      <dc:creator>BFS</dc:creator>
      <dc:date>2007-05-10T22:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: CAN RTR feature</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133422#M1876</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Think of it... how would the hardware know how to respond to a RTR frame? Are you suggesting that there should be an 8 byte hardware data buffer for every possible identifier on the bus...? What would be the point in letting the hardware do this? Maybe you would get a slight gain in speed, I see no other purpose.&lt;BR /&gt;&lt;BR /&gt;Also, correct me if I'm wrong, but I believe that the MSCAN hardware signals for a new frame after it has checked the End-of-frame. That gives the app at least 3 CAN-bus cycles of intermission frame space to react and produce a high-priority frame. Unless you have a very high baudrate on the bus, that should be no match for the CPU. With a standard baudrate of 125kbps and a HCS12 running with 8MHz, you'd have 384 cpu ticks to finish the task.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 May 2007 15:56:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133422#M1876</guid>
      <dc:creator>Lundin</dc:creator>
      <dc:date>2007-05-16T15:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: CAN RTR feature</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133423#M1877</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;automatic RTR reply is supported by FlexCAN modules (e.g. on power PC or new DSC devices) but not by the simpler MSCAN module&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;BR /&gt;Daniel&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 May 2007 22:15:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133423#M1877</guid>
      <dc:creator>DanielM</dc:creator>
      <dc:date>2007-05-17T22:15:58Z</dc:date>
    </item>
    <item>
      <title>Re: CAN RTR feature</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133424#M1878</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Dear Lundin,&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;You said&lt;/STRONG&gt; &lt;EM&gt;: Think of it... how would the hardware know how to respond to a RTR frame?&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;For example PIC18F2480 says that:&lt;/STRONG&gt; &lt;FONT face="Helvetica" size="2"&gt;&lt;/FONT&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="2"&gt;23.2.3.1 Programmable TX/RX and&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="2"&gt;Auto-RTR Buffers&lt;/FONT&gt;&lt;/P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;/FONT&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;The ECAN module contains 6 message buffers that can be programmed as transmit or receive buffers. Any of&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;these buffers can also be programmed to &lt;FONT color="#FF3300"&gt;automatically&lt;/FONT&gt; handle RTR messages.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="3"&gt;&lt;STRONG&gt;&lt;FONT face="Arial" size="2"&gt;Another example that&amp;nbsp; Daniel says that&lt;/FONT&gt; :&lt;/STRONG&gt;&lt;/FONT&gt; &lt;FONT size="2"&gt;&lt;EM&gt;automatic RTR reply is supported by FlexCAN modules (e.g. on power PC or new DSC devices) but not by the simpler MSCAN module&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="2"&gt;&lt;STRONG&gt;So these means that hardware RTR is possible but not in MSCAN (that was the right answer!)&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="2"&gt;&lt;STRONG&gt;You said :&lt;/STRONG&gt; &lt;EM&gt;Are you suggesting that there should be an 8 byte hardware data buffer for every&lt;BR /&gt;possible identifier on the bus...?&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="2"&gt;&lt;EM&gt;&lt;STRONG&gt;&lt;U&gt;Dear Lundin I don't suggest anything. There was a simple question and that was about supporting or not supporting hardware RTR. The answer is also very simple. "No hardware support"&amp;nbsp;,as freescale's technical support said:&lt;/U&gt;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="Helvetica" size="1"&gt;&lt;FONT size="2"&gt;&lt;BR /&gt;There is no internal HW mechanism which recognize data/remote frame. It has to be done by user SW. by Ladislav&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="2"&gt;My Problem was not in receiving these remote frames but in interrupting the CPU by these frames. However, thanks for your interest and trying to help with this question.&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 May 2007 20:37:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133424#M1878</guid>
      <dc:creator>BFS</dc:creator>
      <dc:date>2007-05-23T20:37:51Z</dc:date>
    </item>
    <item>
      <title>Re: CAN RTR feature</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133425#M1879</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;hi ,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I am facing problem while handling interrupts in MC9S12XDP512 for codewarrior IDE i am not using XGATE.the linker file generated by it is not supporting the vector.c file which contains interrupt handling routines.so i need to write my own linker file can u suggest me ways how to write my own linker file to keep my own files and routines of interrupt in linker file in desired locations so please suggest me ways i am facing this problem from a weeek please show me some path.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;thanks in advance&lt;/DIV&gt;&lt;DIV&gt;bye&lt;/DIV&gt;&lt;DIV&gt;sunil&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jun 2007 14:12:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133425#M1879</guid>
      <dc:creator>sunil99</dc:creator>
      <dc:date>2007-06-01T14:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: CAN RTR feature</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133426#M1880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Sunil posted a new thread with this question.&lt;BR /&gt;See&amp;nbsp;&amp;nbsp; &lt;A class="subj_read" href="http://forums.freescale.com/message?board.id=16BITCOMM&amp;amp;message.id=3969" rel="nofollow" target="_blank"&gt;using code warrior for MC9S12XDP512 how to write my own linker file for it. i am not using XGATE&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jun 2007 15:16:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/CAN-RTR-feature/m-p/133426#M1880</guid>
      <dc:creator>Alban</dc:creator>
      <dc:date>2007-06-01T15:16:50Z</dc:date>
    </item>
  </channel>
</rss>

