Differences and Applications of NXP S32N vs. S32Z Processors

[noobsplzwin]

Hello everyone,

I'm looking for insights into the differences and suitable applications of the NXP S32N and S32Z processors. Both seem capable of domain control and virtualization, but I'm unsure about their specific advantages and best use cases.

From what I understand:

• S32N55 features 16x Arm Cortex-R52 cores, targeted at central vehicle controllers, with a focus on high-performance, real-time processing, and extensive communication interfaces.
• S32Z2 has 8x Arm Cortex-R52 cores, designed for real-time control and zonal processing, emphasizing safety with ISO 26262 ASIL D compliance.

Can anyone provide more detailed comparisons or experiences with these processors in automotive applications?

Additionally, does anyone know the expected release time for development boards for these processors?

Thanks in advance!
Connor

[lukaszadrapa · Accepted solution]

Hi @noobsplzwin 

in very short, S32N is much more powerful. It's intended for real-time super-integration of vehicle functions, so it can replace several ECUs. It's like S32Z + S32G in one package.

There are some nice video presentations like:

https://www.nxp.com/video/accelerate-your-sdv-journey-with-nxp-s32-coreride-platform:SDV-JOURNEY-S32...

https://www.nxp.com/video/nxp-introduces-s32-coreride-platform-and-s32n-processor-family:NXP-INTRO-S...

Because these devices are still in preproduction status, please contact your local sales office for details about the availability. If you don't have direct NXP sales contact:

https://www.nxp.com/support/sample-and-buy/distributor-network:DISTRIBUTORS

I believe that boards for S32Z/E should be already available in some limited quantities.

Regards,

Lukas

[noobsplzwin]

Hi Lukas,

Thank you for the detailed response and the video links. I've watched the demo video, and it looks exactly like the kind of application I have in mind. I have a few questions:

1. Use of Extra Controllers: I noticed that the demo is using additional S32K3 and S32K1 controllers to manage the actuators. Could you explain the rationale behind this setup? Is the concept that the S32N runs different control algorithms/logic, sends the actual control commands to the zone controllers (S32K3/S32K1) via CAN, and then the S32K1 and S32K3 handle the actual hardware control? S32N should also be able to do the work of S32k, right?

2. Third-Party Software Integration: The S32 CoreRide platform appears to integrate a lot of third-party software. Specifically, will the µ-visor Hypervisor from Green Hills Software be part of the NXP SDK, and will it be available for free to the public? 

3. QNX Integration: Regarding QNX, has its integration already been completed as part of the NXP SDK? Will we be able to use it directly upon release?

4. Hypervisor Integration: We've been working on the hypervisor for many years on RISC-V, dealing with memory and hardware I/O conflicts... I have successfully run our hypervisor in a QEMU environment with ARM R52, and it performed quite well. Is there any chance we can integrate our hypervisor into the NXP CoreRide platform? What would be the process for such an integration?

Thank you for your assistance.

Best regards,
Connor

[lukaszadrapa]

Hi @noobsplzwin 

Please notice that S32N is not supported by our online support team yet because it is still in certain phase of pre-production. The support is currently available only to direct customers via their FAE. For more details, I have to redirect you to your NXP sales or FAE person or to distribution FAE as already mentioned earlier. Thanks for understanding.

Regards,

Lukas