Does optiLoader report success when you burn the bootloader again?
I am trying to figure out how I can use the sesrial monitor just through usb.
Did you use the 16 MHZ crystal & caps
OptiLoader Bootstrap programmer.2011 by Bill Westfield (WestfW)Target power on! ...Starting Program Mode [OK]Reading signature:950FSearching for image... Found "optiboot_atmega328.hex" for atmega328P Start address at 7E00 Total bytes read: 502Setting fuses for programming Lock: 3F FFE000 Low: FF FFA000 High: DE FFA800 Ext: 5 FFA400Programming bootloader: 512 bytes at 0x3F00 Commit Page: 3F00:3F00 Commit Page: 3F40:3F40 Commit Page: 3F80:3F80 Commit Page: 3FC0:3FC0Restoring normal fuses Lock: 2F FFE000Target power OFF!Type 'G' or hit RESET for next chip
100 topics about this "out of sync" issue and there is not an exact consensus on the cause.
Yes, that should have been a successful bootloader burn.If optiloader is still sending that sort of dialog to the serial port when you try to re-program the bootloader, it means that your chips are NOT dead. At least, not totally dead...
The "out of sync" message is a bit like a young child telling his parents "it hurts!"; it can have a lot of different causes, and the uploader doesn't even have the vocabulary to be clearer about what it is that isn't working. :-(
So is there any standard "troubleshooting sequence" when dealing with "out of sync" errors.
After you burn the optiboot bootloader in the 386 chip and install it in your Duemilanove are you selecting "Arduino UNO" under Tools->Boards? The Duemilanove uses an older bootloader with a slower baud rate.
Another possibility is that the Auto Reset isn't working.
Should I now load optiBoot using optiLoader onto those 2 Atmega328p chips? Is there any advantage?
Load the same boot loader on all of the chips !!!This way all the program/uploading of the sketches will be the same.