Hi, Can you tell us your full command line ? Does it always return the same bad signature ? What does give the same command with -v option ?
D. Le dim. 6 juin 2021 à 17:09, <[email protected]> a écrit : > Hi! > > The chip surely was reprogrammed (it contains some marking over the > original). I’ve tried to read/write other chips with my programmer (STK200 > h/w + AVRDUDE) and everything was OK. So: > > > > - I’m sure that my connections are OK > - Tested board have an XTALL > - I’m sure that signature IS NOT read only 😊 > > > > If there are some ideas please reply. > > > > Alex > > > > *From:* Martin Stejskal <[email protected]> > *Sent:* Wednesday, June 2, 2021 11:25 AM > *To:* [email protected] > *Cc:* [email protected] > *Subject:* Re: MC with reflashed signature > > > > Hi, the signature bytes are in read only memory. If programmer read them > incorrectly, there is HW related issue. > > > > Double check wires and connectors. They should be tight connection (loose > cables/connectors = problems). > > > > Also you might changed oscillator settings, so actually your target device > does not have proper clock source. If so, you can use any signal generator > and inject external clock (around 1 MHz or more) to XTAL1 pin. That usually > works. > > > > Regards > > Martin > > > > On Tue, Jun 1, 2021, 17:37 <[email protected]> wrote: > > Hello, folks! Need some help! > > > > Is it possible by the means of AVERDUDE to read the complete image of the > MC (FLASH, EPROM, fuses, signatures, etc.) into one file that could be > flashed into a new chip? (including signature bytes) The main problem is > that signature bytes of the original chip were changed and it is necessary > to use -F option. > > Does AVERDUDE know how to alter signature bytes? If not, how to do it? > > > > So far I have unsatisfactory result: > > program enable instruction not defined for part "ATxmega32D4" > > avrdude.exe: AVR device not responding > > avrdude.exe: initialization failed, rc = -1 > > avrdude.exe: AVR device initialized and ready to accept instructions > > avrdude.exe: Device signature = 0x987ba0 > > avrdude.exe: Expected signature for ATxmega32D4 is 1E 95 42 > > avrdude.exe done. Thank you. > > > > So the program understands that there was a command to ignore the > signature mismatch, but still does not go further. > > It would be nice to have the correct command syntax (including where to > insert "-F") from the experts.. > > > > Thanks, Alex > > > >
