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

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

RE: [avr-gcc-list] uisp - atmega16 "dead" after setting high/low fuses


From: Boyapati, Anitha
Subject: RE: [avr-gcc-list] uisp - atmega16 "dead" after setting high/low fuses
Date: Sat, 26 Feb 2011 20:51:24 +0800

Hi Rieker,

I think 'AVR Freaks' might be a better place to know more about device 
troubleshooting. 

HTH
Anitha

>-----Original Message-----
>From: address@hidden
>[mailto:address@hidden On
>Behalf Of Rieker Flaik
>Sent: Saturday, February 26, 2011 1:33 PM
>To: address@hidden
>Subject: [avr-gcc-list] uisp - atmega16 "dead" after setting high/low fuses
>
>Hi,
>
> I did a ATMega16-Hobby-Project a while ago. Today I changed the source
>code, compiled it and tried to upload the hex-file into the chip. But it
>wasn't possible because uisp couldn't even detect the chip-model. "Maybe
>I falsely set some Lock-Bits a while ago", I thought and took a second
>ATMega16 from my cubicle of electronic equipment and tested it with:
>
>uisp -dlpt=/dev/parport0 --rd_fuses -dprog=dapa
>
>  I remember that it showed the correct chip-model and the default
>values for all fuses.
>
>  In my design I use a external crystal. So I tried to set the
>fuse-bytes accordingly:
>
>HIGH_BYTE:
>  7 OCDEN   "On Chip Debug"        1
>  6 JTAGEN  "JTAG"                 1
>  5 SPIEN   "Serial Programming"   0
>  4 CKOPT   "Oscillator Option"    0
>  3 EESAVE  "EEPROM is preserved"  1
>  2 BOOTSZ1 "Boot Size"            0
>  1 BOOTSZ0 "Boot Size"            0
>  0 BOOTRST "Reset Vector"         1
>
>        0b11001001==0xC9
>
>LOW_BYTE:
>  7 BODLEVEL "Brown-out"           1
>  6 BODEN    "Brown-out enabled"   1
>  5 SUT1     "Start-up Time"       1
>  4 SUT0     "Start-up time"       1
>  3 CKSEL3   "Clock"               1
>  2 CKSEL2   "Clock"               1
>  1 CKSEL1   "Clock"               1
>  0 CKSEL0   "Clock"               1
>
>        0b11111111==0xFF
>
>did a:
>
>uisp -dlpt=/dev/parport0 --wr_fuse_h=0xC9 --wr_fuse_l=0xFF -dprog=dapa
>
> and the device was gone :-(
>
>Even a "uisp -dlpt=/dev/parport0 --rd_fuses -dprog=dapa" doesn't work.
>
>What could be the problem?
>
>Thanks,
> rieker
>
>
>
>_______________________________________________
>AVR-GCC-list mailing list
>address@hidden
>http://lists.nongnu.org/mailman/listinfo/avr-gcc-list



reply via email to

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