S32G: About PID and SEMA42 of XRDC module

[Kojimaa]

Hi NXP:

  Do I have to manually call Rm_XrdcSetProcessID() or Rm_SemaphoreLockGate() which provided by the driver when I want to switch PID or lock the sema gate? 

  Can it be assigned to OS Tasks/ISRs/Applications through configuration tools such as EB tresos ?

Thanks

[Daniel-Aguirre]

HI,

We may not be understanding your request, for which we apologize in advance.

As you are saying, both the "Rm_XrdcSetProcessID" and "Rm_SemaphoreLockGate" are to be called if you are looking for setting the PID or locking the SEMA42 Gate module, respectively. This can be seen under the Rm Driver UM:

As for the assignment, can you share more information on this regard? Are you looking to call these functions from either Tasks/ISRs/Application?

The requirements for the RM module should be provided under the RM Driver IM.

Please, let us know.

[Kojimaa]

Hi,

  Thanks for your reply.

   My description may not be clear, I mean, for example, if a task/application needs to switch PID to run in other domain or lock a SEMA gate , do I need to manually call the API? Can the OS automatically complete the switching operation like MPU through prior configuration ?

   In addition, can you provide me with UM and IM for RM drivers ? I didn't find them

Thanks

[Daniel-Aguirre · Accepted solution]

Hi,

For changing the PID or locking a SEMA42 gate on runtime we see that the API is required. This can be seen under the "Xrdc_Ip_Example_integrated_with_Semaphore_S32G274A_M7" example, where they move the process from domain 0 to domain 1, as well as lock the respective SEMA42 gate.

We understand that this should be done explicitly. Some examples are provided under the S32G2 RM [Section 15.8.7.2, Page 604, S32G2 Reference Manual, Rev. 7, February 2023].

Also, there is the AN13024 which explains more about XRDC itself. May provide useful information.

Still, could be that we are misunderstanding the request. Again, we apologize if this is true.

As for both UM and IM, they should be located under the installation path of the RTD. One example could be the following:

"C:\nxp\S32DS.3.4\S32DS\software\PlatformSDK_S32XX_2022_03\SW32_RTD_4_4_3_0_2_D2203\Rm_TS_T40D11M30I2R0\doc"

Where it can vary depending on the RTD/IDE versions.

Please, let us know.