- Silicon Labs Community
- Welcome and Announcements
- Silicon Labs Knowledge Base
- 8-bit MCU
- 32-bit MCU
- Bluetooth / Wi-Fi
- Other Products Category
- Optical/RH/Temp Sensor
- Other Products
- Hardware and Software Tools
- Simplicity Studio and Software
- General Discussions and Suggestions
- Chinese Forum
- Software Libraries
- Development Kits
- Reference Designs
- Third Party Tools
- White Papers
- Official Blog of Silicon Labs
- Chinese Blog
11-05-2016 11:46 AM
I haven't connected any devices apart from my multimeter to my SLSTK2000A (EFM8UB1 kit) yet, but I have been tinkering with the sample code using the on-board LED.
I was using the Linux version of Simplicity Studio in Ubuntu 16.04 (Simplicity Studio 4). It was working fine one evening while I had it plugged in via the kit USB connector, and all of a sudden it wouldn't flash it anymore. I then plugged it into my laptop that runs Windows 10, and it won't work on that either.
The SLSTK2000A kit looks normal (the LCD displays the Silicon Labs logo, the blue LED to the left comes on, and the yellow LED to the left blinks like it usually does).
It detects it correctly when I use the 'Add Device' option, but it just won't upload the code.
I really hope it isn't permanently damaged. Thank you for your time...
11-07-2016 12:17 PM
This may seem like a tedious step, but can you go to the Launcher and select the Devices tab. From there select Refresh to see if the board is displayed once again. After the board is detected and you highlight the top level J-Link as shown in the picture. From there, go back to the IDE and select the Debug icon. This should load the flash and start the debugger.
If it does not connect, can you then try going to the project settings and selecting the correct part (it was probably correct, but just trying it again). Select the Board / Part / SDK as shown in the figure below and select the correct part.
11-07-2016 03:49 PM
Thanks for your reply. I tried that, and it was set to the correct board, but the Universal Bee was not listed in the board options. The correct MCU was available in the MCU options list, though.
This is the error I get when trying to debug.
11-07-2016 04:17 PM
I just let it try to install something that like firmware tools for the kit (it suddenly asked me if I wanted to download it), it said it failed, and now the kit can't be detected at all. The yellow LED I mentioned to the left no longer comes on. The LCD is now blank.
11-07-2016 05:17 PM
From the launcher select to Change the adapter firmware.
If that doesn't work please submit a support ticket so that we can determine if the board is bad.
11-07-2016 05:33 PM
That is good news. Let's start from the beginning just to make sure. Can you select the blinky example project and bring it into the IDE? Try to build, download, and run the code to see if that basic project works?
11-07-2016 05:43 PM
Yes, and I am now able to select the board in the project properties as you said to.
I have now created the Blinky sample project, but I get the following error:
'Failed to connect to device
TCF error report:
Error text: No adapter found
Error code: 131073'
11-07-2016 06:27 PM
In the Launcher window can you go to your devices tab and select Refresh? See if the debugger shows up there. Highlight it and then go to the IDE and try to download? If you can send a screen capture of the Device window that would be helpful too.
11-08-2016 08:06 AM
just some things
several problems akin to yours have been related to "somewhat fuzzy" USB hubs
several problems akin to yours have been related to laptops with insufficient USB power
try disconnecting as much as you can from the USB and insert the programmer directly in your PC
11-08-2016 08:21 AM
I did that too. I have been using the kit USB connector to the left of the board, but not the other connector at the bottom of the board. Do I need to plug in both for this?
11-08-2016 10:25 AM
I see your SDK is at 4.0.1. Can you try updating your Studio install for the SDKs and 8 bit devices just to make sure everything is the latest? The latest SDK is 4.4.1. Once updated, you may be prompted to update the board firmware again. Go ahead and do that if needed.
11-08-2016 11:15 AM
In addition to updating your install, can you look in the Studio installation directory for siagent log files? The files will be in ./developer/adapter_packs/efm8/ and named siagentefm8_log_<procid>.txt. Please attach that and we will take a look at it.
11-08-2016 05:30 PM
Ok, here are the SDK versions installed.
There were several of the siagent files you mentioned, so I attached one from November 7.
11-10-2016 10:23 AM
Sorry...that is correct.
Can you try and review the log output when starting the debug session? To do this run:
tail –f /var/log/kern.log
from a command line. That command will show the last 20-ish lines in the kern.log file. As new log lines are written to the file, you will see them in the command window.
Attach the log file so we can review that as well?
11-10-2016 09:20 PM
nicholas@nicholas-CQ5715F:~$ tail –f /var/log/kern.log tail: cannot open '–f' for reading: No such file or directory ==> /var/log/kern.log <== Nov 10 22:15:30 nicholas-CQ5715F kernel: [ 3463.564809] usb 3-2: new full-speed USB device number 2 using ohci-pci Nov 10 22:15:30 nicholas-CQ5715F kernel: [ 3463.739891] usb 3-2: New USB device found, idVendor=1366, idProduct=0105 Nov 10 22:15:30 nicholas-CQ5715F kernel: [ 3463.739903] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 10 22:15:30 nicholas-CQ5715F kernel: [ 3463.739911] usb 3-2: Product: J-Link OB Nov 10 22:15:30 nicholas-CQ5715F kernel: [ 3463.739917] usb 3-2: Manufacturer: Silicon Labs Nov 10 22:15:30 nicholas-CQ5715F kernel: [ 3463.739922] usb 3-2: SerialNumber: 000440041466 Nov 10 22:15:30 nicholas-CQ5715F kernel: [ 3463.802574] cdc_acm 3-2:1.0: ttyACM0: USB ACM device Nov 10 22:15:30 nicholas-CQ5715F kernel: [ 3463.803117] usbcore: registered new interface driver cdc_acm Nov 10 22:15:30 nicholas-CQ5715F kernel: [ 3463.803119] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Nov 10 22:16:57 nicholas-CQ5715F kernel: [ 3550.741076] usb 3-2: USB disconnect, device number 2
11-14-2016 02:11 PM
We cannot tell what exactly is going on from the logs submitted, but it appears there is a disconnect message showing up for some reason. We are trying to duplicate what you are seeing and will report back our findings.
11-14-2016 06:08 PM
I do not know the erase utility for the EFM's but whichever erase utility there is should allow a full erase regardless of "able to connect"
if your previous workings have (accidentally) written to the protect region that is what you need.