Manual input of "Os Isr Handler" on Ipcf

[KONISH]

Hello. I have a question about setting of IPCF on Vector Davinci Configurator.

Environment
I am using the environments below.
・Microcontroller : S32K358
・Vector Davinci configurator classic : 5.30.30 SP1
・RTD : SW32K3_S32M27x_RTD_R21-11_5.0.0
・IPCF : SW32K3_IPCF_4.2.0_D2412

Back ground & Question
I'm trying to configulate "Os Isr Handler" of "IpcfInstance" with Vector Davinci configurator classic for AUTOSAR project.
The window that is displayed by [...] of "Os Isr Handler" requires Manual input.
Is the requirement correct?

If the requirement is correct, please let me know what kind of path is required.
If the requirement is not correct, do we need some other plug-in or some other setting?

Best regards.

[KONISH]

Thank you for your immediate answers.

Reply for your answers

1. Do you use AUTOSAR Os provided by Vector?

　　Yes, I use AUTOSAR Os.

2. Because in the picture that you share we can’t see the OS configuration the question is if there are one or more OsISR configurated?

      Yes, there are four OsISR configurations below on my project.
      They are OsISR for CAN communication.

additional questions

According to your answers, is OsISR for IPCF necessary when applying IPCF?

Is it right that filling out "Reference path" of "Os Isr Handler" above with the path of the OsISR for IPCF?

If OsISR for IPCF necessary is necessary, do we have some reference for OsISR for IPCF?

For example, what kind of reference is needed for "Isr Resource Ref" of OsISR for IPCF settting?

Thank you and best regards.

[nxf94150]

Hello,

Bellow you can find the answers:

Q: According to your answers, is OsISR for IPCF necessary when applying IPCF?

A: OsISR is needed to be added to IPCF only if you want to use it in Interrupt mode( one core trigger an MU interrupt and the other one is receiving it and processing the messages in a callback function). IPCF can be used in polling mode and no interrupt for IPCF need to be configured, no need to configure Os ISR Handler from IPCF configuration. In this case Inter Core Rx IRQ parameter should be set to IPC_IRQ_NONE.

Q: Is it right that filling out "Reference path" of "Os Isr Handler" above with the path of the OsISR for IPCF?

A: If one of those four IRQ that appears in the pictures are applying to IPCF, interrupt used to notify the other core that data are available then fill manually reference path with the desired OSISR path like in bellow picture.

If the configured interrupts are not applying to IPCF then you can use polling mode (with no interrupts needed for IPCF) or add a dedicated interrupts in Os for IPCF and reference in Os ISR Handler from IPCF configuration.

Please check also IPCF_S32K3_4.2.0_User_Manual.pdf chapter 2.2.1 Integration with NXP RTOS.

Q: If OsISR for IPCF necessary is necessary, do we have some reference for OsISR for IPCF?

A: I assume that above answer cover also this point, if not please give more details because it not clear.

Q: For example, what kind of reference is needed for "Isr Resource Ref" of OsISR for IPCF setting?

A: "Isr Resource Ref" of OsISR is not used and you don’t need to configure something for IPC.

If there are any other questions or something is still not clear maybe we can have a meeting to support you with the configuration of IPCF.

Best regards,

Daniel

[KONISH]

Thank you for your answers.

●Question about IPCF mode

I plan to apply "Interrupt mode" of IPCF for our target project, therefore Os ISR Handler is needed to be fileld out.

So I'm making "ipc_shm_mu_notification" under the path "Os/OsIsrs" as Os ISR Handler for IPCF interrupt mode.

Do we have some reference or example for "OsIsr" configuration regarding IPCF?

●Question about how to link IPCF with OsIsr.

To link IPCF with OsIsr above, is it OK to fill out "Os Isr Handler" of IPCF with "/ActiveEcuC/Os/ipc_shm_mu_notification/".

[nxf94150]

Hello,

Q: So I'm making "ipc_shm_mu_notification" under the path "Os/OsIsrs" as Os ISR Handler for IPCF interrupt mode.
A: Yes, that is correct.

