[bug #49740] Bad EEPROM write on Linux 64

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[bug #49740] Bad EEPROM write on Linux 64

Matthijs Kooijman-2
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 mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

[bug #49740] Bad EEPROM write on Linux 64

Matthijs Kooijman-2
Follow-up Comment #1, bug #49740 (project avrdude):

> I tried the same code and the same operations on Windows7
> 64-bit and everything works fine.

Same AVRDUDE version, too?


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?49740>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

[bug #49740] Bad EEPROM write on Linux 64

Matthijs Kooijman-2
Follow-up Comment #2, bug #49740 (project avrdude):

Probably not. I installed WinAvr a couple of days ago but it seems to be old.
I do not know how to check version. I will try to find the version tomorrow.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?49740>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

[bug #49740] Bad EEPROM write on Linux 64

Matthijs Kooijman-2
Follow-up Comment #3, bug #49740 (project avrdude):

Windows AVRDUDE version is 5.10


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?49740>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

[bug #49740] Bad EEPROM write on Linux 64

Matthijs Kooijman-2
Follow-up Comment #4, bug #49740 (project avrdude):

I uninstalled the latest AVRDUDE and installed AVRDUDE version 5.11. This one
seems to work well.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?49740>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

[bug #49740] Bad EEPROM write on Linux 64

Matthijs Kooijman-2
Follow-up Comment #5, bug #49740 (project avrdude):

That's what I excpected.

So it's an issue with recent AVRDUDE versions.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?49740>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev