Timothy Smith [EMAIL PROTECTED] wrote:
that example is fine, i understand what's happening ( i think ) but
how would i controll the speed of the led blinking? would i use a
different ISR, such a timer compare?
This example is probably not the best example to learn about timers in
general, as
Hi all,
I am new to this maling
list .actually I am doing a project on AVR microcontrollers, but i m
surrounded by number of queries,
1. which are the patches necessary for avr-gcc,which version should i use .
2. the patches available on net are compatible to which linux kernel , r they
hello avr people i've been reading and working through various tutorials
on avr's, and i've managed to to program one and make led's on various
ports turn on and off, however i'm having a little trouble understanding
the timer functions.
See:
http://sourceware.org/bugzilla/show_bug.cgi?id=1272
Suddenly with binutils 2.16, the -Tdata option passed to the
linker ceased to work, while --section-start,.data= remained
functional.
Carlos Lamas analyzed in a thread at avrfreaks.net:
I don't know about WinAVR, but for linux, I did not need to install any
patches. I justed installed gcc for avr,
libc, and the binutils and I'm up and running fine. This was just a
couple weeks ago using Fedora--which is similar to redhat. My
installation procedure is outlined here:
From: rajeev joshi [EMAIL PROTECTED]
[...]
4.While working on windows which compiler, simulator shpuld use ,right now
i
m having codevision AVR ,AVR studio .
5. But i m not gettin how to work on WINAVR .
What is your goal?
If you have to get a project out, and you have a paid license for
Amen to the comment below!!! It's the first time I've seen anyone else voice that opinion. I've been running enterprise class UNIX servers, Oracle instances, and writing code in umpteen languages for years yet AVRFreaks still manages to confound me.
Sorry for hijacking the thread.
Tubbs-
On Tue, Mar 07, 2006 at 10:50:42AM +0100, Joerg Wunsch wrote:
There are two -Tdata options passed down to the linker. Obviously,
the order of evaluation has been changed between binutils 2.15 and
2.16, but we can hardly blame them for this.
This is a genuine problem of our current setup.
I'm sure this is a stupid question, but I was wondering...
I noticed that in the avr-libc header pgmspace.h that there are
declarations including:
extern size_t strlen_P(PGM_P) __ATTR_CONST__; /* program memory can't
change */
extern size_t strnlen_P(PGM_P, size_t) __ATTR_CONST__; /*
