Known Issues#

499669, 499661

The EmberZNet SDK's dynamic multiprotocol (DMP) sample applications rely on the Micrium OS and Bluetooth SDKs also being installed. If those SDKs are not installed, the DMP sample applications are still presented as options. Attempting to create a DMP sample application may fail, or may appear to complete but subsequently fail to generate because of unresolved dependencies on those SDKs. Subsequently installing those SDKs may not resolve the issues in that existing DMP sample application project.

Install the Micrium OS and BLE SDKs before creating an EmberZNet DMP sample application project.

501464

Pintool is showing errors for pin selections in modules you are not currently configuring, even if, by selecting a different module, you were expecting any pin assignments previously made to no longer matter.

Find the 'Selected Module' that has the pin conflict and set the field to 'None' to remove the conflict.

520104

The project shows indexer (semantic) errors.

Try unchecking the following in Preferences > C/C++ > Indexer: 1) Index source files not included in the build; 2) index unused headers; and 3) Allow heuristic resolution of includes. Click Apply and Close.

522243

Building a project when a Proprietary Radio Configuration or a Bluetooth GATT Configuration contains unsaved changes causes a race condition, which leads to a case where the build picks up the old configuration.

Save the configuration before building the project or build the project again.

620727

When Radio Boards are used that contain both an EFR32 or EFM32 target as well as one of the Energy Friendly EFP parts, the Launcher perspective incorrectly shows the EFP as the target part and so the Preferred SDK is wrong and there are no software examples for the board.

Create a new project through File > Silicon Labs Project Wizard so that the Target, SDK, and Toolchain Selection dialog opens. In the Target Device drop down, select the other target part on the board. If it is not already displayed, select the correct Gecko SDK Suite in the SDK drop down list. from the list. Click Next. Now the correct software examples will be listed for the board.

637660

If the Energy Profiler is started for an EFR32xG2x (series 2) part from the Simplicity IDE perspective using the Profile icon or Profile As, the displayed current might be artificially high.

Press the reset button on the WSTK or board. The profile will continue, but the current will go to the correct level. If the application has not changed - so the flash does not need to be updated - then just start the capture directly from the Energy Profiler perspective with the Quick Access > Start Energy Capture option.

652484

When using the GNU Debugger (GDB) Attach or Connect sessions for 32-bit devices, may the debugger halts the application in a loop, e.g. while loop to delay application. In this scenario, if the user attempts to step through code, the debugger may go into a state where it appears to be "stuck" in that block of code and make repeated register reads.

Press the "Suspend" button, followed by the "Step Return" button in the GUI to move up the call stack to the calling method, where you can continue stepping as normal. In rare cases, this workaround does not work and the debugger is "stuck" in the loop; either let GDB proceed executing logic or terminate and start a new GDB session.

652496

Studio creates temporary launch configuration for GDB Attach and Connect sessions at runtime, but does not save the launch configurations. They should be saved so they can re-used and customized by users.

None

652646

When deleting a project that opens an HTML read-me file, the opened editor with the HTML file does not close even though the resource document in the project is deleted.

This is a copy of the file the browser has cached, so simply close the window.

653933

Opening the Device Configuration dialog causes the Silink daemon to run targeting the selected device. Subsequently, when Simplicity Studio runs Silink daemon and a GDB session that both target the device, the GDB session starts in an invalid state where the debugger cannot read the device's memory, cannot set breakpoints, etc. NOTE: For custom devices, such as a customer's PCB device, after the GDB session starts Simplicity Studio's CPU usage may go up to 100% and RAM consumed goes up to 5GB.

Terminate the Silink executable process after closing the Device Configuration dialog and before starting the GDB session.