[avrdude-dev] [bug #51320] 0x00 written as 0xFF when byte count is less than 0x10

[Andrzej Pietrasiewicz]

Follow-up Comment #5, bug #51320 (project avrdude):


[comment #2 comment #2:]
> In further troubleshooting of my issue, I did examine the verbose output
during the writing and flashing of the blink-2560-mod hex file. Interestingly,
the bitbang_cmd() output shows that it did write "00" for the byte in
question. During the read, "FF" is being read. I do know that if I read the
firmware with AVR Studio it will also confirm the byte mismatch so even though
avrdude bitbang shows "00", it is either not writing it (and FF is a remnant
of the initial chip erase) or it is writing FF.
> 
> I have attached two more images showing the verbose output during this
scenario.
> 
> (file #41126, file #41127)

    _______________________________________________________

Reply to this item at:

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

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