Taken from:
If you can use an Arduino to burn the boot loader on a blank Atmega328, can you use this same configuration to burn it on the TQFP package? I could I mount the Atmega TQFP, crystal, and caps on my board, and one of these headers connected just like it is on the UNO
Then once I have the Arduino boot loader on the TQFP Atmega328, I could finish populating my board and load sketches over serial via an FTDI cable?
Here is a thread about making boards for the SMT 328.
http://arduino.cc/forum/index.php/topic,69622.120.html
If you are going to the trouble, you might want to consider a 32u ..... The chip that is for the Leonardo that has not see the light yet, it has on board USB capability.
cyclegadget:
Here is a thread about making boards for the SMT 328.http://arduino.cc/forum/index.php/topic,69622.120.html
If you are going to the trouble, you might want to consider a 32u ..... The chip that is for the Leonardo that has not see the light yet, it has on board USB capability.
A long thread. A lot of talk about boards, but I didn't see anything specific on loading a bootloader on the TQFP.
The bootload is done after the boards are assembled. I don't know of a solution for putting a bootloader on the chip without soldering it to a board first. I would not care if I had a bootloader or not until I was successful getting the chip soldered to the board...Soldering and making the board is the hard part in my opinion. I built 10 small arduinos but, only 8 accepted the bootloader. I have yet to fix the issues with the reamaining 2.
As far as loading the bootloader goes, it is the same procedure as working with the dip 328.
...I think for my first SMD project, I'll all surface mount, except the Atmega328.
To give you some information about developing boards... If you are using Eagle to design you board, here is another thread that contains schematics for building Leonardo clones. On important thing mentioned was the selection of the crystal's package. http://arduino.cc/forum/index.php/topic,78631.0.html
I recommend watching some videos at Sparkfun and Youtube about SMD soldering. I had never did SMD before building my small Arduinos. I was happily surprised how easy it was....I had thought it was for "super solder gurus" rather than a hobbyist like me.
Here is a bunch of tutorials for using Eagle ..I have no affiliation with the video maker: Cadsoft EagleCad Tutorial Lesson 1 - YouTube
SouthernAtHeart:
Then once I have the Arduino boot loader on the TQFP Atmega328, I could finish populating my board and load sketches over serial via an FTDI cable?
Sure. Typically you'll do it afterwards via an on-board ICSP header as others have already mentioned. But, on the first all SMD board I designed I only added an FTDI header, so I built an adapter ala TQFP 32 Pin Socket Mount by ril3y - Thingiverse.
My only regret is not building a complete target board (with ICSP header, resonator, 10k resistor and de-coupling caps) but this worked fine for me. If you've got more money than time, check out the stuff on eBay (search for TQFP32 and find, among others, http://www.ebay.com/itm/QFP32-TQFP32-FQ-FP32-PQFP32-TO-DIP32-Socket-Adapter-/230726458579?pt=LH_DefaultDomain_0&hash=item35b85e5cd3).
And soldering these things isn't that hard, especially if you can do 0805 (or even 1206) passives. Just remember that the solder wick is your friend. I try and solder each pin with a minimal amount, but always go back thru with the wick to remove any excess (as well as any solder bridges).
It's not that hard really.
FWIW,
Brad
KF7FER
I'm trying to burn the bootloader to the TQFP atmega328p. I'm getting this error: "Expected signature for Atmega328 is 1E 95 14. Double check chip, or use -F to override this check"
No idea of how to use "-F" or what it actually means.
Plecto:
I'm trying to burn the bootloader to the TQFP atmega328p. I'm getting this error: "Expected signature for Atmega328 is 1E 95 14. Double check chip, or use -F to override this check"No idea of how to use "-F" or what it actually means.
That's the command line option that you would pass to avrdude to tell it to ignore the signature mismatch. An m328p (device name to avrdude for atmega328p) has a signature of 1E 95 0F so you seem to be telling it that you have an m328, but you really have an m328p.
I have no idea how to override the command line arguments passed to avrdude by the arduino software.
Re: Loading Arduino Bootloader on TQFP Atmega
To get back to the original thread... A socket for programming would be easy, If you made a cutout that was exactly the size of the chip at the final bend and plated the last half mm of the PC tracks with 200 micron gold to could catch all 32 pins between a footprint around the edges of the cutout and a bakelite type of rigid plastic or other hard non conductive material and make a good working programming fixture, I made several that worked out very nicely for both SO and Quad packages. I made 2 panels that fit under the pressure plate one with a square cutout in it and one with a rectangular cutout. The thicker gold at the ends was nice for long life and good electrical contact.
Doc
That's the command line option that you would pass to avrdude to tell it to ignore the signature mismatch. An m328p (device name to avrdude for atmega328p) has a signature of 1E 95 0F so you seem to be telling it that you have an m328, but you really have an m328p.
I have no idea how to override the command line arguments passed to avrdude by the arduino software.
I figured out the problem. It was true as you said, I chose a guide on how to burn a bootloader to an m328 chip, not m328p. I just simply chose "Ardunio UNO" as the board and it worked out okay. I was too hung up on that error message telling me that the TQFP and the DIP had different signatures, but that wasn't the case at all 
One last question though. The TQFP has more pins than the DIP, how will the arduino deal with that? Can I simply write "analogRead(7);"?
That's cool. It looks like your description in the boards.txt file should specify an xxx.build.variant of eightanaloginputs instead of standard. xxx is the prefix for your specific board type in the boards.txt file.
I'm not sure that eightanaloginputs is going to solve everything for you, but it might help get you going. It looks like A6 and A7 are already defined though in the standard xxx.build.variant.