Zak Kemble

@EclipseBoom Yes, that is expected. Auto-detect tries to automatically detect the MCU for you, but it currently only works with parts that use the SPI programming interface. Selecting an MCU...

The whole idea of auto-detect is to simply detect what MCU you have your programmer connected to and automatically select it from the drop-down list. If you don't want it...

Ok, so you're asking for a new feature that only verifies that the connected microcontroller is the correct part. I'll add it to the todo list, but I've no idea...

Yes, avrdude can read just the signature if only the programmer and MCU parameters are passed to it (that's how the auto-detect feature works), but AVRDUDESS still needs a new...

Awesome thanks! Though, there seems to be a few missed translations - TOOLTIP_LOWFUSE TOOLTIP_HIGHFUSE TOOLTIP_EXFUSE BITCLOCK FORMAT VERBOSITY AVRDUDEKILLED UPDATE_BADXML FILEFMT_BIN

Added! Translations will be in the next release. Yeah, detect doesn't always work depending on the MCU and programmer combination. Not a bug, just a limitation at the moment. See...

> > > Looks like the german language file is missing. I am not able to build. > > Severity Code Description Project File Line Suppression State > Error Could...

Blame the avrdude guys for sticking "The" in there :P I'll see about making the drop down list searchable, or an option to switch between displaying description and ID.

Hmm, I would rather find out the root cause of the issue. If I release a new dll it will just stop working again. The 1.0.4 .dll provided in this...

Usually, I only update binaries when I make a new release (there's only been 3 releases). There's been no changes since [v1.0.4](https://github.com/zkemble/libmcp2221/releases/tag/v1.0.4) release, so both the source code and binaries...