<?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 abort CAN trans in S12 / MagniV Microcontrollers</title>
    <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/abort-CAN-trans/m-p/661141#M13964</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am using a 9S12XEQ384 and a 9s12DG256 with the same code for CAN initialisation at 500K baud and processing interrupts.&amp;nbsp; Both processors do the same as far as CAN retry.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The problem I want to solve is that sometimes I can upset the bus and it will retry a transmission about 150us after the last failure to send.&amp;nbsp; This never gives the bus any chance to send any other messages.&amp;nbsp; It never goes buss off.&amp;nbsp; From what I understand it should leave the bus alone for around 2.8ms.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to abort the CAN messages I have pending, but I don't think my processor should take over the bus.&lt;/P&gt;&lt;P&gt;Is there something in my initialisation that may cause this.&amp;nbsp; Is there an auto off bus recovery I am missing?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can see the transmit and receive error counters go up to about 130 to 135 when the above happens. &amp;nbsp; Should it not get to 254 and go bus off?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Wade Whitehorn&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 Feb 2017 14:51:14 GMT</pubDate>
    <dc:creator>dastek</dc:creator>
    <dc:date>2017-02-01T14:51:14Z</dc:date>
    <item>
      <title>abort CAN trans</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/abort-CAN-trans/m-p/661141#M13964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am using a 9S12XEQ384 and a 9s12DG256 with the same code for CAN initialisation at 500K baud and processing interrupts.&amp;nbsp; Both processors do the same as far as CAN retry.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The problem I want to solve is that sometimes I can upset the bus and it will retry a transmission about 150us after the last failure to send.&amp;nbsp; This never gives the bus any chance to send any other messages.&amp;nbsp; It never goes buss off.&amp;nbsp; From what I understand it should leave the bus alone for around 2.8ms.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to abort the CAN messages I have pending, but I don't think my processor should take over the bus.&lt;/P&gt;&lt;P&gt;Is there something in my initialisation that may cause this.&amp;nbsp; Is there an auto off bus recovery I am missing?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can see the transmit and receive error counters go up to about 130 to 135 when the above happens. &amp;nbsp; Should it not get to 254 and go bus off?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Wade Whitehorn&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Feb 2017 14:51:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/abort-CAN-trans/m-p/661141#M13964</guid>
      <dc:creator>dastek</dc:creator>
      <dc:date>2017-02-01T14:51:14Z</dc:date>
    </item>
    <item>
      <title>Re: abort CAN trans</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/abort-CAN-trans/m-p/661142#M13965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;it is an alchemy. However,...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually we have met following issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) There are incompatible CAN interface ICs used for physical CAN bus. Only devices with the same electrical and timing characteristics are able to communicate.&lt;/P&gt;&lt;P&gt;2) Wrong communication speed design. &lt;/P&gt;&lt;P&gt;3) Wrong SW approach. (I have attached SW examples which can help you to compare or test the system)&lt;/P&gt;&lt;P&gt;4) Have you tried to use CAN in loopback mode to check SW?&lt;/P&gt;&lt;P&gt;5) Wrong PCB design. There could be some EMI which affect CAN bus. Please check by oscilloscope signals at CAN bus and also at MCU’s CAN pins.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reference manual - MC9S12XEP100&lt;/P&gt;&lt;P&gt;register - CANCTL1&lt;/P&gt;&lt;P&gt;bit - BORM&lt;BR /&gt;Bus-Off Recovery Mode — This bit configures the bus-off state recovery mode of the MSCAN. Refer to&lt;BR /&gt;Section 16.5.2, “Bus-Off Recovery,” for details.&lt;BR /&gt;0 Automatic bus-off recovery (see Bosch CAN 2.0A/B protocol specification)&lt;/P&gt;&lt;P&gt;1 Bus-off recovery upon user request&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I am not able to detect error correctly the standard approach of mine to detect an error is following:&lt;/P&gt;&lt;P&gt;1) loopback mode&lt;/P&gt;&lt;P&gt;2) 2 nodes at the same MCU connected by R/diode described (no interface IC)&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.mikrocontroller.net/attachment/28831/siemens_AP2921.pdf"&gt;http://www.mikrocontroller.net/attachment/28831/siemens_AP2921.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;3) No interface solution from item 2 between two devices&lt;/P&gt;&lt;P&gt;4) Interface IC solution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regrads,&lt;/P&gt;&lt;P&gt;Ladislav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Feb 2017 10:27:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/abort-CAN-trans/m-p/661142#M13965</guid>
      <dc:creator>lama</dc:creator>
      <dc:date>2017-02-02T10:27:15Z</dc:date>
    </item>
  </channel>
</rss>

