From: SourceForge.net <no...@so...> - 2011-08-30 09:26:57
|
Feature Requests item #3289022, was opened at 2011-04-18 21:59 Message generated for change (Comment added) made by joerg_wunsch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=425410&aid=3289022&group_id=39505 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements (example) Group: None Status: Open Priority: 5 Private: No Submitted By: Markus Baertschi (markus_b) Assigned to: Nobody/Anonymous (nobody) Summary: Allow for the same device designations as avrdude Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: Joerg Wunsch (joerg_wunsch) Date: 2011-08-30 11:26 Message: 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). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=425410&aid=3289022&group_id=39505 |