[feature-request #5] Allow for the same device designations as avrdude

[avrs-admin]

markus_b 2011-04-18 19:59:32

Avarice has requires a long device description, like 'attiny85', avrdude uses a short string 't85' for the same device. Both programs should accept the same designations.

This issue was migrated from https://sourceforge.net/p/avarice/feature-requests/5/

[avrs-admin]

joerg_wunsch 2011-08-30 09:26:57

Unlike AVRDUDE (which has to know the device type beforehand in order to know which protocol/protocol variant to talk), you can normally get away in AVaRICE without specifying any device ID. As AVaRICE can only talk either JTAG or debugWIRE (which is distinguished by the -w option), it is then safe to query the JTAG ID over this connection.

AVaRICE will then use the queried ID to select the device from the device table. The only useful purpose of the -P option is when you're using a device that is not officially supported, but can be talked to by selecting a compatible device (the -P option always works as an override over the queried device ID).

[avrs-admin]

markus_b 2011-08-30 18:23:17

I see, so unified device names are not that important. But I propose a change of wording in the man page and the built-in help.

Existing: -P, --part Target device name (e.g. atmega16) New: -P, --part Target device name (e.g. atmega16). Optional, avarice autodetects the device via JTAG or dW.

[avrs-admin]

joerg_wunsch 2011-08-30 19:03:07

Thanks for the suggestion, I did it that way, and documented that -P acts as an override to the automatic device detection.

[avrs-admin]

joerg_wunsch 2011-08-30 19:03:07

• assigned_to: nobody --> joerg_wunsch
• status: open --> closed