Hi,
I'm using S32 Design Studio 3.4 with the S32K1xx SDK RTM 4.0.1 for the S32K142.
I'm facing an issue where the .mex file and ConfigTools (Pins/Clocks/Peripherals) no longer open.
What happens:
I have already tried:
The project builds correctly, but the Configuration Tools editor never opens.
Has anyone seen this issue before? Is this caused by an SDK installation problem, corrupted Config Tools, or a workspace issue?
Any suggestions would be appreciated.
Hi @VaneB,
Thank you for your reply.
I installed S32K1xx SDK RTM 4.0.3 in S32 Design Studio 3.4 and created a new Hello project using the 4.0.3 SDK (not an imported project).
The project builds correctly, but the .mex file still does not open in the Configuration Tools editor.
When I double-click the .mex file, I can select S32 Configuration Tools as the editor, but after clicking OK, nothing happens.
I also verified that the Configuration Tools plugins (Pins Tool, Clocks Tool, Peripherals Tool, Framework, etc.) are installed.
Could you please advise what else I should check? Is there a known issue with the Configuration Tools editor not opening in S32DS 3.4?
Thank you.
Please note that S32K1xx SDK RTM 4.0.1 is not compatible with S32DS 3.4. For IDE version, the supported SDK versions are S32K1xx SDK RTM 4.0.2 and 4.0.3.
Based on the error, it looks like the IDE cannot find the SDK path. This can happen if the SDK is not installed, the project was imported, or the SDK location configured in the project does not match the SDK installed on your machine.
BR, VaneB
If you access any of the ConfigTools tools, are you able to see and select the project you created from the drop-down list?
VaneB_0-1785858415839.png
And .project file :
不知道為什麼 別的 .dox檔案 都是 :
就是偶爾會冒出幾個 硬要標新立異 用 S32SDK_S32K1XX_RTM_4.0.2
Similar conflicts have occurred many times before.
Didn't your company think about resolving the conflict?
When installing SDK 4.xx, the installer automatically determines whether it is compatible with the current IDE version!
At least display a warning message.
Instead of having a bunch of people using the same equipment for so long, only to have problems arise later...
You all replied one by one saying that your IDE version is not suitable for installing the ooxx version of the SDK.
Some end-users will know in advance which "which" version of the IDE their SDK version is compatible with.
You should have prevented this from happening in the first place.
Instead of trying to stop everyone from misusing it like this, you then come to criticize it.
Those who agree, please click.