Product Release Announcement Automotive Processing S32 Design Studio for S32 Platform v3.3         Austin, Texas, USA Sep 22, 2019   The Automotive Processing's Software Development Tools Engineering Team at NXP Semiconductors is pleased to announce the release of the  S32 Design Studio v3.3 Here are some of major features: Eclipse Neon 4.6 Framework GNU tools: GCC version 6.3.1 20170509, build 1620 revision g01b30c3 GCC version 9.2.0 20190812, build 1649 revision gaf57174 NPW support for GCC 9.2 toolchain (available for selected devices only) S32 Configuration Tool framework 1.1 update 1 with the Pin, Clock, Peripheral, DCD, IVT, DDR and QuadSPI Configuration tools  The wizards for creating application, library projects and projects from project examples for the supported processor families The S32DS Extensions and Updates tool S32 Trace Tool S32 Debugger support PEMicro® debugger support Lauterbach Trace32® support Green Hills compiler support S32 Flash Tool Peripheral Registers view and EmbSys Registers view SDK management Support for importing MCAL configuration to a custom SDK Support for migration: project with GCC 6.3.1 toolchain to GCC 9.2 toolchain S32DS for ARM  projects for S32K1 device to S32DS 3.3, including SDK* * available with S32K1 package, not yet released Release is available for download on NXP web and from S32DS 3.3. Please make sure that you get new activation ID for this version. Support for S32S247TV and S32V23x is available on public update site and release location. S32V23x support: S32SDK S32V234 RTM 1.0.1  S32 Configuration tools - Pins, CLocks, Peripheral (installed with SDK package) S32 Debugger (with S32 Debug Probe) support for ARM cores S32 Trace for A53 cores GCC version 6.3.1 20170509, build 1574 S32 Flash Tool support AMMCLIB 1.1.20 P&E and Lauterbach debuggers support Note: Vision Extension package 1.0.0 is not compatible with S32 Design Studio 3.3, if you need to work with VSDK and Vision tools - it is recommended to stay on S32DS 3.2 untill a new version of Vision Extension package is released   S32S247TV support: Support for S32S247TV new project wizards, GCC 6.3.1 and GHS compilers S32SDK S32S247TV EAR 0.8.1  S32 Configuration tools - Pins, CLocks, Peripheral, DCD, IVT (installed with SDK package) S32 Debugger (with S32 Debug Probe) support  S32 Flash Tool support Lauterbach support P&E and Lauterbach debuggers support S32 Design Studio Versions   S32DS IDE for S32 Platform S32DS IDE for Arm® S32DS IDE for Power Architecture® S32DS IDE for Vision Devices Supported S32V23x S32K1xx MPC56xx S32V234 S32S247TV KEA MPC57xx   S32 Platform Devices MAC57D54H S32R2xx/S32R3xx   Integrated NXP Tools S32 Flash Tool FreeMASTER FreeMASTER DDR stress tool DDR stress tool     Integrated Configuration Tools S32 Configuration Tools Processor Expert Configuration Tool Processor Expert Configuration Tool  DDR configuration tool Pins Wizard Pins Wizard Pins Wizard Clocks configuration Peripheral/Drivers configuration   Peripheral/Drivers configuration   Peripheral/Drivers configuration   DCD/IVT configuration       DDR configuration tool       Integrated NXP Software S32 SDK S32K1 SDK S32 SDK Vision SDK FreeRTOS FreeRTOS FreeRTOS Linux BSP AMMCLib for S32V23x AMMCLib for KEA and S32K AMMCLib for MPC56xx and MPC57xx MCUs   Vision SDK KEA SDK Radar SDK Linux BSP MQX OS/MQX Drivers for MAC57D54H     Compilers: NXP GCC 6.3.1* NXP GCC 9.2 NXP GCC 6.3.1* NXP GCC 4.9* NXP GCC 6.3.1* GreenHills GreenHills GreenHills   IAR IAR Diab     GCC 4.9*     DEBUGGERS Built-in GDB interface: S32 Debugger/S32 Debug Probe P&E Multilink/Cyclone/OpenSDA P&E Multilink/Cyclone/OpenSDA S32 Debugger/S32 Debug Probe P&E Multilink/Cyclone/OpenSDA Segger J-Link   P&E Multilink/Cyclone/OpenSDA DEBUGGERS supported: Lauterbach Lauterbach Lauterbach Lauterbach   iSystem iSystem   IAR PLS   Host Operating Systems: Microsoft Windows® 7/8/10 64-bit OS (with 32-bit binaries)  – Ubuntu 14.04, 16.04 (64 bit) – Debian 8 (64 bit) – CentOS 7 (64 bit) Microsoft Windows® 7/8/10 32/64-bit OS (with 32-bit binaries)  – Ubuntu 14.04, 16.04 (64 bit) – Debian 8 (64 bit) – CentOS 7 (64 bit) Microsoft Windows® 7/8/10 32/64-bit OS (with 32-bit binaries)  – Ubuntu 14.04, 16.04 (64 bit) – Debian 8 (64 bit) – CentOS 7 (64 bit) Microsoft Windows® 7/8/10 32/64-bit OS (with 32-bit binaries)  – Ubuntu 14.04, 16.04 (64 bit) – Debian 8 (64 bit) – CentOS 7 (64 bit) Vision specific tools : NXP APU Compiler     NXP APU Compiler ISP assembler     ISP assembler ISP and APEX graph tools     ISP and APEX graph tools Radar specific tools :     SPT assembler       SPT Explorer/ SPT graph tool   Complete S32 Design Studio for S32 Platform v3.3 release notes are attached.   Installation To download the installer please visit the S32 Design Studio product page download section or click the direct here.     The installer requires the Activation ID to be entered. You should receive a notification email including the Activation ID after the download of the installation package starts. The installer installs just the base tools/package. In order to start development it is necessary to install at least one Development package. Currently the only development packages available are S32S2xxTV and S32V2xx. The application packages are managed by S32DS Extensions and Updates. Technical Support S32 Design Studio issues are tracked through the S32DS Public NXP Community space. https://community.nxp.com/community/s32/s32ds  

        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Vision v2.0          Austin, Texas, USA September 15, 2017 The Automotive Microcontrollers and Processors’ Embedded Tools Team at NXP Semiconductors, is pleased to announce the release of the S32 Design Studio for Vision  v2.0. The S32 Design Studio enablement simplifies and accelerates the deployment of ADAS vision and neural network solutions in automotive, transportation and industrial applications. Release Content Eclipse Neon 4.6 Framework GNU Tools for ARM® Embedded Processors (launchpad) build (4.9.3 20150529) ARM64: Linaro GCC 4.9-2015.05 Libraries included: newlib, newlib-nano and ewl2 (ewl and ewlnano) NXP Array Processor Unit (APU) Compiler P&E Multilink/Cyclone/OpenSDA (with P&E GDB Server) Fully integrated Vision SDK release v.1.0.0. (for the details on the feature set of SDK please refer to Reference Manuals) New Project wizard to create application, library and Visual Graph projects for supported devices Visual Graph tools to support ISP and APU/APEX2 program development Peripherals Register View DDR configuration and validation tools Lauterbach debugger support by new project wizard Kernel Aware debugging for FreeRTOS, OSEK. Devices supported: S32V234 Complete S32 Design Studio for Vision v2.0 release notes are available here. Installation To download the installer please visit the S32 Design Studio product page downloads section or click the direct here. The installer requires the Activation ID to be entered. You should receive a notification email including the Activation ID after the download of the installation package starts. For more information about the product installation see S32DS Vision 2.0 Installation Manual.   Technical Support S32 Design Studio issues are tracked through the S32DS Public NXP Community space. https://community.nxp.com/community/s32/s32ds  

        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power v1.2             S32 Design Studio for Power v1.2 (Windows/Linux) has been released. This is a complete installer which does not require any previous version to be installed. To download the installer please visit download section: www.nxp.com/s32ds What is new? New devices: • MPC5632M, MPC5633M, MPC5634M • MPC5642A • MPC5674F • MPC5673K, MPC5674K, MPC5675K • S32R372 New features: • Compiler update – see details in compiler release notes attached below • View for the Special Purpose Registers added • Improvements for Peripherals Register view • Added support for Semihosting/Debug console for single core devices • RESET functionality added, the hardware reset2 is executed for main/boot core and individual core reset for secondary cores. • Improvements for SPT diagram to display instruction labels and key parameters • SDK mechanism improvements to support SDK per build configuration • FreeMaster Serial Communication driver 2.0 integrated • iSystem debugger support added to New Project Wizard • SPT assembler update • Updated P&E debug plugins and drivers to the latest and greatest versions Note: The plugins to support GreenHills, IAR, iSystem, Lauterbach are not included and have to be installed from corresponding update site or installation. S32DS release notes are available here. GCC Build tools release notes are here.   Installation Notes The installer requires NEW Activation ID to be entered during the installation. You should receive an email including the Activation ID after starting the download process e.g:    

