On Wed, 14 Aug 2024 01:47:05 +0300 kodcode <kodc...@gmx.com> wrote: > Doesn't work for me. > Have you tried your solution (with an usbasp)? > > On Sun, Aug 11, 2024 at 06:35:50PM +0200, Rob Schmersel wrote: > > On Sun, 11 Aug 2024 00:51:31 +0300 > > kodcode <kodc...@gmx.com> wrote: > > > > > Please try to run your command as root. > > > (I don't need to specify the port with -P) > > > > > > - > > > kodcode > > > On Sat, Aug 03, 2024 at 09:06:33PM +0800, Sadeep Madurange wrote: > > > > On 2024-08-03 15:39:14, Sadeep Madurange wrote: > > > > > I'm trying to flash a atmega328p using avrdude using > > > > > > > > > > avrdude -p atmega328p -c usbasp -P /dev/cuaU0 -D -U > > > > > flash:w:blink.ihex:i > > > > > > > > > > The command fails with error > > > > > > > > > > avrdude: error: could not find USB device with vid=0x16c0 > > > > > pid=0x5dc vendor='www.fischl.de' product='USBasp' > > > > > > > > I managed to get things working with the arduino programmer > > > > instead of usbasp. > > > > > > > > -- > > > > Sadeep Madurange > > > > PGP: 103BF9E3E750BF7E > > > > > > > > > > > Or better yet, add 'dialer' as a group to your user: > > # usermod -G dialer [user] > > >
I have not tried it with avrdude/usbasp as I don't own one, but serial ports are owned by root:dialer. sfp$ ls -l /dev/cua* crw-rw---- 1 root dialer 8, 128 Aug 11 16:59 /dev/cua00 crw-rw---- 1 root dialer 8, 129 Aug 11 16:59 /dev/cua01 ... crw-rw---- 1 root dialer 66, 128 Aug 11 16:59 /dev/cuaU0 crw-rw---- 1 root dialer 66, 129 Aug 11 16:59 /dev/cuaU1 ... So adding yourself to the dialer group will allow access to the ports from your user. This works for me with other devices, e.g. accessing the serial port on an SBC/microcontroller (even programming arduino's directly) What does dmesg show for the usbasp when connected? If it does not show as a ucom device it will indeed not work
