Subject: bug#364 closed by Mark Hindley <[email-masked]> (Re: bug#364: Beowulf: avrdude does not work with Atmel-ICE any more)

From: "Devuan bug Tracking System" <[email-masked]>
Date: Thu, 16 Feb 2023 13:54:06 +0000

This is an automatic notification regarding your bug report
which was filed against the avrdude package:

#364: Beowulf: avrdude does not work with Atmel-ICE any more

It has been closed by Mark Hindley <[email-masked]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <[email-masked]> by
replying to this email.

-- 
364: https://bugs.devuan.org/cgi/bugreport.cgi?bug=364
Devuan Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#364: Beowulf: avrdude does not work with Atmel-ICE any more
From: Mark Hindley <[email-masked]>
To: Nikolaus Klepp <[email-masked]>
Cc: [email-masked]
Date: Thu, 16 Feb 2023 13:51:52 +0000

Nik,

On Thu, Feb 16, 2023 at 01:36:33PM +0100, Nikolaus Klepp wrote:
> You can close the bugreport.

Thanks closing.

> avrdude 6.3 needs to be either run by root or you add this udev rule for normal users - the udev rule comming with the avrdude package is not sufficient:
> 
> #/etc/udev/rules.d/99-avarice.rules 
> # Atmel Corp. JTAG ICE mkII, etc ....
> SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="03eb", ENV{ID_MODEL_ID}=="2101", MODE="0666"
> SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="03eb", ENV{ID_MODEL_ID}=="2107", MODE="0666"
> SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="03eb", ENV{ID_MODEL_ID}=="2141", MODE="0666"

If you feel that is worth fixing in the packaging, please report to Debian.

Mark

Subject: Beowulf: avrdude does not work with Atmel-ICE any more
From: "Dr. Nikolaus Klepp" <[email-masked]>
To: [email-masked]
Date: Sat, 30 Nov 2019 14:35:33 +0100

Package: avrdude
Version: 6.3-20171130

avrdude cannot communicat with Atmel-ICE any more (Atmel-ICE firmware version 1.0 and 1.29, programmer workes on ascii). avrdude can kind-of communicate with the programmer the first time it is plugged in. But the second time it cannot communicate at all:

Example: connect via terminal to testboard fails.

$ avrdude -c atmelice_isp -p m328p  -t

avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_recv(): Unexpected response 0xb0
avrdude: stk500v2_jtag3_recv(): error in jtagmkII_recv()
avrdude: AVR device initialized and ready to accept instructions

Reading |                                                    | 0% 0.00savrdude: jtag3_edbg_send(): Unexpected response 0x81, 0x11
avrdude: jtag3_edbg_recv(): Unexpected response 0x80
avrdude: stk500v2_jtag3_recv(): error in jtagmkII_recv()
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_send(): Unexpected response 0x81, 0x11
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_recv(): Unexpected response 0xc0
avrdude: stk500v2_jtag3_recv(): error in jtagmkII_recv()
Reading | #################                                  | 33% 0.85savrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_send(): Unexpected response 0x81, 0x11
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_recv(): Unexpected response 0xb0
avrdude: stk500v2_jtag3_recv(): error in jtagmkII_recv()
Reading | ################################################## | 100% 1.45s

avrdude: Device signature = 0x303030
avrdude: Expected signature for ATmega328P is 1E 95 0F
         Double check chip, or use -F to override this check.
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_send(): Unexpected response 0xd0, 0x4c
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_recv(): Unexpected response 0xc0
avrdude: stk500v2_jtag3_recv(): error in jtagmkII_recv()
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_send(): Unexpected response 0x00, 0x02
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_recv(): Unexpected response 0xb0
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_send(): Unexpected response 0x60, 0x4d
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_recv(): Unexpected response 0xc0
avrdude: Short read, read only 0 out of 512 bytes
avrdude: jtag3_edbg_signoff(): failed to read from serial port (0)

avrdude done.  Thank you.

$ avrdude -c atmelice_isp -p m328p  -t
avrdude: usbhid_open(): No response from device
avrdude: jtag3_edbg_prepare(): failed to read from serial port (-1)
avrdude: failed to sync with the JTAGICE3 in ISP mode

avrdude done.  Thank you.

I do not know if this is a kernel problem, a libusb problem or a avrdude problem. Other programmers (usbasp-clone) work.

Nik

-- 
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...