[Top][All Lists]

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

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

From: Andrzej Pietrasiewicz
Subject: [avrdude-dev] [bug #51320] 0x00 written as 0xFF when byte count is less than 0x10
Date: Sun, 28 Jul 2019 11:37:04 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

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
> (file #41126, file #41127)


Reply to this item at:


  Message sent via Savannah

reply via email to

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