AVR Lesson: Setup - Revision history

ITechGeek: Undo revision 3999 by Yrewevaca (talk)

2010-11-24T06:30:59Z

Undo revision 3999 by Yrewevaca (talk)

← Older revision		Revision as of 06:30, 24 November 2010
Line 1:		Line 1:
	~~----~~
	<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
	~~----~~
	~~=[http://yjucofi.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=~~
	~~----~~
	~~=[http://yjucofi.co.cc CLICK HERE]=~~
	~~----~~
	~~</div>~~
	The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.		The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.

Line 29:		Line 21:


	'''MAC:'''~~<~~br />		'''MAC:'''<br />
	Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:		Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:

	An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode		An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode

	Makefile template which ROCKS - all you have to do after is change the DEVICE you're~~<~~br /> using along with PROGRAMMER and FUSES. (Will LINK my file here for reference ~~<~~br /> email Q if i forget)		Makefile template which ROCKS - all you have to do after is change the DEVICE you're<br /> using along with PROGRAMMER and FUSES. (Will LINK my file here for reference <br /> email Q if i forget)

	main.c file that is just a stupid simple C template to get you started		main.c file that is just a stupid simple C template to get you started
Line 42:		Line 34:
	== Chips ==		== Chips ==

	So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&~~amp;~~func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.		So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.

	A shortlist of the coolest chips includes:		A shortlist of the coolest chips includes:

Yrewevaca at 02:41, 24 November 2010

2010-11-24T02:41:38Z

← Older revision		Revision as of 02:41, 24 November 2010
Line 1:		Line 1:
			----
			<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
			----
			=[http://yjucofi.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
			----
			=[http://yjucofi.co.cc CLICK HERE]=
			----
			</div>
	The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.		The first step is to get set up with all the necessary hardware and software to start making your controllers do your bidding.

Line 21:		Line 29:


	'''MAC:'''<br />		'''MAC:'''<br />
	Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:		Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:

	An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode		An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode

	Makefile template which ROCKS - all you have to do after is change the DEVICE you're<br /> using along with PROGRAMMER and FUSES. (Will LINK my file here for reference <br /> email Q if i forget)		Makefile template which ROCKS - all you have to do after is change the DEVICE you're<br /> using along with PROGRAMMER and FUSES. (Will LINK my file here for reference <br /> email Q if i forget)

	main.c file that is just a stupid simple C template to get you started		main.c file that is just a stupid simple C template to get you started
Line 34:		Line 42:
	== Chips ==		== Chips ==

	So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.		So you're set to program, but you need a couple chips. [http://www.avrfreaks.net/index.php?module=Freaks%20Devices&func=viewDev This page at AVRFreaks] has some of the specs and all the datasheets in one place, but it's a bit overwhelming.

	A shortlist of the coolest chips includes:		A shortlist of the coolest chips includes:

Hexagon5un: /* Programmer */

2008-07-02T19:34:50Z

Programmer

← Older revision		Revision as of 19:34, 2 July 2008
Line 10:		Line 10:
	This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.		This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.

	Indeed, if any of that seems too complicated, just connect some wires from a parallel port to the right pins on the AVR (perhaps directly onto your breadboard?) and you're started. For more on that style of programmer, see [[AVR Tutorial: Bootstrapping the AVR]]		Indeed, if any of that seems too complicated, just connect some wires from a parallel port to the right pins on the AVR (perhaps directly onto your breadboard?) and you're started. There's an adapter for doing just that floating around the lab somewhere. For more on that style of programmer, see [[AVR Tutorial: Bootstrapping the AVR]]

	== Software ==		== Software ==

Hexagon5un: /* Chips */

2008-07-02T19:16:09Z

Chips

← Older revision		Revision as of 19:16, 2 July 2008
Line 46:		Line 46:
	'''Mega 48''' -- 28 pins. All of the bells and whistles, with 4k program memory. 6 ADC channels, buncha timers, SPI/I2C/USART communications. They'll do what you want.		'''Mega 48''' -- 28 pins. All of the bells and whistles, with 4k program memory. 6 ADC channels, buncha timers, SPI/I2C/USART communications. They'll do what you want.

	'''Mega 88, 168''' and beyond ~~-- You~~'~~re writing micro-controller code that requires 16k?!?! Time to learn assembler, parallel out your tasks to a couple chips~~, ~~or step up to something like an ARM platform~~, ~~IMO~~.		'''Mega 88, 168''' and beyond. A lot of power for under $10. Overkill for most of my (Elliot's) small projects, but when you need the memory, you need the memory.

Hexagon5un: /* Chips */

2008-07-02T19:14:53Z

Chips

← Older revision		Revision as of 19:14, 2 July 2008
Line 40:		Line 40:
	'''Tiny13''' -- Smallest and cheapest. 8 pins, 5 of them useful. 1k program memory. Goes everywhere. Cheaper and more versatile than a 555 IC. Some hardware SPI/I2C support, but it's a pain to write for.		'''Tiny13''' -- Smallest and cheapest. 8 pins, 5 of them useful. 1k program memory. Goes everywhere. Cheaper and more versatile than a 555 IC. Some hardware SPI/I2C support, but it's a pain to write for.

	'''Tiny45''' -- Another 8-pin, but with a high-speed PWM clock and 4k of program memory. ~$0.75 from Digikey. Can be made to run at 16MHz+ using its internal oscillator, making firmware USB a reality. Some hardware SPI/I2C support like the Tiny13.		'''Tiny45''' -- Another 8-pin, but with a high-speed (64MHz!) PWM clock and 4k of program memory. ~$0.75 from Digikey. Can be made to run at 16MHz+ using its internal oscillator, making firmware USB a reality. Some hardware SPI/I2C support like the Tiny13.

	'''Tiny2313''' -- 20 pins. It's the cheapest/smallest unit with > 5 usable pins. Hardware USART makes serial communication (e.g. with your computer) reasonably simple, which can be sweet for debugging or datalogging.		'''Tiny2313''' -- 20 pins. It's the cheapest/smallest unit with > 5 usable pins. Hardware USART makes serial communication (e.g. with your computer) reasonably simple, which can be sweet for debugging or datalogging.

Hexagon5un: /* Software */

2008-07-02T19:14:21Z

Software

← Older revision		Revision as of 19:14, 2 July 2008
Line 16:		Line 16:
	The standard toolchain consists of a GCC-based C cross-compiler, the AVR-libc libraries, and the software to run your programmer: ''avrdude.'' Feel free to write the C or assembler code using whatever editor you like best.		The standard toolchain consists of a GCC-based C cross-compiler, the AVR-libc libraries, and the software to run your programmer: ''avrdude.'' Feel free to write the C or assembler code using whatever editor you like best.

	~~For~~ Windows~~, it~~'~~s all~~ put together nicely with [http://sourceforge.net/projects/winavr WinAVR]. Download and install. If you're using a parallel port programmer, you'll need to also run the included ''giveio.bat'' file to get yourself permissions.		'''Windows:''' The whole toolchain is put together nicely with [http://sourceforge.net/projects/winavr WinAVR]. Download and install. If you're using a parallel port programmer, you'll need to also run the included ''giveio.bat'' file to get yourself permissions.

	~~For~~ Linux~~, it~~'~~s not that hard either.~~ I'm most familiar with Ubuntu these days. As of 2008/04, "sudo apt-get install avrdude avr-libc binutils-avr gcc-avr" will set you up. Or fetch tarballs and compile it yourself. (I'll incluce versions here in a few.)		'''Linux:''' I'm most familiar with Ubuntu these days. As of 2008/04, "sudo apt-get install avrdude avr-libc binutils-avr gcc-avr" will set you up. Or fetch tarballs and compile it yourself. (I'll incluce versions here in a few.)

	~~For Mac, I don't have a Mac. Is any of this [http://www.ladyada.net/learn/avr/setup-mac.html from Ladyada's site] useful?~~

	'''MAC:'''<br />		'''MAC:'''<br />

Hexagon5un: /* Programmer */

2008-07-02T19:12:58Z

Programmer

← Older revision		Revision as of 19:12, 2 July 2008
Line 9:		Line 9:

	This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.		This part may seem daunting -- it's not. Dive in or get someone to help you. The Ladyada kit is a good first/second soldering project.

			Indeed, if any of that seems too complicated, just connect some wires from a parallel port to the right pins on the AVR (perhaps directly onto your breadboard?) and you're started. For more on that style of programmer, see [[AVR Tutorial: Bootstrapping the AVR]]

	== Software ==		== Software ==

Q at 14:40, 12 June 2008

2008-06-12T14:40:55Z

← Older revision		Revision as of 14:40, 12 June 2008
Line 23:		Line 23:
	Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:		Wanted to note something quick about my MAC experience so far (Q): I haven't really read the link to ada's site about programming AVR for MAC but 'AVRMacPack' is really cool! In OSX it's a simple .pkg file to install and drop into /Applications - then as long as you've installed XCode (that comes with macbook in the 2nd CD 'Developer Tools' section) they have this great little script in there called 'avr-project'. When you run this little badass piece of code it creates a DIR for your project called /FIRMWARE and three things:

	An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode		An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode

	Makefile template which ROCKS - all you have to do after is change the DEVICE you're<br /> using along with PROGRAMMER and FUSES. (Will LINK my file here for reference <br /> ''email Q if i forget)''		Makefile template which ROCKS - all you have to do after is change the DEVICE you're<br /> using along with PROGRAMMER and FUSES. (Will LINK my file here for reference <br /> email Q if i forget)

	main.c file that is just a stupid simple C template to get you started		main.c file that is just a stupid simple C template to get you started

	In addition to the compiler and programming software, it's nice to have an [[AVR Makefile]] that automates the cross-compilation build process. Comment in/out the first few defines to match your environment.		In addition to the compiler and programming software, it's nice to have an [[AVR Makefile]] that automates the cross-compilation build process. Comment in/out the first few defines to match your environment.

Q at 14:40, 12 June 2008

2008-06-12T14:40:06Z

← Older revision		Revision as of 14:40, 12 June 2008
Line 25:		Line 25:
	An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode		An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode

	Makefile template which ROCKS - all you have to do after is change the DEVICE you're<br /> using along with PROGRAMMER and FUSES. (Will LINK my file here for reference - email Q if i forget)		Makefile template which ROCKS - all you have to do after is change the DEVICE you're<br /> using along with PROGRAMMER and FUSES. (Will LINK my file here for reference <br /> ''email Q if i forget)''

	main.c file that is just a stupid simple C template to get you started		main.c file that is just a stupid simple C template to get you started

Q at 14:39, 12 June 2008

2008-06-12T14:39:18Z

← Older revision		Revision as of 14:39, 12 June 2008
Line 25:		Line 25:
	An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode		An .xcodeproj file - this is a template (with skeleton code) for writing your program in Xcode

	Makefile template which ROCKS - all you have to do after is change the DEVICE you're using along with PROGRAMMER and FUSES. (Will LINK my file here for reference - email Q if i forget)		Makefile template which ROCKS - all you have to do after is change the DEVICE you're<br /> using along with PROGRAMMER and FUSES. (Will LINK my file here for reference - email Q if i forget)

	main.c file that is just a stupid simple C template to get you started		main.c file that is just a stupid simple C template to get you started