Devuan bug report logs - #364
Beowulf: avrdude does not work with Atmel-ICE any more

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: Mark Hindley <mark@hindley.org.uk>
Subject: bug#364: marked as done (Beowulf: avrdude does not work with
 Atmel-ICE any more)
Message-ID: <handler.364.D364.16765555553541.ackdone@bugs.devuan.org>
References: <Y+40+IOw0Oa2UeP1@hindley.org.uk>
 <201911301435.33199.dr.klepp@gmx.at>
X-Devuan-PR-Message: closed 364
X-Devuan-PR-Package: avrdude
X-Devuan-PR-Keywords: debian
Reply-To: 364@bugs.devuan.org
Date: Thu, 16 Feb 2023 13:54:01 +0000
Content-Type: multipart/mixed; boundary="----------=_1676555641-3562-0"

[Message part 1 (text/plain, inline)]

Your message dated Thu, 16 Feb 2023 13:51:52 +0000
with message-id <Y+40+IOw0Oa2UeP1@hindley.org.uk>
and subject line Re: bug#364: Beowulf: avrdude does not work with Atmel-ICE any more
has caused the Devuan bug report #364,
regarding Beowulf: avrdude does not work with Atmel-ICE any more
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.devuan.org
immediately.)


-- 
364: https://bugs.devuan.org/cgi/bugreport.cgi?bug=364
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: "Dr. Nikolaus Klepp" <dr.klepp@gmx.at>

To: submit@bugs.devuan.org

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

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 ...

[Message part 3 (message/rfc822, inline)]

From: Mark Hindley <mark@hindley.org.uk>

To: Nikolaus Klepp <office@klepp.biz>

Cc: 364-done@bugs.devuan.org

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

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

Send a report that this bug log contains spam.