A simple jumper from the arduino board's reset pin to the 1284p reset pin should fix that situation. Try that and let us know how it works.
You may have to also remove the reset pull-up resistor on the 1284p chip as there is already a reset pull-up on the arduino board and having two in parallel may be too low a resistance for the auto-reset pulse to pull the signal low on initiation of the DTR signal.
Still, got the error, "avrdude: stk500_getsync(): not in sync: resp=0x00".
A simple jumper from the arduino board's reset pin to the 1284p reset pin should fix that situation. Try that and let us know how it works.
You may have to also remove the reset pull-up resistor on the 1284p chip as there is already a reset pull-up on the arduino board and having two in parallel may be too low a resistance for the auto-reset pulse to pull the signal low on initiation of the DTR signal.
Still, got the error, "avrdude: stk500_getsync(): not in sync: resp=0x00".
That's too bad. The error message just means that AVRDUDE and the bootloader aren't talking to each other. Are you sure you are selecting the proper comm port and board type (1284p) to use in the arduino IDE?
It's hard to debug hardware issues remotely. If I was there I would hook up the logic analyzer. Perhaps an LED and 1K resistor on each of Tx/Rx lines to confirm data is getting through?
Any ideas why I can change and upload the blink sketch as much as I want but as soon as I try to upload a larger file I get the error?
Edit: I am getting RX TX led activity for about 2 seconds than nothing. On smaller sketches this seems to be enough time to get it uploaded before it goes out of sync? I am so lost...
I get the same issue with teh 1284P using Mighty1284 Optiboot (Bobuino pinmap).
I can upload Blink but not larger sketches. I eventually gave up and just program via ISP. It's a bit of a pain for serial monitor as I have to keep switching my USB>TTL adapter to monitor, but I'm just going to order another cheap one to use with MTTTY for monitoring.
I have seen mention that trying a swap of the crystal resonator, or switching to a ceramic resonator can cure it, but I've not tried that as yet.
If anyone does know a link to a definitive fix then it would be useful to knoe.
tack:
I get the same issue with teh 1284P using Mighty1284 Optiboot (Bobuino pinmap).
I can upload Blink but not larger sketches. I eventually gave up and just program via ISP. It's a bit of a pain for serial monitor as I have to keep switching my USB>TTL adapter to monitor, but I'm just going to order another cheap one to use with MTTTY for monitoring.
I have seen mention that trying a swap of the crystal resonator, or switching to a ceramic resonator can cure it, but I've not tried that as yet.
If anyone does know a link to a definitive fix then it would be useful to knoe.
This really sounds like the 1284P DIP internal hardware bug effecting the serial input pin. The folks over at avrfreaks site had lots on it in the past. Seems the fix is to wire a low pass filter to the serial input pin which is a .1 ufd cap from the rec pin to ground and a series 10K resistor from the pin to whatever is supplying the serial data. Date code on the chip may or may not help identify a vulnerable chip. Another fix is to use a bootloader for the 1284P that was been compiled to use the second serial port on the 1284P that wasn't effected by with internal hardware bug. There was such a bootloader made available a while back by someone. Who remembers all those details.
And of course these days you can use a arduino board running the arduinoISP sketch and upload your sketch using the IDE file/upload with programmer option the IDE now offers.
I am getting an error message when trying to download the .hex and .txt file. Can you look into this please? I would love to see if those 2 files would fix my issue. Thanks
tack:
I get the same issue with teh 1284P using Mighty1284 Optiboot (Bobuino pinmap).
I can upload Blink but not larger sketches. I eventually gave up and just program via ISP. It's a bit of a pain for serial monitor as I have to keep switching my USB>TTL adapter to monitor, but I'm just going to order another cheap one to use with MTTTY for monitoring.
I have seen mention that trying a swap of the crystal resonator, or switching to a ceramic resonator can cure it, but I've not tried that as yet.
If anyone does know a link to a definitive fix then it would be useful to knoe.
I worked for a while with Atmega1284P in the past weeks and I also experienced problems during the upload of a sketch using the bootloader.
I looked for help on the form (here and following posts) then I googled and found on AvrFreaks that this could be an hardware bug on the USART0 (read here).
So I solved using an RC filter with a 10K resistor in series and a 100 pF capacitor to ground, both put very close to the TX RX pin of the Arduino 1284P. Also, cut a little the pins of the capacitor.
Try it.
And he ran the serial ports fast in his applicatio. We never did anything special for the serial ports with low pass filters.
I suspect poor wiring where the error is occurring.
"skyjumper
Posted: May 24, 2011 - 04:12 AM
Joined: Feb 15, 2011
Posts: 81
Location: Smithfield, RI
Hm, I have been building a 1284P based product for a while and its serial intensive, no problems noticed here. I just wrote an app on my wire wrapped prototype with its 1284P in DIP. We'll see how long it runs.
Is there any info about what triggers this bug, or exactly what problems it causes?"
CrossRoads:
Was that some specific date-code lot of parts? I have never seen that happen.
Yes, (datecode 1017) was mentioned for the avrfreaks site poster, but not clear if it applies to other date codes. Probably need to research Atmel errata notes for that chip series. I'm pretty sure it was also limited to DIP package only, but that sounds kind of strange as I would think the dies are the same for any datecode chips made?