S32 Design Studio (S32DS) supports Wind River Eclipse plug-in which integrates Wind River Diab tool chain for e200 (PowerPC architecture) into Eclipse IDE. S32DS integration by a new project wizard that allows to create a new project with Wind River Diab build tools. The generated executable can be then debugged by any supported debugger plug-in (PEMicro, iSystem, PLS, Lauterbach) S32 Design Studio versions that support Wind River Diab plugin: S32DS Power v1.1+   Installation instructions First of all make sure you have Wind River Diab tools installed on your machine.  You can start with Wind River Diab Compiler 5.9.6 Evaluation  Anyway, after your evaluation period expires you need a valid license from Wind River to be able to use this plug-in in S32DS. The plug-in is available with the Diab compiler and it's located here: "<WindRiver home folder>\compilers\eclipse_cdt"   1. Run S32 Design Studio and go to menu "Help" -> "Install New Software" and  click on "Add..." button. Enter the local location to the folder above. 2. select the "Diab Compiler Support for Eclipse C/C++ IDE " and click "Next"   3. Read and Tick " I Accept the terms of the license agreement" and agree with installation of the unsigned content. 4. When the plug-in is successfully installed you will be asked to restart S32DS.     5. Set the path to the Diab compiler for your workspace (S32DS_DIAB_PATH environment variable) in the Window->Preferences->C/C++->Build->Build Variables (Show System Variables). If you switch the workspace you will need to enter this path again. Now you should be able to create a new project with Wind River Diab toolchain available: The created project includes Diab specific files such as "dld", startup code as well as tools specific setup in the project properties (Project Properties->C/C++ Build->Settings (Tools Settings Tab)    Enjoy building with Wind River Diab plug-in in S32DS!

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture 2017.R1 Update 11          What is new? S32 SDK for Power Architecture RTM 3.0.0 supporting  S32R274, S32R372, MPC574x-B-C-G, MPC574x-P, MPC574x-R and MPC577x-B-E-C (see the S32 SDK release notes) Integrated Radar SDK RTM 1.2.1 (see the Radar SDK release notes) This is a cumulative update - it includes all of the content of previous updates (Update 1, Update 2, Update 3, Update 4, Updates 5 and 6, Update 7, Update 8, Update 9, Update 10  ). Installation instructions The update is available for online installation (via S32DS Eclipse Updater) or offline installation (direct download link)  installation:  go to menu "Help" -> "Install New Software..." dialog  select predefined update site "S32DesignStudio - http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_POWER_2017.R1/updatesite" select all available items and click "Next" button offline installation:   go to S32 Design Studio for Power product page -> Downloads section or use direct link to download the update archive zip file  Start S32DS and go to "Help" -> "Install New Software..." Add a new "Archive" repository and browse to select the downloaded update archive zip file you downloaded in the previous step Select all available items and click "Next" button.   This will start the update installation process.

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture 2017.R1 Updates 5 and 6          What is new? S32 SDK for Power Architecture 1.0.0 RTM supporting MPC574xx.  Service Pack supporting MPC5775 B/E This is a cumulative update - it includes all of the content of previous updates (Update 1, Update 2, Update 3, Update 4 ). Installation instructions The update is available for online (via S32DS Eclipse Updater) or offline installation (direct download link) online installation:  go to menu "Help" -> "Install New Software..." dialog  select predefined update site "S32DesignStudio - http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_POWER_2017.R1/updatesite" select all available items and click "Next" button   offline installation:   go to S32 Design Studio for Power product page -> Downloads section or use  direct link to download the update archive zip file  Start S32DS and go to "Help" -> "Install New Software..." Add a new "Archive" repository and browse to select the downloaded update archive zip file you downloaded in the previous step Select all available items and click "Next" button.   This will start the update installation process.

