Unable to Configure Platform Module in EB tresos AutoCore Template Project

GaneshBhagwat

Subject: Unable to Configure Platform Module in EB tresos AutoCore Template Project

Hi NXP Experts,

I am working with EB tresos and would like to use both the RTE and other AUTOSAR software layers provided by the AutoCore project template. I am able to generate the configuration successfully and the project builds and runs as expected.

However, I am encountering an issue with the Platform module configuration.

When I create a project using the AutoCore Template for CORTEXM-S32K35x, I can add the Platform module, but its configuration parameters are not available for editing. The configuration view appears restricted, and I cannot access the settings that I need to modify.

In contrast, when I create a blank project for CORTEXM-S32K3xx, I can access and edit all Platform module configuration parameters without any issues.

My primary requirement is to configure interrupt-related settings within the Platform module for my application.

I have attached screenshots showing both scenarios:

AutoCore Template project – Platform configuration is not editable.
Blank S32K3xx project – Platform configuration is fully accessible and editable.

I would appreciate your guidance on the following questions:

Is the limited Platform configuration a known restriction or expected behavior of the AutoCore Template?
Can the Platform module be used together with AUTOSAR OS in the AutoCore environment, or are there any limitations or dependencies that prevent this?
What is the recommended method for configuring interrupts when using the AutoCore Template?
Is there an AutoCore Template available for the generic CORTEXM-S32K3xx platform, similar to the one provided for CORTEXM-S32K35x?
Are there any detailed application notes, example projects, or reference guides that demonstrate the integration and usage of AUTOSAR OS with the AutoCore Template?

If additional project information or configuration details are required, I would be happy to provide them.

Thank you for your support.

Best regards,

Ganesh

danielmartynek

Hello @GaneshBhagwat,

I understand:

In a blank S32K3xx project, the Platform module is fully editable
In the AutoCore template project, the same module is restricted

A success in a blank project proves that the NXP RTD driver plugins and configuration parameters are valid. The failure inside the template indicates a template integration or module conflict, which is maintained and delivered by Elektrobit, therefore, this should be handled by Elektrobit support, not NXP.

BR, Daniel

GaneshBhagwat

Hello Daniel,

Thank you for the clarification.

However, the issue does not appear to be limited to the AutoCore template. I can reproduce the same behavior in a project created without the AutoCore template when selecting the CORTEXM-S32K35x target.

Since the restriction is also present outside the AutoCore environment, could you please have a look and advise if there are any known limitations, configuration dependencies, or checks that I can perform to further investigate the issue?

Any guidance on possible root causes or debugging steps would be greatly appreciated.

Best regards,
Ganesh

danielmartynek

Hello @GaneshBhagwat,

Still, EB tresos is not an NXP product.
Could you please specify which NXP RTD revision and S32K3xx part number you are using?

GaneshBhagwat

Hello @danielmartynek ,

Thank you for your response.

Regarding your question, I am primarily using RTD 5 in my projects. However, to investigate this issue further, I also installed and tested RTD 4, RTD 6, and RTD 7. I observed the same behavior across all RTD versions.

The screenshot attached in my previous reply was taken using RTD 6.

Since the issue is reproducible across multiple RTD releases, I am trying to understand whether this behavior is related to the selected target/platform configuration (CORTEXM-S32K35x) rather than a specific RTD version.

Could you please advise:

Which specific S32K35x devices are expected to support full Platform module configuration within EB tresos?
Is there any known limitation or dependency when using the CORTEXM-S32K35x target that would cause the Platform configuration to be restricted or hidden?
Are interrupt-related Platform configurations expected to be managed through another module (for example, OS or Mcu configuration) when targeting S32K35x devices?
Is there a recommended reference project or example configuration that demonstrates the expected Platform module setup for S32K35x devices?

My goal is mainly to configure interrupt handling for the application, so any guidance on the recommended approach for S32K35x would be very helpful.

Thank you for your support and assistance.

Best regards,
Ganesh

danielmartynek

Hi @GaneshBhagwat,

I'm looking at S32K358 RTD 6.0.0 examples imported to EB Tresos 29, they are all configured with target CORTEXM/S32K3xx, and the Platform driver can be reconfigured. Also, I don't see target CORTEXM/S32K35x to be available in Tresos for new projects.

BR, Daniel

GaneshBhagwat

@danielmartynek