Hi All!

You are welcome.  We are working on making the older versions available.  Also, this new version v5.2.4 should be available on the regular website now.  Thanks again!

Regards,

Mitch

Hi All,

Sorry for the problems you have been experiencing with Mac VCP driver v5.2.3, and thank you for your bug reports!    We have fixed this compatibility issue in the driver attached to this post.  The attached driver has been tested on MacOS 10.11, 10.13, 10.14, and 10.15.  This should be available on our website shortly.

As for the availability of previous versions, this is a request we have heard expressed, and are discussing to determine how to best address the request.  Thank you for your patience.  Please let me know if you have any questions or have continued issues with driver v5.2.4.

Regards,

Mitch

Hi Tiago,

Thank you for your question about the Mac OSx VCP installer v5.2.3, and for providing detailed information.  I wanted to let you know that I am looking into this with our driver team and will let you know what I find out.  Thanks!

Regards,

Mitch

HI Norm,

I will contact you directly to discuss finding a solution to this issue.  Thank you.

Regards,

Mitch

Hello,

This question appears to be a duplicate of one asked on 10/25/2019.  Please refer to the response posted on the original thread:

https://www.silabs.com/community/mcu/32-bit/forum.topic.html/graceful_usb_msdcontentionhandling-is2f

Thank you!

Regards,

Mitch

Hi Norm,

Do you know if the client has tried this with more than one USB Debug Adapter (UDA), or have all of the failed results been using the same UDA?  

The message about "new version 40, old version 34" is given by the software tools (i.e. IDE) when upgrading the UDA firmware when first attaching, and should not necessarily indicate a problem.  

Regards,

Mitch

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