This Example demonstrates an alternative way to multi-core projects. This is basically a single eclipse project that generates the single elf file for dual core MCU (MPC5777C) See the project structure below where the sources for each core are separated into a core specific source folder: Main core0 [e200z7_0] performs basic initialization (Clocks, ports..) Each core initializes the interrupt controller in order to service interrupts generated by PIT (Periodic Interrupt Timer): Core 0 (e200z7_0) services PIT channel 0 interrupts generated once per second. Core 1 (e200z7_1) services PIT channel 2 interrupts generated once per two seconds.

This instruction details the steps to create an image vector table, then subsequently generate a blob image which can be written to external flash on the S32R45 EVB. For this, the 'hello_world_s32r45' example project from the S32R45 SDK installed to S32 Design Studio IDE. This instruction shows the process for QSPI, however, SD, MMC, and eMMC are also supported.   The Image Vector Table (IVT) image is a set of pointers to other images which are required by the BootROM. It typically contains the following images, though not all are required to create a valid IVT image: DCD Self-Test DCD HSE Application Bootloader   The IVT Tool enables configuration and generation of the IVT image as specified in the BootROM reference manual.   Prerequisites Before using the IVT Tool, it will be useful to have already generated the binary image from your application project, it will be an input to the IVT. It may also be necessary to include a DCD image, for example, to initialize the SRAM. For application bootloader image, follow the steps in HOWTO: Generate S-Record/Intel HEX/Binary file, selecting 'Raw binary' option. For DCD image, follow the steps in HOWTO: Use DCD Tool To Create A Device Configuration Data Image .     Procedure With desired project open in project explorer (C/C++ perspective), switch to IVT perspective. Click on 'Open IVT'. In the Boot Configuration section, check that the correct Boot Target is selected. For the demonstration here, M7_0 is the correct selection. Check the 'Interface selection' section. If your intended boot device is SD, MMC or eMMC, then change the setting from QuadSPI Serial Flash. If your intended boot device is QuadSPI AND you do not have a QuadSPI parameter file to specify, then uncheck the box for 'Configure QuadSPI parameters'. QuadSPI parameters change some flash registers' settings away from the default setting and are generally required for larger memory sizes (for ex. applications over 1 MB in size, for some supported devices). From the Image Table section, depending on your configuration, turn off all unused images. For the demonstration here, the following will be changed to Reserved: Self-Test DCD, Self-Test DCD (backup), DCD (backup), Application bootloader (backup). The following images will remain enabled: DCD, Application bootloader. In DCD section of the Image Table, click 'Browse File' and select the DCD binary file. Ignore the red shading on the Start address and Size in bytes fields for now. Now the red shading should be resolved. This is appearing because when the DCD section was enabled, it added a block to the Memory Layout map. But the other blocks in the map are unchanged resulting in overlaps. To resolve this, click on the ‘Align’ button from within the Automatic Align section.. After the Memory Map has been aligned, a confirmation message will be displayed and the red shading will disappear. In Application bootloader section, again use  'Browse File' and select the application binary. When the application boot image is loaded, the tool processes the file to check if it contains the header for the application bootloader image. If the header is not found, it means that the file is only the raw code (the bin generated by S32 Design Studio) and it will be necessary to provide the values for RAM start & entry addresses (code length is automatically calculated), as noted with the expanded view and red shading. To set the RAM start pointer and entry pointer addresses, from to the C/C++ perspective: From Project Explorer on the C/C++ perspective, open the linker file (hello_world_s32r45\Project_Settings\Linker_Files\S32R45_common_ram.ld) and locate the RAM start address and enter it in both the RAM start pointer AND RAM entry pointer fields in the IVT Tool. Since the application binary file which was loaded is just a raw binary file, it is necessary to generate the full application bootloader image. The Export Image function takes the values entered for the RAM start & entry pointers and Code length, then generates the Application bootloader header. This header is added to the raw binary file producing a new image, the full application bootloader image file. Within the Application bootloader section, click 'Export Image' and enter a meaningful name for the image file. In addition to being a necessary source component of the IVT image, this file can more easily be shared or re-used to as an input to other IVT images. After the file has been generated, you will notice that the address settings section has collapsed. This is because it has replaced the file you originally selected with the newly generated one and the tool has recognized that the file contains the required header information. Click 'Export Blob Image' to generate the blob image file. This is what will be flashed to the target. Now that the Blob Image is generated, the 'Flash Image' button could be used to program the image to the target over serial connection, use the S32 Flash Tool, or over the JTAG connection using the Flash Programmer within the S32 Debugger (QSPI only).

