I'm running Simplicity Studio v3 on Linux (Ubuntu 14.04 LTS). I have EFM32WG-STK3800 kit connected to my computer. The first time I connected it all worked as expected, suggested to update the firmware. An error window popped up after that, but the new version seemed to be running (it now has Mbed drag-and-drop function). After that, Simplicity Studio shows "No hardware detected" in the "Detected hardware" frame.
Note the following:
* OS reports a J-Link OB USB device connected
* There is a virtual COM port CDC
* MSD (Mbed USB device) works
So, is it just a software propblem? Am I stuck with Mbed forever? Or is there a way to get Simplicity to connect to the board again?
Having the mbed firmware on the board should not prevent Studio from working. What linux file browser are you using? If possible try closing it because if the mbed device is opened by another process Studio might have trouble accessing the connection. Also try re-starting Studio to make sure the detection process is re-initialized.
Let me know if this helps.
I'm using Gnome Shell. Not sure what the file browser is, maybe Nautilus, but in any case is not easy to avoid it. I did try "unmounting" the MSD.
No level of restarting helped: Simplicity, Gnome or PC.
I have a Windows virtual machine with Simplicity Studio and it works correctly when connecting the J-Link OB USB device.
Can you check if the content of your /etc/udev/rules.d/99-jlink.rules matches that of SimplicityStudio_v3/common/tcf/plugins/99-jlink.rules ?
This file should have been set up by setup.sh, but something might have gone wrong..
If that looks fine, can you please try to download Segger's tools from https://www.segger.com/jlink-software.html and try to connect using JLinkExe? That may help us figure out what's wrong.
udev rules are as correct... actually, JLinkExe found the device.
I found an error log, but there are only complains about optimization level settings.
Simplicity Studio produces many log files. If you go to Help > Report Bug..., follow the steps and upload the zip file as an attachment here we may be able to help you better.
Well... here it is some plugins are trying to link to libjlinkarm.so.5 which does not exist (libjlinkarm.so.4 is there though). I have libjlinkarm.so.5 for 64bit which won't link, so just created a symbolic link from libjlinkarm.so.4 to libjlinkarm.so.5 and it worked. Not elegant, but allows me to me work.
Logs of the error are attached. The error can be seen in siagent_log_3707.txt
Update: I downloaded Simplicity Studio again (md5sum was different from the previous file) to solve a problem with the IDE, and this time the link was included!
I also try to work with Simplicity on linux but by Giant Gecko board is not detected.
With the Tool "JLinkExe" and the command "ShowEmuList" I got the device.
In the log file I found only an UnstisfiedLinkError to a swt lib:
libXtst.so.6 can not open shared object file: no such file or directory ... libswt-pi-gtk.so
but I think this should not be the problem, isnt it?
There are many logs, did you check them all? You can get Simplicity to generate a compressed file containing all the logs.
Also, if you search for libswt-pi-gtk.so you'll find a lot of errors related to Eclipse on Debian or Ubuntu, but usually somewhat old releases.
I've got the same error on debian with the latest Studio freshly dowloaded.
I managed to solve it by installing missing package:
apt-get install libqt4-network:i386