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 ?
One of our FAEs started facing what sounds like the same or similar issue recently. After he updated the debug adapter firmware, the debug adapter were no longer recognized by Simplicity Studio. If you open the Windows Device Manager, does the JLink device show up under "Other devices"? If so if you right click the device and select "Update Driver Software..." and use the "Search automatically..." option is it able to find and install the driver software? If not you can select the manual option and browse for the JLink drivers in C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\installers\Segger_JLink or else download it from the Segger website (https://www.segger.com/downloads/jlink#J-LinkSoftwareAndDocumentationPack ).
The FAE found that after updating the JLink driver, the debug adapter firmware had been updated to the latest version.
Please let me know if this helps or if you are seeing a different issue on your computer.
I tried as you said. I downloaded the Software from Seeger and installed it. The J-Link device did not found the driver automatilly.
I tried the x64 folder of the Seeger installation, there are two cat files. I tried to set the driver manually for all included devices listed, J-Link 1..3, J-Link driver.
All are not recognized in the Simplicity IDE,
Connecting to device with serial number 440143469 .inspect_emdll [ERROR: Error while opening a device: Cannot connect to J-Link via USB.
I started the studio with normal user rights and also as admin. Just did not work.
Is the J-Link now bricked?
I believe you need to use the x86 folder from the Segger installation for the 32-bit drivers (even though your PC is 64-bit). That is what Segger told the FAE that was experiencing the issue.
In no way would the STK be bricked, once the correct driver is installed it will be recognized again. There are also ways to recover an STK by either using Simplicity Commander from the command line ( from a command prompt and the C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\commander directory type 'commander device recover') or else by forcing the STK back into its bootloader mode as it is plugged into the USB port.
I tried the same on my colleges Laptop and it works. Seems to be something related to Windows 7.