S32 Design Studio (S32DS) for Power architecture supports PLS UDE Eclipse plug-in to debug S32DS projects via a PLS probe directly in S32DS Eclipse IDE. This feature is supported by all versions of S32DS for Power.   This plug-in supports the features below: Seamless integration of complete functionality of Universal Debug Engine inside of the Eclipse IDE UDE provides an own perspective of the Eclipse IDE and integrates UDE workspace in Eclipse workspace Code breakpoint can be set either by C/C++ editors or by UDE specific functions For more details about the plugin read  "UDE Eclipse datasheet" located in the download section of PLS web site.   Installation instructions First of all make sure you have PLS UDE debugger installed on your computer. Then let's proceed to eclipse plug-in installation.   1. go to menu "Help" -> "Install New Software" and  click on "Add..." button and search PLS UDE installation folder for the archive file named "UDEEclipse4Integration.zip" 2. select the Universal Debug Engine component and click "Next"     3. Finally you proceed to the installation. You will be asked to confirm installation of unsigned content. The UDE plugin requires restart after the installation.     Create a new project with UDE  You should be able to create a new S32DS project via S32DS new project wizard where PLS UDE Debugger support is now available. The UDE plugin enables a new group of UDE eclipse debug configurations to manage (create, delete, adjust) The UDE debug configuration created with a new project requires some changes before you can proceed to debugging. 1. Enter a new UDE workspace name under "<Project>\.ude" folder by clicking on "New Workspace" button 2. Create a new UDE Target configuration file. click on "Create Configuration" button and select "Use a default target configuration" and your target MCU. (in this example MPC5744P). Save the configuration file into your project folder e.g. "<Project>\Project_Settings\Debugger\nxp_mpc5744p_cut2_debug_jtag.cfg" Running the debugger opens UDE specific debug eclipse view where you can benefit from many advanced debugging features including tracing, scripting... Enjoy debugging with PLS UDE Eclipse plug-in in S32DS!

PEmicro’s debug configuration allows user to modify JTAG communication shift frequency between debug interface and the target. By default, this frequency is set to a maximum value of 5000KHz, to take advantage of the fastest run control and FLASH programming experience: At the same time, not every PowerPC processor might be able to support highest debug shift frequencies with all PEmicro debug interfaces. For example, debug frequency for MPC5634M board used in conjunction with Multilink Universal FX RevC , needs to be lowered to 4000Khz in order to succeed. Hence, if debug session fails to successfully start up or fails on FLASH programming, lowering a debug shift frequency by a factor of 2 or 4 is the first trouble shooting recommendation. To get to PEmicro’s debug configuration window, one should select “Debug Configuration” from the menu next to a debug icon, and switch over to the Debug tab, within “Debug Configuration” menu pop- up.

Please note: AMMCLib SDK is standalone from S32/MPC SDK, it is intended for users who will not use the S32/MPC SDK. The AMMCLib SDK does not support all toolchains listed in S32DS new project wizard. For the toolchains it does support, It does not support all versions. The available SDKs will vary depending upon the toolchain which is selected. When creating a new S32DS Application Project, you may have noticed the S32K14x_AMMCLib_xxx SDK option in the Select SDK menu. This is the standalone version of the AMMCLib. If you plan to use one of the S32/MPC SDKs, then it most likely contains an integrated version of the AMMCLib. For this integrated case, the AMMCLib is accessed like any other S32/MPC SDK component and you would not need to add the standalone version. To add the AMMCLib SDK to your project, simply add it in the New Project Wizard (as pictured above) or add it later through the project properties menu, SDKs: Select the SDK from the list and then click 'Attach/Detach...' Click in the column for each build configuration for which you wish to have the SDK attached. You can remove SDKs by clicking the '+', causing it to disappear. It should also be noted that there exist example projects which demonstrate usage of the AMMCLib, though these show usage of the S32/MPC SDK integrated version. When working in your project, you can use the SDK Explorer to drag and drop macros and function calls into your code. To add the SDK Explorer view to your perspective, there are at least 2 methods: 1) Menu method a) Window -> Show View -> Other... OR Alt + Shift + Q, Q b) Filter on 'SDK' c) Select 'SDK Explorer' d) Click OK 2) Quick Access method a) Type 'SDK' b) Select 'SDK Explorer' To access the macros and function calls from the SDK Explorer: 1) Go to the Project Explorer and select your project to make it active. 2) Go to SDK Explorer and all of the SDKs you included in the project will be listed. 3) For the SDK you wish to access, expand the folders and files until you can see the function you wish to add. You can set some filters to hide unwanted content. 4) Simply drag and drop the macro/function call into your source file. The #include statement for the associated header file will be automatically added near the top of your source file. Happy math coding with AMMCLib!

