Inquiry regarding AUTOSAR OS/RTE availability for S32K144 and recommended Hybrid workflow

[jipoman]

Hello,

I am currently working on an AUTOSAR-based project using the S32K144EVB. I am utilizing the RTD (Real-Time Drivers) provided by NXP through EB tresos for MCAL-level configurations.

However, I have noticed that while RTD is provided, a standard-compliant AUTOSAR OS and RTE do not seem to be included in the free software package. Instead, FreeRTOS is often used in the examples.

I would like to clarify the following two points:

1. Availability of Free/Open-source AUTOSAR OS and RTE: Does NXP provide a standard-compliant AUTOSAR OS and RTE for the S32K1 series as a free or open-source package? If not, are there any recommended third-party open-source alternatives that are compatible with NXP RTD?

2. Recommended Workflow for "AUTOSAR-inspired" Architecture: If a standard OS/RTE is not provided for free, is the following "Hybrid" approach considered the best practice for prototyping?

• MCAL: Using NXP RTD (configured via EB tresos).

• OS: Integrating FreeRTOS manually within S32DS.

• RTE/Service Layer: Manually implementing an abstraction layer (RTE-like interfaces and SchM critical sections).

If there is a more efficient or recommended way to achieve a "standard-like" architecture without a commercial stack, please let me know.

Best regards,

jipoman

[VaneB]

Hi @jipoman 

The RTE module included in the RTD package is provided as a support stub only and does not support configuration. It is intended solely for testing purposes.

For a fully functional and configurable RTE solution, you will need to obtain a compatible package from a third‑party vendor, such as Elektrobit (EB), Vector, or other AUTOSAR tool providers.

BR, VaneB