Q: Do we have some reference or example for "OsIsr" configuration regarding IPCF?
A: We have and example in IPCF installer for NXP RTOS at following path (it was configured using Tresos) "C:\NXP\SW32K3_IPCF_4.2.0_D2412\eclipse\plugins\Ipcf_TS_T40D34M42I0R0\examples\IPCF_AutosarOS_S32K358_M7_0", it can help you and bring more clarity.

Q: To link IPCF with OsIsr above, is it OK to fill out "Os Isr Handler" of IPCF with "/ActiveEcuC/Os/ipc_shm_mu_notification/".
A: Yes, it should be like that.

Let me know if everything is working as expected.
Have a nice day!

Best regards,
Daniel

[KONISH]

Thank you for your answers.

●Problem: Errors and warning occur at Os Isr Handler even if the handler is manually dsfilled out with proper path.

According to errors and warning, node of OsIsrHandler cannot be found out from IpcfInstance.

Is there some other setting for linkage between IpcfInstance and OsIsr?

●Current setting:

・OsIsr

I added OsIsr for IPCF, following the example of IPCF installer for NXP RTOS that you mentioned last time.

Link to Os Isr Handler is filled out with proper path to the Handler that is copied from the Short Name Path below.

[nxf94150]

Hello,

It seems that path is not recognized, did you try also with "/MICROSAR/Os/OsIsr/ipc_shm_mu_notification"?
If this will not work I would recommend to make a call and check directly on your configuration.

Best regards,
Daniel

[KONISH]

Hello.

This is additional information about the problem.

If we changed configuration environment from Davinci configurator to EB tresos, the errors and warnings are solved.

Therefore the problem seems to be caused by Davinci configurator or matching between Davinci configurator and EB tresos. Currenly we're asking about the solution to tool vendor to realize IPCF source code generation as CDD of AUTOSAR with Davinci configurator.

If we got some information, we'll let you know about it.

[nxf94150]

Hello,

Thank you for all the information's and I'm glad to hear that in EB Tresos everything is working good.

Please let me know when you get an answer from vendor tool.

If we have any other information I will also let you know.

Best regards,

Daniel

[KONISH · Accepted solution]

Hello.

According to tool vendor, Davinci configurator cannot generate NXP IPCF source code although we can configure NXP IPCF as MCAL with Davinci configurator.
Because Davinci configurator officially does not apply NXP IPCF as MCAL.

Manual input of "Os Isr Handler" of IPCF caused by difference in interrupt hanlder path between NXP IPCF's arxml file and Davinci configurator. And even if we fill out "Os Isr Handler" manually and properly, errors and warning occur because of Davinci configurator's application above.

If we changed the path in arxml file manually, we can solve the errors and warnings above and then other errors occurs a lot.

Therefore we're planing to change our approach to include NXP IPCF source files to AUTOSAR platform.

Thank you for your kind cooperation.

Best regards.

[nxf94150]

Hello,

Thank you for detailed explanation and following back on this topic.

If there is something else where we can help just let me know.

Best regards,
Daniel

[KONISH]

Supplement:

According to tool vendor, Davinci configurator cannot generate NXP IPCF source code although we can configure NXP IPCF as MCAL with Davinci configurator.
Because Davinci configurator officially does not apply NXP IPCF as MCAL.

Because Davinci configurator officially does not apply NXP IPCF as MCAL for S32K3xx.
Therefore be sure to check that NXP IPCF is applicable for the target micro controller before applying NXP IPCF.

[KONISH]

Thank you for your answer.

In case Os Isr Handler of IpcfInstance is filled with  "/MICROSAR/Os/OsIsr/ipc_shm_mu_notification" instead of "/AUTOSAR/...", new warning below is added.

Currently we're investigating the causes of "ID = TresosXXXXX" of the errors and the warnings that we mentioned last time to solve them.
Do you know the causes of "ID = TresosXXXXX" above or do you know some reference about the causes?

[nxf94150]

Hello ,

We have a few points that need clarification:

1. Do you use AUTOSAR Os provided by Vector?
2. Because in the picture that you share we can’t see the OS configuration the question is if there are one or more OsISR configurated?

If you have them configured then it could be an issue and you need to use the manual option to select the reference to the configured OsISR for IPCF parameter Os Isr Handler.

As an example for manual configuration you need to use highlighted path with your specific OsISR path

Please let me know if more information are needed.

Best regards,

Daniel