******************************************************************************** * Detailed Description: * This example shows, how to use printf function in project. * Files uart_console_io.c, uart.c and uart.h was added. These files contain * necessary functions for correct printf() functionality * * * Test HW:         FRDMPK144-Q100 * MCU:             PS32K144HFVLL 0N77P * Terminal:        9600-8-no parity-1 stop bit-no flow control on LPUART1 * Fsys:            160 MHz * Debugger:        Lauterbach Trace32 *                  PeMicro USB-ML-PPCNEXUS *                  OpenSDA embedded debug * Target:          internal_FLASH, internal RAM * EVB connection:  default

One of the many great features of the S32DS is the ability to access the Linux BSP file system on the SD card in the S32V234-EVB. Once connected, you can drag and drop files between your PC and the EVB. Once you have completed HOWTO: Setup S32V234 EVB2 for debugging with S32DS and Linux BSP  and HOWTO: Setup A Remote Linux Connection in S32DS (S32V234), you are ready to setup the Remote Systems view to connect to the Linux files system to view and access the file system. Prerequisite Before starting this procedure, make sure the BSP is loaded onto the SD Card, the SD Card is inserted into the SD Card Slot, the ethernet cable is connected to both the EVB and the network port, and the EVB is powered up. 1) Go to 'Window -> Show View -> Other' 2) Expand 'Remote Systems', then select "Remote Systems' and click OK 3) Click 'Define a connection to remote system' button OR right-click in the Remote Systems window and select 'New Connection...' from the list Right-click menu 4) Select 'SSH Only' 5) Enter the IP address noted from HOWTO: Setup A Remote Linux Connection in S32DS (S32V234) for Host name, enter a descriptive name for the connection (optional) and click Finish. 6) Right-click on the connection name in the Remote Systems window and select 'Connect' OR expand the folders under the connection name until the login window appears: Connection_name -> Sftp Files -> Root (window appears) 7) Enter "root" for User ID and since the BSP comes with ID root without a set password, leave the password field blank. 😎 Click OK 9) The Linux file system is now visible in the Remote Systems window. You can drag and drop files to and from here. Expand the folders to see the contents.

        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture v1.2, Update 3            September 21, 2017   What is new? S32 SDK EAR 0.8.1 supporting MPC5748G & MPC5748C. The new project wizard now offers the new version of S32 SDK: "New S32 Project from Example" offers additional demos and examples. The complete S32 SDK EAR 0.8.1 release notes attached below. Installation instructions This is a cumulative installer - all previous updates (except previous version of S32 SDK EAR 0.8.0) are included so you do not need to install any previous update. The update is available for online (Eclipse Updater) or offline (direct download link) installation. online installation go to menu "Help" -> "Install New Software..." dialog  select predefined NXP S32 Design Studio update repository select all available items http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_POWER_1_2/com.freescale.s32power.updatesite click "Next" button offline installation  go to S32 Design Studio product page -> Downloads section or use the direct download linkand download the "S32 Design Studio for Power v1.2 - Update 3" file. Start S32DS and go to "Help" -> "Install New Software..." Add a new "Archive" repository and browse to select the downloaded Update 3 archive file Select all available items and click "Next" button.

