[avrdude-dev] [bug #34281] Wrong Chip ID#

[Brian Stott]

Follow-up Comment #4, bug #34281 (project avrdude):

- Solved -

Solution: 
The offending/difficult line is in 'avrdude.conf'.

There is a callout in the specific chip information block: "signature        =
XXXXXXXX;" I changed this signature to match the physical chip ID. This error
is gone and avrdude now returns the following statement.: "avrdude.exe: Device
signature = 0x1e9514"

Request: Adjust avrdude source to accept multiple IDs for a single device
separated by comma ',' Or make the signature generic and/or optional. 

Thank you for your responses.

Since I don't use CLI tools anymore (10yrs+) or program the solution was a
little elusive. 

Reply to suggestions -

ISP Clock is irrelevant to chip ID. Right? I'm not sure. I'd used various
ranges on -B and -b from 1-4800. My chip is wired with external 16Mhz
crystal.

I found that the programming device was of no matter. I'd used several with
the same result. I'd also seen in other forums the same results of others
using programmers other than the ones I tested. My Devices - USBasp, Arduino
Duemilanove as AVR programmer, [Two FT232RL]FTDI bitbang method, FTDI friend
clone (serial programmer).

I'd also looked at the datasheet. Kinda irrelevant too. Several events are
working here. (1) avrdude is distributed with configs and sources. (2) Mfg.
Documentation is distributed. (3) Chips are ID'd. --- They appear to not
always be in sync?

Effect on: All avrdude - the problem propagates from the original to the
variants.

Avrdude varieties used: avrdude (direct download), Arduino (included), WinAVR,
and avrdude-serjtag. All gave same ID error. 

Invoking switch '-F' had no effect. I had the '-F' option invoked. 





    _______________________________________________________

Reply to this item at:

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

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