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. Some of the fields may become red shaded after the file is loaded. This is OK as it is showing the memory layout is no longer aligned. This will be resolved in a later step.  Scroll down to the 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 (in this case: hello_world\Project_Settings\Linker_Files\<device_name>_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. Use copy and paste to add the values to the Application Boot Image settings. Since the application binary file which was loaded for this example 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 the automatically calculated 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. Before the Blob image can be generated, all of the images must be properly aligned within the memory map. You will likely also see error messages regarding segment overlaps, but even without this error it is good to check that the alignment is correct. In the Automatic Align section, if you have a dedicated area of the memory you can specify the start address and then click 'Align'. If you don't have a dedicated area, then use the default automatic align start address of 0x0 (QSPI), or 0x1000 (SD, MMC, eMMC). Click 'Align' to automatically align the images to this address. Upon successful completion of the alignment, all of the red shading will be removed. 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, or use the S32 Flash Tool.

Pin muxing is the process of assigning a peripheral function to a physical pin. This video will explain how fast and easy is to a configured pin muxing using Pins Tool from S32 Configuration Tool suite. Example is a UART project from S32V microcontroller SDK.

        Product Release Announcement Automotive Processing S32 Design Studio for ARM 2.2         January 31, 2020   The Automotive Processing's Embedded Tools Team at NXP Semiconductors is pleased to announce the release of the S32 Design Studio for Arm® v2.2.  Here are some of its major features: GNU Bare-Metal Targeted Tools for Arm® 32-bit Embedded Processors (GCC version 6.3.120170509, revision g7fea41d) GNU Tools for Arm® Embedded Processors (Launchpad) (GCC version 4.9.3 20150529,revision 227977) Libraries: NewLib, NewLib Nano, EWL, and EWL Nano Semihosting for Arm® 32-bit Bare-Metal Targeted toolchain MSYS2 32bit version 1.0.0 GDB 7.12.1 with Python support The wizards for creating application, library projects and projects from project examples The S32DS Extensions and Updates tool Support for importing projects from CodeWarrior for MCU v.10.6 and Kinetis Design Studio Support for importing MCAL configuration to a custom SDK IAR v7.x and v8.11.2 compiler support Green Hills compiler support SEGGER J-Link (with SEGGER GDB Server) iSystem, Lauterbach and IAR debuggers support PEMicro debugger support (P&E Multilink/Cyclone/OpenSDA) Kernel Aware debugging for FreeRTOS, OSEK MQX 4.2 for MAC57D54H EmbSys Registers view support FreeMASTER Serial Communication Driver v2.0 Sample Drivers for KEA family (Evaluation grade) Integrated S32SDK RTM 3.0.2 Integrated AMMCLIB SDKs 1.1.18 The Getting Started page   NOTE Support for S32V234 was moved to S32 Design Studio for S32 Platform 3.x and not included into S32 Design Studio for ARM anymore. The complete S32 Design Studio for ARM 2.2 release notes are attached below.   Installation Notes Please visit the S32 Design Studio for ARM product page - download section or direct link to download the installer. The installer requires the NEW Activation ID to be entered during the installation. You should receive an email that includes your Activation ID after starting the download.   Technical Support S32 Design Studio issues are tracked through the S32 Design Studio Public NXP Community space: https://community.nxp.com/community/s32/s32dsS32 Design Studio    

IVT - short for Image Vector Table, is an image with a set of pointers to other images which are required at boot by the embedded BootROM. This video will explain using S32V chip how IVT tool works and covers create and flash SDK's PIT example.

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 S32G274A EVB. For this, the 'hello_world_s32g274a' example project from the S32G274 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. 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. Some of the fields may become red shaded after the file is loaded. This is OK as it is showing the memory layout is no longer aligned. This will be resolved in a later step. In Application bootloader section of the Image Table, click 'Browse File' icon and select the image as noted in the Prerequisites section. 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: Open the linker file and locate the RAM start address and enter it in both the RAM start pointer AND RAM entry pointer fields in the IVT Tool. Use copy and paste to add the values to the Application Boot Image settings. The length must be adjusted since it is not 8 byte aligned. Since 14020 / 8  = 1752.5, we will round up to 1753. Then, 1753 * 8 = 14024, so we will enter 14024. 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 to represent that this information is now included in the application bootloader image which will be used to generate the Blob image file. 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).