S32 Design Studio for S32 Platform - 3.6.x releases   Date Version Release content/NPI support Download link Notes November 28, 2025 S32DS 3.6.5   S32K3 S32K1 S32M2 S32G S32ZE S32N S32R41 S32R45 S32R47 SAF8xxx S32J nxp.com Flexera Win/Linux installer for S32DS 3.6.5 with all public NPI's  integrated September 30, 2025 S32DS 3.6.4   S32K3 S32K1 S32M2 S32G S32ZE S32N S32R41 S32R45 S32R47 SAF8xxx nxp.com Flexera Automotive Software Package Manager Win/Linux installer for S32DS 3.6.4 with all public NPI's  integrated July 31, 2025 S32DS 3.6.3 S32K3 S32K1 S32M2 S32G S32ZE S32R41 S32R45   nxp.com Flexera Automotive Software Package Manager Win/Linux installer for S32DS 3.6.3 with all public NPI's  integrated May 30, 2025 S32DS 3.6.2 S32K3 S32K1 S32M2 S32G S32ZE S32R41 S32R45   nxp.com Flexera Automotive Software Package Manager Win/Linux installer for S32DS 3.6.2 with all public NPI's  integrated March 31, 2025 S32DS 3.6.1 S32K3 S32K1 S32M2 S32G S32ZE S32R41 S32R45 nxp.com Flexera Automotive Software Package Manager Win/Linux installer for S32DS 3.6.1 with all public NPI's  integrated Nov 29, 2024 S32DS 3.6.0 S32K3 S32K1 S32M2 S32G S32ZE S32R41 S32R45 nxp.com Flexera Automotive Software Package Manager Win/Linux installer for S32DS 3.6.0 with all public NPI's  integrated   S32 Design Studio for S32 Platform - 3.5.x releases   Date Version Release content/NPI support Download link Notes July  29, 2022 S32DS 3.5 base/platform package Flexera Win/Linux installer for S32DS 3.5  Sep 30, 2024 S32DS 3.5.14 Update 14 with support for S32Z2/E2 SPF2 Add-On 1.5.0 download offline package installable on previous S32DS 3.5.x installations via S32DS Extensions and Updates (see installation Note* from below) Jul 31, 2024 S32DS 3.5.13 Update 13 with support for: S32R45 Development Package 3.5.13 S32Z2/E2 Development Package 3.5.13 S32K3xx Development Package 3.5.13 S32K39x Development Package 3.5.13 S32M2xx Development Package 3.5.13 S32R45 Radar Extension 1.5.0 S32R45 BBE32 Add-On 1.5.0 S32Z2/E2 SPF2 Add-On 1.4.0 download May 31, 2024 S32DS 3.5.12 Update 12 with support for: S32N5 Development Package 3.5.12 SAF85xx and SAF86xx Development Package 3.5.12 SAF85xx Radar Extension Package 1.2.0 SAF85xx and SAF86xx BBE32 Add-On 1.3.0 download Mar 29, 2024 S32DS 3.5.11 Update 11 with support for: S32Z2/E2 SPF2 Add-On 1.3.0 SAF86xx Development Package 3.5.11 SAF86xx BBE32 Add-On 1.2.0 download Jan 31, 2024 S32DS 3.5.10  Update 10 download Dec 20, 2023 S32DS 3.5.9  Update 9 download Nov 29, 2023 S32DS 3.5.8 Update 8 with support for: S32K3xx Development Package 3.5.8 S32M2xx Development Package 3.5.8 download Sep 29, 2023 S32DS 3.5.6 Update 6 with support for: S32Z2/E2 Development Package 3.5.6 S32Z2/E2 SPF2 Add-on package for  1.2.0 S32K39x Development Package 3.5.6 download Aug 31, 2023 S32DS 3.5.5 Update 5 with support for: S32R45 Development Package 3.5.5 Radar Extension and BBE32 Add-on package for S32R45 1.4.0 S32V2 Development Package 3.5.5 download Jul 31, 2023 S32DS 3.5.4 Update 4 with support for: S32K1 Development Package 3.5.4 download Jun 30, 2023 S32DS 3.5.3 Update 3 with support for: S32Z27/E27 Development Package S32R41 Development Package S32R41 Radar Extension Package S32R41 BBE32 Add-on download Feb 28, 2023 S32DS 3.5.2 Update 2 with support for: S32G, S32R41, S32V2 Development Packages download (Note*) Installation procedure for platform update/development/extended/add-on packages: Install S32 Design Studio v3.5 (base/platform) version using Win/Linux installer Download the archive files for platform/dev/ext/add-on package. Start S32 Design Studio v3.5 and install the application package. Go to  Help > S32DS Extensions and Updates. In the S32DS Extensions and Updates dialog box, click Add Update Sites. Navigate to the directory with the downloaded ZIP file. Choose it and click Open, then click OK. You will get back to  S32DS Extensions and Updates and can use this dialog to select desired packages. Q: How to install S32DS 3.5.6 ? A: install S32DS 3.5 base/platform using Win/Linux installer and apply Update 6 or apply Update 6 on existing S32DS 3.5.1-5 installation S32 Design Studio for S32 Platform - legacy versions   S32 Design Studio for S32 Platform 3.4 (Windows/Linux) S32 Design Studio for S32 Platform 3.4 Update 1 (for S32G2) S32 Design Studio for S32 Platform 3.3 (Windows/Linux)  S32 Design Studio for S32 Platform 3.2 (Windows/Linux)  S32 Design Studio 3.2 - Update 191226 S32 Design Studio 3.2 - Update 191219 S32 Design Studio 3.1 (Windows/Linux) S32 Design Studio 3.1 - Update 2    S32 Design Studio 3.1 - Update 190708  S32 Design Studio 3.1 - Update 190508  S32 Design Studio 2018.R1 (Windows/Linux)   Development packages S32K1 Service Pack 1 (S32 Design Studio 3.4) S32K1xx dev package and S32 SDK for S32K1xx RTM 4.0.0 (S32 Design Studio 3.3) Extension packages Vision Extension Package for S32V234 1.2.0 (S32 Design Studio 3.3) Vision Extension Package for S32V2xx 1.0.0 (for S32 Design Studio 3.1)   S32DS for Arm S32 Design Studio for Arm 2.2 (Windows/Linux)  S32 Design Studio for Arm 2.2 - Update 1 S32 Design Studio for Arm 2018.R1 (Windows/Linux)  S32 Design Studio for Arm 2018.R1 - Update 11  S32 Design Studio for Arm 2018.R1 - Update 10  S32 Design Studio for Arm 2018.R1 - Update 9  S32 Design Studio for Arm 2018.R1 - Update 8  S32 Design Studio for Arm 2018.R1 - Update 7 S32 Design Studio for Arm 2018.R1 - Update 6  S32 Design Studio for Arm 2018.R1 - Update 5 S32 Design Studio for Arm 2018.R1 - Update 4  S32 Design Studio for Arm 2018.R1 - Update 3 S32 Design Studio for Arm 2018.R1 - Update 2 S32 Design Studio for Arm 2018.R1 - Update 1 S32 Design Studio for Arm v2.0 (Windows/Linux) S32 Design Studio for Arm v2.0 - Update 3 S32 Design Studio for Arm v2.0 - Update 2 S32 Design Studio for Arm v2.0 - Update 1 S32 Design Studio for Arm v1.3 (Windows/Linux)  S32 Design Studio for Arm v1.3 - Update 3 &amp; 4 S32 Design Studio for Arm v1.3 - Update 2 S32 Design Studio for Arm v1.3 - Update 1 S32 Design Studio for ARM v1.2 (Windows/Linux)    S32DS for Power S32 Design Studio for Power Architecture v2.1 (Windows/Linux)  S32 Design Studio for Power Architecture v2.1 - Update 14 S32 Design Studio for Power Architecture v2.1 - Update 13 S32 Design Studio for Power Architecture v2.1 - Update 12 S32 Design Studio for Power Architecture v2.1 - Update 10  S32 Design Studio for Power Architecture v2.1 - Update 8  S32 Design Studio for Power Architecture v2.1 - Update 7  S32 Design Studio for Power Architecture v2.1 - Update 2  S32 Design Studio for Power Architecture v2.1 - Update 1  S32 Design Studio for Power Architecture 2017.R1 (Windows/Linux)  S32 Design Studio for Power Architecture 2017.R1 - Update 11  S32 Design Studio for Power Architecture 2017.R1 - Update 10  S32 Design Studio for Power Architecture 2017.R1 - Update 9 S32 Design Studio for Power Architecture 2017.R1 - Update 8 S32 Design Studio for Power Architecture 2017.R1 - Update 7  S32 Design Studio for Power Architecture 2017.R1 - Updates 5 and 6  S32 Design Studio for Power Architecture 2017.R1 - Update 4 S32 Design Studio for Power Architecture 2017.R1 - Update 3  S32 Design Studio for Power Architecture 2017.R1 - Update 2 S32 Design Studio for Power Architecture 2017.R1 - Update 1 S32 Design Studio for Power v1.2 (Windows/Linux)   S32 Design Studio for Power v1.2 - Update 3 S32 Design Studio for Power v1.2 - Update 2 S32 Design Studio for Power v1.2 - Update 1 S32 Design Studio for Power v1.1 (Windows, Linux)  S32 Design Studio for Power v1.1 - Update 1 S32 Design Studio for Power v1.0 (Windows)    Other Hot Fixes S32 Design Studio Offline activation issue hot fix 

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for ARM® 2018.R1  Update 8          What is new? S32K1xx SDK BETA 2.9.2 supporting S32K116, S32K118, S32K142, S32K144, S32K146, and S32K148. This is a cumulative update - it includes all the content of previous updates (Update 1, Update 2, Update 3, Update 4, Update 5, Update 6, Update 7 ) Installation instructions The update is available for  (via Eclipse Updater) or offline installation (direct download link)  installation:  go to menu "Help" -> "Install New Software..." dialog  select predefined update site "S32DesignStudio - http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_ARM_2018.R1/updatesite" select all available items and click "Next" button   offline installation:   go to S32 Design Studio for ARM product page -> Downloads section or use direct link to download the update archive zip file Start S32DS and go to "Help" -> "Install New Software..." Add a new "Archive" repository and browse to select the downloaded update archive .zip file you downloaded in the previous step Select all available items and click "Next" button.   This will starts the update installation process.

