Support for S32K388EVB-Q289 Evaluation Board

[DianaT08]

I intend to integrate zephyr on the S32K388EVB-Q289 board which is based on the S32K388 MCU. I've seen that zephyr already supports MR-CANHUBK344 with the S32k344 MCU but since the S32K388 has additional features (such as more cores, bigger memory and extra peripherals), it seems that the existing S32K344 support wouldn't be directly compatible or sufficient for S32K388. I'm wondering if there are any plans in the future to add support for this in zephyr and also in the hal_nxp repository. Thank you!

[manuargue]

Hi @DianaT08, thanks for your interest! NXP is currently checking internally regarding S32K388 support and will update you as soon as we have more information.

[DianaT08]

Hi @manuargue, are there any updates on this? Thanks!

[manuargue]

Hi @DianaT08, NXP currently does not have plans to upstream S32K388 support in Zephyr. However, we are happy to support your efforts by making the necessary bare-metal drivers (RTD) and device headers available upstream, so that you can perform the integration on your end.

That said, we would greatly appreciate it if the S32K388 port could be contributed back to the Zephyr upstream repository. If this approach works for you, please let us know your expected timeline for the integration.

Thank you!

[DianaT08]

Hi @manuargue, thank you for the response! I really appreciate the offer to make the bare-metal drivers and device headers available upstream. That would be very helpful for getting started.
At this point I don't have a clear timeline for the integration. The initial idea was to add support for the S32K388EVB-Q289 board but this changed to adding support for a custom board based on the S32K388 MCU (which would be made in-house by my company). Due to internal policy, contributing this support upstream wouldn’t be possible.

[manuargue]

Hi @DianaT08, thank you for your feedback.
Given that your company currently does not intend to contribute the S32K388 Zephyr integration upstream, NXP is unable to support with the upstreaming of the baremetal drivers.
I will move this discussion to closed. However, should your company plans change, NXP remains open and willing to support the integration effort.
Thanks