PEmicro’s GDB Server can take advantage of four useful SWO debug tools: Power Measurement SWO ITM Console SWO Data capture Real-Time Expressions. This document describes how to enable and use these features. Note: To set up streaming for SWO debug features, the user should check the “Enable Streaming” checkbox in Debug Configurations during setup. Then the port should be specified in the Streaming Server Port text box. Hardware Requirements The following versions (or later) of PEmicro hardware interfaces are required to take advantage of SWO streaming functionality: Multilink FX Rev. C Multilink Universal Rev. D Multilink ACMP Rev. B Real-Time Power Measurement To enable Power Measurement capture, an active debug session must already be in process. Click the Gear Icon on the title bar of the PEmicro "Power Measurement” window. Select the frequency of data capture and check the Enable box. After clicking OK, Power Recording is now active. Note:    The Multilink FX debug probe is required for Real-Time Power Measurement Power Configuration Dialog The next time the target MCU is run, real-time power measurement readings will be shown. The user can start/stop power recording, zoom, export data, and more SWO Printf Console The SWO Printf Console will display messages which are streamed through the SWO pin and captured by the Multilink. There are two main configuration steps needed to leverage this feature. First, the project must be configured to re-direct the printf() statements to the SWO Printf peripheral. This is done at project creation time. Second, the green "Play" button on the SWO ITM Console needs to be clicked during an active debug session. This will cause data collection of SWO printf information to occur on the next Resume. Once data is streaming, the red “Stop” button will stop data streaming. Printf() Statements Displayed In SWO ITM Console The Multilink automatically measures the data communication rate on the SWO pin and adjusts to it automatically. This auto-detect sequence is done each time the processor is stopped in debug mode. If the running code changes the core frequency, a breakpoint should be set after the frequency change so the Multilink can adjust to the new SWO communications rate (which is a function of the core frequency). SWO Data capture The SWO Data view allows the user to configure variables to be tracked such that any reads and writes to these variables are captured and streamed to the Multilink via the SWO pin. This view shows all of the realtime access which have occurred along with the timing of the different accesses. For SWO data, there is a bit more setup.  The user needs to select the 'Eyeglasses+' symbol which will bring up a popup of Add datawatch items.  Simply enter the information of the different variables to be tracked. Up to four separate variables can be tracked simultaneously. In this example, we select that we wish to capture read and writes of the ledsOn and seconds variables. Once added, the user needs to select which watches data will be captured by checking the "Enable trace" boxes in the SWO Data window and then click the Green Arrow to set the program to start capture on Resume.Upon resuming the application, the right side of the window will show the access which are occurring. Note that this happens in real-time; the microcontroller is not stopped when accesses occur (i.e. the is separate from data breakpoints). Variable Read/Writes Displayed In Real Time The Multilink automatically measures the data communication rate on the SWO pin and adjusts to it automatically. This auto-detect sequence is done each time the processor is stopped in debug mode. If the running code changes the core frequency, a breakpoint should be set after the frequency change so the Multilink can adjust to the new SWO communications rate (which is a function of the core frequency). Real-Time Expressions This view is similar to the standard Eclipse "Expressions" window with the exception that its contents will update in real-time without the device being halted in debug mode. Just add the appropriate variables to the Real Time Expressions window and you will see them updating in real-time. Add Variables To Real-Time Expressions Windows

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio 3.2  Update 191219          What is new? S32 SDK for S32V234 RTM 1.0.1 package (Windows only) Installation instructions The update is available for online (via Eclipse Updater) or offline installation (direct download link)  online installation:  go to menu "Help" -> "S32DS Extensions and Updates" dialog  select from available items and click "Install/Update" button   offline installation:   go to S32 Design Studio product page -> Downloads section or use direct link to download the update archive zip file Start S32 Design Studio and go to "Help" -> "S32DS Extensions and Updates" Add a new "Add.." S32DS Software Site and browse to select the downloaded update archive .zip file you downloaded in the previous step         Select from available items and click "Install/Update" button. This will start the update installation process.

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio 3.2  Update 191226          What is new? Vision Extension Package for S32V234 1.1.0 with VSDK 1.5.0 integrated.(VSDK Release Notes) This is a cumulative update (includes previous updates: Update 191219) Installation instructions The update is available for online (via Eclipse Updater) or offline installation (direct download link)  online installation:  go to menu "Help" -> "S32DS Extensions and Updates" dialog  select from available items and click "Install/Update" button   offline installation:   go to S32 Design Studio product page -> Downloads section or use direct link to download the update archive zip file Start S32 Design Studio and go to "Help" -> "S32DS Extensions and Updates" Add a new "Add.." S32DS Software Site and browse to select the downloaded update archive .zip file you downloaded in the previous step         Select from available items and click "Install/Update" button. This will start the update installation process.

