S32 Design Studio

S32 Design Studio Release Notes

Rev. 1.2 — 31 July 2025 Release notes

1 Getting Started
NXP Semiconductors is pleased to announce the release of the S32 Design Studio for S32 Platform 3.6.3
for NXP Arm based devices and hardware accelerators. S32 Design Studio for S32 Platform is based on the
Eclipse open development platform and integrates the Eclipse IDE, GNU Compiler Collection (GCC), GNU
Debugger (GDB), and other software to offer designers a straightforward development tool with no code-size
limitations.
This package contains:
• GNU Bare-Metal Targeted Tools for Arm® 32-bit Embedded Processors:
– GCC version 11.4 20230528, build 1763 revision gf703eb2
– GCC version 10.2 20200723, build 1728 revision g5963bc8
– GCC version 9.2.0 20190812, build 1649 revision gaf57174
• GNU BareMetal Targeted Tools for Arm® 64-bit Embedded Processors:
– GCC version 11.4 20230528, build 1763 revision gf703eb2
– GCC version 10.2 20200723, build 1728 revision g5963bc8
– GCC version 9.2.0 20190812, build 1649 revision gaf57174
• GNU Linux Targeted Tools for Arm® 64-bit Embedded Processors:
– GCC version 11.4 20230528, build 1763 revision gf703eb2
– GCC version 10.2 20200723, build 1728 revision g5963bc8
– GCC version 9.2.0 20190812, build 1649 revision gaf57174
1
• Libraries: NewLib, NewLib Nano
• Semihosting for Arm® 32-bit and 64-bit bare-metal target toolchains.
• MSYS2 2022.06-1.
• Eclipse 2023-12 framework, CDT 11.4, and Java17.
• GDB 15.1 with Python 3.10.x support.
• S32 Debugger (with S32 Debug Probe) support for Arm® cores.
• S32 Debugger provides OS Awareness support for FreeRTOS, OSEK, and Zephyr OS.
• S32 Trace for Arm® Cortex®-A53, R52, M33, M7 cores with S32 Debugger.
• S32 Flash Tool.
• PEmicro® debugger support.
• Lauterbach Trace32® support.
• IAR debugger support.
• TASKING debugger support.
• Segger debugger support.
• Green Hills compiler support.
• IAR compiler support.
• Diab compiler 7.x support.
• The S32DS Extensions and Updates Tool.

1 The availability of libraries depends on the toolchain version and the core type. Tools for Arm® 64-bit processors support NewLib libraries only. Tools for Arm® 32-bit processors do
not support EWL libraries for the Cortex®-R52 and Cortex®-M33 cores.
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

• The SDK integration is provided with more software packages. The SDK packages can be installed and
updated with the S32DS Extensions and Updates Tool.
• SDK Management.
• The migration support is provided to upgrade:
– SDK version attached to the project,
– GCC-based toolchain for project.
• S32 Configuration Tools with important additions in Pins, Clocks, peripherals, eFUSE, IVT, DCD, QuadSPI,
DDR, ICE, and GTM tools.
• The wizards for creating application, library projects and projects from project examples for the supported
2
processor families
• The Getting Started page.
• Peripheral Registers view.
• Arm System Registers view.
• Watch registers view.
• Memory Spaces view.
• S32DS MMU Viewer.
• S32DS Debug Perspective.
• S32DS C/C++ Perspective.
• Threads (Zephyr RTOS) view.
• Smart card support for secure debugging.
• Multiple Elf Loading for S32 Debugger.
• Remote Probe Connection.
• Global Variables view.
• OS Details browser view.
• Cross-Trigger support:
– UI option to configure various states(source/destination)
– Cross Trigger state control - enable, disable, clear

