Hi, I'm having some trouble programming my ATMega328, it worked fine with the setup in which it is currently in, but then it had some problems, which if I recall correctly came after I tried to set the fuses. The microchip is hooked up to an LCD screen and the code tells it to first clear the screen (fill a white rectangle) then write text. That should occur within a few milliseconds. I'm watching the text come in pixel by pixel now, over 5 minutes after plugging in the power to the micro... How is it possible that the chip is running SO SLOWLY?! I would read back the fuses to you, but I get an initialization error every time I try to program... It's hooked up to an external 8MHz oscillator... Is there any way to salvage the chip? If I can't seem to program it...?
Thanks very much.
(Typically I would just order some more chips, but I'm in college now and the mail takes WEEKS to get! It's TERRIBLE! I may even get a PO box because it's sooo bad)
ATMega chip running... Too slowly to program? Maybe?
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
-
- Posts: 1119
- Joined: Wed Jun 13, 2007 9:17 am
-
- Posts: 12151
- Joined: Thu Apr 06, 2006 4:21 pm
Re: ATMega chip running... Too slowly to program? Maybe?
you might have turned on the 32khz oscillator?
-
- Posts: 1119
- Joined: Wed Jun 13, 2007 9:17 am
Re: ATMega chip running... Too slowly to program? Maybe?
Hmm, it's possible, what would you recommend to fix this?
Is there anything I can do with just a USBTiny or would I need something more?
Is there anything I can do with just a USBTiny or would I need something more?
-
- Posts: 12151
- Joined: Thu Apr 06, 2006 4:21 pm
-
- Posts: 1119
- Joined: Wed Jun 13, 2007 9:17 am
Re: ATMega chip running... Too slowly to program? Maybe?
Oh, thank you... Well, I tried it out and got this error:
But I went ahead with the instructions anyway, got no more errors until I tried to program again, to which I got the standard initialization failed...
Edit:
Turns out that the chip wasn't ever erased during that process, it's still got it's slow-running code on it.
Code: Select all
avrdude -p m328p -c usbtiny -P usb -tuF
avrdude: initialization failed, rc=-1
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
avrdude: Expected signature for ATMEGA328P is 1E 95 0F
Edit:
Turns out that the chip wasn't ever erased during that process, it's still got it's slow-running code on it.
Please be positive and constructive with your questions and comments.