This short video is a presentation of DDR tool. It contains a minimum requirement and troubleshooting for starting with DDR and S32G and an initialization training for S32G2-EVB

DCD(short for Device Configuration Data) is the configuration information that BootROM uses to configure the peripherals on the device. This video will explain using S32V how DCD works and create a simple example to have RUN1 as default run mode.

This short video will present an overview of S32 Configuration Tool. Tools that are briefly overviewed: Pins tool, clock tool, peripheral tool, DCD tool and IVT tool.

Problem details: 1) S32 Design Studio exits unexpectedly after workspace is selected AND Workspace folder .metatdata file '.log' contains Java errors. 2) Installer immediately rolls back following activation code entry AND Installer log contains: ==== License activation log start: ==== # # A fatal error has been detected by the Java Runtime Environment: # #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x5afc8c19, pid=10540, tid=0x000031a4 # # JRE version: Java(TM) SE Runtime Environment (8.0_202-b08) (build 1.8.0_202-b08) # Java VM: Java HotSpot(TM) Client VM (25.202-b08 mixed mode windows-x86 ) # Problematic frame: # C  [cll_app.dll+0x18c19]   Resolution: Trusted Storage is corrupted and needs to be re-initialized. Windows host: -> Delete 'C:\ProgramData\FLEXNet' This folder may be hidden by default, so then it would be necessary to change Windows Explorer settings to show hidden items. Linux host: /usr/local/share/macrovision/storage

On some versions of Windows 10, there is an issue which could impact your ability to open documents from the Getting Started page in S32 Design Studio. While we have resolved this issue in some of the newer releases, not all editions of S32 Design Studio have been updated since this issue was discovered. Also, you may required to use an older release. The problem occurs when a document linked within the Getting Started window of S32 Design Studio. The S32 Design Studio is configured to use the Windows default web browser to open the files. For some Windows 10 installations, Microsoft Edge is the default browser and it is unable to correctly open the requested file. The typical error message is as shown below: To resolve the issue, it is necessary to change the default browser within your Windows preferences. Here are some steps to do that: 1) Click on 'Settings' from the Windows Start Menu 2) Type 'browser' in the search bar, then select 'Choose a default web browser' 3) Click on the currently selected Web browser to bring up the selection menu and select 'Internet Explorer' or 'Google Chrome' 4) Relaunch S32 Design Studio and try again to open the document from the link in Getting Started page.

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture v2.1 Update 7          What is new? Integrated S32 SDK for Power Architecture RTM 3.0.2 (see the S32 SDK release notes) This is a cumulative update - it includes all the content of previous updates (Update 1,Update 2 ) Installation instructions The update is available for online installation (via S32DS Extensions and Updates) or offline installation (direct download link)  installation:  go to menu "Help" -> "S32DS Extensions and Updates" dialog  select from available items and click "Install/Update" 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 S32 Design Studio and go to "Help" -> "S32DS Extensions and Updates", then click 'Go to Preferences' link And add a new site "Add..." repository and browse to select the downloaded update archive zip file you downloaded in the previous step Select the 'S32 Design Studio for Power Architecture Device Package' and 'Update with S32 SDK 3.0.2 for Power Architecture' packages and click "Install/Update" button.   This will start the update installation process.

UART0 communication is supported in the latest version of MPC5746R Bootloader .rbf file (attached below) + Supported UART0/LINFlexD_0: PD13-PD14 pins(Speed: 115200b/s)   Tested on the dev boards:   Development Board MPC5746R-252DC MPC57xx-MOTHERBOARD Processor PPC5746RTMMT5 - 1N83M  

Example contains modified startup code to be able run in BookE only mode. For GNU gcc and as you need to add -mno-vle parameter in project properties:  For debugging with PE Micro you need to use modified Initialization script in Advanced options: Please note that there is no STD C BookE only library available:

