Can anyone recommend a good AVR book...
in [Basics]
|
From: martin.shoebridge on 26 Sep 2006 17:57 Try avrfreaks.net I think there is a tutorial on there....... <mrdarrett(a)gmail.com> wrote in message news:1159284655.132929.53890(a)k70g2000cwa.googlegroups.com... > ... for a beginner? > > And what's the difference, anyway, between the AVR and the ATxxxxxxxx > series of chips? > > TIA > > Michael >
From: Rich Webb on 26 Sep 2006 19:18 On 26 Sep 2006 10:35:19 -0700, mrdarrett(a)gmail.com wrote: > >Joerg wrote: >> Hello Michael, [snip...snip...] >> Seriously, as Linnix wrote, you may not need one. I started with the TI >> MSP430, thought about buying a book but after taking a look at one I >> realized how fast some of the contents become obsolete. By the time it's >> printed there is a slew of new uC variations that are now used by everyone. >> >> Main things to get started: Learn the design environment, play around, >> try to make the blinky-LED work, try to change blink rates or pattern, >> load again and so on. Then study the family guide and the data sheet for >> a long, long time. After that you know all the assembler words the uC of >> choice understands and what they mean. Even if you never do assembler >> you need to become familiar with the peripherals on board and how they >> can affect or impair each other. >> >> If you really want a book recommendation I'd post again at >> comp.arch.embedded where among many uC experts there is also Ulf >> Samuelsson from Atmel. I am sure he'd know which books are good. Ulf is >> very responsive, I wish TI and others would participate as well. >> >> -- >> Regards, Joerg >> >> http://www.analogconsultants.com > > >Ah ok. (Actually until you mentioned it I didn't even notice linnix >had replied inline to my first question. Sorry 'bout that, linnix. >:-) > >Was browsing over at amazon.com and was getting worried about some of >the comments the users said... The AT90-series were the (AFAIK) "original" processors in the AVR family. That family recently split into the ATmega-series with an enhanced instruction set (and, generally, larger processors) and the ATtiny family that is, well, tiny by comparison. There is some slop-over, with the relatively new AT90CAN128 chip being an almost identical twin to the ATmega128. All you really need to get started is, say, an ATmega8, an AVRISP programmer or the STK500 (if you don't have breadboards and bench power supplies handy), a copy of the free AVR Studio, and the device manual. The individual chapters in the manual do a good job of explaining how to tickle the various peripherals. The on-line help in AVR Studio handles the assembler and instruction set. Like Joerg, I typically approach a new processor with the embedded equivalent of "Hello, world!": get one pin to toggle at an intended rate using one of the chip's timers and an interrupt service routine. That's enough to validate that I grok the toolchain, can create a runnable image and get it loaded, and can sling around the necessary bits to handle ISRs and I/O. From there, the rest is just coding ... -- Rich Webb Norfolk, VA
From: John B on 27 Sep 2006 04:53 On 27/09/2006 the venerable Rich Webb etched in runes: > On 26 Sep 2006 10:35:19 -0700, mrdarrett(a)gmail.com wrote: > > > > > Joerg wrote: > >> Hello Michael, > [snip...snip...] > >> Seriously, as Linnix wrote, you may not need one. I started with > the TI >> MSP430, thought about buying a book but after taking a look > at one I >> realized how fast some of the contents become obsolete. > By the time it's >> printed there is a slew of new uC variations that > are now used by everyone. > > > > >> Main things to get started: Learn the design environment, play > around, >> try to make the blinky-LED work, try to change blink rates > or pattern, >> load again and so on. Then study the family guide and > the data sheet for >> a long, long time. After that you know all the > assembler words the uC of >> choice understands and what they mean. > Even if you never do assembler >> you need to become familiar with > the peripherals on board and how they >> can affect or impair each > other. > > > > >> If you really want a book recommendation I'd post again at > >> comp.arch.embedded where among many uC experts there is also Ulf > >> Samuelsson from Atmel. I am sure he'd know which books are good. > Ulf is >> very responsive, I wish TI and others would participate as > well. > > > > >> -- > >> Regards, Joerg > > > > >> http://www.analogconsultants.com > > > > > > Ah ok. (Actually until you mentioned it I didn't even notice linnix > > had replied inline to my first question. Sorry 'bout that, linnix. > > :-) > > > > Was browsing over at amazon.com and was getting worried about some > > of the comments the users said... > > The AT90-series were the (AFAIK) "original" processors in the AVR > family. That family recently split into the ATmega-series with an > enhanced instruction set (and, generally, larger processors) and the > ATtiny family that is, well, tiny by comparison. > > There is some slop-over, with the relatively new AT90CAN128 chip being > an almost identical twin to the ATmega128. > > All you really need to get started is, say, an ATmega8, an AVRISP > programmer or the STK500 (if you don't have breadboards and bench > power supplies handy), a copy of the free AVR Studio, and the device > manual. The individual chapters in the manual do a good job of > explaining how to tickle the various peripherals. The on-line help in > AVR Studio handles the assembler and instruction set. > > Like Joerg, I typically approach a new processor with the embedded > equivalent of "Hello, world!": get one pin to toggle at an intended > rate using one of the chip's timers and an interrupt service routine. > That's enough to validate that I grok the toolchain, can create a > runnable image and get it loaded, and can sling around the necessary > bits to handle ISRs and I/O. From there, the rest is just coding ... You can also download a demo version of a C compiler from the Imagecraft website. It's free for 45 days and then becomes code limited to 8K which is still fine for the mega8. -- John B
From: jrwalliker on 27 Sep 2006 05:34 The latest version of Atmel's AVR development environment works together with winavr. This means that you can write a C program and single-step it in the simulator, watching register, memory and i/o port values. One thing to watch out for if you use a serial in-circuit programmer - it is easy to lock yourself out of the device by setting the fuses incorrectly. In particular, setting the watchdog timer to "continuous" prevents reprogramming of the device or even the watchdog fuse! John
From: Simon Dice on 27 Sep 2006 12:53
I Agree with the others, but If you still want a reference book for programming in C the AVRs, I can recomend you this one: Embedded C Programming and the Atmel AVR Authors are Barnett, Cox &Ocull you can get it from B&N |