avrdude-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avrdude-dev] avrdude and usbasp


From: René Liebscher
Subject: Re: [avrdude-dev] avrdude and usbasp
Date: Sat, 14 Jan 2012 17:37:42 +0100
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1

   Am 14.01.2012 17:14, schrieb Mark:

   Here's what I got
   Flash the firmware from repository.
   /home/arturj/kkmulticopter/lib/avrdude/linux/avrdude -C
   /home/arturj/kkmulticopter/lib/avrdude/linux/avrdude.conf -p m168p -P
   usb -c usbasp-clone -B 8 -e -U lfuse:w:0xe2:m -U hfuse:w:0xde:m
   avrdude: Warning: cannot query product for device: No error
   avrdude: error: could not find USB device with vid=0x16c0 pid=0x5dc
   ...
   Looks like this happens inside usbOpenDevice function. If product name
   can not be read, function returns an error and program considers this a
   fatal failure. Perhaps instead we shoud just display a warning and not
   return an error or calling code should not consider this a fatal error,
   just a warning and continue. If we didn't have product id to begin
   with, chances are we don't care what it is. So change
   ...

   If you can not read it, this should be not ignored if there is a value
   to be checked specified in the config file.
   I will change it to either not reading it at all if there is a value
   specified or to ignore the error only in this case.

   Also, why are we making original USBasp, it's old version and NIBObee
   special cases hardcoded into usbasp_open function? Shouldn't the code
   be made generic and these 3 also moved to config file?

   If we remove it now many people will complain (especially users of old
   usbasp, if there are any, and users of nibobee) as they can no longer
   program their devices. May be we should add additional entries for them
   in the config file now and remove these special cases some versions
   later. So there is enough time people can change their settings.
   Kind regards
   Rene


reply via email to

[Prev in Thread] Current Thread [Next in Thread]