Help! I broke it too!

[grumpygasbag]

Hi,

I wanted to try a new firmware on my Ice Tube so I built a parallel port programmer exactly as described here...

<http://arduino.cc/it/Hacking/ParallelProgrammer>

I followed the instructions on the tutorial page (except for using dapa instead of usbtiny).

It looks like I got AVRdude talking to the clock ok but after flashing the chip it gave an error and now my clock won't start (no beeps or anything). The relevant output from AVRdude is copied below. Can anyone help me out with this?

Thanks in advance.

C:\>avrdude -c dapa -P lpt1 -p m168 -U flash:w:iv.hex

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9406
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 "iv.hex"
avrdude: input file iv.hex auto detected as Intel Hex
avrdude: writing flash (11142 bytes):

Writing | ################################################## | 100% 4.45s

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

Reading | ################################################## | 100% 3.97s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
0x0c != 0xff
avrdude: verification error; content mismatch

avrdude: safemode: lfuse changed! Was e2, and is now ff
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: hfuse changed! Was c6, and is now ff
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: efuse changed! Was 1, and is now 7
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: Fuses OK

avrdude done. Thank you.

[grumpygasbag]

Well, I got it going again. Seems it's better to program the clock without the backup battery in place.

I still got an error during verification but at least now I have a clock that's working!

[Agent_24]

That DAPA programmer interface is very basic and not exactly reliable. Your verification error may be caused by that. Make sure you have a good shielded parallel cable too.

You may want to try something better like an STK200 compatible. I use this one myself and haven't had any problems with it so far.

[grumpygasbag]

Thanks Agent_24. The verification reliability does indeed seem to be a problem, and the very distinct lack of screening on my cable probably has something to do with it but I got wbp's firmware installed and working ok nevertheless. My clock is now auto-dimming perfectly and when I get the chance I'm going to see if I can get the GPS going too.

I think if I decide to do anything more than just a single firmware update, I will get a USB programmer.