1.1 Installation
The S32 Design Studio for S32 Platform 3.6.3 RFP installation package contains the base tools and the
installer. Support for the NXP Arm® based processor families is provided with more software packages. The
packages can be installed on the product from the S32DS Extensions and Updates tool or downloaded from the
product webpage.
Note: The user needs administrator/root privileges to install S32 Design Studio for S32 Platform 3.6.3 RFP
Note: The plug-ins to support third-party compilers or debuggers such as Lauterbach Trace32® are not
included in the installation package and have to be installed from the corresponding sites or installation
packages.
Run the installation package. The wizard guides you through the installation process.
New functionality can be added to S32 Design Studio for S32 Platform 3.6.3 RFP with more software packages,
updates, and patches. Software packages add support for specific NXP Arm® based processor families.
Updates and patches extend the general functionality of the product and correct software defects.
New functionality can be added directly from the Internet or from a downloaded archive. If your computer is
connected to the Internet, select S32DS Extensions and Updates on the Help menu to find and install all
updates and packages available. If your computer does not have access to the Internet, you can download

2 Support for wizards and the project examples are provided in the device-specific software packages.
RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

2 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

software packages, updates, and patches from the product page and install them from the archive files using
the S32DS Extensions and Updates tool.

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

3 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

2 Release Specifics

2.1 Release Details

This release has RFP quality in terms of testing and quality documentation. RFP release contains all features
and is fully tested on Customer Engineering Samples or Qual Intend Samples. RFP release is software release
that can be used in cars production. RFP release is delivered with complete software documentation, quality
package and safety package.

2.2 Supported Features

• Integrated updated versions of the tools packages:
– S32 Debugger Core 3.6.3
– S32 Flash Tool 2.3.3
– S32Trace 3.6.3
– S32 Configuration Tool 1.8.6
• The S32DS 3.6.3 installer includes the newest Platform and Platform Tools package 3.6.3, GCC 11.4, 10.2,
9.2, public development packages for S32G, S32R41,, S32R45, S32Z/E, S32K1, S32M2 version 3.6.0 and
S32K3 3.6.3

2.3 Recommended configuration

