I'm testing here, and found another problem. (still using Serial Single Sided with Atmega8, parallel port cable)

Using DOS Prompt under WinXP, burnpara.bat from 0007 version works fine: the pin13 led turns off before burning bootloader, and reset button blinks this led.burnpara from 0010 version doesn't work: the pin13 led remains dim bright before bootloader, and reset button doesn't work.

I saw differences between these files. On 0010 there isn't a command before uisp: -v=4. the line cd.. doesn't work, since the burnpara file is located two levels over root. And the last line cd bootloader doesn't work too, because the directory name is bootloaderS. I made the changes on 0010, and didn't work.I copyied 0010 on 0007 directory and vice-versa and they run but don't work. The same with uisp file. Can anyone explain this? Can this be related with 0010 bootloader not working with SSS, Mellis?

Adlison: the burnpara.bat file is a bit outdated, so I'm not surprised it doesn't work. Have you installed giveio (linked to from the bottom of the parallel programmer page)? You might need to get permission to access the parallel port (although I would think that uisp would need it too). Also, in the programmers.txt file in ARDUINO/hardware has a parallel.delay key. Try increasing the value from 800 (maybe to 1600 or more).

Giveio is installed, and XP_stop_polling.reg too. Under 0007 directory, burnpara always works. Under 0010, it doesn't.

I changed parallel.delay to 1600, 16000 and 100000. Not working yet.

Independant of parallel.delay changes, something changed while trying. I didn't change anything, but now 0010 bootloader doesn't erase previous bootload done under 0007. It is sending the same error message while bootloading, but just keeps previous bootload and sketches loaded (blink test).

If you set upload.verbose to true in the preferences file (apologies for giving such opaque instructions before), does it display that commands that are used to burn the bootloader (in Arduino 0007 and 0010)? If so, give it a try from the command line. That way, if it doesn't work, you can ask the avrdude folks why uisp can burn a bootloader with your setup and avrdude can't. They might have more of an idea of what's different between the way the two programs work. The mailing list is here - or post here and I can post to the avrdude list.

it doesn't work. I think because it finds the wrong value for device signature of atmega8 (expects 1e9307, but always changing each time you try bootloading - 0x000100, 0x000102,...)

I added -F instruction in this command line and it worked fine.

I saw before in the forum that there is a second command line, like this:avrdude -avrdude.conf Or the results are the same?-v -v -v -v -pm8 -cdapa -i800 -e -Uflash:w:d:\arduino-0010\hardware\bootloaders\atmega8\ATmegaBOOT.hex:i -Ulock:w:0x3F:mI couldn't see it on arduino 0010 messages, because the first command line didn't work, so the second command line is not shown.

Like the first, it nedded the -F instruction to works. But it tooks 10 minutes!

I don't know if is this related (since both works with avrdude), but I tested to Upload sketch without bootloader with Arduino 0010 on Arduino SSS Board and it didn't work. But works fine and fast(!) at dos prompt, with changes on command line (removing [glow]""[/glow] caracters of command line).http://www.arduino.cc/en/Hacking/Programmer

The bootloader should be the same whether you burn it with Arduino 0007 or Arduino 0010.

It's strange that it takes 10 minutes to burn the bootloader with avrdude. Did it work? What happens if you remove -i800 from the command line? Or lower the value from 800 to something smaller?

Right now, you can't specify explicit command line parameters to the Arduino IDE. I'll have to investigate why the device signature is wrong with the parallel programmer and maybe add the -F in that case.

As for the 0xff vs. 0x3f: the high two lock bits aren't used anyway, so those two values are effectively equivalent. avrdude gets confused if you give it 0xff, since when it reads the bits back, it treats the unused ones as 0 and complains that they weren't set properly (since it tried to write 0xff and read back 0x3f).

When you say that uploading without a bootloader works fine from the command prompt, what do you mean? Are you uploading a normal sketch to a board that has a chip with a bootloader on it? Or are you uploading a sketch to a chip using the parallel programmer? The latter isn't supported in Arduino 0010, but it will be in Arduino 0011.

Yes, it works, but only in DOS Prompt. Like I said, not only me, but here http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1192727600 too. I removed the -i800 and it tooks only 40-50 seconds.I found another problem here, still using DOS, AVRdude under 0010 directory and bootloading.When the command uses -Ulock:w:0x3F:m (avrdude -Cavrdude.conf -v -v -v -v -pm8 -cdapa -Ulock:w:0x3F:m -Uhfuse:w:0xca:m -Ulfuse:w:0xdf:m -F -b115200), sometimes it returns an error that breaks execution, asking:

And a curious thing:I've got an Atmega with bootload and blink sketch uploaded.If I burn bootload again with 0007 (on DOS or IDE): the IC gets clean, blinking only with reset.If I burn bootload again with 0010 (on DOS): the IC keeps the blink sketch, blinking each second, even with uisp --erase before.

If you remove the -F from the avrdude command line, can you still burn the bootloader? If not, I should add the -F flag when using a parallel port programmer from the IDE, and that should fix the problem. I'll probably also lower the default delay, since 10 minutes is a ridiculous.

The java.io.IOException: CreateProcess: (error=193) message that you get when trying to upload a sketch is something to do with avrdude not being a valid executable. Is avrdude in c:\ ? Is it really called avrdude, or is it avrdude.exe? Can you try installing the software in a different location?

The difference in blinking between the bootloader included with 0007 and the one included with 0010 is expected. In 0007, the bootloader has a 8 second or so delay, so it takes that long between blinks. In 0010, because of the auto-reset, the timeout is much shorter (less than a second), so the LED blinks - that's just the bootloader timing out and restarting (because there's no other sketch on the board).

If I remove -F it doesn't work. I don't know why, avrdude can't find the correct device signature. (0007 finds it, so the correct number seems to be there). Removing the delay makes it work fine. Is it (the delay) necessary?

In fact, Avrdude is not at C:\. It is at another place, under many directories. But I changed it to C:\ to test if the problem was long directory names. But didn't work. I just renamed it all (the command lines), removing directories at forum to reduce lines and makes it easy to understand. But gonna try at other directories too.

You misunderstood the blink question. The 0010 bootload doesn't erase the previous uploaded sketch (blink led sketch) - even with "uisp --erase" or "avrdude -e". But 0007 bootload erases all.

Okay, it sounds like in Arduino 0011 I should add a -F and lower the delay for parallel port programmers. The delay was in there because David Fowler from ucHobby reported that he needed it to get the bootloader burning to happen reliably, but it may have just been his setup.

Can you post the actual error message you get when trying to upload a sketch with Arduino 0010 (with the real paths in place)? The error that you're getting implies that Windows can't find avrdude, so the path is an important piece in tracking down the problem. Did you move avrdude from where it was relative to the Arduino directory?

Are you sure that the burning the bootloader from 0010 doesn't remove the previous sketch? Have you tried it with different sketches on the board before hand? Does the bootloader still work (i.e. allow you to upload new sketches) even if it didn't erase the previous sketch?

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)

Sometimes, if I run avrdude under DOS, I can upload sketch. Sometimes don't.When it doesn't runs, the message is:

about the sketch not uploading on DOS sometimes, was my fault. I didn't press reset.

And the uploading sketches on IDE was my fault too. I removed the "arduino-0010-win" directorykeeping only "arduino-0010". That was causing the error 193.I didn't thought this could be a problem because I removed the 0007 directory too, and it is still working. But now I understand there's a difference using uisp or avrdude (java).

So the only remaining problem is bootloading with IDE(perhaps including -F and removing -i can solve it).