veyepar: After Arduino

Author(s):	Robert Mibus
Location	MCC2
Date	jan Thu 31	Days Raw Files
Start	16:35	First Raw Start	error-in-template
Duration	0:45:00	Offset	None
End	17:20	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2013.linux.org.au/schedule/30037/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf After_Arduino.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

So you've started playing with this cool thing called "Arduino". You're having fun with buttons and LEDs and have started making some real projects that use them.

But then you realise a few limitations: they can be bulky, they're a little expensive, they don't have quite enough flash, they have too many I/O pins, or maybe they're just entirely too easy to use and you want some new challenges. What do you do?

You attend this presentation! :)

This presentation is neatly divided in half; the first (Hardware) half talks about:
* What Arduino hardware really is
* What makes up an Arduino system
* In-Circuit System Programmers (ie., that six-pin header you
basically never use).
* What similar hardware exists
* How YOU can make a cheaper and simpler platform for yourself
* Your ATmega chip's little brother, the ATtiny...

The second half focuses on the Arduino software:
* What the Arduino software brings you
* How the Arduino software limits you
* Using make & avr-gcc to build software for AT{mega,tiny} chips
* Accessing the registers that control the processor directly
* How software really uses the hardware interrupts
* Getting more than two interrupts
* Using the on-board timers to hand-bake PWM and other things
* Faster I/O
* Shrinking your application

If you ever PEEKed and POKEd with a C64, and are now fiddling with Arduinos - this is the talk for you.

Comment:

production notes