Known Issues#

Simplicity Studio® Version





When the GDB debugger is suspended the first time, an Interrupt Failed popup might be seen.

There is no work around, just click OK and then the debug session can be continued.


Changing the Target Part in Project Configurator does not work correctly on customer hardware.

Either create a new software example for the desired target part and port in code changes or manually change the component ID in the .slcp and .slps files with a text editor and then open the Project configurator and do a Force Generation.


Project Configurator does not allow some components with 0 dependents to be uninstalled.

This is a UI bug where dependencies exist on the component but are not being displayed. If the component must not be used, then start with a different software example that does not use the component.


Project Configurator rename functionality does not work.

Use the Simplicity IDE rename command instead. Right-click the project folder in the Project Explorer view and select Rename....


GDB Debugger session fails to start if non-English character in workspace path. Also the source code lookup will fail.

Use File > Switch Workspace… to switch to a workspace with only English characters in the path – so possibly outside of the Users directories.


GDB Debug Session Launch fails with "Error in final launch sequence" popup.

Typically, the debug session will launch successfully the next time or after a Simplicity Studio restart. If the issue persists, edit the debug configuration Run > Debug configurations… and uncheck the 'Continue' box on the Startup tab. The debug session will stop before main(), but clicking Resume will run to main().