Simplicity Studio v4 installation fails after starting for the first time. A "Problem Occurred" dialog box appears.
How do I troubleshoot network related installation issues when adding components to Simplicity Studio v4?
Simplicity Studio v4 Installation Errors
The following scenarios are examples of network related installation issues when installing components in Simplicity Studio v4.
Problem Occurred Dialog
A dialog box pops up with the following text:
Problem Occurred 'Downloading asset://common/salesforce.properties' has encountered a problem. Download error There are no assets defined. Please check your settings.
Connection Error Dialog
A dialog box pops up with the following text:
Connection Error Dialog Connection Error Please check your internet connection. Unable to connect to the public update site. If you are behind a firewall, you may need to configure network proxy settings from the Network Connection Preferences To view installed components when offline go to the About Simplicity Studio dialog.
New Solution Dialog is Empty
A New Solution dialog appears with no content.
Network Connectivity Troubleshooting
All of the error messages described above generally indicate that Studio has failed to install the required components. After running Studio for the first time, users must select which components to install before creating a solutions or project or viewing documents and release materials. Studio requires an active internet connection with properly configured network or proxy settings to install these components. The majority of users with a typical open network configuration should not need to take any action to configure their network settings in Studio. Only users on a network with a firewall that blocks access to the Studio servers or users that are required to use a proxy server to access external servers may be required to manually enter their network proxy settings into the Studio Network Connection Preferences dialog.
Studio Update Server Access
In order to install or update Studio components, your computer must be able to access the following domains:
https://developer.silabs.com (port 443)
https://siliconlabs.force.com (port 443)
If you are not sure if your network allows access to these servers or if you require the use of a proxy server to access external sites, please contact your IT administrator.
Testing Server Access
You can test access to Studio update servers manually using a web browser. Firefox is recommended as it does not generally use the local system certificate store for SSL certificates.
Ensure that you have access to the following servers when using your web browser:
If you can successfully connect to https://developer.silabs.com via web browser, you should see an html page with the words "devtools".
If you can successfully connect to https://siliconlabs.force.com via web browser, verify that you can successfully login with your Silicon Labs user account.
Configuring a Proxy Server
For users on a network requiring the use of a proxy server to access Studio update servers, check with your IT administrator on the correct proxy server IP address and port for HTTP, HTTPS, ans SOCKS protocols.
When you first run Studio and the program can't detect an active internet connection, the Connection Error Dialog will appear.
To configure your proxy settings for Studio, click Network Connection Preferences. Note that Studio has a standalone version of a Java runtime included in the installation directory that does not use the same network proxy settings as other Java runtimes installed on a machine.
You may also reach the proxy setting dialog by clicking the Settings button on the top-left side of the toolbar (next to the Sign In button). Then navigate to Network Connections.
Users who don't require a proxy server should select the Direct setting under Active Provider to completely bypass the proxy entries below.
Uses may configure Studio to try to determine proxy settings automatically from their system settings by selecting the Native setting under Active Provider.
If Studio can't automatically determine the required proxy settings using Native, choose Manual. The Proxy entries allow the user to specify a proxy server and port to use for the three interface types: HTTP, HTTPS, SOCKS. Make sure to configure the host and port for each of these three interfaces. Also enter User and Password information if your proxy server requires authentication. The Proxy bypass items allows users to enter hostnames that are reached directly without going through the proxy server settings configured under Proxy entries. By default, localhost and 127.0.0.1 should be bypassed (don't use proxy server settings) since these resolve to the local machine (ie offline installer files, local archives, etc).
Note that the Proxy entries and Proxy bypass items will not have any effect unless they are checked via selecting the Manual setting.
See the Eclipse documentation for Network Connections on how to configure proxy settings within Studio at:
Installing Studio Components on Another Network
Another alternative to install Studio components is to temporarily connect to another network that is not blocking access to Studio update servers and does not require proxy server settings. Connect to an available network and install all components as required. Note that many resources including documentation (PDFs) are downloaded on demand, requiring an active network connection until all required resources have been accessed and downloaded. You may need to download documentation and part/debug support files by creating and debugging a project as well as viewing reference manuals and datasheets before these files are downloaded and saved for offline access.
To download assets using the Studio Package Manager (recommended):
1. Launch Studio while connected to an open network with access to Studio servers
2. Click on the Update Software button on the top-left side of the toolbar
3. Click the Assets tab from the Package Manager dialog
4. Check Filter by connected product checkbox to show only assets for the connected products such as starter kits and wireless starter kits or uncheck the checkbox to show all assets
5. Check the checkboxes next to all assets required for development of the desired products
6. Click Install to fully download and install all selected assets
The following steps should be followed to open a GIT repository within Simplicity Studio V4:
1. Install Simplicity Studio V4 here - http://www.silabs.com/products/development-tools/software/simplicity-studio
2. Type CTRL-3 and in the search box start typing "Install New Software" and select the command when it is available.
3. In the "Work with:" window enter this url (it is the version compatible with Simplicity Studio): 'http://download.eclipse.org/egit/updates-4.11/' and click the [Add...] link. In the popup give it a name like 'egit' and then click [OK].
4. Only select the 'Git integration for Eclipse' checkbox in the available updates and then continue through to install the software.
Additional updates to some Simplicity Studio packages might be presented as well and if there are any it is okay to install those updates as well.
After the installation, Simplicity Studio needs to be restarted and then a "Git" perspective should be available within Simplicity Studio.
Information about Cloning a Git Repository can be found in this KB article.
If Simplicity Studio V3.3 is being used, then the following knowledge base articles explain how one can debug an EFM8/EFM32 product on a custom board:
For SS V4, the hardware set up for the EFM8, EFM32, EFR32 or BGM devices remains the same and can be referred to from the Knowledge Base articles listed above. The Simplicity Studio configuration, however, has been modified to make changing debug modes easier. There is no Kit Manager in V4, and debug modes can be changed directly from the Launcher perspective.
To prepare your setup:
1. Connect the debug pins between the debugger and the target board as described in the Knowledge Base articles above.
2. Power the custom board.
3. Connect the STK to the host and move the switch to the AEM or Debug position or connect a JLink debugger to the host.
In Simplicity Studio, perform the following steps to connect to a target board using an STK in debug OUT mode:
1. Launch Simplicity Studio V4 and select the root element in the Device view of the STK.
2. The Launcher perspective shows the Debug mode, and there is a link next to it to change the debug mode.
3. Click on Change. In the subsequent J-link window, under the Adapter Configuration tab, change Debug Mode to OUT.
4. Go to the Device Hardware tab in the same window. Change the Target Part to the target MCU. Leave the Target Interface as SWD. Click OK.
5. The device information will be updated in the Device view in the Launcher perspective.
6. These steps may need to be repeated after closing and reopening Simplicity Studio.
An alternative way to get the J-link window (Step 3) open would be to right click the root element and select Device Configuration. Steps 3 - 6 will remain the same.
Now you can debug the external EFM8/EFM32/EFR32/BGM MCU using Simplicity Studio V4.