<?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>MCX Microcontrollers中的主题 Running Rpmsg-Lite Bare-Metal using MCUXpresso SDK 24.12</title>
    <link>https://community.nxp.com/t5/MCX-Microcontrollers/Running-Rpmsg-Lite-Bare-Metal-using-MCUXpresso-SDK-24-12/m-p/2058853#M2632</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm trying to make a simple rpmsg-lite programm using the bare metal environment from the 24.12 SDK.&lt;/P&gt;&lt;P&gt;My Hardware is the Phytec &lt;SPAN class=""&gt;phyCORE®&lt;/SPAN&gt;-i.MX 8M Plus Module mounted on the Phytec Pollux Dev-Board.&lt;/P&gt;&lt;P&gt;The M7 core is started from the linux side with remoteproc.&lt;/P&gt;&lt;P&gt;After the &lt;SPAN&gt;BOARD_InitHardware&lt;/SPAN&gt;&lt;SPAN&gt;() call I execute my bss_rpmsg_init() function.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;#define RPMSG_LITE_NS_ANNOUNCE_STRING "rpmsg-raw"
#define LOCAL_EPT_ADDR (30U)

int bss_rpmsg_init(void){
    logDebug("bss_rpmsg_init()");
    copyResourceTable();
    __disable_irq();
    my_rpmsg = rpmsg_lite_remote_init((void *)RPMSG_LITE_SHMEM_BASE, RPMSG_LITE_LINK_ID, RL_NO_FLAGS);
    __enable_irq();
    logDebug("wait for link up ...");
    rpmsg_lite_wait_for_link_up(my_rpmsg, RL_BLOCK);
    logDebug("link up");
    logDebug("create ept ...");
    my_ept1   = rpmsg_lite_create_ept(my_rpmsg, LOCAL_EPT_ADDR, rpmsg_rx_cb, &amp;amp;myStruct);
    logDebug("done");
    logDebug("announce ns: %s", RPMSG_LITE_NS_ANNOUNCE_STRING);
    (void)rpmsg_ns_announce(my_rpmsg, my_ept1, RPMSG_LITE_NS_ANNOUNCE_STRING, RL_NS_CREATE);
    logDebug("Nameservice sent, ready for incoming messages...");
    return 0;
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;On the Linux side I'm running a 6.6.23 kernel based on &lt;A href="https://github.com/phytec/linux-phytec-imx/tree/v6.6.52-2.2.0-phy" target="_blank" rel="noopener"&gt;https://github.com/phytec/linux-phytec-imx/tree/v6.6.52-2.2.0-phy&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Following is the Linux-Console Output:&lt;/P&gt;&lt;PRE&gt;[860311.074110] remoteproc remoteproc0: Booting fw image /lib/firmware/PDM-600_iMX7D-M4.elf, size 261696&lt;BR /&gt;[860311.084054] rproc-virtio rproc-virtio.3.auto: assigned reserved memory node vdevbuffer@55400000&lt;BR /&gt;[860311.097941] virtio_rpmsg_bus virtio0: rpmsg host is online&lt;BR /&gt;[860311.103675] rproc-virtio rproc-virtio.3.auto: registered virtio0 (type 7)&lt;BR /&gt;[860311.110594] remoteproc remoteproc0: remote processor imx-rproc is now up&lt;BR /&gt;[860311.128014] virtio_rpmsg_bus virtio0: msg received with no recipient&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The message "virtio_rpmsg_bus virtio0: msg received with no recipient" is triggered after the rpmsg_ns_announce() call.&lt;/P&gt;&lt;P&gt;This can be traced back to the &lt;A href="https://github.com/phytec/linux-phytec-imx/blob/v6.6.52-2.2.0-phy/drivers/rpmsg/virtio_rpmsg_bus.c" target="_self"&gt;virtio_rpmsg_bus.c Module&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The expected on the Linux side is a Message like: "virtio_rpmsg_bus virtio0: creating channel rpmsg-raw addr 0x1e"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Attached are my CMakeLists and config.cmake files.&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 10 Mar 2025 15:26:03 GMT</pubDate>
    <dc:creator>michaelschuehle</dc:creator>
    <dc:date>2025-03-10T15:26:03Z</dc:date>
    <item>
      <title>Running Rpmsg-Lite Bare-Metal using MCUXpresso SDK 24.12</title>
      <link>https://community.nxp.com/t5/MCX-Microcontrollers/Running-Rpmsg-Lite-Bare-Metal-using-MCUXpresso-SDK-24-12/m-p/2058853#M2632</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm trying to make a simple rpmsg-lite programm using the bare metal environment from the 24.12 SDK.&lt;/P&gt;&lt;P&gt;My Hardware is the Phytec &lt;SPAN class=""&gt;phyCORE®&lt;/SPAN&gt;-i.MX 8M Plus Module mounted on the Phytec Pollux Dev-Board.&lt;/P&gt;&lt;P&gt;The M7 core is started from the linux side with remoteproc.&lt;/P&gt;&lt;P&gt;After the &lt;SPAN&gt;BOARD_InitHardware&lt;/SPAN&gt;&lt;SPAN&gt;() call I execute my bss_rpmsg_init() function.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;#define RPMSG_LITE_NS_ANNOUNCE_STRING "rpmsg-raw"
#define LOCAL_EPT_ADDR (30U)

int bss_rpmsg_init(void){
    logDebug("bss_rpmsg_init()");
    copyResourceTable();
    __disable_irq();
    my_rpmsg = rpmsg_lite_remote_init((void *)RPMSG_LITE_SHMEM_BASE, RPMSG_LITE_LINK_ID, RL_NO_FLAGS);
    __enable_irq();
    logDebug("wait for link up ...");
    rpmsg_lite_wait_for_link_up(my_rpmsg, RL_BLOCK);
    logDebug("link up");
    logDebug("create ept ...");
    my_ept1   = rpmsg_lite_create_ept(my_rpmsg, LOCAL_EPT_ADDR, rpmsg_rx_cb, &amp;amp;myStruct);
    logDebug("done");
    logDebug("announce ns: %s", RPMSG_LITE_NS_ANNOUNCE_STRING);
    (void)rpmsg_ns_announce(my_rpmsg, my_ept1, RPMSG_LITE_NS_ANNOUNCE_STRING, RL_NS_CREATE);
    logDebug("Nameservice sent, ready for incoming messages...");
    return 0;
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;On the Linux side I'm running a 6.6.23 kernel based on &lt;A href="https://github.com/phytec/linux-phytec-imx/tree/v6.6.52-2.2.0-phy" target="_blank" rel="noopener"&gt;https://github.com/phytec/linux-phytec-imx/tree/v6.6.52-2.2.0-phy&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Following is the Linux-Console Output:&lt;/P&gt;&lt;PRE&gt;[860311.074110] remoteproc remoteproc0: Booting fw image /lib/firmware/PDM-600_iMX7D-M4.elf, size 261696&lt;BR /&gt;[860311.084054] rproc-virtio rproc-virtio.3.auto: assigned reserved memory node vdevbuffer@55400000&lt;BR /&gt;[860311.097941] virtio_rpmsg_bus virtio0: rpmsg host is online&lt;BR /&gt;[860311.103675] rproc-virtio rproc-virtio.3.auto: registered virtio0 (type 7)&lt;BR /&gt;[860311.110594] remoteproc remoteproc0: remote processor imx-rproc is now up&lt;BR /&gt;[860311.128014] virtio_rpmsg_bus virtio0: msg received with no recipient&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The message "virtio_rpmsg_bus virtio0: msg received with no recipient" is triggered after the rpmsg_ns_announce() call.&lt;/P&gt;&lt;P&gt;This can be traced back to the &lt;A href="https://github.com/phytec/linux-phytec-imx/blob/v6.6.52-2.2.0-phy/drivers/rpmsg/virtio_rpmsg_bus.c" target="_self"&gt;virtio_rpmsg_bus.c Module&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The expected on the Linux side is a Message like: "virtio_rpmsg_bus virtio0: creating channel rpmsg-raw addr 0x1e"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Attached are my CMakeLists and config.cmake files.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 10 Mar 2025 15:26:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCX-Microcontrollers/Running-Rpmsg-Lite-Bare-Metal-using-MCUXpresso-SDK-24-12/m-p/2058853#M2632</guid>
      <dc:creator>michaelschuehle</dc:creator>
      <dc:date>2025-03-10T15:26:03Z</dc:date>
    </item>
    <item>
      <title>Re: Running Rpmsg-Lite Bare-Metal using MCUXpresso SDK 24.12</title>
      <link>https://community.nxp.com/t5/MCX-Microcontrollers/Running-Rpmsg-Lite-Bare-Metal-using-MCUXpresso-SDK-24-12/m-p/2062193#M2681</link>
      <description>&lt;P&gt;Hi Michael&lt;/P&gt;
&lt;P&gt;I would suggest you check below link,&amp;nbsp; a similar issue was discussed.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/NXP-Designs/virtio-rpmsg-bus-virtio0-msg-received-with-no-recipient/td-p/1437807" target="_blank"&gt;virtio rpmsg bus virtio0: msg received with no recipient - NXP Community&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Fri, 14 Mar 2025 15:24:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCX-Microcontrollers/Running-Rpmsg-Lite-Bare-Metal-using-MCUXpresso-SDK-24-12/m-p/2062193#M2681</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2025-03-14T15:24:41Z</dc:date>
    </item>
  </channel>
</rss>

