As Nicholas Flowers wrote: > - I'd like it to be a "usb" interface, not a serial (I want to keep > my data bridge clearly separate from the programming interface)
So a CDC device is nothing you could live with? > - the stk500v2 have hard-coded vid/pid (can't read from config file). AVRISPmkII talks a very specific protocol which so far has only been implemented by Atmel's original device, plus maybe a couple of clones which try to clone it as best as possible (including VID/PID), so they are accepted by Atmel Studio. If you think you have a need to read the VID/PID for that from the config file, that should be simple to add. So far, nobody needed it. > - the usbtiny/usbasp will accept a vid/pid, but not a serno (like > usbdev_open seems to allow). Both are meant to work with fairly simple firmware implementations (based on VDEV). Again, adding a serial number check might not be too hard, it's just that these implementations typically don't feature a serial number. -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) _______________________________________________ avrdude-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/avrdude-dev
