Bad Atmel Behaviour

An annoying barrier to entry for new users is QMK Toolbox's behaviour with Atmel chips. I know unlike other MCUs they must be selected manually, but this is quite a typical event when dealing with IBM Model F controllers:

Note:

• QMK Toolbox correctly identifies the device as 32u2
• But tries to flash it as a 32u4 because that's the default value in the non-obvious MCU pulldown menu up at the top right
• QMK Toolbox reports the error and gives up

The user is left baffled.

May I suggest two ideas:

• If the MCU identifies itself, as this one did—I believe most or perhaps all Xwhatsit-based 32u2 controllers include the text 32u2 in this string—try flashing as that MCU
• Exhaustively try the various Atmel MCUs in the pulldown, until one works, as an "Auto" mode which should be the default; unless overridden manually by an advanced user

Sure, a failure like the screenshot above is no surprise to an experienced user, but it's a poor experience and in this common case an easily avoided failure.

No source file or test is named. Start by tracing QMK Toolbox’s MCU selection pulldown and flashing path, then determine how device identification and failed Atmel attempts are handled. Done means the default behavior avoids the reported 32u2-versus-32u4 failure while still allowing manual MCU selection.