<?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>S32K中的主题 Bus-off management using AUTOSAR with RTD</title>
    <link>https://community.nxp.com/t5/S32K/Bus-off-management-using-AUTOSAR-with-RTD/m-p/1426987#M14395</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I try to implement automatic bus-off recovery using RTD AUTOSAR driver (CAN.h).&lt;/P&gt;&lt;P&gt;I didn't find documentation, but I tried lots of configuration. My findings are :&lt;/P&gt;&lt;P&gt;-&amp;nbsp;For automatic bus-off recovery, peripheral option "Can Auto BusOff Recovery" must be checked and bus-off interruption must be disabled. In this case the communication recover automatically after a short cut&amp;nbsp; between CAN_L and CAN_H, it's what I need, &lt;EM&gt;BUT&lt;/EM&gt; I have no way to transmit the Bus Off state to the application in order to log the error state -&amp;gt; Do I miss something ?&lt;/P&gt;&lt;P&gt;- For&amp;nbsp;manual bus-off recovery,&amp;nbsp;peripheral option "Can Auto BusOff Recovery" could be checked or unchecked, but BUS-OFF interrupt shall be enabled in order to restart the CAN communication. It's ok for me, because I can log the error and restart the communication when I want.&lt;/P&gt;&lt;P&gt;In both cases, using interruption will put automatically the controller in stopped state, it this a requirement of AUTOSAR driver ?&lt;/P&gt;&lt;P&gt;Thanks for your help&lt;/P&gt;</description>
    <pubDate>Fri, 11 Mar 2022 15:45:40 GMT</pubDate>
    <dc:creator>BeCy</dc:creator>
    <dc:date>2022-03-11T15:45:40Z</dc:date>
    <item>
      <title>Bus-off management using AUTOSAR with RTD</title>
      <link>https://community.nxp.com/t5/S32K/Bus-off-management-using-AUTOSAR-with-RTD/m-p/1426987#M14395</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I try to implement automatic bus-off recovery using RTD AUTOSAR driver (CAN.h).&lt;/P&gt;&lt;P&gt;I didn't find documentation, but I tried lots of configuration. My findings are :&lt;/P&gt;&lt;P&gt;-&amp;nbsp;For automatic bus-off recovery, peripheral option "Can Auto BusOff Recovery" must be checked and bus-off interruption must be disabled. In this case the communication recover automatically after a short cut&amp;nbsp; between CAN_L and CAN_H, it's what I need, &lt;EM&gt;BUT&lt;/EM&gt; I have no way to transmit the Bus Off state to the application in order to log the error state -&amp;gt; Do I miss something ?&lt;/P&gt;&lt;P&gt;- For&amp;nbsp;manual bus-off recovery,&amp;nbsp;peripheral option "Can Auto BusOff Recovery" could be checked or unchecked, but BUS-OFF interrupt shall be enabled in order to restart the CAN communication. It's ok for me, because I can log the error and restart the communication when I want.&lt;/P&gt;&lt;P&gt;In both cases, using interruption will put automatically the controller in stopped state, it this a requirement of AUTOSAR driver ?&lt;/P&gt;&lt;P&gt;Thanks for your help&lt;/P&gt;</description>
      <pubDate>Fri, 11 Mar 2022 15:45:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Bus-off-management-using-AUTOSAR-with-RTD/m-p/1426987#M14395</guid>
      <dc:creator>BeCy</dc:creator>
      <dc:date>2022-03-11T15:45:40Z</dc:date>
    </item>
    <item>
      <title>Re: Bus-off management using AUTOSAR with RTD</title>
      <link>https://community.nxp.com/t5/S32K/Bus-off-management-using-AUTOSAR-with-RTD/m-p/1895661#M36988</link>
      <description>&lt;P&gt;Hi, I had the same problem, did you solve it?&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2024 05:40:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Bus-off-management-using-AUTOSAR-with-RTD/m-p/1895661#M36988</guid>
      <dc:creator>JuXinyang</dc:creator>
      <dc:date>2024-06-28T05:40:04Z</dc:date>
    </item>
  </channel>
</rss>