Windows
• PC with a 2.6 GHz Intel® Pentium® compatible processor or better.
• 8 GB of RAM.
• 30 GB of disk space (when installing all product features or all updates.
• 24 GB of temporary storage (required only during the product installation).
• USB port for communications with target hardware.
• Ethernet port for communications with target hardware (optional).
Linux
• PC with a 2.6 GHz Intel® Pentium® compatible processor or better.
• 8 GB of RAM.
• 25 GB of disk space for installation files (full product or updates).
• 20 GB of temporary storage (required only during the product installation).
• USB port for communications with target hardware.
• Ethernet port for communications with target hardware (optional.
S32 Design Studio for S32 Platform 3.6.3 RFP Installation Guide specifies the installation prerequisites for Linux
platforms.

2.4 Operational minimum configuration

Windows
• PC with 1.8 GHz Intel® Pentium® compatible processor.
• 4 GB of RAM.
• 25 GB of disk space.
• 20 GB of temporary storage (required only during the product installation).
• USB port for communications with target hardware.

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

4 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

Linux
• PC with 1.8 GHz Intel® Pentium® compatible processor.
• 4 GB of RAM.
• 20 GB of disk space.
• 16 GB of temporary storage (required only during the product installation).
• USB port for communications with target hardware.

2.5 Host operating system support

• Microsoft® Windows® 10 64-bit.
S32 Design Studio for S32 Platform 3.6.3 RFP supports all editions of the operating systems listed above and is
limited only by the requirements of the Java runtime Environment.
• Microsoft® Windows® 11 64-bit.
S32 Design Studio for S32 Platform 3.6.3 RFP supports all editions of the operating systems listed above and is
limited only by the requirements of the Java Runtime Environment.
• Ubuntu LTS 24.04 64-bit
S32 Design Studio for S32 Platform 3.6.3 RFP supports all editions of the operating systems listed above and is
limited only by the requirements of the Java runtime Environment.

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

5 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

3 Changes List

3.1 New Features

• Enhanced debugging efficiency by at least 20% when using S32 Debugger.
• Added support for 'Live view' mechanism in Global Variables and Memory Spaces when 'GDB non-stop mode'
is active. There are two new widgets, 'Preferences...' option to set the desired refresh rate and 'Live Refresh'
action to start seeing the data live while target is running.
• Expressions can now be viewed from Global variables when 'GDB non-stop mode' is active.
• Enabled support in 'Additional Images' tab from S32 Debugger configuration for cases when additional source
objects (e.g. elf file) are loaded in Flash memory.
• Enabled 'Advanced Settings' section to set the CCS IP and Port for 'S32 Debugger Flash Programmer' debug
configuration type.
• Find & Paste functions were enabled in Memory Management Unit (MMU) view.
• Added an option to export the registers descriptions while data is exported in 'Watch registers view'.
• Core assign entry, in case of using SMP, was added in 'Task List (FreeRTOS)' view.
• Exported configuration from 'S32DS Extensions and Updates' can now be saved on disk.
• Restored the project export functionality to be used in IAR Workbench.
• Added support for "Enable auto build" in 'S32 Debugger' configuration.
• Improvements in mcme.fill_mem Python function.
• Enable non stop mode also for load and debug application from flash in the same debug session.

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

6 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

4 Known Issues

4.1 Known issues

4.1.1 Breakpoints/Watchpoints Issues

Problem Workaround
Conditional watchpoint and breakpoints Avoid using conditions for breakpoints and watchpoints,
instead check for condition in the code and set a normal
Conditional breakpoints and watchpoints, including those
breakpoint.
using ignore counts, may not work sometimes.
Watchpoints set on complex data types are not hit Avoid setting watchpoints at complex data types.
When debugging on a target connected with s32 debug
probe, a debug session ignores a watchpoint set on a
variable of a complex data type (such as a structure or
other). a watchpoint set on an item of a basic data type
inside a complex variable works correctly.
Duplicated error dialog Close the pop-up box, then close it again.
When adding more watchpoints than supported by the
device, the pop up box with the “not enough hardware
resources for processing” error message is displayed twice.
Step out work incorrect with dbg_derived_types source Set a breakpoint at function end and run to breakpoint.
The ghs toolchain does not generate dwarf call frame As a workaround s32ds removes the debug frames info to
information that is suitable for unwinding the call stack. For force the gdb client to recreate the frames. Sometimes this
third-party debuggers incapable of unwinding the call stack method may not work and lead to incorrect behavior for step
through an alternate means (disassembling code), this may out command.
nullify the ability to walk the call stack or view variables
saved in previous frames.

4.1.2 VDK Issues

Problem Workaround
Stepping over the try-catch block fails on a vdk The issue is specific for projects compiled with NewLib.
Recreate a project and select NewLib Nano as the library.
When debugging a project on a vdk, an attempt to step over
the try-catch block fails.
Debugging on a VDK may fail Run a debug session in Virtualizer Studio.
Some errors may occur due to unexpected termination of a
debug session or unsupported registers and watchpoint, and
so on.

4.1.3 Linux Issues

Problem Workaround
USB connection failure when debugging with S32 Debug Connect the probe to USB. Set up the debug configuration
Probe on Linux VM to use the Ethernet connection rather than USB. Specify the
virtual IP address of the probe in the connection settings of
A debug session fails on a Linux virtual machine with s32
the debug configuration. To obtain the required value, run
debug probe connected through usb. debugging with an
the following command:
sudo ifconfig -a
RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

7 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

S32 debug probe connected through Ethernet can be done The displayed output includes a section for the virtual
successfully. Ethernet interface created on Linux for communication with
the probe over the physical USB link. The inet addr value
in this section is a local IP address starting with “169.254”.
Take the HWaddr value in the section and convert the
last two bytes into decimal notation. Append the resulting
numbers to “169.254” to obtain the required virtual IP
address.

Getting started page Install Webkit1 for GTK2 using the following command:
Should be displayed blank in Linux. sudo apt-get
install libwebkitgtk-1.0-0
S32 Design Studio has multiuser install issue on Linux To install the S32 Design Studio for multiple users, perform
the following steps:
• Under the user with sudo rights:
– Install the S32 Design Studio to the /opt/NXP/S32DS.3.
xfolder,
– Change permission:sudo chmod -R 770/opt/NXP/S32
DS.3.x
– Run the S32 Design Studio from the /opt/NXP/S32DS.3.
4 folder and close.
– Change permission:sudo chmod 770 /dev/shm/cll_
mutex sudo chmod -R 770 /opt/NXP/S32DS.3.x/eclipse/
configuration
– Add the second S32DS user without sudo rights to the
first user group: sudo usermod -aG <sudo_user_name>
<S32DS_user_name>
– Switch the user to the <S32DS_user_name>,
– Run the S32 Design Studio from the /opt/NXP/S32
[Link].
Connecting via Telnet to the S32 Debug Probe There are two options to access the S32 Debug Probe
configuration console fails configuration console:
When connecting multiple S32 Debug Probes • Connect using one or more serial port device files at: /dev/
simultaneously to a Linux host using USB, Telnet will only be ttyACM0(first probe), /dev/ ttyACM1(second probe), and
able to connect to the first device. so on, with a program such as screen.
• Connect using Telnet by adding temporary IP route table
entries to the Linux host for the S32 Debug Probes:
– Identify the virtual IP address of the probes running the
following command:sudo ifconfig -a
The displayed output includes a section for the virtual
Ethernet interface created on Linux for communication
with the probe over the physical USB link. The inet addr
value in this section is a local IP address starting with
“169.254”. Take the ether value in the section and convert
the last two bytes into decimal notation. Append the
resulting numbers to “169.254” to obtain the required
virtual IP address.
Example: ether value62:9F:B4:C6:D2:E3 translates to IP
address [Link]
Identify the IP route matching each probe's local IP
address using the IP route's src field. To list the existing IP
routes, use the following command:ip route
Example of S32 Debug probe route:
[Link]/16 dev enx629fb4c6d2e3 proto kernel scope
link src [Link] metric 101

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

8 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

Add a new route by replacing the [Link]/16 subnet

in the existing route with the calculated virtual IP address
for each probe using the following command: sudo ip route
add <new_ip_route>
Example:Sudo ip route add [Link] dev
enx629fb4c6d2e3 proto kernel scope link src
[Link] metric 101
• Connect to S32 Debug probe using Telnet

4.1.4 Startup/Display Issues

Problem Workaround
Disassembly view content might be destroyed Close the Disassembly view and open it again by selecting
occasionally Window > Show View > Disassembly on the menu.
Views are not updated instantly after executing a Use the step command to see refreshed views
command in the GDB console
The register variable is not shown in Memory View Information on which register is assigned for the variable can
be found in:
If the compiler locates the variable in a register the debugger
cannot show it in the memory view. "view memory" selection • the Disassembly view;
for this variable generates the error message: "cannot view • the error message in the Expression view. If "encounter"
memory on and(counter)" was added in the Expression view, then the error message
contains the information like this:
Failed to execute MI command:
-data-evaluate-expression *(encounter) Error message
from debugger back end: Address requested for identifier
"counter" which is in register $r<reg_num>
Project with huge number of macros freezes S32DS IDE Manually tune the [Link] file by removing the following
lines:
The huge count of macros is critical for indexing sources.
Editing a file with many macros causes 100% cpu usage and -Xms256m
freezes s32ds ide. -Xmx2048m

The peripheral View is crashing, when applying the

selection on launch, in Debug View
Design Studio becomes unresponsive Filtering the content using the search bar of the
Configuration tab restores smooth tab switching.
On Ubuntu 24.04, Design Studio becomes unresponsive,
when going to the Configuration tab, and then browsing
between any other tab in the same window.

4.1.5 Installation/Uninstallation/Launch Issues

Problem Workaround
Creating project in the root of drive C:\ fails Create a subdirectory in the root directory (for example, C:
\Projects) and specify this location in the project creation
When creating a project in the root directory, the project
wizard.
wizard shows the "can't create directory: c:\project_name"
error message. windows does not allow the users to create
files in this location.
Cannot install Eclipse p2 installation units on Ubuntu Use the "Select All" option in all windows instead of "Always
20.04 distribution when "Always trust all authorities" or trust all authorities" or "Always trust all content".
"Always trust all content" is selected

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

9 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

For these cases, the "always trust everything confirmation"

window becomes hidden and the user cannot access it. this
is an Eclipse issue documented here: [Link]
eclipse-equinox/p2/issues/570.
Launching S32Debug Group on Secure parts generate Fill Password in S32Debugger Configuration.
NPE error
Uninstallation of P&E drivers If you do not need the P&E drivers for other products and
devices, uninstall them before the product uninstallation.
The p&e device drivers are not uninstalled with uninstallation
of s32 design studio. After that, an attempt to uninstall them
manually can cause errors
S32 Debugger and/or S32 Trace no longer work after Restart S32 Design Studio and install the update again,
update fails due to "access denied" error as instructed in the dialog. Once the update completes
successfully, functionality should be restored to normal.
When installing the platform package in s32ds extensions
and updates after having used the s32 debugger or s32
trace, an error message may appear to state that access is
denied to files in use. After this, the s32 debugger and s32
trace may no longer function
Hyperlinks may not work Set a different browser as the default one.
They may not work correctly when microsoft Edge (early
versions) is configured as the default browser.
Silent Mode installation:
The uninstall mechanism is using the same logic as the
installation, meaning if the installer was installed using silent
mode, the uninstall will also be silent and it will not prompt
the user for any confirmation.
An error message is displayed when upgrading the Upgrade the platform directly from S32 Design Studio 3.6.3
platform from S32 Design Studio 3.6.2 to 3.6.3 from installer.
“S32DS Extensions and Updates”.
The message is not harmful to the current session and user
can continue the normal work after pressing OK button.

4.1.6 Build Issues

Problem Workaround
GHS project with/without SDK build failed after For GHS projects with/without SDK, after renaming of the
renaming of the project project activate clean and refresh procedures before building
Header files are copied to the project, and the rename
process affects the paths. ghs build system believes that
the files are not changed and does not update them during
building - this is the ghs build system specific.
GHS project build gives the "Unresolved inclusion" Not to break the C dialect specification, we recommend
warning when including a standard C library adding a path to include files manually: Open project
properties, go to C/C++ General > Preprocessor Include
GHS toolchain specific implementation does not contain a
Paths, Macros, and so on, > CDT User Setting Entries
build-in spec detector.
and add an Include Directory with the path to GHS folder,
for example ${S32DS_GHS_PATH}\ansi, and the Contains
system headers option selected.
The headless build system gives the "Managed build To further avoid this error messages, install the GHS
system manifest file error" toolchain.

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

10 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

This error appears if the ghs toolchain is not installed. it

is the eclipsed build system specific, but it is not an error
technically and does not affect a build success.
Projects renaming out of the workspace is not Use one of the following options:
supported • Copy the project to the workspace (use file system
S32DS cannot perform its custom rename procedure for options).
a project out of the workspace used in the session. the • Import the project with copying files to the workspace.
eclipsed default renaming gets the wrong result (problems Change to another workspace with the project to rename
with launch configurations and other related files). (when using several workspaces)
Setting PYTHONHOME and PYTHONPATH path is not These two environment variables should not be set (user or
supported system level) when working with S32 Design Studio.
The scenario in which a user sets the environment variables
python home and python path is not supported, as it can
lead to unexpected results

4.1.7 Debugging Issues

Problem Workaround
S32 Debugger program counter does not support HEX- When creating a Debug Configuration, at the startup tab
value setting use one of the following options:
• Use a label or function name instead for the Set program
counter at field in runtime Options,
• Uncheck the Set program counter at and add the
following commands to the Run commands field: set
$pc=<HEX-value> -exec-until *<HEX-value>
Variables view and Expressions view do not display the Use the Details number format in these views as it is the
values correctly only format that will display the correct value in this context.
Debugging on S32 Debugger: variables view and
expressions view may not display the value of some
variables correctly if those variables have been used in
macros.
Debugging on S32 Debugger may fail Close the Variables view or make it inactive for a critical part
of code (until pointers are not initialized in code).
Variables view may pose a problem when entering some
function with uninitialized pointers as it generates random
access which may corrupt the debugger. sometimes the
invalid access may be generated when debugging optimized
code (ghs toolchain) where the pointer location shared with
some variable.
Only addresses added on the central core remain saved Terminate the debug sessions on each core individually,
dont terminate all.
When debugging, multicore launch and add some memory
monitor addresses and terminate&relaunch the debug
session, only addresses added on central core remain saved
\
Relaunching session may result in an error
Cannot run in parallel two debug sessions.

4.1.8 Importing Issues

Problem Workaround

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

11 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

Import C/C++ Executable as S32DS project with To debug the imported ELF project, manually fill in the
Lauterbach required absolute paths for the following fields in the launch
configuration: Configuration File, Initial Working Directory,
when importing a C/c++ executable with lauterbach, the
and PRACTICE Script
configuration file and practice script fields in the launch
configuration are empty
Import C/C++ Executable as S32DS project with Tasking To debug the imported ELF project, manually fill in the
required absolute path for the workspace field in the launch
when importing a c/c++ executable with tasking, the
configuration
workspace field in the launch configuration is empty
Folders are not excluded if the SDK is migrated on a Reload the SDK and exclude the old SDK folder from the
S32DS 3.4.1 imported project build path after the migration to a newer version of the SDK.
This would correctly exclude the backup folders.

4.1.9 DIAB Issues

Problem Workaround
“Move to” line in DIAB might not work accordingly Don't change PC in projects compiled with DIAB.
Debugging of Cortex A53 projects with Diab Compiler Perform some stepping within the debug session.
Debug session stops with "no source available for "main()
at". It is due to diab version 7.0.3 have some limitations on
debugging. Debug info for c files isn’t loaded in time. After
stopping at the main function, several assembler commands
must be executed before debug info will be loaded

4.1.10 Trace Issues

Problem Workaround
S32 Trace shows that no trace has been collected for
application built with GCC 11.4:
S32 Trace does not support applications with DWARF-5
debug format, and will fail to open the application file when
decoding. Starting with GCC 11.4 the default format is
DWARF-5, and even if we change this for our project back to
DWARF-4, the other precompiled code in the application will
still be in DWARF-5 and block the decoding.
For M7 cores, during the trace collection some other
packages might be generated outside the actual
execution of the core.

4.2 Problem Reporting Instructions

The S32 Design Studio for S32 Platform general issues is tracked through the S32DS Public NXP Community
space: [Link]
For confidential cases and cases which cannot be publicly shared on the NXP Community follow the steps
described here: [Link]
For cases with PEmicro submit a support request: [Link]

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

12 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

5 Legal Information

5.1 Legal Information

Definition - Information in this document is provided solely to enable system and software implementers to use
NXP products. There are no express or implied copyright licenses granted hereunder to design or fabricate any
integrate circuits based on the information in this document.
Warranty - NXP makes no warranty, representation, or guarantee regarding the suitability of its products for
any particular purpose, nor does NXP assume any liability arising out of the application or use of any product
or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental
damages. “Typical” parameters that may be provided in NXP data sheets and/or specifications can and do
vary in different applications, and actual performance may vary over time. All operating parameters, including
“typicals”, must be validated for each customer application by customer's technical experts. NXP does not
convey any license under its patent rights nor the rights of others. NXP sells products pursuant to standard
terms and conditions of sale, which can be found at the following address: [Link]/SalesTermsandConditions.
Right to make changes: Full phrase - NXP Semiconductors reserves the right to make changes to information
published in this document, including without limitation specifications and product descriptions, at any time and
without notice. This document supersedes and replaces all information supplied prior to the publication hereof.
Short phrase - NXP reserves the right to make changes without further notice to any products herein.
Suitability for use: Suitability for use in automotive applications – Automotive Product (Functional
Safety) - This NXP product has been qualified for use in automotive applications. It has been developed in
accordance with ISO 26262, and has been ASIL-classified accordingly. If this product is used by customer
in the development of, or for incorporation into, products or services (a) used in safety critical applications or
(b) in which failure could lead to death, personal injury, or severe physical or environmental damage (such
products and services hereinafter referred to as “Critical Applications”), then customer makes the ultimate
design decisions regarding its products and is solely responsible for compliance with all legal, regulatory, safety,
and security related requirements concerning its products, regardless of any information or support that may
be provided by NXP. As such, customer assumes all risk related to use of any products in Critical Applications
and NXP and its suppliers shall not be liable for any such use by customer. Accordingly, customer will indemnify
and hold NXP harmless from any claims, liabilities, damages and associated costs and expenses (including
attorneys’ fees) that NXP may incur related to customer’s incorporation of any product in a Critical Application.
Suitability for use in automotive applications - This NXP Semiconductors product has been qualified for
use in automotive applications. Unless otherwise agreed in writing, the product is not designed, authorized
or warranted to be suitable for use in life support, life-critical or safetycritical systems or equipment, nor in
applications where failure or malfunction of an NXP Semiconductors product can reasonably be expected to
result in personal injury, death or severe property or environmental damage. NXP Semiconductors and its
suppliers accept no liability for inclusion and/or use of NXP Semiconductors products in such equipment or
applications and therefore such inclusion and/or use is at the customer's own risk.
Applications - Applications that are described herein for any of these products are for illustrative purposes
only. NXP Semiconductors makes no representation or warranty that such applications will be suitable for the
specified use without further testing or modification. Customers are responsible for the design and operation
of their applications and products using NXP Semiconductors products, and NXP Semiconductors accepts
no liability for any assistance with applications or customer product design. It is customer’s sole responsibility
to determine whether the NXP Semiconductors product is suitable and fit for the customer’s applications
and products planned, as well as for the planned application and use of customer’s third party customer(s).
Customers should provide appropriate design and operating safeguards to minimize the risks associated
with their applications and products. NXP Semiconductors does not accept any liability related to any default,
damage, costs or problem which is based on any weakness or default in the customer’s applications or
products, or the application or use by customer’s third party customer(s). Customer is responsible for doing all
necessary testing for the customer’s applications and products using NXP Semiconductors products in order

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

13 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

to avoid a default of the applications and the products or of the application or use by customer’s third party
customer(s). NXP does not accept any liability in this respect.
No offer to sell or license - Nothing in this document may be interpreted or construed as an offer to sell
products that is open for acceptance or the grant, conveyance or implication of any license under any
copyrights, patents or other industrial or intellectual property rights.
Export control - mandatory but not applicable (to software product)
Translations - mandatory but not applicable
Security - While NXP Semiconductors has implemented advanced security features, all products may
be subject to unidentified vulnerabilities. Customers are responsible for the design and operation of their
applications and products to reduce the effect of these vulnerabilities on customer’s applications and products,
and NXP Semiconductors accepts no liability for any vulnerability that is discovered. Customers should
implement appropriate design and operating safeguards to minimize the risks associated with their applications
and products.
Notice: All referenced brands, product names, service names, and trademarks are the property of their
respective owners.
NXP, the NXP logo, NXP SECURE CONNECTIONS FOR A SMARTER WORLD, Airfast, Altivec, CodeWarrior,
ColdFire, ColdFire+, CoolFlux, CoolFluxDSP, the CoolFlux logo, EdgeLock, EdgeScale, EdgeVerse, eIQ,
Embrace, Freescale, the Freescale logo, GreenChip, the GreenChip logo, HITAG, ICODE, I - CODE,
Immersiv3D, JCOP, Kinetis, Layerscape, MagniV, Mantis, MIFARE, the MIFARE logo, MIFARE CLASSIC,
MIFARE DESFire, MIFARE FleX, MIFARE Plus, MIFARE Ultralight, MIFARE 4Mobile, the MIFARE4Mobile
logo, MiGLO, mobileGT, NTAG, the NTAG logo, PEG, Plus X, PowerQUICC, Processor Expert, QorIQ, QorIQ
Qonverge, Qorivva, RoadLINK, the RoadLINK logo, SafeAss ure, SmartM X, StarCore, Symphony, Tower,
TriMedia, UCODE, the UCODE DNA logo, VortiQa and Vybrid are trademarks of NXP. All other product or
service names are the property of their respective owners. AMBA, Arm, Arm7, Arm7TDMI, Arm9, Arm11,
Artisan, [Link], Cordio, CoreLink, CoreSight, Cortex, DesignStart, DynamIQ, Jazelle, Keil, Mali, Mbed,
Mbed Enabled, NEON, POP, RealView, SecurCore, Socrates, Thumb, TrustZone, ULINK, ULINK2, ULINK-
ME, ULINK-PLUS, ULINKpro, μVision, Versatile are trademarks or registered trademarks of Arm Limited (or
its subsidiaries) in the US and/or elsewhere. The related technology may be protected by any or all of patents,
copyrights, designs and trade secrets. All rights reserved. Oracle and Java are registered trademarks of
Oracle and/or its affiliates. The Power Architecture and [Link] word marks and the Power and [Link]
logos and related marks are trademarks and service marks licensed by [Link]. Synopsys, Synopsys
Designware and Virtualizer are trademarks or registered trademarks of Synopsys, Inc. in the U.S. and/or other
countries. TRACE32 is a registered trademark of Lauterbach GmbH. IAR, the IAR logo and IAR Embedded
Workbench are trademarks or registered trademarks of IAR Systems AB. Green Hills and the Green Hills logo
are trademarks or registered trademarks of Green Hills Software in the US and/or internationally. PEmicro
iSystem Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft
Corporation in the United States and/or other countries. Intel, the Intel logo and Pentium are trademarks of Intel
Corporation or its subsidiaries.

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

14 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

6 Acronyms

6.1 Acronyms
The following table shows the acronyms used in this document.

Table 1. Acronyms
Acronym Description
ARM Advanced RISC Machine
EWL Embedded Warrior Library
GCC GNU Compiler Collection
GDB GNU Debugger
GB Gigabyte
I/O Input/output
IDE Integrated Development Environment
MCU Microcontroller Unit
RAM Random Access Memory
RTD Real-Time drivers
S32DS S32 Design Studio for S32 Platform
SDK Software Development Kit
VDK Visualizer Development Kit

6.2 How to reach us

How to Reach Us:

Homepage:
[Link]
Web Support:
[Link]/support

© NXP 2025 B.V. All rights reserved.

For more information, please visit: [Link]

For sales office addresses, send an email to: salesaddresses@[Link]

Revision: 1.2, 07/2025

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

15 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

7 Revision history

7.1 Revision Table

Table 2. Revision history
Revision Number Changes Date
1.0 New Documentation Template 31.03.2025
1.1 New features and bugfixes 28.05.2025
1.2 New features and bugfixes 14.07.2025

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

16 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

Tables
Tab. 1. Acronyms .........................................................15 Tab. 2. Revision history ...............................................16

RN00294 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved.

Release notes Rev. 1.2 — 31 July 2025 Document feedback

17 / 18
NXP Semiconductors
S32 Design Studio
S32 Design Studio Release Notes

Contents
1 Getting Started .................................................1
1.1 Installation ..........................................................2
2 Release Specifics ............................................ 4
2.1 Release Details ................................................. 4
2.2 Supported Features ........................................... 4
2.3 Recommended configuration ............................. 4
2.4 Operational minimum configuration ................... 4
2.5 Host operating system support ..........................5
3 Changes List .................................................... 6
3.1 New Features .................................................... 6
4 Known Issues .................................................. 7
4.1 Known issues .................................................... 7
4.1.1 Breakpoints/Watchpoints Issues ........................ 7
4.1.2 VDK Issues ........................................................7
4.1.3 Linux Issues .......................................................7
4.1.4 Startup/Display Issues ....................................... 9
4.1.5 Installation/Uninstallation/Launch Issues ........... 9
4.1.6 Build Issues ..................................................... 10
4.1.7 Debugging Issues ............................................ 11
4.1.8 Importing Issues .............................................. 11
4.1.9 DIAB Issues .....................................................12
4.1.10 Trace Issues .................................................... 12
4.2 Problem Reporting Instructions ....................... 12
5 Legal Information ...........................................13
5.1 Legal Information ............................................. 13
6 Acronyms ....................................................... 15
6.1 Acronyms ......................................................... 15
6.2 How to reach us .............................................. 15
7 Revision history .............................................16
7.1 Revision Table ................................................. 16

© 2025 NXP B.V. All rights reserved.

For more information, please visit: [Link] Document feedback
Date of release: 31 July 2025
Document identifier: RN00294