[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[avrdude-dev] [bug #49740] Bad EEPROM write on Linux 64
From: |
Rada Berar |
Subject: |
[avrdude-dev] [bug #49740] Bad EEPROM write on Linux 64 |
Date: |
Wed, 30 Nov 2016 08:18:11 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/53.0.2785.143 Chrome/53.0.2785.143 Safari/537.36 |
URL:
<http://savannah.nongnu.org/bugs/?49740>
Summary: Bad EEPROM write on Linux 64
Project: AVR Downloader/UploaDEr
Submitted by: ujagaga
Submitted on: Wed 30 Nov 2016 08:18:06 AM GMT
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name: Rada Berar
Originator Email:
Open/Closed: Open
Release: 6.3
Discussion Lock: Any
Programmer hardware:
Device type: USBtiny
_______________________________________________________
Details:
I am using USBTiny programmer with AtTiny2313. When programming whether from
Eclipse or Therminal on XUbuntu 16.04, 64-bit, I get error:
....
avrdude: verifying ...
avrdude: 2042 bytes of flash verified
avrdude: reading input file "CDC.eep"
avrdude: input file CDC.eep auto detected as Intel Hex
avrdude: writing eeprom (128 bytes):
Writing | ################################################## | 100% 21.47s
avrdude: 128 bytes of eeprom written
avrdude: verifying eeprom memory against CDC.eep:
avrdude: load data eeprom data from input file CDC.eep:
avrdude: input file CDC.eep auto detected as Intel Hex
avrdude: input file CDC.eep contains 128 bytes
avrdude: reading on-chip eeprom data:
Reading | ################################################## | 100% 1.94s
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
0x00 != 0x43
avrdude: verification error; content mismatch
When I try to read fuses or device ID, Eclipse repports it can not understand
avrdude output.
By using the chip, I verified that the EEPROM was written all 0x01 except for
last three bytes which were fine.
I tried the same code and the same operations on Windows7 64-bit and
everything works fine. The EEPROM gets written OK, Eclipse reads avrdude
output OK.
I tried the latest avrdude6.3 and the result is the same.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?49740>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [avrdude-dev] [bug #49740] Bad EEPROM write on Linux 64,
Rada Berar <=