<?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>S32GのトピックRe: Mismatch API between S32G ipc-shm and ipc-shm-us Linux BSP</title>
    <link>https://community.nxp.com/t5/S32G/Mismatch-API-between-S32G-ipc-shm-and-ipc-shm-us-Linux-BSP/m-p/1401328#M423</link>
    <description>&lt;P&gt;Hi Kawin&lt;/P&gt;
&lt;P&gt;IPCF is shared between multiple devices, so the targeted device is determined by the branch used. For the S32G2, you will need to use release/SWS32G2_IPCF_4.3.0_D2109 for IPCF 4.3.0 in both repos. For subsequent IPCF releases, the branch name will reflect the IPCF version accordingly but the name will always start with release/SWS32G2.&lt;/P&gt;
&lt;P&gt;Within the ipc-shm-us repo, I believe the submodule is improperly configured in which it should be pointing to the release/SWS32G2_IPCF_4.3.0_D2109 branch. In previous releases, it is configured to use the appropriate version's branch in ipc-shm rather than master. We have reached out to the IPCF development team for clarification and will let you know when they reply.&lt;/P&gt;
&lt;P&gt;In the meantime, configuring .gitmodules within ipc-shm-us to use the release/SWS32G2_IPCF_4.3.0_D2109 branch of ipc-shm should allow for multi-instance support in userspace applications. You can see this change to multi-instance support throughout ipc-shm.h from the ipc-shm repo. Within this header file, many of the functions have been updated to include the instance number as part of their parameters.&lt;/P&gt;</description>
    <pubDate>Wed, 19 Jan 2022 03:58:12 GMT</pubDate>
    <dc:creator>andrei_skok</dc:creator>
    <dc:date>2022-01-19T03:58:12Z</dc:date>
    <item>
      <title>Mismatch API between S32G ipc-shm and ipc-shm-us Linux BSP</title>
      <link>https://community.nxp.com/t5/S32G/Mismatch-API-between-S32G-ipc-shm-and-ipc-shm-us-Linux-BSP/m-p/1399046#M400</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;ipc-shm release/bsp30.0 added multi-instance support while this feature is missing in ipc-shm-us release/bsp30.0.&lt;/P&gt;&lt;P&gt;What is the right ipc-shm and ipc-shm-us versions I should use for Linux BSP 30.0 and IPCF 4.3?&lt;/P&gt;&lt;P&gt;Don't know if you notice this but submodule branch is always pointing to master:&lt;/P&gt;&lt;P&gt;&lt;A href="https://source.codeaurora.org/external/autobsps32/ipcf/ipc-shm-us/tree/.gitmodules?h=release%2Fbsp30.0" target="_blank" rel="noopener"&gt;https://source.codeaurora.org/external/autobsps32/ipcf/ipc-shm-us/tree/.gitmodules?h=release%2Fbsp30.0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Kawin&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jan 2022 19:36:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Mismatch-API-between-S32G-ipc-shm-and-ipc-shm-us-Linux-BSP/m-p/1399046#M400</guid>
      <dc:creator>kawin</dc:creator>
      <dc:date>2022-01-13T19:36:56Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch API between S32G ipc-shm and ipc-shm-us Linux BSP</title>
      <link>https://community.nxp.com/t5/S32G/Mismatch-API-between-S32G-ipc-shm-and-ipc-shm-us-Linux-BSP/m-p/1399596#M406</link>
      <description>&lt;P&gt;Any updates on this?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jan 2022 17:57:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Mismatch-API-between-S32G-ipc-shm-and-ipc-shm-us-Linux-BSP/m-p/1399596#M406</guid>
      <dc:creator>kawin</dc:creator>
      <dc:date>2022-01-14T17:57:02Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch API between S32G ipc-shm and ipc-shm-us Linux BSP</title>
      <link>https://community.nxp.com/t5/S32G/Mismatch-API-between-S32G-ipc-shm-and-ipc-shm-us-Linux-BSP/m-p/1401328#M423</link>
      <description>&lt;P&gt;Hi Kawin&lt;/P&gt;
