next topic »

[on:]

Hi all,

I've been working on a design using an Atmega1284P-PU in the DIP package, however due to space constraints may have to switch to the 1284P-AU in the TQFN package.

Now, I'm not using a bootloader - I am simply flashing with an AVR ISP Mk II over ICSP.  I will still have USB communications available for serial debugging and SD storage download, however that is another story. How would I go about using the P-AU version with the Ardunio IDE?

1) I'm assuming i'll need to make another entry in boards.txt as the device signature will be different.
2) Regarding fuses and lockbits etc, I'll set these with Atmel Studio - so all the trouble people have been having with bootloaders, is not a problem here.
3) Setting pin definitions, again - i'm assuming another file will be needed somewhere here? Here is where I'm a little lost.

[Reply #1 on:]

My understanding is that the package doesn't matter, so you should not need another pin definition file or boards.txt entry.

Eg. the UNO does not have two entries for the DIP versus SMD versions.

[Reply #2 on:]

Does the device signature not change then between package type?

[Reply #3 on:]

I don't think the signature is package-dependant. I can't say for sure with the '1284p but with the 328's I've used, it didn't matter if they were DIP or SMD.

[Reply #4 on:]

1. 1284P-PU, 1284P-AU, 1284P-MU all have the same device signature.
2. That's one way to do it. I use my MKii to burn a bootloader to set the fuses, and then File:Upload using Programmer to load the sketch.  Mostly because I don't like waiting around for Atmel Studio start up.
3.  Pins_arduino.h is the same for package to package. It maps the software names to port names. The software doesn't care how you then get from the port to the physical pin or what the physical pin numbers are.

[Reply #5 on:]

See the diffs attached to http://code.google.com/p/arduino/issues/detail?id=1055 for some additional documentation on pins_arduino.h

[Reply #6 on:]

2. That's one way to do it. I use my MKii to burn a bootloader to set the fuses, and then File:Upload using Programmer to load the sketch.  Mostly because I don't like waiting around for Atmel Studio start up.

Many thanks again - that's how I successfully did my 1284P-PUs, I just thought that a different signature would mean different bootloader, but now I know it's all the same.

Cheers!