AVR GCC getting started?


I have been searching for a "how to" or a "Getting started" programming with GCC to program the Atmel line of microcontrollers. So far met with little success.

Specifically I have been using AVRedit (A nice Windows front end for GCC) to do the coding and then uploading with UISP.

What I am looking for is how to control basic I/O, read ADC inputs, loops, servo control ect.

Anyone know of any code examples/information/links?

Thanks for any fish.


Reply to
Loading thread data ...

It's all in the data sheets.

When you're working embedded, most of the time (even in C) you won't find boilerplate functions like InitializeADC() or ReadADC(). You may be able to use C syntax for reading/writing processor peripheral registers but you'll still need to handle much of the grunt work yourself.

General purpose functions *could* be used but that means hauling around the extra code in the function for such things as argument validation and error trapping/reporting.

One thing you might want to do is download a demo version of the Imagecraft AVR C compiler. It's a full version but time limited to 30 days. It includes a GUI "Application Builder" where you specify the chip you're using and the clock speed and then point'n'click through the peripheral setup. When you're done it can write the skeleton of the C code (complete with a stub for main()) that handles the peripheral initialization.

Reply to
Rich Webb

formatting link
has all the info you could just about ever want. They have tutorials and examples on their site. You can get the GCC compiler from there as well.

Reply to
Earl Bollinger

RVKBASIC is a good starting place and there are a number of great articles on the program from Nuts and Volts. I can see if I can get permission to send them to you. I am waiting on permission to post them on the bastoc.com site, but I think the author will send them to you. I can ask if I can. There is an update coming out sometime today on RVKBASIC.

Reply to
Larry Hatch

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.