avrdude-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #58251] only odd bytes are programmed / programming only works in t


From: Lukas Raschendorfer
Subject: [bug #58251] only odd bytes are programmed / programming only works in terminal mode.
Date: Sun, 26 Apr 2020 16:27:32 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/78.0.3904.108 Chrome/78.0.3904.108 Safari/537.36

URL:
  <https://savannah.nongnu.org/bugs/?58251>

                 Summary: only odd bytes are programmed / programming only
works in terminal mode.
                 Project: AVR Downloader/UploaDEr
            Submitted by: funkyluke
            Submitted on: Sun 26 Apr 2020 08:27:30 PM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: funkyluke
        Originator Email: 
             Open/Closed: Open
                 Release: 6.3
         Discussion Lock: Any
     Programmer hardware: avrisp2
             Device type: 8535

    _______________________________________________________

Details:

EEP Programming works:

avrdude -p8535 -cavrisp2 -Pusb -U eeprom:w:eep.hex --> verifies OK

Flash Programming:

root@luke-hp:~# cat short.hex 
:200000000102030405060708091011121314151617181920212223242526272829303132E6
:00000001FF

root@luke-hp:~# avrdude -p8535 -cavrisp2 -Pusb -q -q -U flash:w:short.hex 
avrdude: verification error, first mismatch at byte 0x0001
         0xff != 0x02

root@luke-hp:~# cat short-readback.hex 
:2000000001FF03FF05FF07FF09FF11FF13FF15FF17FF19FF21FF23FF25FF27FF29FF31FF84
:00000001F

 --> Note that every other (even) byte is 0xFF (not programmed)
But:

root@luke-hp:~# avrdude -p8535 -cavrisp2 -Pusb -t

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.11s

avrdude: Device signature = 0x1e9303 (probably 8535)
avrdude> e
>>> e 
avrdude: erasing chip
avrdude> write flash 0x00 0x11 0x22 0x33 0x44 0x55 0x66 0x77 0x88
>>> write flash 0x00 0x11 0x22 0x33 0x44 0x55 0x66 0x77 0x88 

avrdude> dump flash 0x00 32
>>> dump flash 0x00 32 
0000  11 22 33 44 55 66 77 88  ff ff ff ff ff ff ff ff  |."3DUfw.........|
0010  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|

--> so writing in general seems to work, just not using -U and a hex file ?!

Thanks for looking into this!




    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?58251>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]