avrdude-dev
[Top][All Lists]
Advanced

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

Re: [avrdude-dev] Device signture not observed


From: Brian Dean
Subject: Re: [avrdude-dev] Device signture not observed
Date: Tue, 25 Nov 2003 19:16:23 -0500
User-agent: Mutt/1.5.5.1i

On Wed, Nov 26, 2003 at 10:31:00AM +1100, idefixx wrote:

> By the way, I found another bug: If I tell AVRdude to program an
> ATmega163, but use an AT90S8535 as a hardware to prgram, AVRdude
> doesn't complain about it. It correctly reads the signature bytes of
> the AT90S8535 (0x1E9303) and even though the option was "-p m163"
> (signature 0x1E9402), AVRdude starts programming the flash
> performing the commands

Actually AVRDUDE does not check the signature bytes at all, other than
to check that they are reasonable and it looks like a chip is on the
other end.  It's up to the person running AVRDUDE to correctly
identify the chip on the command line.

While this feature could certainly be added, it's never been a high
priority and, for me at least, I would consider this to be in the
"bells and whistles" category.  If it was added, then -p option would
become redundent or at least maybe made optional.

-Brian




reply via email to

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