[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re[2]: [avr-gcc-list] UISP and ATtiny15
From: |
Theodore A. Roth |
Subject: |
Re[2]: [avr-gcc-list] UISP and ATtiny15 |
Date: |
Mon, 19 Apr 2004 12:41:44 -0700 (PDT) |
On Mon, 19 Apr 2004, Alexander Popov wrote:
> Hello!
>
> Monday, April 19, 2004, 7:27:18 PM, Ted Roth wrote:
>
> TAR> Have you looked into this (from the data sheet)?
>
> TAR> When the RSTDISBL Fuse is programmed 0 , the External Reset function
> TAR> of pin PB5 is disabled(1). Default value is unprogrammed 1.
> TAR> Programming this fuse while in the Low-voltage Serial Programming mode
> TAR> will disable future In-System downloading attempts.
>
> Of course I know this and I avoid "One time-programming" of my
> processors. This is not the case, since '--dvoltage=3' fixes the
> problem and fiture programming is possible.
>
> Does someone have ATtiny15L to test if this is a common problem and if some
> fixing of UISP is required?
Here's what I'm seeing. Without the -dvoltage option, I always see this:
$ uisp -dprog=stk200 --erase
An error has occurred during the AVR initialization.
* Target status:
Vendor Code = 0xff, Part Family = 0xff, Part Number = 0xff
Probably the wiring is incorrect or target might be `damaged'.
With either -dvoltage=3 or =5, I get this after cycling the power (the
tiny15 in is a stk500 with vtg set to 3.0 V, but I connecting to the
device via a stk200):
$ uisp -dprog=stk200 -dvoltage=3 --erase
Atmel AVR ATtiny15 is found.
Erasing device ...
Reinitializing device
Atmel AVR ATtiny15 is found.
$ uisp -dprog=stk200 -dvoltage=3 --erase
Cannot identify device because it is locked.
Device similar to the ATmega103-old is found.
Erasing device ...
Reinitializing device
Cannot identify device because it is locked.
Device similar to the ATmega103-old is found.
And just for kicks, I tried the same thing with the stk500:
$ uisp -dprog=stk500 -dpart=attiny15 --erase
Firmware Version: 1.7
Atmel AVR ATtiny15 is found.
Firmware Version: 1.7
$ uisp -dprog=stk500 -dpart=attiny15 --erase
Firmware Version: 1.7
Cannot identify device because it is locked.
Device similar to the ATmega103-old is found.
Firmware Version: 1.7
This is reproducible and I have to cycle the power to "clear" the error
(what ever that means).
Again, just for kicks, I tried using avrdude:
$ avrdude -c stk200 -p t15 -e
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.03s
avrdude: Device signature = 0x1e9006
avrdude: erasing chip
avrdude done. Thank you.
$ avrdude -c stk200 -p t15 -e
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x000102
avrdude: current erase-rewrite cycle count is -1195788103 (if being tracked)
avrdude: erasing chip
avrdude done. Thank you.
Seems to give identical results. I'm wondering if the signals are
correct. When I get some more time, I'll try looking at this with a
scope, but I'm out of time for today...
I'm using uisp version 20040311 and avrdude 4.3.0cvs (don't know when I
did my last checkout though).
---
Ted Roth
PGP Key ID: 0x18F846E9
Jabber ID: address@hidden