Mismatch API between S32G ipc-shm and ipc-shm-us Linux BSP

cancel
Showing results for 
Search instead for 
Did you mean: 

Mismatch API between S32G ipc-shm and ipc-shm-us Linux BSP

Jump to solution
73 Views
kawin
Contributor III

Hi there,

ipc-shm release/bsp30.0 added multi-instance support while this feature is missing in ipc-shm-us release/bsp30.0.

What is the right ipc-shm and ipc-shm-us versions I should use for Linux BSP 30.0 and IPCF 4.3?

Don't know if you notice this but submodule branch is always pointing to master:

https://source.codeaurora.org/external/autobsps32/ipcf/ipc-shm-us/tree/.gitmodules?h=release%2Fbsp30...

Thank you,

Kawin

Tags (3)
0 Kudos
1 Solution
24 Views
andrei_skok
NXP TechSupport
NXP TechSupport

Hi Kawin

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.

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.

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.

View solution in original post

0 Kudos
2 Replies
25 Views
andrei_skok
NXP TechSupport
NXP TechSupport

Hi Kawin

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.

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.

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.

View solution in original post

0 Kudos
58 Views
kawin
Contributor III

Any updates on this?

0 Kudos