Avr2011 Programming The Kit - Revision history

Tslagle at 20:50, 3 April 2012

2012-04-03T20:50:54Z

← Older revision		Revision as of 20:50, 3 April 2012
Line 74:		Line 74:

	* Bugs in your code -> failure to compile. If you get something like: <br><code>Compiling: LED_Demo.c <br>LED_Demo.c: In function ‘main’: <br>LED_Demo.c:22: error: expected ‘;’ before ‘while’ <br>make: *** [LED_Demo.o] Error 1 </code> <br>you have an error in your code that's preventing compilation. Read the error output for hints, tweak your code, and try again. (In this case, I left out a ';' in line 20.)		* Bugs in your code -> failure to compile. If you get something like: <br><code>Compiling: LED_Demo.c <br>LED_Demo.c: In function ‘main’: <br>LED_Demo.c:22: error: expected ‘;’ before ‘while’ <br>make: *** [LED_Demo.o] Error 1 </code> <br>you have an error in your code that's preventing compilation. Read the error output for hints, tweak your code, and try again. (In this case, I left out a ';' in line 20.)

			[[Category:AVR_Class]]

Hexagon5un: /* Hookup: */

2011-03-15T16:28:09Z

Hookup:

← Older revision		Revision as of 16:28, 15 March 2011
Line 1:		Line 1:
			= Software: =

			If you haven't already installed the laptop-side software toolchain, see [[Installing AVR Toolchain]] and come on back.


	= Hookup: =		= Hookup: =

Hexagon5un: /* If there are errors... */

2011-03-06T18:20:36Z

If there are errors...

← Older revision		Revision as of 18:20, 6 March 2011
Line 68:		Line 68:
	* /dev/ttyUSB0 not found. Is the FTDI cable plugged in? Try "lsusb" to see if it's there. Try "ls /dev/ttyUSB*" to see if it's registered as USB1. Edit Makefile accordingly, and remember that you'll probably have to change it back later.		* /dev/ttyUSB0 not found. Is the FTDI cable plugged in? Try "lsusb" to see if it's there. Try "ls /dev/ttyUSB*" to see if it's registered as USB1. Edit Makefile accordingly, and remember that you'll probably have to change it back later.

	* Bugs in your code -> failure to compile. If you get something like:		* Bugs in your code -> failure to compile. If you get something like: <br><code>Compiling: LED_Demo.c <br>LED_Demo.c: In function ‘main’: <br>LED_Demo.c:22: error: expected ‘;’ before ‘while’ <br>make: *** [LED_Demo.o] Error 1 </code> <br>you have an error in your code that's preventing compilation. Read the error output for hints, tweak your code, and try again. (In this case, I left out a ';' in line 20.)
	<~~pre~~>Compiling: LED_Demo.c
	LED_Demo.c: In function ‘main’:
	LED_Demo.c:22: error: expected ‘;’ before ‘while’
	make: *** [LED_Demo.o] Error 1
	</~~pre~~>
	you have an error in your code that's preventing compilation. Read the error output for hints, tweak your code, and try again. (In this case, I left out a ';' in line 20.)

Hexagon5un: /* If there are errors... */

2011-03-06T18:16:08Z

If there are errors...

← Older revision		Revision as of 18:16, 6 March 2011
Line 68:		Line 68:
	* /dev/ttyUSB0 not found. Is the FTDI cable plugged in? Try "lsusb" to see if it's there. Try "ls /dev/ttyUSB*" to see if it's registered as USB1. Edit Makefile accordingly, and remember that you'll probably have to change it back later.		* /dev/ttyUSB0 not found. Is the FTDI cable plugged in? Try "lsusb" to see if it's there. Try "ls /dev/ttyUSB*" to see if it's registered as USB1. Edit Makefile accordingly, and remember that you'll probably have to change it back later.

			* Bugs in your code -> failure to compile. If you get something like:
	* Bugs in your code -~~- failing~~ to compile. If you get something like		<pre>Compiling: LED_Demo.c
	<pre>Compiling: LED_Demo.c
	LED_Demo.c: In function ‘main’:		LED_Demo.c: In function ‘main’:
	LED_Demo.c:22: error: expected ‘;’ before ‘while’		LED_Demo.c:22: error: expected ‘;’ before ‘while’
	make: *** [LED_Demo.o] Error 1		make: *** [LED_Demo.o] Error 1
	</pre> you have an error in your code that's preventing compilation. Read the error output for hints, tweak your code, and try again. (In this case, I left out a ';' in line 20.)		</pre>
			you have an error in your code that's preventing compilation. Read the error output for hints, tweak your code, and try again. (In this case, I left out a ';' in line 20.)

Hexagon5un: /* If there are errors... */

2011-03-06T18:13:36Z

If there are errors...

