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:

For additional information about problems presumably relating to your device or third-party equipment or software, refer to the documentation provided by the product’s manufacturer.

Table 1. 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 2. Installation
Symptom Possible solution
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 Go to Preferences.
  3. Ensure the list of available software sites includes the following location:

    http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_3.1
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 3. 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 4. 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 Project > Open Update Project Dialog, select the files expected in the project's board folder, and click OK. Find the details in Editing a device configuration.
Table 5. 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.
Table 6. 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.