I have been using S32 DesignStudio 3.4 for quite some time for working with the S32K144 and find creating a new project, configuring the device and using the SDK so intuitive.
I decided to try the latest version of DesignStudio 3.6.4 and notice that there does not appear to be an SDK anymore but instead real-time drivers. Also, I create a new project from example and choose a simple Dio example and straight away, it will not build because a number of files are missing. Clicking on the .mex file opens the device configuration and most modules seem to be in error:
Why does this not compile without errors "out of the box" ?!
I then by accident found that you could right click on the error in the Problems window and choose to 'Add the SDK component' which then removes all the errors and the code builds
How is that intuitive !?
Sorry for the rant but it feels the design tools are becoming less intuitive over time.
Andy
Okay, so I created a new Dio project from example. Selected the project in the project explorer view. In the Config Tools menu, I clicked Update Code. It showed "No Change" for all of the source files. I hit Okay then build the project and get a number of errors including:
- ../src/main.c:26:10: fatal error: Mcu.h: No such file or directory
- C:/NXP/S32DS.3.6.4/S32DS/software/PlatformSDK_S32K1_S32M24/RTD/BaseNXP_TS_T40D2M30I0R0/include/Mcal.h:61:10: fatal error: DeviceDefinition.h: No such file or directory
It is interesting that this time, if I open the Peripherals view, I don't see errors against any of the modules like I did the first time.
However, why does it not build?
Andy
