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

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

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

456 Views
jipoman
Contributor II

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

0 Kudos
Reply
1 Reply

420 Views
VaneB
NXP TechSupport
NXP TechSupport

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

%3CLINGO-SUB%20id%3D%22lingo-sub-2359122%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EInquiry%20regarding%20AUTOSAR%20OS%2FRTE%20availability%20for%20S32K144%20and%20recommended%20Hybrid%20workflow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2359122%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20am%20currently%20working%20on%20an%20AUTOSAR-based%20project%20using%20the%20%3CSTRONG%3ES32K144EVB%3C%2FSTRONG%3E.%20I%20am%20utilizing%20the%20%3CSTRONG%3ERTD%20(Real-Time%20Drivers)%3C%2FSTRONG%3E%20provided%20by%20NXP%20through%20%3CSTRONG%3EEB%20tresos%3C%2FSTRONG%3E%20for%20MCAL-level%20configurations.%3C%2FP%3E%3CP%3EHowever%2C%20I%20have%20noticed%20that%20while%20RTD%20is%20provided%2C%20a%20standard-compliant%20%3CSTRONG%3EAUTOSAR%20OS%20and%20RTE%3C%2FSTRONG%3E%20do%20not%20seem%20to%20be%20included%20in%20the%20free%20software%20package.%20Instead%2C%20FreeRTOS%20is%20often%20used%20in%20the%20examples.%3C%2FP%3E%3CP%3EI%20would%20like%20to%20clarify%20the%20following%20two%20points%3A%3C%2FP%3E%3CP%3E%3CSTRONG%3E1.%20Availability%20of%20Free%2FOpen-source%20AUTOSAR%20OS%20and%20RTE%3A%3C%2FSTRONG%3E%20Does%20NXP%20provide%20a%20standard-compliant%20AUTOSAR%20OS%20and%20RTE%20for%20the%20S32K1%20series%20as%20a%20free%20or%20open-source%20package%3F%20If%20not%2C%20are%20there%20any%20recommended%20third-party%20open-source%20alternatives%20that%20are%20compatible%20with%20NXP%20RTD%3F%3C%2FP%3E%3CP%3E%3CSTRONG%3E2.%20Recommended%20Workflow%20for%20%22AUTOSAR-inspired%22%20Architecture%3A%3C%2FSTRONG%3E%20If%20a%20standard%20OS%2FRTE%20is%20not%20provided%20for%20free%2C%20is%20the%20following%20%22Hybrid%22%20approach%20considered%20the%20best%20practice%20for%20prototyping%3F%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3EMCAL%3A%20Using%20NXP%20RTD%20(configured%20via%20EB%20tresos).%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EOS%3A%20Integrating%20FreeRTOS%20manually%20within%20S32DS.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3ERTE%2FService%20Layer%3A%20Manually%20implementing%20an%20abstraction%20layer%20(RTE-like%20interfaces%20and%20SchM%20critical%20sections).%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EIf%20there%20is%20a%20more%20efficient%20or%20recommended%20way%20to%20achieve%20a%20%22standard-like%22%20architecture%20without%20a%20commercial%20stack%2C%20please%20let%20me%20know.%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3Ejipoman%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2359475%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Inquiry%20regarding%20AUTOSAR%20OS%2FRTE%20availability%20for%20S32K144%20and%20recommended%20Hybrid%20workflow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2359475%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F261369%22%20target%3D%22_blank%22%3E%40jipoman%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20RTE%20module%20included%20in%20the%20RTD%20package%20is%20provided%20as%20a%20support%20stub%20only%20and%20does%20not%20support%20configuration.%20It%20is%20intended%20solely%20for%20testing%20purposes.%3C%2FP%3E%0A%3CP%3EFor%20a%20fully%20functional%20and%20configurable%20RTE%20solution%2C%20you%20will%20need%20to%20obtain%20a%20compatible%20package%20from%20a%20third%E2%80%91party%20vendor%2C%20such%20as%20Elektrobit%20(EB)%2C%20Vector%2C%20or%20other%20AUTOSAR%20tool%20providers.%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EBR%2C%20VaneB%3C%2FP%3E%3C%2FLINGO-BODY%3E