Quick Fix is a feature of the Java editor in Eclipse which enables a user to resolve problems found in the Java code of their project. This feature is available to be used within S32 Design Studio for some problems. Such problems will be identified with the 'light bulb' icon in the description field, as shown below: For example, such problems sometimes occur when importing a project created in a previous version of S32 Design Studio, are provided from another user, or some files in a project have become corrupted. To resolve issues identified with the 'light bulb' icon, right-click on the problem and from the pop-up menu, select 'Quick Fix'.  The Quick Fix menu will appear, providing the available solutions for the problem. In most cases, there will be just one solution. Click finish to implement the fix. In some cases, more information will be required from the user to complete the fix. Complete the form to provide the additional information, then click OK. Now the problem should be resolved.

Migration guide You can use a project that was created in an earlier version of S32 Design Studio for Power Architecture 2.1, but it requires changes according to the new product directory structure. The following explains how to import and configure your project. Click File > Import... > General > Existing Projects into Workspace, then click Next. Click Browse... and browse to the project location, click OK, select the Copy projects into workspace option, then click Finish. If the Problems view displays the following warning: "The hardware settings required for project not found", right-click it and select Quick Fix on the context menu. Select the project from the Resource list and click Finish. Specify the Family, Device and Core settings. Click OK. For the EWL source code debugging, open the debug configuration settings, switch to the Source tab, select Path Mapping: EWL and click Edit. Update the e200_ewl2 location: Compilation Path: e200_ewl2 Local file system path: <s32ds_for_power_dir>\S32DS\build_tools\e200_ewl2 Depending on the project type, update the following environment variables and file locations. For projects with the SPT tools: open the project settings, click C/C++ Build > Settings > SPT Assembler. Update the SPT include files location: "${SPT_TOOLCHAIN_DIR}/inc" for the SPT1 tools, "${SPT2_TOOLCHAIN_DIR}/inc" for the SPT2 tools, and "${SPT2.5_TOOLCHAIN_DIR}/inc" for SPT2.5 accordingly. For projects with the attached PEx SDK: after you import the project, the path validation notification appears. Click Yes to open the S32 SDK Specific properties page and update SDK path (click Browse and navigate to the <s32ds_for_power_dir>/S32DS/software/<sdk_name> folder). If you import the project example, additionally open the project settings, click C/C++ Build > Build Variables and update the S32_SDK_PATH value: ${eclipse_home}/../S32DS/software/<sdk_name>. For projects with the attached FreeMaster or AMMCLIB SDKs: open the project settings, click C/C++ Build > Settings and update the SDK paths on the following pages: Standard S32DS C/C++ Compiler > Includes Standard S32DS C/C++ Linker > Libraries Standard S32DS Assembler > General For the FreeMaster SDK project, additionally navigate to the project folder, open the .project file, and update the linkedResources locations. If some errors and warnings still occur, try to close and reopen your project, or restart S32DS for Power Architecture.

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for ARM® 2018.R1  Update 11          What is new? S32K1xx SDK RTM-SR 3.0.2: SBC driver now supports UJA1169 as well as both UJA1168 and UJA1168A SBC variants (S32 SDK release notes) AMMCLIB v.1.1.18 for S32K1xx, KEA and S32V234 (AMMCLIB release notes) 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, Update 8, Update 9, Update 10  ) Installation instructions The update is available for online (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.

        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for S32 Platform v3.2         Austin, Texas, USA Sep 30, 2019    The Automotive Microcontrollers and Processors' Embedded Tools Team at NXP Semiconductors is pleased to announce the release of the S32 Design Studio for S32 Platform v3.2.  Here are some of its major new features: Multiple builds of the GNU tools can be installed. The SDK integration is provided with additional software packages. The SDK packages can be installed and updated with the S32DS Extensions and Updates tool. The GHS toolchain support is provided by the project wizard (available for particular devices). The CMSIS-DAP debugging is supported by particular devices. The UART communication speed of S32 Flash Tool is improved. The latest versions of P&E debugger plug-in and drivers are provided. S32 Debugger provides OS Awareness support for FreeRTOS and OSEK. S32 Debugger provides preliminary support for secure debugging with the Password and Challenge/Response authentication methods. New type of Launch Groups is defined for S32 Debugger, which allows you to create S32 Debugger specific configurations and use the new "Wait for stop on breakpoint" post launch action. The SDK migration support is provided to upgrade an SDK version attached to the project. The S32DS Extensions and Updates tool notifies about dependencies and incompatible packages. The progress bar is displayed for the S32 Debugger flash programmer. 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 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.2 release notes are available here.   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 application 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