I expect that this error message stems from the assembler. Try to compile the
sources with -S and I expect that you won't see this error.
I expect that the virtual tables are aligned on a 4-byte boundary (as usually
is useful for 32 bit systems).
Bjoern.
-Ursprüngliche Nachricht-
Von
On Mon, 2007-02-26 at 13:22 -0700, Eric Weddington wrote:
> The line that you have above does some pretty needles math. You should be
> able to just simply do:
>
> fptr = (FuncPtr)pgm_read_word(&funcs_table[i]);
>
> Does that make any difference in the size of your code? It would be
> interes
As Shaun Jackman wrote:
> >There's no equivalent set of command-line switches for each
> >-mmcu= option. Alas, it's really required to patch each and
> >any new AVR into a few locations in binutils and GCC.
>
> So far it seems to work. It's very possible that I just got lucky.
You're likely run
Hi,
Can anyone please point me to some resources for learning about
interfacing C and assembler modules in gcc-avr?
I've been looking at the asmdemo code from avr-libc, but it only goes
part way with overall explanation.
I'm especially needing to learn how to write assembler (.S) modules
contain
On 2/26/07, Joerg Wunsch <[EMAIL PROTECTED]> wrote:
"Shaun Jackman" <[EMAIL PROTECTED]> wrote:
> I was definitely missing something!
You are missing even more, like the selection of the crtX.o file.
There's no equivalent set of command-line switches for each
-mmcu= option. Alas, it's really r
On 2/26/07, Joerg Wunsch <[EMAIL PROTECTED]> wrote:
David McNab <[EMAIL PROTECTED]> wrote:
> The code in /doc/examples/asmdemo in the avr-libc tree is only
> limited value, because all the assembler code seems to be just ISRs,
> with no calling between C and assembler.
Sorry, I simply couldn't
David McNab <[EMAIL PROTECTED]> wrote:
> The code in /doc/examples/asmdemo in the avr-libc tree is only
> limited value, because all the assembler code seems to be just ISRs,
> with no calling between C and assembler.
Sorry, I simply couldn't fit anything into it like that that would
serve as a u
David McNab <[EMAIL PROTECTED]> wrote:
> I'm especially needing to learn how to write assembler (.S) modules
> containing C-callable functions, and how to handle issues like:
http://www.nongnu.org/avr-libc/user-manual/FAQ.html#faq_reg_usage
--
cheers, J"org .-.-. --... ...
"Shaun Jackman" <[EMAIL PROTECTED]> wrote:
> I was definitely missing something!
You are missing even more, like the selection of the crtX.o file.
There's no equivalent set of command-line switches for each
-mmcu= option. Alas, it's really required to patch each and
any new AVR into a few locat
Hi,
Can anyone please point me to some resources for learning about
interfacing C and assembler modules in gcc-avr?
I've been looking at the asmdemo code from avr-libc, but it only goes
part way with overall explanation.
I'm especially needing to learn how to write assembler (.S) modules
contain
On 2/26/07, Shaun Jackman <[EMAIL PROTECTED]> wrote:
I'm attempting to use the AT90PWM2, which isn't yet supported by GCC
with a simple -mat90pwm2 switch. Are the following switches
equivalent?
avr-gcc -mmcu=avr4 -minit-stack=0x2ff -D__AVR_AT90PWM2__
Am I missing anything? My STK500/STK520 boar
I'm attempting to use the AT90PWM2, which isn't yet supported by GCC
with a simple -mat90pwm2 switch. Are the following switches
equivalent?
avr-gcc -mmcu=avr4 -minit-stack=0x2ff -D__AVR_AT90PWM2__
Am I missing anything? My STK500/STK520 board isn't yet behaving
exactly `right'. That's a rather
On 2/26/07, Joerg Wunsch <[EMAIL PROTECTED]> wrote:
"Shaun Jackman" <[EMAIL PROTECTED]> wrote:
> The AT90PWM2B has a different signature than AT90PWM2, but avrdude
> 5.3.1 doesn't seem to support the AT90PWM2B. What is the difference
> between the AT90PWM2 and the AT90PWM2B?
I think there's a m
> -Original Message-
> From:
> [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> org] On Behalf Of David McNab
> Sent: Sunday, February 25, 2007 5:16 PM
> To: avr-gcc-list@nongnu.org
> Subject: [avr-gcc-list] More observations: array of pointers
> to functions
>
> I tried the approach
"Shaun Jackman" <[EMAIL PROTECTED]> wrote:
> The AT90PWM2B has a different signature than AT90PWM2, but avrdude
> 5.3.1 doesn't seem to support the AT90PWM2B. What is the difference
> between the AT90PWM2 and the AT90PWM2B?
I think there's a migration document from Atmel. I just tried to
review
Message: 1
Date: Sun, 25 Feb 2007 19:16:11 +0100
From: "Gervasio Varela" <[EMAIL PROTECTED]>
Subject: [avr-gcc-list] Warnings with virtual methods in avr-g++
To: avr-gcc-list@nongnu.org
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Hello all,
I'm getting
Message: 1
Date: Wed, 21 Feb 2007 22:38:35 -0600 (CST)
From: "Kevin Neff" <[EMAIL PROTECTED]>
Subject: [avr-gcc-list] Reset on TIMER1 Overflow
To: AVR-GCC-list@nongnu.org
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain;charset=iso-8859-1
I have an ATMega128 that is resetting unexpectant
The AT90PWM2B has a different signature than AT90PWM2, but avrdude
5.3.1 doesn't seem to support the AT90PWM2B. What is the difference
between the AT90PWM2 and the AT90PWM2B? I haven't been able to find
the answer in the data sheet. In any case, I used the entry for the
AT90PWM2 in avrdude.conf an
OK, I am sorry. I did not read the definition of Memory Segment field
very well. The address is interrupted as a "Word" address. Not a "Byte
address".
So there is no problem. Except with my reading skills. Sorry about that.
No problem. You're not the only one to have suffered from word/byt
19 matches
Mail list logo
