Assembled the clock, and daliclock came up working fine. I soldered the header for the usb port in, which makes assembling the case "interesting", but got it done...
Then tried to put in the seven segment clock (an aside here: where, exactly, are the *.hex files? Whichever clock you choose, you seem to end up in the same place?) and got:
C:\>avrdude -c arduino -P COM8 -p m328p -b 57600 -U flash:w:monochron.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x1e950f
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 "monochron.hex"
avrdude: input file monochron.hex auto detected as raw binary
avrdude: writing flash (32768 bytes):
Writing | ################################################## | 100% 16.12s
avrdude: 32768 bytes of flash written
avrdude: verifying flash memory against monochron.hex:
avrdude: load data flash data from input file monochron.hex:
avrdude: input file monochron.hex auto detected as raw binary
avrdude: input file monochron.hex contains 32768 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 13.84s
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x7800
0x65 != 0x0c
avrdude: verification error; content mismatch
avrdude: safemode: Fuses OK
avrdude done. Thank you.
Went to the daliclock area (I think) and tried that:
C:\>avrdude -c arduino -P COM8 -p m328p -b 57600 -U flash:w:monochrondali.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x1e950f
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 "monochrondali.hex"
avrdude: input file monochrondali.hex auto detected as raw binary
avrdude: writing flash (32768 bytes):
Writing | ################################################## | 100% 16.12s
avrdude: 32768 bytes of flash written
avrdude: verifying flash memory against monochrondali.hex:
avrdude: load data flash data from input file monochrondali.hex:
avrdude: input file monochrondali.hex auto detected as raw binary
avrdude: input file monochrondali.hex contains 32768 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 13.81s
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x7800
0x23 != 0x0c
avrdude: verification error; content mismatch
avrdude: safemode: Fuses OK
avrdude done. Thank you.
So, what should I be looking for?
Thanks all in advance.
Bad firmware load on what was a working monochron
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
-
- Posts: 5
- Joined: Sat Feb 05, 2011 11:56 am
-
- Posts: 12151
- Joined: Thu Apr 06, 2006 4:21 pm
Re: Bad firmware load on what was a working monochron
does it work?
-
- Posts: 5
- Joined: Sat Feb 05, 2011 11:56 am
Re: Bad firmware load on what was a working monochron
It displays a random pattern on the lcd, and flashes. It doesn't work.
-
- Posts: 5
- Joined: Sat Feb 05, 2011 11:56 am
Re: Bad firmware load on what was a working monochron
Well, duh. The 32768 byte file I was downloading wasn't the 7-segment, or the dali. I took monochron.hex from firmware on the page you get to when you click on Code at GitHub on the http://www.ladyada.net/make/monochron/newclock.html page...but that gets you to a page where, if you select "firmware" you don't get the 7-segment code, but something else... I had ignored the "Download" button.
Sorry for the wasted bandwidth, and your time.
Sorry for the wasted bandwidth, and your time.
Please be positive and constructive with your questions and comments.