MiniPOV lfuse, hfuse, efuse changed verification errors

[JohnChina]

I just finished making the MiniPOV from scratch..So, I do not have the preprogrammed ATTiny2313 chip. I am using a USB to Serial converter cable, on Windows XP. Where do I start to program the chip?
Sorry, I am sure that this is already stated somewhere, but I cannot find specific steps. This is my first micro-controller project.
Thanks,
John

Update: I used the following command, which ... finally worked... once.

C:\WinAVR-20100110\bin>avrdude -p attiny2313 -P com3 -c dasa -U flash:w:minipov.
hex

At the end of the Read cycle I received 3 Veriry errors :
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x005a
0xcf != 0x2d
avrdude: verification error; content mismatch

avrdude: safemode: lfuse changed! Was 64, and is now 0
Would you like this fuse to be changed back? [y/n] y
avrdude: and COULD NOT be changed
avrdude: safemode: hfuse changed! Was df, and is now 0
Would you like this fuse to be changed back? [y/n] y
avrdude: and COULD NOT be changed
avrdude: safemode: efuse changed! Was ff, and is now 0
Would you like this fuse to be changed back? [y/n] y
avrdude: and COULD NOT be changed
avrdude: safemode: Fuses not recovered, sorry

The first time I selected N for all three. This didn't work so, I tried again and used Y. That time it worked. Now when I am trying to program another ATTiny2313 chip with one of the other hex files supplied (mypov.hex, eyebeam.hex) choosing Y or N to these error messages do not work. After I disconnect the serial cable, nothing happens.

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 1.20s

avrdude: Device signature = 0x1e910a
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed

To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "minipov.hex"
avrdude: input file minipov.hex auto detected as Intel Hex
avrdude: writing flash (336 bytes):

Writing | ################################################## | 100% 144.26s

avrdude: 336 bytes of flash written
avrdude: verifying flash memory against minipov.hex:
avrdude: load data flash data from input file minipov.hex:
avrdude: input file minipov.hex auto detected as Intel Hex
avrdude: input file minipov.hex contains 336 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 137.73s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x005a
0xcf != 0x2d
avrdude: verification error; content mismatch

avrdude: safemode: lfuse changed! Was 64, and is now 0
Would you like this fuse to be changed back? [y/n] y
avrdude: and COULD NOT be changed
avrdude: safemode: hfuse changed! Was df, and is now 0
Would you like this fuse to be changed back? [y/n] y
avrdude: and COULD NOT be changed
avrdude: safemode: efuse changed! Was ff, and is now 0
Would you like this fuse to be changed back? [y/n] y
avrdude: and COULD NOT be changed
avrdude: safemode: Fuses not recovered, sorry

avrdude done. Thank you.

[JohnChina]

Update:
I am now using the Make program-minipov command to program the MiniPOV. I have 4 chips and have been able to program 2 of them successfully. However, the process involved repeated attempts (a dozen or more). I could never get any of the other hex files to work, only minipov. I have been answering No to the lfuse, hfuse, and efuse has changed question, though sometimes I try answering Yes too.

I would appreciate it if someone could point me in the right direction.
Thanks!

DIY - FIRST: Are you using a Minipov3 from a kit or from DIY?
WinXP and Win7 - SECOND: What OS and computer are you using?
USB adapter - THIRD: Are you using a USB adapter or a serial port?
No - FOURTH: Did the minipov light up at all when you turned it on?
See previous messages - FIFTH: What -specifically- isn't working?
SIXTH: Post screenshots (NOT copy&paste) of what is happening
SEVENTH: Post clear, in-focus, not-blurry, easy to see photos of the top and bottom of the kit. If the photos are blurry, unfocused, and difficult to see they will only make it harder to debug what is going on

If you post all of this information the first time, it will save many days of you waiting for me to ask you!

[adafruit]

unfortunately as you have seen, its very hard to debug DIY versions, so we do not offer support for them. the site has all information on minipov3 design

[JohnChina]

Thanks for your reply. I fully understand that I need to debug my own DIY. I was only asking to be directed in the right direction (url), since this is my first micro-controller project.

Your designs show two different values for the zeners, actually 3 if you take the board layout into consideration, which shows 3v ones. In the parts list, it states 5.1 volt zeners, but I have seen other places where it states 5.6 volt zeners. Is this, or could this make a difference? From my limited understanding, this could be the cause of the problem. since the zeners are used to clamp the programming input from the serial interface...and this is where my device is having the problem. It works fine once programmed. BTW, I am using 5.1v zeners

I will continue to search on my own for what the lfuse, hfuse, and efuse is and how it should be configured. If anyone has an url to direct me to I would appreciate it.

[mtbf0]

have a look at the make file. hfuse and efuse are left in their default states. lfuse can be set properly by using

Code: Select all

make burn-fuse