&lt;P&gt;IPCF is shared between multiple devices, so the targeted device is determined by the branch used. For the S32G2, you will need to use release/SWS32G2_IPCF_4.3.0_D2109 for IPCF 4.3.0 in both repos. For subsequent IPCF releases, the branch name will reflect the IPCF version accordingly but the name will always start with release/SWS32G2.&lt;/P&gt;
&lt;P&gt;Within the ipc-shm-us repo, I believe the submodule is improperly configured in which it should be pointing to the release/SWS32G2_IPCF_4.3.0_D2109 branch. In previous releases, it is configured to use the appropriate version's branch in ipc-shm rather than master. We have reached out to the IPCF development team for clarification and will let you know when they reply.&lt;/P&gt;
&lt;P&gt;In the meantime, configuring .gitmodules within ipc-shm-us to use the release/SWS32G2_IPCF_4.3.0_D2109 branch of ipc-shm should allow for multi-instance support in userspace applications. You can see this change to multi-instance support throughout ipc-shm.h from the ipc-shm repo. Within this header file, many of the functions have been updated to include the instance number as part of their parameters.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2022 03:58:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Mismatch-API-between-S32G-ipc-shm-and-ipc-shm-us-Linux-BSP/m-p/1401328#M423</guid>
      <dc:creator>andrei_skok</dc:creator>
      <dc:date>2022-01-19T03:58:12Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch API between S32G ipc-shm and ipc-shm-us Linux BSP</title>
      <link>https://community.nxp.com/t5/S32G/Mismatch-API-between-S32G-ipc-shm-and-ipc-shm-us-Linux-BSP/m-p/1617330#M2500</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have trouble in IPCF communication between A53 and M7. I am using s32g274 hardware.&amp;nbsp;&lt;/P&gt;&lt;P&gt;From this link, i have built the modules manually- git clone &lt;A href="https://source.codeaurora.org/external/autobsps32/ipcf/ipc-shm/" target="_blank"&gt;https://source.codeaurora.org/external/autobsps32/ipcf/ipc-shm/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Copied these ipc-shm-dev.ko, ipc-shm-sample.ko and ipc-shm-uio.ko files to board.&lt;/P&gt;&lt;P&gt;In uboot level, i have executed the below commands, [IPCF_Example_S32G274_M7_0.bin downloaded from NXP]&lt;/P&gt;&lt;P&gt;=&amp;gt; dcache off&lt;BR /&gt;=&amp;gt; mw.q 0x34000000 0x0 0x100000&lt;BR /&gt;=&amp;gt; fatload mmc 0:1 0x80000000 IPCF_Example_S32G274_M7_0.bin&lt;BR /&gt;=&amp;gt; cp.q 0x80000000 0x34300000 0x60000&lt;BR /&gt;=&amp;gt; startm7 0x34401000&lt;BR /&gt;Starting CM7_0 core at SRAM address 0x34401000 ... done.&lt;BR /&gt;=&amp;gt;boot&lt;/P&gt;&lt;P&gt;Board is booted and able to load the modules as shown below:&lt;/P&gt;&lt;P&gt;root@ubuntu-s32g274ateraaceubuntu:/home/bluebox# insmod ipc-shm-dev.ko&lt;BR /&gt;root@ubuntu-s32g274ateraaceubuntu:/home/bluebox# insmod&amp;nbsp; ipc-shm-sample.ko&lt;BR /&gt;root@ubuntu-s32g274ateraaceubuntu:/home/bluebox#&lt;/P&gt;&lt;P&gt;While sending the message it is failed:&lt;BR /&gt;root@ubuntu-s32g274ateraaceubuntu:/# dmesg -c &amp;gt; /dev/null&lt;BR /&gt;root@ubuntu-s32g274ateraaceubuntu:/# echo 10 &amp;gt; /sys/kernel/ipc-shm-sample/ping&lt;BR /&gt;root@ubuntu-s32g274ateraaceubuntu:/# [ 2392.119337] ipc-shm-sample: send_data_msg(): failed to get buffer for channel ID 1 and size 16&amp;nbsp;root@ubuntu-s32g274ateraaceubuntu:/# dmesg -c&lt;BR /&gt;[ 2392.119301] ipc-shm-sample: starting demo...&lt;BR /&gt;[ 2392.119326] ipc-shm-sample: ch 0 &amp;gt;&amp;gt; 20 bytes: SENDING MESSAGES: 10&lt;BR /&gt;[ 2392.119337] ipc-shm-sample: send_data_msg(): failed to get buffer for channel ID 1 and size 16&lt;BR /&gt;root@ubuntu-s32g274ateraaceubuntu:/#&lt;/P&gt;&lt;P&gt;Can you please help me. Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Mar 2023 05:02:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Mismatch-API-between-S32G-ipc-shm-and-ipc-shm-us-Linux-BSP/m-p/1617330#M2500</guid>
      <dc:creator>Vineesha</dc:creator>
      <dc:date>2023-03-17T05:02:54Z</dc:date>
    </item>
  </channel>
</rss>

