Hi Norm,

Thank you for your question regarding problems with the Silicon Labs 8-bit USB debug adapter.  I have a few questions to help with debugging this issue:

1) Can you confirm that the device is powered correctly (check voltage on all power rails)?

2) This may be an issue with reprogramming the USB Debug Adapter (UDA), which is usually handled automatically during the process of connecting/programming using the UDA.  Please try running the USB Rest Utility and then try connecting/programming again:

https://www.silabs.com/documents/login/software/USB_Reset_Utility.zip

https://www.silabs.com/products/development-tools/software/8-bit-8051-microcontroller-software#driver

3) This knowledge base article contains tips on debugging another error message but may be relevant to this case as well:

https://www.silabs.com/community/mcu/8-bit/knowledge-base.entry.html/2010/08/26/debugging_detected-D0t5

Thank you, and please let me know if you have any questions.

Regards,
Mitch

Hi Guy,

A couple things:

1) Yes, you should observe the timing constraint that you mentioned for C2CK.  Sorry for missing that when I recommended changing the debug strobe speed earlier.  You should be able to change that, but with the constraint that T_C2CK_low < 5 us.  

2) With regard to your custom hardware, I recommend:

• removing the 0.1 uF cap connected via 1k ohm resistor to the C2CK line.  This will make that network into a 2k pullup on C2CK, which should be ok.
• Changing the other 0.1 uF cap to 4.7 uF, as 0.1 uF is not enough bypass capacitance on the VDD supply.

3) If you are still having troubles after increasing the C2CK clock speed to meet the timing requirements and the hardware changes, please capture oscilliscope traces of the C2CK and C2D signals during operation with enough detail to see rise and fall times and overall timing, and post those here. 

4) Also, please let me know the results of running your original (HF clock) code on your custom target as well as your test of running with LFOSC0 on the STK.

Thank you!

Regards,

Mitch

Hi Guy,

A couple things:

1) Yes, you should observe the timing constraint that you mentioned for C2CK.  Sorry for missing that when I recommended changing the debug strobe speed earlier.  You should be able to change that, but with the constraint that T_C2CK_low < 5 us.  

2) With regard to your custom hardware, I recommend:

• removing the 0.1 uF cap connected via 1k ohm resistor to the C2CK line.  This will make that network into a 2k pullup on C2CK, which should be ok.
• Changing the other 0.1 uF cap to 4.7 uF, as 0.1 uF is not enough bypass capacitance on the VDD supply.

3) If you are still having troubles after increasing the C2CK clock speed to meet the timing requirements and the hardware changes, please capture oscilliscope traces of the C2CK and C2D signals during operation with enough detail to see rise and fall times and overall timing, and post those here. 

4) Also, please let me know the results of running your original (HF clock) code on your custom target as well as your test of running with LFOSC0 on the STK.

Thank you!

Regards,

Mitch

Hi Guy,

I am not familiar with the Invalid Installation message you are getting about Studio, but given this, I would recommend trying a fresh installation of the latest version of Simplicity Studio to see if this resolves your connection and debug issues.  Thanks!

Regards,

Mitch

Hi Guy,

One thing you could try is changing the default JLink speed to a slower speed to try and match the internal oscillator speed and not have a large mismatch between the debugger speed and the core clock speed.  Try doing this by right clicking your JLink adapter for the EFM8BB1 starter kit board in Simplicity Studio Launcher under the [Debug Adapters] tab, then clicking [Device configuration...].  Then, click on the [J-Link Configuration] tab and change the J-link speed:

Does this help and are you able to debug?  Thanks!

Regards,

Mitch

Hi Zeka,

Thank you for your request for a code review for your EFM8UB2 application.  I will be out of the office on Monday, November 25, as well as Thursday and Friday, November 28-29, however I will take a look and try to provide some feedback on the device initialization and peripheral use aspects of your application this Tuesday and Wednesday.  Thank you for your patience.

Regards,

Mitch

MCU Applications Engineer

Hello,

Thank you for contacting Silicon Labs with this support request.  I have escalated this case to our ProSLIC & Voice DAA Support Team.  Thank you.

Regards,

Mitch