Problem description When installing S32 Design Studio using the offline activation method (Offline activation on S32 ) the installer may pop up an error dialog: " Error: "Invalid offline response, ResponseType"." This typically occurs on the computers that have no previous installation of S32 Design Studio.   Affected versions S32DS for ARM v1.1, v1.2, v1.3 S32DS for Power v1.1 S32DS for Vision v1.0 Newer versions should include the fix already. Solution Option A) Easiest solution is to use online method instead of offline. But in some cases it may not be possible (LAN restrictions, computer is not connected to the Internet or there is some other network obstacle etc.) Option B) Apply the hot fix attached. See the instructions below how to proceed for Windows and Linux (Ubuntu) users   Windows users Download and extract the attached archive file "licfix.zip" to your local machine (same package for Windows and Linux) Run "clean.bat" to reset trusted storage  Run "setts.bat" to run the activation fix and enter your activation ID for the product you need to activate Select offline activation type and save generated "request.xml" file Submit generated "request.xml" to your nxp.com account offline activation section and generate activation response "activation.xml" Save the created activation response, refresh the Activation response dialog and select the saved file The script is then successfully terminated and now you should be able to install S32 Design Studio Linux (Ubuntu) users Download and extract the attached archive file "licfix.zip" to your local machine (same package for Windows and Linux) Add the executable right to configure.sh script chmod 777 configure.sh Run the script as admin with parameter "install" to install appropriate libraries sudo ./configure.sh install Run the script as admin with parameter "reset" to reset trusted storage into its initial state  sudo ./configure.sh reset Run the script as admin with parameter "activate" to proceed to activation process sudo ./configure.sh activate Enter your activation ID for the product you need to activate Select offline activation type and save generated "request.xml" file Submit generated "request.xml" to your nxp.com account offline activation section and generate activation response "activation.xml" After this step the script should be terminated without any error message.   Now you should be able to install S32 Design Studio on your computer. Special thanks to Denis Robert and zhongzheng liu for your help with fix testing and to all of you who reported this nasty issue. Thank you!!! Stan

