Forum Replies Created
Two initial questions:1. Have you reprogrammed the Peggy at all?2. Have you selected the “P2” or the “Ser” configuration option?
Yes, that would be the problem right there. That’s actually a different chip, with a different signature, from the one supported by Arduino.You can work around this by changing the expected signature in your avrdude.conf file, following the instructions from this thread: http://www2.evilmadscientist.com/forum/viewtopic.php?showtopic=4997
Exactly what chip are you using? Are you certain that it’s a ‘328P, not just a ‘328?The verbose option, as I said, is in the Arduino preferences.
And, to be clear, you are *not* reporting nearly enough information here to figure out what the problem is. I can give you a list of things to check (like, for example, that your target chip actually is an an ATmega328P), but until you can see the actual error, it’s pretty hard to guess what might be wrong.
Do you have the verbose option turned on?
You *do not* want to override the check. This is a *symptom* of something else wrong, not the cause of the problem.
There is supposed to be a line above that one, saying what it actually read– the “expected signature” line always follows that if the value is wrong. It should be something like “avrdude: Device signature = 0x1e9514 .You may need to just scroll up a line to see it.If you’re doing this from within the Arduino IDE, you may need to turn on verbose mode in the preferences.
Can you say what signature you *are* getting?
Hi David,It would be helpful if you would ask for assistance *before* getting to the point that you conclude that you can’t make it work or that you feel that you need to tell us repeatedly that your son is disappointed. We can make it work, but it’s a lot easier (for everyone) if you ask for help before you get frustrated.The “Unexpected char: “i”” error *may* indicate that you tried to open up the Arduino program that you generated with Processing. Is this possible? If so, open the file with Arduino and try again. Until very recently, all Arduino files were saved with file extension “.pde” –this has been a source of confusion, especially now that “.ino” is recommended.Regardless of the extension type, Arduino will *always* insist that a new file should go in a like-named folder. Allow it to assist you with this process.The “Peggy2 does not name a type” error means that you do not have the Peggy2 library for Arduino installed. You will need to install this before any Peggy program will work, whether or not it was generated with PeggyDraw 2.* Download the Peggy2 library for Arduino, here:* Install the Peggy 2 library: Unzip it, and place the resulting file in your Arduino libraries folder.* If you have trouble locating your libraries folder, look for the “sketchbook” folder location in Arduino preferences. This is a folder, usually named “Arduino,” somewhere on your computer system. If there is not a folder named “libraries” (all lower case) in you sketchbook folder, make one, and put the library there.* Restart the Arduino program after having done so.Please let me know how it goes. If you do come across additional difficulty, we’re here to help.-Windell
The Bulbdial clock has a number of brightness options, including a “sleep” mode where the LEDs are fully off– usually managed by the ‘z’ button. You should be able to add a feature that turns off the LEDs at night without too much trouble.July 20, 2012 at 12:09 am in reply to: want to charge supercapacitor and the battery by the solar panel #20758
>if your cap is not big enough get a bigger one ;)Yes, that’s the right answer.
Then the crystal caps are indeed the likely culprit– the crystal may simply not run if the caps are that far off from spec. It’s likely worse than you think, because a breadboard adds quite a bit of stray capacitance, too.
I’m not entirely clear on what you’re trying to do, and what’s not working here.– Is the AVR working correctly when it is in the Diavolino, or in the breadboard, or both?– What’s not working, or otherwise leading you to suspect a clock issue?
Likely not hopeless; the FTDI chips are pretty well supported, and generally can be made to work one way or another. (I do not have the same level of confidence with respect to the leostick.)See if you can map your adapter onto the “standard” FTDI cable pinout, to make sure of which pin is supposed to go where, and make sure that your environment is set up correctly: right port and board type and all that.