<?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_DeInit API Error in S32K</title>
    <link>https://community.nxp.com/t5/S32K/CAN-DeInit-API-Error/m-p/2190903#M53758</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/213197"&gt;@Embedded_novice&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;1. The controller modes are defined in the AUTOSAR specification, thus described in the FlexCAN MCAL driver user manual found under the following path: "&lt;STRONG&gt;C:\NXP\S32DS.3.X.X\S32DS\software\PlatformSDK_S32K3\RTD\Can_43_FLEXCAN\doc\RTD_CAN_43_FLEXCAN_UM.pdf&lt;/STRONG&gt;"&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Snag_a0158d5.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/362154iC909B41A57E9BC49/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Snag_a0158d5.png" alt="Snag_a0158d5.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;2. By AUTOSAR standards, yes, it is mandatory. The processing logic depends on the driver implementation. For example, in the FlexCAN driver, functions called are&amp;nbsp;&lt;SPAN&gt;FlexCAN_Ip_SetStartMode() and&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;FlexCAN_Ip_SetStopMode(), both of which enable and disable the module, respectively.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;AUTOSAR specification also provides a transition diagram in their CAN specification document:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Snag_a0e08b2.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/362155i2F6D00495DE4E6C0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Snag_a0e08b2.png" alt="Snag_a0e08b2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Julián&lt;/P&gt;</description>
    <pubDate>Wed, 22 Oct 2025 16:40:55 GMT</pubDate>
    <dc:creator>Julián_AragónM</dc:creator>
    <dc:date>2025-10-22T16:40:55Z</dc:date>
    <item>
      <title>CAN_DeInit API Error</title>
      <link>https://community.nxp.com/t5/S32K/CAN-DeInit-API-Error/m-p/2189148#M53682</link>
      <description>&lt;P&gt;HI.&lt;/P&gt;&lt;P&gt;I attempted to shut down the CAN controller before the BOOTLOADER jumped to the APP, but when I called CAN_DeInit, it actually wasn't re-initialized, resulting in incorrect frames being sent on the CAN bus after the jump. I would like to know if there are any problems with this logical judgment. I have set CtrlState to TRUE, but the reverse initialization requires it to be FALSE in order to execute.&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="CAN_DeInit.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/361650i4E55AA0680B38758/image-size/large?v=v2&amp;amp;px=999" role="button" title="CAN_DeInit.png" alt="CAN_DeInit.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Oct 2025 10:38:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/CAN-DeInit-API-Error/m-p/2189148#M53682</guid>
      <dc:creator>Embedded_novice</dc:creator>
      <dc:date>2025-10-20T10:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: CAN_DeInit API Error</title>
      <link>https://community.nxp.com/t5/S32K/CAN-DeInit-API-Error/m-p/2190147#M53733</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/213197"&gt;@Embedded_novice&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Before calling CAN_DeInit, set all controllers to STOPPED to allow it to de-init properly:&lt;/P&gt;
&lt;LI-CODE lang="c"&gt;/* Stop Can controller */
Can_43_FLEXCAN_SetControllerMode(Can_43_FLEXCANConf_CanController_CanController_0, CAN_CS_STOPPED);

/* De-Initialize Can driver */
Can_43_FLEXCAN_DeInit();&lt;/LI-CODE&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Julián&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2025 17:44:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/CAN-DeInit-API-Error/m-p/2190147#M53733</guid>
      <dc:creator>Julián_AragónM</dc:creator>
      <dc:date>2025-10-21T17:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: CAN_DeInit API Error</title>
      <link>https://community.nxp.com/t5/S32K/CAN-DeInit-API-Error/m-p/2190348#M53737</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;I understand your train of thought now. I would like to know if this state transition diagram is correct. Additionally, I have two more questions:&lt;BR /&gt;1. Where can I find this state transition in the manual of the MCU? I didn't see any similar state description in the RM.&lt;BR /&gt;2. Is this state transition mandatory? Is the same processing logic applied in other MCU architectures?&lt;BR /&gt;Thank you very much for your help!&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ModeSwitch.png" style="width: 844px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/361982iEC375E02605EABA1/image-size/large?v=v2&amp;amp;px=999" role="button" title="ModeSwitch.png" alt="ModeSwitch.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Oct 2025 01:56:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/CAN-DeInit-API-Error/m-p/2190348#M53737</guid>
      <dc:creator>Embedded_novice</dc:creator>
      <dc:date>2025-10-22T01:56:56Z</dc:date>
    </item>
    <item>
      <title>Re: CAN_DeInit API Error</title>
      <link>https://community.nxp.com/t5/S32K/CAN-DeInit-API-Error/m-p/2190903#M53758</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/213197"&gt;@Embedded_novice&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;1. The controller modes are defined in the AUTOSAR specification, thus described in the FlexCAN MCAL driver user manual found under the following path: "&lt;STRONG&gt;C:\NXP\S32DS.3.X.X\S32DS\software\PlatformSDK_S32K3\RTD\Can_43_FLEXCAN\doc\RTD_CAN_43_FLEXCAN_UM.pdf&lt;/STRONG&gt;"&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Snag_a0158d5.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/362154iC909B41A57E9BC49/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Snag_a0158d5.png" alt="Snag_a0158d5.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;2. By AUTOSAR standards, yes, it is mandatory. The processing logic depends on the driver implementation. For example, in the FlexCAN driver, functions called are&amp;nbsp;&lt;SPAN&gt;FlexCAN_Ip_SetStartMode() and&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;FlexCAN_Ip_SetStopMode(), both of which enable and disable the module, respectively.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;AUTOSAR specification also provides a transition diagram in their CAN specification document:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Snag_a0e08b2.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/362155i2F6D00495DE4E6C0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Snag_a0e08b2.png" alt="Snag_a0e08b2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Julián&lt;/P&gt;</description>
      <pubDate>Wed, 22 Oct 2025 16:40:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/CAN-DeInit-API-Error/m-p/2190903#M53758</guid>
      <dc:creator>Julián_AragónM</dc:creator>
      <dc:date>2025-10-22T16:40:55Z</dc:date>
    </item>
  </channel>
</rss>

