<?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 Why is status set to kStatus_FLEXCAN_UnHandled  in callback in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Why-is-status-set-to-kStatus-FLEXCAN-UnHandled-in-callback/m-p/1180312#M58764</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm working on a recieve only CAN application that reads data from a sensor.&lt;/P&gt;&lt;P&gt;I planned to retrieve data with &lt;EM&gt;FLEXCAN_TransferReceiveNonBlocking&lt;/EM&gt; but realized that &lt;EM&gt;status is constantly set to kStatus_FLEXCAN_RxBusy &lt;/EM&gt;even with no sensor connected at all. A call to &lt;EM&gt;FLEXCAN_TransferHandleIRQ&lt;/EM&gt;(EXAMPLE_CAN, &amp;amp;flexcanHandle); will invoke the callback with status set to &lt;EM&gt;kStatus_FLEXCAN_UnHandled. S&lt;/EM&gt;omething obviously seems to be wrong, does anyone have any hints how to best troubleshoot this? The callback looks like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;static void flexcan_callback(CAN_Type *base, flexcan_handle_t *handle, status_t status, uint32_t result, void *userData)
{
    switch (status)
    {
        /* Process FlexCAN Rx event. */
        case kStatus_FLEXCAN_RxIdle:
            if (RX_MESSAGE_BUFFER_NUM == result) {
                rxComplete = true;
            }
            LOG_INFO("kStatus_FLEXCAN_RxIdle\r\n");
            break;
        case kStatus_FLEXCAN_UnHandled:
        	LOG_INFO("kStatus_FLEXCAN_UnHandled\r\n");
        	break;
        default:
        	LOG_INFO("in flexcan_cb, status 0x%x(%d)\r\n",status,status);
    }

}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 10 Nov 2020 23:59:46 GMT</pubDate>
    <dc:creator>stdcerr</dc:creator>
    <dc:date>2020-11-10T23:59:46Z</dc:date>
    <item>
      <title>Why is status set to kStatus_FLEXCAN_UnHandled  in callback</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Why-is-status-set-to-kStatus-FLEXCAN-UnHandled-in-callback/m-p/1180312#M58764</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm working on a recieve only CAN application that reads data from a sensor.&lt;/P&gt;&lt;P&gt;I planned to retrieve data with &lt;EM&gt;FLEXCAN_TransferReceiveNonBlocking&lt;/EM&gt; but realized that &lt;EM&gt;status is constantly set to kStatus_FLEXCAN_RxBusy &lt;/EM&gt;even with no sensor connected at all. A call to &lt;EM&gt;FLEXCAN_TransferHandleIRQ&lt;/EM&gt;(EXAMPLE_CAN, &amp;amp;flexcanHandle); will invoke the callback with status set to &lt;EM&gt;kStatus_FLEXCAN_UnHandled. S&lt;/EM&gt;omething obviously seems to be wrong, does anyone have any hints how to best troubleshoot this? The callback looks like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;static void flexcan_callback(CAN_Type *base, flexcan_handle_t *handle, status_t status, uint32_t result, void *userData)
{
    switch (status)
    {
        /* Process FlexCAN Rx event. */
        case kStatus_FLEXCAN_RxIdle:
            if (RX_MESSAGE_BUFFER_NUM == result) {
                rxComplete = true;
            }
            LOG_INFO("kStatus_FLEXCAN_RxIdle\r\n");
            break;
        case kStatus_FLEXCAN_UnHandled:
        	LOG_INFO("kStatus_FLEXCAN_UnHandled\r\n");
        	break;
        default:
        	LOG_INFO("in flexcan_cb, status 0x%x(%d)\r\n",status,status);
    }

}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 10 Nov 2020 23:59:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Why-is-status-set-to-kStatus-FLEXCAN-UnHandled-in-callback/m-p/1180312#M58764</guid>
      <dc:creator>stdcerr</dc:creator>
      <dc:date>2020-11-10T23:59:46Z</dc:date>
    </item>
    <item>
      <title>Re: Why is status set to kStatus_FLEXCAN_UnHandled  in callback</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Why-is-status-set-to-kStatus-FLEXCAN-UnHandled-in-callback/m-p/1180969#M58776</link>
      <description>&lt;P&gt;Okay,&lt;/P&gt;&lt;P&gt;I see now that a call to FLEXCAN_TransferHandleIRQ(EXAMPLE_CAN, &amp;amp;flexcanHandle) triggers my callback with &lt;EM&gt;status&lt;/EM&gt; set to &lt;EM&gt;kStatus_FLEXCAN_UnHandled&lt;/EM&gt; and I also realized that a call to FLEXCAN_TransferReceiveNonBlocking() continously sets &lt;EM&gt;status&lt;/EM&gt; to &lt;EM&gt;kStatus_FLEXCAN_RxBusy &lt;/EM&gt;while &lt;EM&gt;mbState&lt;/EM&gt; of my mailbox is set to 1 (&lt;EM&gt;kFLEXCAN_StateRxData&lt;/EM&gt;) when I pause execution in the callback (that got called with status &lt;EM&gt;UnHandled&lt;/EM&gt;).&lt;/P&gt;&lt;P&gt;My callback never gets called with &lt;EM&gt;kStatus_FLEXCAN_RxIdle &lt;/EM&gt;even though I have something like (and I know that my sensor is continually sending out CAN frames at 250kb/s, I have a monitor connected to the same wires):&lt;/P&gt;&lt;PRE&gt;while (!rxComplete) {&lt;BR /&gt;(void)FLEXCAN_TransferReceiveNonBlocking(EXAMPLE_CAN, &amp;amp;flexcanHandle, &amp;amp;rxXfer);&lt;BR /&gt;FLEXCAN_TransferHandleIRQ(EXAMPLE_CAN, &amp;amp;flexcanHandle);&lt;BR /&gt;}&lt;/PRE&gt;&lt;P&gt;where rxComplete is set true in the callback (when called with &lt;EM&gt;kStatus_FLEXCAN_RxIdle&lt;/EM&gt;).&lt;/P&gt;</description>
      <pubDate>Wed, 11 Nov 2020 17:12:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Why-is-status-set-to-kStatus-FLEXCAN-UnHandled-in-callback/m-p/1180969#M58776</guid>
      <dc:creator>stdcerr</dc:creator>
      <dc:date>2020-11-11T17:12:31Z</dc:date>
    </item>
  </channel>
</rss>

