The latest updates to Windows 10 and Windows 7 have caused reported issues with Silicon Labs' Toolstick adapters, 8-bit debug adapters, and 32-bit debug adapters.
The updates in question are:
KB4487044 (Win10 ver 1809)
KB4487017 (Win10 ver 1803)
The reported behavior is that the debug adapters do not enumerate properly. Affected devices will not show up in the Windows Device Manager. Example bug reports are linked below.
If you are running into these issues you can try to roll back the above updates. However note that Microsoft places some restrictions on rolling back an update. For more information about rolling back a windows update and Microsoft's restrictions on uninstalling updates click the links below.
If you are able to roll back these updates but still experience issues, please submit a support ticket here.
Silicon Labs is in contact with Microsoft and we are working to resolve the issue. Updates will be posted here.
when I try to upload Code on my SLSTK2010A board (with an EFM8SB1) today -yesterday it worked perfectly- , it wants me to run an Adapter firmware update. But unfortunately I always get errors doing this. After trying it via device configuration or Simplicity Commander, the error "The kit is still in Bootloader mode, it seems like the Installation failed." occurs. As a consequence, I can't even choose the debug mode. When I try it via Simplicity Commander, an MCU Change throws out "An error was encountered trying to set the debug mode: EMLINK failed."
I would be grateful for any idea how to fix this.
Are there any options to generate a Makefile from Simplicity Studio.I cannot longer stand the 'Simplicity' of it
The 32-bit USB Debug Adapter (black colour nowadays) is no longer visible for applications such as uVision 4 or with the USB UDA Firmware Reset Utility.
This is fairly recent - as it was working properly few months ago.
Reading threads on this subject show that this issue is well present.
Furthermore a colleague has the same issue with another UDA-32 and another Win7 enterprise SP1 Laptop.
We tried with professional IT support to remove the in the Microsoft Device Manager HID duplicates and I have removed the security update (12-Feb-2019) with no effect on this issue.
We are now exhausting our possibilities with Win 7 - and it seems- according to forum threads - that windows 10 users have a restored UDA-32 visibility by applications.
Any advice regarding this UDA-32 invisibility issue is welcome.
Hi, I have a project that I have been working on and was building perfectly fine until I decided to edit the .isc file. I changed the value of Device Name and then clicked "Generate" and the project no longer builds. Upon opening up the properties for the project I find that the includes and symbols (and seemingly some other things) have all been deleted! Is there a way to make that not happen or to easily fix it afterwards?
I have a linker problem after convert a project to C++, so I tried to convert a new fresh empty-soc project and I got similar errors. The JPitt's solution in a previous post didn't work for me.
This is what I did:
1. Create a empty SoC project for BGM13P22F512GA with Gecko SDK Suite: Bluetooth 2.11.0
2. Test it, it will work.
3. Convert to C++ project using option "Convert MCU project to C or C++", clean and build the project.
Finished building: ../app.c Finished building: ../init_app.c Finished building: ../init_board_efr32xg1.c Finished building: ../init_mcu_efr32xg1.c Finished building: ../pti.c Finished building: ../main.c Finished building: ../hardware/kit/common/drivers/mx25flash_spi.c Building target: soc-empty.axf Invoking: GNU ARM C++ Linker arm-none-eabi-g++ -g -gdwarf-2 -mcpu=cortex-m4 -mthumb -T "/Users/XXXXX/SimplicityStudio/v4_workspace/soc-empty/bgm13p22f512ga.ld" --specs=nosys.specs -Xlinker --gc-sections -Xlinker -Map="soc-empty.map" -mfpu=fpv4-sp-d16 -mfloat-abi=softfp --specs=nano.specs -o soc-empty.axf "./platform/emlib/src/em_assert.o" "./platform/emlib/src/em_burtc.o" "./platform/emlib/src/em_cmu.o" "./platform/emlib/src/em_core.o" "./platform/emlib/src/em_cryotimer.o" "./platform/emlib/src/em_crypto.o" "./platform/emlib/src/em_emu.o" "./platform/emlib/src/em_gpio.o" "./platform/emlib/src/em_i2c.o" "./platform/emlib/src/em_msc.o" "./platform/emlib/src/em_rmu.o" "./platform/emlib/src/em_rtcc.o" "./platform/emlib/src/em_se.o" "./platform/emlib/src/em_system.o" "./platform/emlib/src/em_timer.o" "./platform/emlib/src/em_usart.o" "./platform/emdrv/sleep/src/sleep.o" "./platform/Device/SiliconLabs/BGM13/Source/GCC/startup_bgm13.o" "./platform/Device/SiliconLabs/BGM13/Source/system_bgm13.o" "./hardware/kit/common/drivers/mx25flash_spi.o" "./hardware/kit/common/drivers/retargetio.o" "./hardware/kit/common/drivers/retargetserial.o" "./hardware/kit/common/bsp/bsp_stk.o" "./app/bluetooth/common/util/infrastructure.o" "./app.o" "./application_properties.o" "./gatt_db.o" "./init_app.o" "./init_board_efr32xg1.o" "./init_mcu_efr32xg1.o" "./main.o" "./pti.o" "/Users/XXXXX/SimplicityStudio/v4_workspace/soc-empty/platform/radio/rail_lib/autogen/librail_release/librail_module_efr32xg13_gcc_release.a" "/Users/XXXXX/SimplicityStudio/v4_workspace/soc-empty/platform/radio/rail_lib/autogen/librail_release/librail_config_bgm13p22f512ga_gcc.a" "/Users/XXXXX/SimplicityStudio/v4_workspace/soc-empty/protocol/bluetooth/lib/EFR32BG13P/GCC/libbluetooth.a" "/Users/XXXXX/SimplicityStudio/v4_workspace/soc-empty/protocol/bluetooth/lib/EFR32BG13P/GCC/binapploader.o" "/Users/XXXXX/SimplicityStudio/v4_workspace/soc-empty/protocol/bluetooth/lib/EFR32BG13P/GCC/libmbedtls.a" "/Users/XXXXX/SimplicityStudio/v4_workspace/soc-empty/protocol/bluetooth/lib/EFR32BG13P/GCC/libpsstore.a" -lm -Wl,--start-group -lgcc -lc -lnosys -Wl,--end-group /Users/XXXXX/SimplicityStudio/v4_workspace/soc-empty/protocol/bluetooth/lib/EFR32BG13P/GCC/libbluetooth.a(ll_radio_pa.c.obj): In function `ll_radioInitPA': ll_radio_pa.c:(.text.ll_radioInitPA+0x70): undefined reference to `RAIL_TxPowerCurvesDcdc' ll_radio_pa.c:(.text.ll_radioInitPA+0x74): undefined reference to `RAIL_TxPowerCurvesVbat' collect2: error: ld returned 1 exit status make: *** [soc-empty.axf] Error 1
I'm working with Mac OS 10.14.3 and Simplicity Studio SV18.104.22.168.
Thanks in advance!.
I've got a Blue Gecko Module Wireless Starter Kit. After installing the Studio on my Windows 7 PC I was noticed that I should update the firmware of on board J-Link PRO OB.
Ok I've started it waited a long time so that it can finished but after an hour it did not finished.
I can still connect via ethernet to the board and load the firmware on it. But the onboard JLink is only displayed in windows device manager with no installed driver.
Where can I get the driver from? It is still possible to reflash the J Link ?
I've been using the toolstick adapter for years without issue. A few days ago, toolstick stopped working. Plug in the toolstick and Windows more or less rejects the device at a low level. I have multiple toolsticks and see the same across devices. I also have multiple Windows machines and all exhibit the same behavior.
The failure occurred after Windows update KB4487017.
Rolling back the update enables the toolstick to work again. This is confirmed on multiple Windows machines.
We can only hold off the Windows update for 30 days.
All software affected including Flash programming utility, Simplicity Studio, etc... Software does not recognize the toolstick is plugged in.
I'm a student and for a group project we're working on a Bluetooth Mesh network using Simplicity Studio and the thunderboard sense2. When i tried installing the program though, i kept getting several errors all due to a lack of heap space (lang.outofmemoryerror and java heap space errors) . I already reinstalled the program completely for like 10 times and it doesn't solve the problem. I've also tried everything from the following thread: https://www.silabs.com/community/wireless/zigbee-and-thread/knowledge-base.entry.html/2017/04/10/heap_issues_withsim-x83A . When i try to make the maximum heap size bigger like it said in the file it has no affect on the actual heap space available. I installed simplicity studio on an old laptop of mine and there it works just fine, there i can even modify the heap space using the studio.ini file as it should.
When i did number 3 in the thread linked above (monitoring the heap space), i noticed that it's stuck on 256MB and i'm unable to make it any bigger.
I really hope someone can help me because i'm already stuck on this for several weeks now.
Thanks in advance!
I just installed the implicity studio and using IDE to import an existing project to workspace (C8051F340 project, using license keil 8051 v9.53). After building the project, an error happen as shown in attached file: Program "make" not found in PATH.
How can I solve this problem.
Ive tried posting this issue im facing on the bluetooth forum, link:
And was redirected here.
I am trying to convert a soc-empty project from c to c++.
The board im using is the development board BGM121 ( BRD4302A).
i have followed the instructions from the link:
The steps ive taken so far:
1) create a new project with Bluetooth SDK 22.214.171.124 on the development board BGM121 ( BRD4302A, SLWSTK6102A)
2) Testing out that the empty C project are able to compile and build. - which it is, without errors
3) converted the C project to C++ by Project -> Convert -> Convert MCU project to C or C++ -> ...
As further testing, ive tried to build it on a linux virtual machine aswell ( in case Windows 10 somehow conflicted ) got the same result.
Since a while ago I can no longer update Simplicity Studio.
For information I started the studio with run_studio.sh in a command line.
A SDK board is plugged in the USB.
I started the update of the first proposed update.
It failed with the error message shown in the screenshot.
The studio was setup with the SDK board plugged.
With the current version I can edit/compile/debug
I deleted the cache and logs of the Simplicity Studio without any visible differences
I tried a fresh installation, but with this installation I can not update too.
It detects the SDK and collects the parts to install.
But nothing happens pressing the "next" button to start installation.
Than I installed the windows version under wine.
Any ideas what could be wrong?
My linux is gentoo.
I would like to use the rfsense feature for waking from deepsleep by Bluetooth. I am trying to create the above project as recommended in KBA_BT_1009. I am getting the following error when I try to create the project:
I have just updated my SDKs:
I thought the issue might be not having the Micrium OS alongside the latest SDK so I tried to update that but that fails:
I would appreciate any help in getting this example project working.