Edit: Unfortunately, I accidentally posted my last response under my test account (used to test the customer experience with our community and ticketing system). I did not intend to post under an account that was not obviously my Silicon Labs employee account. To remedy this, I've re-posted my original response here:

This sounds like a classic tracking / settling time issue. I would take a look at this appnote: https://www.silabs.com/documents/public/application-notes/AN119.pdf

The jist is - when the ADC is enabled, it is tracking the selected input. This input is connected to the ADC's sampling capacitor, so it is being charged to the level of the input. When the ADC is disabled, the sampling capacitor not connected, so it can be discharged. So, after enabling the ADC, you need some time for the input signal to charge the ADC's input capacitor. This time is dependent on how much current the input signal can source. For example, if it is a very high impedance source, it will take longer to charge the ADC.

Edit: Unfortunately, I accidentally posted my last response under my test account (used to test the customer experience with our community and ticketing system). I did not intend to post under an account that was not obviously my Silicon Labs employee account. To remedy this, I've re-posted my original response here:

Hi quya,

I believe development on this tool is actually frozen, so I wouldn't expect any updates on the tool, even though I agree with your suggestions. I have, however, logged these feature requests to an internal ticket so they will be visible in case the tool is updated in the future. Internal ticket number MCUAB-3618.

-Brian

Hi Michael,

I understand your frustration. I will ping the team that provides these keys again and hopefully spur them to act as soon as possible.

-Brian

Edit: Unfortunately, I accidentally posted my last response under my test account (used to test the customer experience with our community and ticketing system). I did not intend to post under an account that was not obviously my Silicon Labs employee account. To remedy this, I've re-posted my original response here:

Hi Michael,

My apologies for the long delay in getting your DMS key. I've escalated this to the team responsible for monitoring xpress@silabs.com and providing these keys to customers, so hopefully the additional visibility will mean a faster response to your request.

-Brian

Hi Luis,

The production programmer has been updated to support the EFM8BB10F2I-QFN20 and EFM8BB10F4I-QFN20 devices. I've attached it to this message (it isn't available on the website quite yet). Let me know if you run into any issues with it.

-Brian

Hi Luis,

The production programmer has been updated to support the EFM8BB10F2I-QFN20 and EFM8BB10F4I-QFN20 devices. I've attached it to this message (it isn't available on the website quite yet). Let me know if you run into any issues with it.

-Brian

Hi Luis,

The production programmer has been updated to support the EFM8BB10F2I-QFN20 and EFM8BB10F4I-QFN20 devices. I've attached it to this message (it isn't available on the website quite yet). Let me know if you run into any issues with it.

-Brian

Hi Luis,

I confirmed that the latest production programmer utility doesn't support all EFM8BB1 devices (specifically, some of the 'I' devices). I am putting in an internal ticket to have that resolved.

In the interim, if you just need to program a device (that is, if you don't need the extra features of the production programmer like serialization), you can use the flash programming utility within Simplicity Studio, since it supports all devices: https://www.silabs.com/products/development-tools/software/simplicity-studio

Alternatively, I believe the standalone Simplicity Production Programmer supports that device: https://www.silabs.com/documents/login/software/Simplicity_Studio_Production_Programmer.zip

Simplicity Commander can connect to these devices, but you would need to be using a Jlink adapter (like a J-link Pro standalone debug adapter, or one of our STK's in debug out mode): https://www.silabs.com/products/mcu/programming-options#programming

Internal ticket: MCUAB-3611