avr-gcc-list
[Top][All Lists]
Advanced

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

Re: [avr-gcc-list] uisp and atmega128 problem


From: Jan Beutel
Subject: Re: [avr-gcc-list] uisp and atmega128 problem
Date: 05 Mar 2002 14:14:23 +0100

yaeh this locking unlocking thing has to do with the fuses and lock
bits. i have not yet dealt with that on linux... 

but it should work on avr studio.

here is my output from an stk500 ( i will check it using an stk300
later):

address@hidden test_hello]$ /usr/local/avr/bin/uisp -v=3
-dprog=stk500 -dserial=/dev/ttyS0 -dpart=ATmega128 --erase 
Vendor Code: 0x02
Part Family: 0x97
Part Number: 0x1e
Device similar to the ATmega103 is found.
Page Write Enabled, size=256
FLASH Write Delay (t_wd_flash): 61111 us
EEPROM Write Delay (t_wd_eeprom): 11111 us

address@hidden test_hello]$ /usr/local/avr/bin/uisp -v=3
-dprog=stk500 -dserial=/dev/ttyS0 -dpart=ATmega128 --upload
if=helloworld.ihex
Vendor Code: 0x02
Part Family: 0x97
Part Number: 0x1e
Device similar to the ATmega103 is found.
Page Write Enabled, size=256
FLASH Write Delay (t_wd_flash): 61111 us
EEPROM Write Delay (t_wd_eeprom): 11111 us
Uploading: flash
##########
(total 312 bytes transferred in 0.35 s (889 bytes/s)

address@hidden test_hello]$ /usr/local/avr/bin/uisp -v=3
-dprog=stk500 -dserial=/dev/ttyS0 -dpart=ATmega128 --verify
if=helloworld.ihex
Vendor Code: 0x02
Part Family: 0x97
Part Number: 0x1e
Device similar to the ATmega103 is found.
Page Write Enabled, size=256
FLASH Write Delay (t_wd_flash): 61111 us
EEPROM Write Delay (t_wd_eeprom): 11111 us
Verifying: flash
#


jb





On Tue, 2002-03-05 at 14:03, Torsten Hahn wrote:
> Am Dienstag, 5. März 2002 11:23 schrieben Sie:
> > yeah,
> >
> > my other post must have gotten lost...
> >
> >
> > you have to check your configure.in file for avr-libc-20020203:
> >
> >
> > address@hidden avr-libc-20020203]$ grep 128 configure.in
> >         AVR_CRT_MEGA='crtm161.o crtm163.o crtm32.o crtm128.o'
> >
> >
> > the line above was commented in the middle, so that the crtm128.0 file
> > didn't get built...
> >
> >
> > i still have a problem verifying flash on the 128l using uisp20020303.
> > any ideas on that?
> >
> 
> Nice, this works. But i also run into trouble using uisp20020303 and the 
> stk200 with the atmega128.
> 
> >>
> uisp -dprog=stk200 -dlpt=/dev/parport0 --erase
> Atmel AVR ATmega128 is found.
> Erasing device ...
> Reinitializing device
> Atmel AVR ATmega128 is found.
> 
> >>
> uisp -v=3 -dprog=stk200 -dlpt=/dev/parport0 --upload if=main.ihex
> 
> Reset inactive time (t_reset) 1000 us
> AVR Direct Parallel Access succeeded after 0 retries.
> Vendor Code: 0x00
> Part Family: 0x01
> Part Number: 0x02
> Cannot identify device because it is locked.
> Device similar to the ATmega103-old is found.
> Page Write Disabled
> FLASH Write Delay (t_wd_flash): 61111 us
> EEPROM Write Delay (t_wd_eeprom): 11111 us
> Uploading: flash
> #Device is locked.
> Address out of memory range.
> 
> I have no idea how to fix this.
> 
> CU,
> Torsten.
> -- 
> Torsten Hahn 
> TU Bergakademie Freiberg - Institut für Experimentelle Physik 
> Silbermannstraße 1, 09596 Freiberg
> mail: address@hidden
> phone: +49 3731 392670 
> avr-gcc-list at http://avr1.org
-- 
Jan Beutel                                 address@hidden
Computer Engineering and Networks Laboratory, ETZ G63
ETH Zurich                              +41 1 632 70 32 Phone
Gloriastrasse 35                          +41 1 632 10 35 Fax
CH 8092 Zurich/Switzerland  http://www.tik.ee.ethz.ch/~beutel

avr-gcc-list at http://avr1.org



reply via email to

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