<?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: remote proc kick failed when rpmsg is launched by U-Boot in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/remote-proc-kick-failed-when-rpmsg-is-launched-by-U-Boot/m-p/2190952#M241584</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/201524"&gt;@hfranco&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope you are doing very well.&lt;/P&gt;
&lt;P&gt;Could you please clarify the processor you are using, BSP version, SDK version and if possible if you are using an EVK from NXP?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Salas.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Oct 2025 18:35:49 GMT</pubDate>
    <dc:creator>Manuel_Salas</dc:creator>
    <dc:date>2025-10-22T18:35:49Z</dc:date>
    <item>
      <title>remote proc kick failed when rpmsg is launched by U-Boot</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/remote-proc-kick-failed-when-rpmsg-is-launched-by-U-Boot/m-p/2189290#M241512</link>
      <description>&lt;DIV class=""&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;When the rpmsg_lite_str_echo demo from MCUXpresso is launched by the remoteproc framework, the RPMSG&lt;/DIV&gt;&lt;DIV class=""&gt;demo works fine, the channel is created and I can send messages between the two cores using /dev/ttyRPMSG30 endpoint.&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;However, when it is launched by U-Boot bootaux command, when the imx_rpmsg_tty demo driver is modprobed,&lt;/DIV&gt;&lt;DIV class=""&gt;the following &amp;nbsp;error happens:&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp; &amp;nbsp; root@colibri-imx8x-06858909:~# modprobe imx_rpmsg_tty&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp; &amp;nbsp; [ 23.060068] imx_rpmsg_tty virtio1.rpmsg-openamp-demo-channel.-1.30: new channel: 0x400 -&amp;gt; 0x1e!&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp; &amp;nbsp; [ 23.069286] Install rpmsg tty driver!&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp; &amp;nbsp; [ 23.174246] imx-rproc imx8x-cm4: imx_rproc_kick: failed (3, err:-62)&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp; &amp;nbsp; root@colibri-imx8x-06858909:~# echo "teste" &amp;gt;/dev/ttyRPMSG30&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp; &amp;nbsp; [ 52.578255] imx-rproc imx8x-cm4: imx_rproc_kick: failed (3, err:-62)&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp; &amp;nbsp; [ 52.686242] imx-rproc imx8x-cm4: imx_rproc_kick: failed (3, err:-62)&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;The code returns TIMER EXPIRED (-62) at (imx_rproc.c)&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;      /*&lt;/DIV&gt;&lt;DIV class=""&gt;       * Send the index of the triggered virtqueue as the mu payload.&lt;/DIV&gt;&lt;DIV class=""&gt;       * Let remote processor know which virtqueue is used.&lt;/DIV&gt;&lt;DIV class=""&gt;       */&lt;/DIV&gt;&lt;DIV class=""&gt;      mmsg = vqid &amp;lt;&amp;lt; 16;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;      err = mbox_send_message(priv-&amp;gt;tx_ch, (void *)&amp;amp;mmsg);&lt;/DIV&gt;&lt;DIV class=""&gt;      if (err &amp;lt; 0)&lt;/DIV&gt;&lt;DIV class=""&gt;            dev_err(priv-&amp;gt;dev, "%s: failed (%d, err:%d)\n",&lt;/DIV&gt;&lt;DIV class=""&gt;                  __func__, vqid, err);&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;where (mailbox.c):&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;      if (chan-&amp;gt;cl-&amp;gt;tx_block) {&lt;/DIV&gt;&lt;DIV class=""&gt;            unsigned long wait;&lt;/DIV&gt;&lt;DIV class=""&gt;            int ret;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;            if (!chan-&amp;gt;cl-&amp;gt;tx_tout) /* wait forever */&lt;/DIV&gt;&lt;DIV class=""&gt;                  wait = msecs_to_jiffies(3600000);&lt;/DIV&gt;&lt;DIV class=""&gt;            else&lt;/DIV&gt;&lt;DIV class=""&gt;                  wait = msecs_to_jiffies(chan-&amp;gt;cl-&amp;gt;tx_tout);&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;            ret = wait_for_completion_timeout(&amp;amp;chan-&amp;gt;tx_complete, wait);&lt;/DIV&gt;&lt;DIV class=""&gt;            if (ret == 0) {&lt;/DIV&gt;&lt;DIV class=""&gt;                  t = -ETIME;&lt;/DIV&gt;&lt;DIV class=""&gt;                  tx_tick(chan, t);&lt;/DIV&gt;&lt;DIV class=""&gt;            }&lt;/DIV&gt;&lt;DIV class=""&gt;      }&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;I inserted some print debugging in loop on the cortex-m side and looks like the cortex-m stops running&lt;/DIV&gt;&lt;DIV class=""&gt;when the kick failed happens, indicating that the cortex-m might have crashed. Do you know why this is happening?&lt;/DIV&gt;&lt;DIV class=""&gt;Any suggestions to debug this issue?&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Hiago.&lt;/DIV&gt;</description>
      <pubDate>Mon, 20 Oct 2025 16:36:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/remote-proc-kick-failed-when-rpmsg-is-launched-by-U-Boot/m-p/2189290#M241512</guid>
      <dc:creator>hfranco</dc:creator>
      <dc:date>2025-10-20T16:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: remote proc kick failed when rpmsg is launched by U-Boot</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/remote-proc-kick-failed-when-rpmsg-is-launched-by-U-Boot/m-p/2190952#M241584</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/201524"&gt;@hfranco&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope you are doing very well.&lt;/P&gt;
&lt;P&gt;Could you please clarify the processor you are using, BSP version, SDK version and if possible if you are using an EVK from NXP?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Salas.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Oct 2025 18:35:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/remote-proc-kick-failed-when-rpmsg-is-launched-by-U-Boot/m-p/2190952#M241584</guid>
      <dc:creator>Manuel_Salas</dc:creator>
      <dc:date>2025-10-22T18:35:49Z</dc:date>
    </item>
    <item>
      <title>Re: remote proc kick failed when rpmsg is launched by U-Boot</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/remote-proc-kick-failed-when-rpmsg-is-launched-by-U-Boot/m-p/2191712#M241615</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/203368"&gt;@Manuel_Salas&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I am using the Colibri i.IMX8QXP from Toradex. BSP version is based on NXP 6.6 kernel, from linux-imx. SDK version is&amp;nbsp;SDK_2_9_0_MIMX8UX5xxxFZ.&lt;/P&gt;&lt;P&gt;For further information, setting 'pd_ignore_unused' as kernel argument fixes the issue.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Hiago.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Oct 2025 16:30:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/remote-proc-kick-failed-when-rpmsg-is-launched-by-U-Boot/m-p/2191712#M241615</guid>
      <dc:creator>hfranco</dc:creator>
      <dc:date>2025-10-23T16:30:40Z</dc:date>
    </item>
  </channel>
</rss>

