This issue was reported on a few different forum posts. Simplicity Studio will crash at somewhat random times. It has been reported as happening when the debugger is launched or when editing a file and deleting several lines from it, but the behavior is not consistent.
The issue has been tracked down to the underlying SWT plug-ins in the Eclipse version on which Simplicity Studio is based. Silicon Labs is working towards updating the underlying Eclipse version, but that will not be ready for some time. In the meantime, the workaround is to replace the two swt jar files with ones that have been patched with updated SWT code. A zip file that contains the two jar files is attached to this KBA. To verify the integrity of the zip file after it is downloaded, verify the md5 of the zip file is 0665ec3711abfbf2c6355cb70fbaf73c. On a Mac from a terminal window this can be checked with the command: 'md5 swt_jar_replacements.zip'
The procedure to replace the jar files is:
1. Exit Simplicity Studio
2. In the directory [SIMPLICITY_STUDIO_INSTALLATION]/Contents/Eclipse/plugins, find the two files
3. Rename the files changing .jar to .jar-xxx, so the original files are available as a backup.
4. Extract the two jar files of the same name from the 'swt_jar_replacements.zip file to the same directory.
5. Start Simplicity Studio
Let us know if you have any troubles with the procedure or still see any Simplicity Studio crashes. Silicon Labs wishes to thank the several customers who have helped to verify the replacement jar files fix the issue.
Simplicity Studio currently does not support IAR ARM toolchains above version 7.80.x, so if the desire is to use the IAR ARM toolchain with Simplicity Studio, then IAR ARM version 7.80 will need to be installed. It can be installed parallel to a version 8.x installation, so that version 8.x can be used for non-Simplicity Studio work. It can be hard to find the older installer on the IAR website, so this is a direct link to the version 7.80.2 installer:
NOTE: A license for the IAR ARM toolchain must be purchased separately from IAR.
After installing the IAR ARM toolchain, if 32-bit product support (MCU or Wireless) has been installed, the toolchain should be automatically detected the next time Simplicity Studio is started. If it isn't detected then it can be added manually by clicking the [Settings] icon from the Launcher perspective and then selecting [Simplicity Studio] > [Toolchains] and clicking the [Add...] button and browsing to the root IAR Embedded Workbench folder (default for Windows: "C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\").
Silicon Labs is planning to add support for IAR versions 8.x to Simplicity Studio and the 32-bit SDKs later this year (2018).
Please note that when first installing Simplicity Studio on a 4K monitor, the entire installation option dialog box may not appear correctly. During a first time installation, after the Log In dialog box, a dialog box with two options ("Install by Device" or "Install by Product Group") will be displayed:
But on 4K monitors the second box for "Install by Product Group" might be clipped like this:
Clicking on the small visible portion of the "Install by Product Group" box will still allow the installation to be completed using that installation method.
Install by Device - This option is best when wanting to only install the minimum number of files for a small group of products is desired and the exact products are known in advance.
Install by Product Group - This is the recommended installation option, it will install broad product support for the entire product group from this selection of products:
Note after the first time installation, when choosing the Update Software icon, a third installation category "Package Manager" will be displayed:
As the text under Package Manager says, the Package Manager allow Product Updates to be installed as well as new SDKs or Tools to be installed or uninstalled.
Silicon Labs hopes this information will help in deciding which installation method to use and in cases were the clipped installation option box is seen.
If a project imported from mbed compiler into Simplicity Studio has a build error - 'undefined reference to __wrap_exit', the following steps need to be followed to fix the error -
1. Right click on the project in Studio
2. Navigate to Properties
3. Under C/C++ Build, go to Settings
4. Under GNU ARM C++ Linker, select Miscellaneous
5. In Linker flags, remove -Wl, --wrap, exit (It is easier to copy the entire list onto Notepad++ and then remove the text)
6. Make sure you leave the other flags as is (there is another flag called -Wl, --wrap, atexit - you don't have to delete this)
7. Build the project
This error is because of a workflow bug in the mbed compiler's online tooling and they are working on fixing this - https://os.mbed.com/questions/77938/mbed_blinky-fails-to-build-on-gcc-undefi/
When Gecko SDK Suite patches are released, they can be installed from the SDKs tab of the Simplicity Studio Package Manager (the “Update Software” icon). If you have access to these SDKs, then “Update” links for them will be seen (if the previous version was not installed then the link will be an “Install” link). If the “Update” link is clicked, a warning message will be displayed indicating that the existing SDK will be overwritten with the new patch version. If this is not desired, then do not install the SDK patch.
At the moment, Simplicity Studio SDK registration mechanism has an issue in the update case where the updated Gecko SDK Suite *is not* displayed in the Studio Settings (preferences) under [Simplicity Studio] > [SDKs]. We are working on fixing this issue, but in the mean time you can do the following after you have updated a Gecko SDK Suite installation:
With the most Simplicity Studio release (January 26th, 2018) there have been several cases of Simplicity Studio hanging when it starts up with the progress indicator saying Simplicity Studio is refreshing the workspace. Silicon Labs has identified and fixed the issue which will be in the next Simplicity Studio release scheduled sometime around February 23rd.
If this lockup occurs, the following work around can be used until the release is available. After exiting Simplicity Studio and using Task Manager if necessary to kill the Progress Information window, use a new workspace by renaming (not deleting as the workspace contains all of your projects) the existing workspace. The default workspace for Windows is at C:\Users\[USERNAME]\SimplicityStudio\v4_workspace. Existing projects can then be imported from the renamed workspace using [File] > [Import...] > [General] > [Existing Projects into Workspace] and then clicking the "Select root directory" radio button and browsing to the location of the renamed workspace. The detected projects will be listed in the Projects window and you can select which projects to import. You should click the option "Copy projects into workspace" and then click Finish.
The lockup can happen (but doesn't always happen) if more than one project is open when Simplicity Studio starts up. So to prevent the issue from occurring again, close all but the current project before exiting Simplicity Studio. The easiest way to close the other projects is to right click on the existing project folder in the Project Explorer and select "Close Unrelated Projects".
Silicon Labs apologizes for the inconvenience this issue causes our customers. This KBA will be updated when the fixed release is published.
This is just a warning that we are seeing an issue with the latest release when customers try to debug a project. Silicon Labs is able to reproduce the issue and we are working on getting a fix published as soon as possible. Until that fix is released it is recommended not to update Simplicity Studio at this time.
Silicon Labs will update this Knowledge base article as soon as the release has been published.
We apologize for this issue.
There is a known issue with the BLE 22.214.171.124 and 126.96.36.199 SDKs if a project is created and only a part is specified not a Silicon Labs development board, then when the AppBuilder is run by pressing the "Generate" button the generation action will fail and a "Configuration Error" dialog box will be shown:
The work around is to choose the radio board that has the part with same 'feature set' on it as the starting point for creating the project and then edit the project to remove the board dependencies. The 'feature set' portion of the target part number is the 3 digits after performance grade. For example for the EFR32BG1B232F256GM56, the BG1B232 indicates the Blue Gecko Series 1 family, the B is the 'basic' performance grade and the feature set is the '232'. This url can be used to help select which radio board to specify in Simplicity Studio: https://www.silabs.com/products/development-tools/wireless/wireless-radio-boards#bluetooth The 'BRD' can be used in place of the 'SLWRB' in the part number.
The following tweaks can be used to speed up your programming speed while using the Simplicity Commander -