Included in the S32DS for ARM is a set of example projects, which include one called 'hello'. This example shows a basic application which activates an LED when a button is pressed on the S32K144EVB-Q100 evaluation board. The S32K SDK is not used in this example. In this HOWTO, we will show how to load the project into the workspace, build, download to the target, and run debug. 1. Create Project a. File -> New -> New S32DS Project from Example   OR from the Dashboard b. Select S32DS Example Projects -> S32K144 -> hello 2. Examine the code a. Locate the project in C/C++ Projects view b. Expand 'hello', then 'src' c. Double-click on 'hello.c', to open the file in the editor 3. Build the project a. Click to select hello project, this is to ensure that the tool knows which project you wish to build. b. Click Build button. By default, the standard 'Debug' build configuration will be used. Projects created using either the New S32DS Project from Example, or New S32DS Project wizard are setup with 3 build configurations: Debug, Debug_RAM, and Release. The 'Debug' configuration contains settings to build the project with the lowest compiler optimization setting and to occupy the Flash memory space on the target. The 'Debug_RAM' configuration is very similar to the 'Debug' configuration with one exception. It is set to occupy the RAM memory space on the target. The 'Release' configuration will build the project with the highest optimization setting and to occupy the Flash memory space on the target. c. From the console tab, the build status output is displayed. Check here to confirm the build completed and there were no errors. 4. Setup Debug Configuration a. Click Run -> Debug Configurations… OR from the Debug button menu b. Expand the 'GDB PEMicro Interface Debugging' group. c. Select the configuration which matches the build configuration you just used to build the project. For each build configuration generated by the new project wizard, it also generates a matching debug configuration. d. Select the Debugger tab. The debug configuration was created with the 'PE Micro GDB server' option selected, but there are several hardware options for this. Select the option which matches your hardware setup. For example, for the S32K144, most likely you have the standard evaluation board, which has OpenSDA integrated. In this case, you would use the OpenSDA interface option. For other MCUs, you may have hardware which requires the USB Multilink or Cyclone. e. Click Refresh to ensure the correct port is selected. 5. Click Debug to start the debugger launch sequence. It is not necessary to click on the 'Apply' button unless setting changes are being made without intention to launch the debugger. The scripts behind the Debug button include the actions of the script behind the Apply button. 6. When the launch sequence completes, the application is executed until the start of main(), where a breakpoint was automatically set. 7. It is now possible to run or step through the code, view variables and registers. 8. Click Resume and when Button 0 is pressed, the LED will turn on as Blue, and when Button 0 is released, the LED turns off. 9. To end the debug session, click the 'Terminate' button. It is a good idea to also click on 'Remove All Terminated Launches', before starting another debug session.

In recent releases of S32DS (Power v2017.R1, ARM v2.0, Vision v2.0) is new feature - you can add custom example into example list by copy example folder into [S32DS_INSTALL]\S32DS\examples path:  If you select New project from example - you can see your recently added project in User Examples folder. You can filter all examples by name or MCU model (for example all examples for S32K148):  Another useful improvement is possibility rename project before is inserted into active workspace. It allows you to have more projects based on the same example: If in your project folder is present description.txt file - the content of the file is shown in Create project dialog:

Function printf is C library function, which sends formatted output to stdout. Because microcontroller does not contain stdout, it it necessary to redirect it to a different type of output. One of the possible way is using UART. All MPC57xx has LinFlexD module, which supports UART mode.   For proper use the LinFlexD module, it is necessary to initialize it and also create simple functions for transmit and receive data. You can create your own file or use the file uart.c in the attachment. If you want to create your own file, please do not forget to implement the methods, which are called by MW MSL libraries to perform console IO (please look at the attached file uart.c).   In uart.h file, you will find correct function prototypes for functions used in uart.c and also some important enum data types.   Third important file is uart_console_io.c which you find in folder, where S32DS was installed. Open the folder and choose path: S32DS/e200_ewl2/EWL_C/src/sys. This file contains routines which implement low-level console IO routines.   Now, we have all basic files which help us to use printf function. So lets create new project and test printf. Example project is created for MPC5744P.   Create new project, choose EWL library and finish project wizard. Include stdio.h to the file, where you want to call printf function.   Now add uart.c and uart_console_io.c files to the project folder src. Add uart.h file to project folder include.   Initialize system clock and clock for peripherals (look at the attached project). In uart.c file, there are settings for GPIO pins, LinFlex initialization for UART mode and also baud rate calculation (please look at the uart.c file in the attachment).   Now it is possible to use printf function. Important point is, that \n character triggers the data sending. Also, if you do not use this \n character, you will get compile error, but I will explain this further in this tutorial.   Run some terminal emulation, for example Putty and use the following settings:   Now open terminal and  run the code in the microcontroller. This should be the result:   /*************************************************************************************************************************************************************************************/ /*************************************************************************************************************************************************************************************/ /*************************************************************************************************************************************************************************************/   This was the easiest way, how to use printf function. But printf also provides some format characters for printing decimals, floating points, etc. All options you can find in ewl_c_reference.pdf document which is place in S32DS installation folder S32DS/help/pdf.   When you want to use some of the characters mentioned above, you get the following compile error:   When you do not use any format characters in printf argument, function _EWL_CDECL puts(const char_t * s) from puts.c file is called on background. But when you use format characters in printf argument, function int_t _EWL_CDECL printf(const char_t * _EWL_RESTRICT format, ...) from printf.c file is called instead of puts.   Variable result saves value, which function __pformatter returns. But function __pformatter is not implemented. Instead of __pformatter, function __pformatterFP (placed in __printformat.c file) is implemented.   So there are two possible workarounds.   First workaround is place the following code to the Linker flags in project properties: -Xlinker --undefined=__pformatterFP -Xlinker --defsym=__pformatter=__pformatterFP   The code says that there is undefined symbol __pformatterFP (part -Xlinker --undefined=__pformatterFP) and define symbol alias __pformatter=__pformatterFP (-Xlinker --defsym=__pformatter=__pformatterFP ). So from my point of view, symbol __pformatter is replaced by __pformatterFP. Now the correct function is called and the project could be successfully built.     Second workaround is add the printf.c file from S32DS installation folder S32DS/e200_ewl2/EWL_C/src/stdio to the project src folder and exchange __pformatter for __pformaterFP. Clean project and recompile.       I hope this document helps you while implementing printf function in your projects.   Regards, Martin