Package: avrdude Version: 6.3-20171130+svn1429-2+b1 Followup-For: Bug #942289
The patch provided in the previous message makes some changes to how ft245r devices parse the port command line parameter. 1) for a default port (no -P provided) or "-P usb" it will select the first ftdi devnum (0). This reverts to the operation prior to upstream patch 8580. 2) for a -P usb:XXXXXXXX it will check if a valid serial number is provided and select the correct ftdi devnum. In this regard it is identical to the functionality of upstream patch 8580. 3) for a -P usb:ftX it will fail. In this regard it is a reversion of the functionality of upstream patch 8580. I think the logic could be altered to allow this type of port selection. I would not be averse to this change and it would accommodate users who have changed to post 8580 port selection semantics. I believe that the helpful message at line 590 of 7e245a25 should be more clear about how to pass "-P usb:ftX" if this variant is kept. 4) for a -P ftX it will select the ftdi devnum provided by X. In this regard it is a reversion to the previous operation prior to upstream patch 8580. I don't know if upstream want to allow the "-P ftX" anymore, or if they want to transition to the "-P usb:ftX" manner of port selection for usb attached devices. The patch does not address the possibility of parsing the usbsn or usbdev parameters from .avrdudrc file. These parameters are available in the pgm structure, but I think an even better way to avoid having to create a custom programmer type would be to parse the default_serial or default_parallel parameters from .avrduderc. I am not familiar enough with avrdude to provide a patch which would look at these parameters and try to use them in the "port" parameter of the ft245r_open function.
