When developing IPCF functionality by creating multiple projects using C++ (or C) on the S32G A-cores, is the init_ipc_shm() function allowed to initialize the configured shared resources only once during runtime? If yes, what are the best architectural recommendations at the system level? My idea is to implement a self-starting service program that performs this initialization once during every device power-up
Solved! Go to Solution.
Hello, @Ariel28
Thanks for your post.
The init_ipc_shm() is called while the application is started, if the application is not crashed/exit, then it may not need to be called for the second time
As is shown above, if you performs this initialization once during every device power-up, then while the application exit/crashed, you may have to call the init_ipc_shm() manually before restarting the application if not resetting the device.
What we provided is the kernel module/libs, the user application design is specific according to different custom requirements, sorry that I do not see some formal recommendation related, I apologize.
BR
Chenyin
Hello, @Ariel28
Thanks for your post.
The init_ipc_shm() is called while the application is started, if the application is not crashed/exit, then it may not need to be called for the second time
As is shown above, if you performs this initialization once during every device power-up, then while the application exit/crashed, you may have to call the init_ipc_shm() manually before restarting the application if not resetting the device.
What we provided is the kernel module/libs, the user application design is specific according to different custom requirements, sorry that I do not see some formal recommendation related, I apologize.
BR
Chenyin
If I have implemented multiple apps on core A, is it necessary for each app to call the init_ipc_shm() method once during startup for initialization? This is something I am eager to understand.