<?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: When porting bootloader program, can message can be received but not sent. in S32K</title>
    <link>https://community.nxp.com/t5/S32K/When-porting-bootloader-program-can-message-can-be-received-but/m-p/1369208#M12723</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;the state&amp;nbsp;&lt;SPAN&gt;flexcan_ MB_ Busy indicates the prepared message is still not successfully transmitted. Question could be why? Lets assume CAN transceiver&amp;nbsp;circuitry is right and transceiver is active. Maybe some errors are detected, like ACK, bit error. If yes, it could be e.g. due to CAN bit setting. If no errors are detected, is the MB's mask interrupt bit still set? If not, I think the only option to leave this within code is to Abort the message using the respective API.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;BR, Petr&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 10 Nov 2021 10:11:06 GMT</pubDate>
    <dc:creator>PetrS</dc:creator>
    <dc:date>2021-11-10T10:11:06Z</dc:date>
    <item>
      <title>When porting bootloader program, can message can be received but not sent.</title>
      <link>https://community.nxp.com/t5/S32K/When-porting-bootloader-program-can-message-can-be-received-but/m-p/1367786#M12678</link>
      <description>&lt;P&gt;When debugging to flexcan_ Flexcan under driver. C_ StaterSendData()--&amp;lt;if(state-&amp;gt;mbs[mb_idx].state)!= FLEXCAN_ MB_ Idle &amp;gt;, the actual state is flexcan_ MB_ Busy, how to solve this problem?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Nov 2021 08:51:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/When-porting-bootloader-program-can-message-can-be-received-but/m-p/1367786#M12678</guid>
      <dc:creator>yanren</dc:creator>
      <dc:date>2021-11-08T08:51:06Z</dc:date>
    </item>
    <item>
      <title>Re: When porting bootloader program, can message can be received but not sent.</title>
      <link>https://community.nxp.com/t5/S32K/When-porting-bootloader-program-can-message-can-be-received-but/m-p/1369208#M12723</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;the state&amp;nbsp;&lt;SPAN&gt;flexcan_ MB_ Busy indicates the prepared message is still not successfully transmitted. Question could be why? Lets assume CAN transceiver&amp;nbsp;circuitry is right and transceiver is active. Maybe some errors are detected, like ACK, bit error. If yes, it could be e.g. due to CAN bit setting. If no errors are detected, is the MB's mask interrupt bit still set? If not, I think the only option to leave this within code is to Abort the message using the respective API.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;BR, Petr&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Nov 2021 10:11:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/When-porting-bootloader-program-can-message-can-be-received-but/m-p/1369208#M12723</guid>
      <dc:creator>PetrS</dc:creator>
      <dc:date>2021-11-10T10:11:06Z</dc:date>
    </item>
    <item>
      <title>Re: When porting bootloader program, can message can be received but not sent.</title>
      <link>https://community.nxp.com/t5/S32K/When-porting-bootloader-program-can-message-can-be-received-but/m-p/1372264#M12815</link>
      <description>&lt;P&gt;I have solved this problem, because the sending status is modified in advance by other functions, resulting in that the information can be received and cannot be sent.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Nov 2021 01:17:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/When-porting-bootloader-program-can-message-can-be-received-but/m-p/1372264#M12815</guid>
      <dc:creator>yanren</dc:creator>
      <dc:date>2021-11-17T01:17:11Z</dc:date>
    </item>
  </channel>
</rss>

