I accidently ordered a 1284 instead of an 1284P is there anyway to modify the support files inorder to make it work I got the 1284P bootloader loaded with a parallel port just by changing the id in the avrdude configuration but what else do I have to change and will it actually work?
As far as I'm aware, the P indicates that it will operate at a lower voltage and has slightly different BOD behavior...neither should matter for the purposes of a Gen7 board, so changing the signature should be sufficient.
got the bootloader loaded, but then I got some odd behavior the program (marlin won't load it's hangs around forever and then gives me a timeout error.
don't exactly know what is going on if I knew I would be up and running with my second board.
I just ran it again I think I'm programming the fuses wrong or when I load the bootload the fuses get changed to something the 1284 can't hack or something
Or some weird problem could use some troubleshooting help what fuses should I use with the 1284 vs the 1284p with marlin?
Getting an stk500 timeout error I dunno what this is due too but it's happening even with the test firmware
Edited 1 time(s). Last edit at 05/26/2013 06:29PM by terramir.
It might be worth a shot to just try burning a hex file directly to rule out any serial comms problems. Turn on the verbose output in the Arduino preferences, load the test sketch from github and click "Verify". Locate the output folder for the .hex file, and burn that hex file as you would the bootloader (It shouldn't overwrite the bootloader). If it works properly, you have a serial problem. If it doesn't, my next guess would be either the crystal or the fuse settings.
Edited 1 time(s). Last edit at 05/27/2013 06:29PM by Rezer.
I seem to have another problem I just verified that it wasn't a problem with my board using a 664P worked fine but only with the 0.23 arduino ide.
I tried flashing the 1284 with the 1284p firmware from with-in 0.23p and the compliler puked all over the place
But flashing even the 664p from 1.0.1 is not happening I got a 20 mhz crystal and well I dunno what to do if 1.0.1 gets stuck 1.0.4 20 mhz bootloaders are supposedly broken but the 16 mhz on the 1.0.0 and 1.0.1 but not the 20 mhz but I can't flash with the 1.0.1 then I'm sorta up shit's creek, maybe that rumor is untrue I'll try using 1.0.4 and the 20mhz ones and see if it works if it doesn't I'll ask traumflug for 1284 (no P ) support files.
> Undoubtly I'm keen on finding out on what makes
> the difference.
> Did you install a more recent driver?
I'm not sure to be honest, I installed the 64 bit driver from the mcp2200 product page and everything has "just worked". I can give more specifics on which version of the driver I have installed when I get home.
> traumflug anyway to make a bootloader for the
> I dunno seems like there fairly the same chip
> Correct me if I'm wrong there
Your problem isn't related to the bootloader hex file, the 1284 and 1284p are functionally identical as far as the bootloader is concerned. The only reason the 644 and 644p have slightly different bootloaders is because the 644p has an additional UART; the 1284s have no such differences. Just changing atmega1284p to atmega1284 in boards.txt is all that is needed to use the arduino ide with an atmega 1284, which it sounds like you've already done. Your problem lies somewhere else, especially if it's really being that finicky with a 644p as well.
Really? I didn't realize the signature was contained in the bootloader itself...my bad. Should still work though, right?
Oh, and I checked the mcp2200 driver version on my windows 7 64 bit machine...it was 1.2 (5.1.2600.3), and I uninstalled it and plugged the board back in. It automagically pulled 1.3 (5.1.2600.7) from windows update and still works fine *shrug*. I have UAC turned off on my machine, unsure if that would make a difference.