Go Down

Topic: Boards with 1284p - full swing oscillator setting - solving upload issues? (Read 5661 times) previous topic - next topic

westfw

Quote
if that is also true for the 1284P fuse settings.

I don't think we can blame the Arduino team for the 1284P fuse settings...

I dunno.  You have to change the fuses to upload programs without the bootloader anyway; if you know enough to do that, you should make sure they're all the way you want them to be.

tack


Quote
if that is also true for the 1284P fuse settings.

I don't think we can blame the Arduino team for the 1284P fuse settings...

I dunno.  You have to change the fuses to upload programs without the bootloader anyway; if you know enough to do that, you should make sure they're all the way you want them to be.


I wasn't implying it was the Arduino team, just if the settings have been derived then it would explain some things.

I initially set the fuses by burning a bootloader to new uC's. In some cases I then wiped the bootloader by programming directly via ISP.

Checking the 1284P maniacbug fuses does show that EESAVE is unset.

Revised fuses (incorporating Full Swing Oscillator and Preserve EEPROM through chip erase) for the 1284P would be:-

LOW FUSE : 0xf7
HIGH FUSE : 0xd6
EXTENDED FUSE : 0xfd

john1993


Quote
setting fuse to destroy ee data every time chip is reflashed. whats up with that.

irrelevant, since the chip is normally programmed via the bootloader, which doesn't do "chip erase" (and never erases the EEPROM) ?


one mans "irrelevant" is another mans "chasing tail for hours" (wait a minute, maybe that can be fun too...  ).

Go Up