← Older revision		Revision as of 18:13, 6 March 2011
Line 67:		Line 67:

	* /dev/ttyUSB0 not found. Is the FTDI cable plugged in? Try "lsusb" to see if it's there. Try "ls /dev/ttyUSB*" to see if it's registered as USB1. Edit Makefile accordingly, and remember that you'll probably have to change it back later.		* /dev/ttyUSB0 not found. Is the FTDI cable plugged in? Try "lsusb" to see if it's there. Try "ls /dev/ttyUSB*" to see if it's registered as USB1. Edit Makefile accordingly, and remember that you'll probably have to change it back later.


			* Bugs in your code -- failing to compile. If you get something like
			<pre>Compiling: LED_Demo.c
			LED_Demo.c: In function ‘main’:
			LED_Demo.c:22: error: expected ‘;’ before ‘while’
			make: *** [LED_Demo.o] Error 1
			</pre> you have an error in your code that's preventing compilation. Read the error output for hints, tweak your code, and try again. (In this case, I left out a ';' in line 20.)

Hexagon5un: /* Programming the Chip */

2011-03-06T18:08:51Z

Programming the Chip

← Older revision		Revision as of 18:08, 6 March 2011
Line 27:		Line 27:
	* Get the chip into bootloader mode		* Get the chip into bootloader mode
	* While you're in the directory with your code and the Makefile, type "make" or "sudo make" into the terminal		* While you're in the directory with your code and the Makefile, type "make" or "sudo make" into the terminal
	* Your code will compile, and it will upload your code to the chip ~~-- if all is well you will see a ghetto progress bar~~		* Your code will compile, and it will upload your code to the chip
	* The chip will automatically reset and start running your program		* The chip will automatically reset and start running your program


	~~It worked if~~ you see <pre>		If all is well, you will see <pre>
	avrdude: erasing chip		avrdude: erasing chip
	avrdude: reading input file "LED_Demo.hex"		avrdude: reading input file "LED_Demo.hex"

Hexagon5un: /* Programming the Chip */

2011-03-06T18:08:06Z

Programming the Chip

← Older revision		Revision as of 18:08, 6 March 2011
Line 29:		Line 29:
	* Your code will compile, and it will upload your code to the chip -- if all is well you will see a ghetto progress bar		* Your code will compile, and it will upload your code to the chip -- if all is well you will see a ghetto progress bar
	* The chip will automatically reset and start running your program		* The chip will automatically reset and start running your program


	It worked if you see <pre>		It worked if you see <pre>

Hexagon5un: /* Programming the Chip */

2011-03-06T18:07:47Z

Programming the Chip

← Older revision		Revision as of 18:07, 6 March 2011
Line 30:		Line 30:
	* The chip will automatically reset and start running your program		* The chip will automatically reset and start running your program

			It worked if you see <pre>
			avrdude: erasing chip
			avrdude: reading input file "LED_Demo.hex"
			avrdude: input file LED_Demo.hex auto detected as Intel Hex
			avrdude: writing flash (156 bytes):

			Writing \| ################################################## \| 100% 0.21s



			avrdude: 156 bytes of flash written
			avrdude: verifying flash memory against LED_Demo.hex:
			avrdude: load data flash data from input file LED_Demo.hex:
			avrdude: input file LED_Demo.hex auto detected as Intel Hex
			avrdude: input file LED_Demo.hex contains 156 bytes
			avrdude: reading on-chip flash data:

			Reading \| ################################################## \| 100% 0.19s



			avrdude: verifying ...
			avrdude: 156 bytes of flash verified

			avrdude: safemode: Fuses OK

			avrdude done. Thank you.
			</pre>

	= If there are errors... =		= If there are errors... =

Hexagon5un: /* Getting the Board Into Bootloader Mode */

2011-03-06T18:05:15Z

Getting the Board Into Bootloader Mode

← Older revision		Revision as of 18:05, 6 March 2011
Line 20:		Line 20:
	* Tap the "A" button (RESET)		* Tap the "A" button (RESET)
	* Now you can release the "B" button		* Now you can release the "B" button

			You can tell you're in bootloader mode because your normal code won't be running. If you had and LED on or blinking, for instance, it won't be now.

	= Programming the Chip =		= Programming the Chip =

Hexagon5un: /* Getting the Board Into Bootloader Mode */

2011-03-06T18:04:18Z

Getting the Board Into Bootloader Mode

← Older revision		Revision as of 18:04, 6 March 2011
Line 13:		Line 13:
	= Getting the Board Into Bootloader Mode =		= Getting the Board Into Bootloader Mode =

	When the chip starts up, the bootloader program checks ~~for~~ the "B" button (connected to PD2) ~~being~~ pressed. If the button is pressed, it sits and waits for programming data to come in over the serial line. If the button isn't pressed, it starts your program. So, what you want to do is reset the chip while the "B" button is pressed.		When the chip starts up, the bootloader program checks if the "B" button (connected to PD2) is pressed. If the button is pressed, it sits and waits for programming data to come in over the serial line. If the button isn't pressed, it starts your program. So, what you want to do is reset the chip while the "B" button is pressed.

	To get the chip into ready-to-program Bootloader Mode:		To get the chip into ready-to-program Bootloader Mode:
Line 20:		Line 20:
	* Tap the "A" button (RESET)		* Tap the "A" button (RESET)
	* Now you can release the "B" button		* Now you can release the "B" button


	= Programming the Chip =		= Programming the Chip =