S32K312 .mex File Not Opening in S32 Configuration Tools, — Need Support for SPI Bring-Up

[abhi_hatte]

Hello NXP Support Team,

We are starting a new large-scale project using the S32K312 microcontroller and are currently in the initial board bring-up phase with the S32K312 development board.

Our first goal is to validate the hardware by implementing a basic SPI communication example. We have completed the installation of the development environment and created a project successfully.

However, we are facing an issue with the configuration tools:

Previously, our project’s .mex configuration file opened correctly in S32 Configuration Tools. Now, the same .mex file does not open anymore, which prevents us from configuring pins, clocks, and peripherals required for SPI initialization.

We have already tried uninstalling and reinstalling S32 Design Studio, but the issue still persists.

We would appreciate your guidance on:

Possible reasons why a .mex file would suddenly stop opening

Whether this could be caused by tool/SDK/RTD version mismatch after reinstall

Recommended approach to proceed with basic SPI bring-up on the S32K312 development board

Development Environment Details

MCU: S32K312

Board: S32K312 Development Board

IDE: S32 Design Studio for S32 Platform v3.5 (Build 240130, Update 10)

S32 Configuration Tools: v1.7.8 (Build 202405220948)

RTD Package: S32K3 RTD v3.0.0 + Patch P01

SDK Used: PlatformSDK_S32K3 v3.0.0

Core: S32K312_M7

OS: Windows 11


Thank you for your support.


Thanks & Regards,
Abhishek Hatte

Firmware Engineer

GEON

[abhi_hatte]

Hello,

I would like to add one more detail that I missed in my original post.

When I attempt to open the .mex configuration file, S32 Configuration Tools shows a progress dialog with the message:

“Opening the configuration SPI_TEST.mex”

This pop-up appears, but after that nothing happens, and the .mex file does not open and I am unable to view or edit the configuration.

I am attaching a screenshot of the progress window for reference.

[VaneB]

Hi @abhi_hatte 

Could you please try the following steps to help resolve the issue?

With the default installation path, the s32ds.ini file is located in: C:\NXP\S32DS.3.5\eclipse\

In this file, please update the parameter Dcom.nxp.swtools.codegenscript.timeout. The default value is 60000, but depending on your PC’s performance, increasing this value can help prevent timeouts during code generation.

In the same s32ds.ini file, look for the memory allocation line, for example: Xms256m. You may increase this value up to the maximum supported by Eclipse—up to approximately 8 GB (8194m).

Lastly, if possible share the .mex file, I can try to reproduce the behavior on my side and help determine whether the issue is related to the environment, project configuration, or another cause.

BR, VaneB

[abhi_hatte]

Hello @VaneB ,

Thank you for your suggestions.

I would like to update that when I closed S32 Design Studio, then deleted the .metadata and RemoteSystemsTempFiles folders from the workspace. After restarting S32DS, the project opened correctly and the issue appears to be resolved.

Thanks & Regards,

Abhishek Hatte

[VaneB]

Hi @abhi_hatte 

Thank you for your feedback. I am glad to hear that the problem has been resolved.

[abhi_hatte]

Hello @VaneB ,

I am currently working on bringing up the S32K312 Development Board using S32 Design Studio.

I would like guidance, example projects, or documentation to verify basic hardware functionality in the following sequence:

 1. RGB LED Test

• As an initial step, I want to confirm the board is operational by toggling the onboard RGB LED.
• Configure GPIO pins for RGB LED
• Blink/toggle each color individually
• Any example project or reference would be helpful

 2. SPI Interface Verification

• After confirming basic GPIO functionality, I want to test the SPI peripheral.
• Configure SPI (preferably LPSPI)
• Send and receive test data
• Loopback example or communication with an external SPI device
• Example project for S32K312 would be highly appreciated

[VaneB]

Hi @abhi_hatte 

For testing the RGB LEDs, I recommend referring to the video included in the Getting Started with the S32K312MINI-EVB Evaluation Board for General Purpose. This video provides a step‑by‑step demonstration on how to configure and program a simple LED blink example. The procedure shown applies to any of the other LEDs on the board.

If you are using the S32K312EVB‑Q172, please consult the board schematic or the Evaluation Board Hardware User Manual, as there are hardware differences compared to the MINI‑EVB.

For SPI communication example codes, please refer to the following community thread where sample implementations have been shared:

• Example S32K31 SPI multiple packet Transmit & Receive : solution for DMA Cache issue
• Example S32K312 SPI Transmit & Receive Using Polling DS3.5 RTD300
• Example S32K312 SPI Transmit & Receive Using Interrupt DS3.5 RTD300