[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[avrdude-dev] Device signture not observed
From: |
idefixx |
Subject: |
[avrdude-dev] Device signture not observed |
Date: |
Wed, 26 Nov 2003 10:31:00 +1100 |
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
40 00 00 xx
48 00 00 xx
40 00 01 xx
48 00 01 xx
40 00 02 xx
.. .. .. ..
which stand for "Write Program Memory (High/Low)" for AT90S8535 and "Load
Program Memory Page (High/Low)" for ATmega163.
AVRdude doesn't show any error message during "Writing" stage. After doing the
read out for verification it shows, that verification failed at byte 0x0000.
The read out is done with
20 00 00 xx
28 00 00 xx
20 00 01 xx
28 00 01 xx
20 00 02 xx
.. .. .. ..
which stand for "Read Program Memory (High/Low)" for both ATmega163 and
AT90S8535.
This behaviour was tested and found on OS Windows XP and 98.
But anyway, after reading the signature AVRdude should actually stop and
complain, that an incorrect device was connected or the -p option was set
incorrect.
/idefixx
- [avrdude-dev] Device signture not observed,
idefixx <=