Re: USBasp -P option failing

[Doom]

Try to type this command :

avrdude -p m328p -c usbasp-clone -P usb:xxx -v

It will show you an error (of course it does not know xxx) and show you what choices are available (thanks to -v option)

Then look at the serial numbers

and then :

avrdude -p m328p -c usbasp-clone -P usb:_serial_number_-v -B 4 -U flash:w:firmware.hex

If it does not work, please show us what both commands return.

Doom.

ᐧ

Le ven. 11 déc. 2020 à 09:12, Doom <doom.mail@gmail.com> a écrit :

Hello,

I use the -P option with Atmel-Ice & avrdude and it works well with 2 programmers at the same time.

Can you show us what does 'lsusb' return ?

D.

Le jeu. 10 déc. 2020 à 20:59, JanHenrik <janhenrik@janhenrik.org> a écrit :

Hey!

I encountered a problem with a multiple USBasp programmer setup and I would like to ask if this is known/if there is a known fix to it. I looked though the bug-reports and searched the internet, however this seems to be a either rather unknown problem or usecase.

The AVRdude documentation states, that multiple USBasp programmers can (only) be distinguished by their physical USB-Bus connection via the '-P' option (e.g. in my case, Linux, '-P usb:001:095', lsusb shows two programmers located at Bus 001 and device 095 and 094). However this does not work, I can write pretty much anything after '-P' (yes even '-P Babelfish' works :D), the last connected programmer is always chosen. Is this a known Issue and is there a fix for it?

I am using two (later more) usbasp-clones (FASTUSBasp based), connected to the same USB-Hub, running the following command: 'avrdude -p m328p -c usbasp-clone -P usb:001:095 -v -B 4 -U flash:w:firmware.hex'


Thank you in advance!

Best Regards
Jan Henrik