Troubleshooting

This section contains a series of tables that describe possible solutions to problems that may occur when using S32 Design Studio . Each table contains:
The troubleshooting tables appear in the following order:

If your problem is not described below, check the list of known issues and workarounds in Release Notes, then refer to the S32 Design Studio community or submit a technical support request.

For additional information about problems presumably relating to your device or included tools, refer to the following documentation:
Table 1. Related Documentation
Documentation for: Location
S32 Debugger Release Notes: /S32DS/tools/S32Debugger/Debugger/
S32 Configuration Tools Release Notes: /Release_Notes/

S32 Configuration Tools Getting Started: Help > Help Contents
S32 Flash Tool Release Notes and User Guide: /S32DS/tools/S32FlashTool/doc/
S32 Trace Tool S32DS Software Analysis Documentation: Help > Help Contents, the pdf version is available in /S32DS/help/pdf/
S32 Debug Probe User Guide: /S32DS/tools/S32Debugger/Debugger/Docs/
GNU Bare-Metal Targeted Tools for Arm 32-bit Embedded Processors Release Notes:
  • GCC 6.3 - /S32DS/build_tools/gcc_b1620/gcc-6.3-arm32-eabi/
  • GCC 9.2 - /S32DS/build_tools/gcc_v9.2/gcc-9.2-arm32-eabi/
  • GCC 10.2 - /S32DS/build_tools/gcc_v10.2/gcc-10.2-arm32-eabi/
  • GDB - /S32DS/tools/gdb_arm/arm32-eabi/
GNU Bare-Metal Targeted Tools for Arm 64-bit Embedded Processors Release Notes:
  • GCC 6.3 - /S32DS/build_tools/gcc_b1620/gcc-6.3-arm64-eabi/
  • GCC 9.2 - /S32DS/build_tools/gcc_v9.2/gcc-9.2-arm64-eabi/
  • GCC 10.2 - /S32DS/build_tools/gcc_v10.2/gcc-10.2-arm64-eabi/
  • GDB - /S32DS/tools/gdb_arm/arm64-eabi/
GNU Linux Targeted Tools for Arm 64-bit Embedded Processors Release Notes:
  • GCC 6.3 - /S32DS/build_tools/gcc_b1620/gcc-6.3-arm64-linux/
  • GCC 9.2 - /S32DS/build_tools/gcc_v9.2/gcc-9.2-arm64-linux/
  • GCC 10.2 - /S32DS/build_tools/gcc_v10.2/gcc-10.2-arm64-linux/
  • GDB - /S32DS/tools/gdb_arm/arm64-linux/
SDK Refer to the corresponding folder in /S32DS/software/
P&E GDB Server Plug-In User Guide: /S32DS/help/pdf/
Hardware Some software packages provide data sheets and reference manuals, refer to the corresponding folder in /S32DS/help/resources/manuals/ and /S32DS/help/resources/hardware/
Table 2. Licensing
Symptom Possible solution
The product license cannot be activated Ensure the Flexera server can be accessed from your workstation. Consult the network administrator of your company.
Table 3. Installation
Symptom Possible solution
The "Insert New Media" message appears when installing S32DS Design Studio for S32 Platform 3.5 Update 6 Make sure there is enough disk space for the product and temporary files. Free up disk space or click the Browse button to select a new location.
New packages and updates are not displayed in the S32DS Extensions and Updates tool Toggle the New button in the S32DS Extensions and Updates window. This toggles off other filters that may block the new packages from being displayed.
Check the Internet connection on your workstation. Reconnect if required.
Ensure the path of the network repository is specified in the user preferences correctly:
  1. Click Help > S32DS Extensions and Updates from the menu.
  2. Click Manage Sites.
  3. Ensure the list of available software sites includes the following location:

    http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_3.4
Ensure the network repository can be accessed from your workstation. Consult the network administrator of your company.
Download the new packages and updates manually. Find the details in Downloading updates manually.
Table 4. Internet Access
Symptom Possible solution
Wireless Internet permanently fails when debugging with S32 Debug Probe (USB) on a PC connected to Wi-Fi Ask the network administrator to allow simultaneous domain and non-domain connections for the user account.
Use a wired Ethernet connection to the domain network.
Connect to an external wireless network, then connect to the domain through a VPN client.
Table 5. Project Files
Symptom Possible solution
The source (header) files do not appear in the project's board folder after saving the device configuration to the project Open the Pins, Clocks, or Peripherals perspective. Click Update Code > Open Update Code Dialog, select the files expected in the project's board folder, and click OK. Find the details in Editing a device configuration.
Table 6. Building
Symptom Possible solution
The toolchain settings display the "Orphaned configuration" warning The "Orphaned configuration. No base extension cfg exists..." message can be caused by missing toolchain. Make sure you installed the package that includes the tools necessary to build this type of project.
Build fails after updating the product version The "Cannot run program: Launching failed. Error: Program not found in PATH" error can be caused by unresolved environment variables for the new product in old workspace. Create a new workspace and import the existing project.
Build fails with multiple unresolved symbols The build failure can be caused by the incorrect C/C++ indexer settings. Indexing can be restricted by file size or by cache size, in which case the indexer may not update the database after some action was performed with a project file, for instance, because the file was too large. Find the details in Adjusting the C/C++ indexer settings for large files.
Build errors are reported without a particular location The build failure can be caused by invalid characters in the resolved paths. Make sure that all your paths use the allowed characters only. Or, refer to Building projects in non-English versions of Windows.
Build fails with memory oveflowed The build failure is caused by lack of RAM (or other memory). Check the available RAM (or other memory) size and make sure you considered it while developing your application.
Assembly files are not build correctly Eclipse CDT is case sensitive and *.s file extensions are not supported. Use the *.S file extensions.
Table 7. Debugging
Symptom Possible solution
Debugging with Lauterbach TRACE32 fails in Linux If the path to the debugged executable is too long, this may cause the TRACE32 debugger failure. Consider using a shorter path. As part of the solution, assign a shorter name to the project, recompile it, and start debugging anew.
Lauterbach TRACE32 running in Linux cannot find t32marm64, t32marm, t32mipu, t32mapex Open the PROFILE file located in your home directory and add the following entry:

export PATH="$PATH:/opt/t32/bin/pc_linux64"

where /opt/t32 is your Lauterbach installation directory.
Modify the CM4.cmm file to use the absolute paths to the reported executables (t32marm64, t32marm, and so on), for instance:

os /opt/t32/bin/pc_linux64/t32marm64 -c ./Project_Settings/Debugger/CA53.t32

os /opt/t32/bin/pc_linux64/t32mapex -c ./Project_Settings/Debugger/APU0.t32
Running a launch group results in unexpected termination of the secondary debug sessions Open the launch group and increase the post-launch delay for the initial debug session. Find the details in Debugging on multiple cores.
Debugging of multicore project fails Previously created functional breakpoints (e.g. "main") are kept in the Breakpoints view. So the execution of <init> launch configuration tries to stop on it. All temporary functional breakpoints should be removed from the Breakpoints view (or disabled) before starting of a debug session.
Connecting to vpsession failed The "com.synopsys.sls.core.CmdException: No session, operation cannot be completed" error can be caused by invalid environment variable value. If you have several Synopsys® Virtualizer Runtime versions, make sure the SNPS_VP_HOME value is set for the currently used version.