Hello Radu,
With the MBD Toolbox for S32K3xx 1.1.0, we do provide both PMSM and BLDC Simulink examples configured for the S32K344 Q257 MCU, tested and developed on the S32K3X4EVB-Q257 and the GD3000, while the MCU peripheral configuration is performed in EB Tresos. Unfortunately, we do not deliver the S32CT examples in this release, and also the integrated AMMCLIB is 1.1.26, not 1.1.27. But both models come with the FreeMaster MCAT projects associated with them.
In terms of blocks and approaches, the toolbox for the S32K3 is much more different than the one for the S32K1, because of multiple reasons:
1. The C code for the S32K3 is generated on top of the Real-Time Drivers, HLD ( AUTOSAR's MCAL Layer) while the C code for the S32K1 is generated on top of the S32SDK (sort of low-level drivers).
2. Both physical MCUs integrate different Timer peripherals for the PWM signals generation. For example, the S32K3 uses the eMIOS to generate PWM signals. These signals are not delivered to the pins directly, instead, they are connected to the LCU peripheral, which doubles each PWM signal, to generate the High and Low gate side signals. This is the main reason why the motor control examples differ so much from the K1 to K3: the motor control peripherals are completely different.
3. The S32K3 uses an external configuration tool(EB Tresos or S32Configurtion Tool) to generate the code which controls the peripherals, while the S32K1 uses Simulink configuration blocks.
SFIO toolbox would help us to test some blocks from AMCLIB (for example clark) directly on the S32k344EVB257ND board with which we intend to develop the application.
The only toolbox capable of generating C code for the S32K3 is the MBD Toolbox for S32K3xx 1.1.0, so there is no SFIO toolbox to generate such code. If you want to test the Clarke Park Transforms on the S32K3, please have a look at the s32k3xx_ammclib_gmclib_foc_(F16/F32/FLT) examples. They are using the AMMCLIB 1.1.26 for the S32K3, the integrated AMMCLIB library for this release.
To be able to run this model using the S32CT, you have to open the Simulink model, go to Hardware Implementation, Tools Paths and select the S32 Config Tools.

The current setup for your Steer-by-wire development system is going to be on the S32K3X4 EVB with Motor GD and do you plan to use the S32 Configuration Tools for the MCU configuration?
Regards,
Marius