[avr-gcc-list] Re: [avr-libc-dev] [bug #29774] prologue/epilogue stack pointer manipulation not interrupt safe in XMega

2010-06-07 Thread Galen Seitz
cc'd(and followups) the avr-gcc list on the slight chance that there's someone there that isn't on the libc list. -- Galen Seitz gal...@seitzassoc.com ___ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr

Re: [avr-gcc-list] GCC 4.4.3 and AVR

2010-03-25 Thread Galen Seitz
distribution are you using? I have RPMs for the following: avr-binutils-2.19 avr-libc-1.6.8 avr-libc-docs-1.6.8 avrdude-5.10 avr-gcc-4.3.3 These should be a close match to Eric's latest WinAVR release. -- Galen Seitz gal...@seitzassoc.com ___ AVR-GCC

[avr-gcc-list] xmega 16A4 and 16D4 support?

2009-10-01 Thread Galen Seitz
://www.avrfreaks.net/index.php?name=PNphpBB2file=viewtopict=75868highlight=16d4 thanks, galen -- Galen Seitz gal...@seitzassoc.com ___ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc-list

Re: [avr-gcc-list] problem building gcc 4.3.2

2009-09-30 Thread Galen Seitz
Georg-Johann Lay wrote: Galen Seitz schrieb: Hi, I'm trying to build RHEL/CentOS packages that match the latest winavr release. I've downloaded Eric's patches and incorporated them into the build process. The build dies during libgcc with this error: ... When I look at avr/libgcc

[avr-gcc-list] problem building gcc 4.3.2

2009-09-29 Thread Galen Seitz
currently require a frame pointer for corre ctness I haven't been able to figure out what I've done wrong. Do Eric's gcc patches require a bootstrap? If so, what is the recommend way of doing this? thanks, galen -- Galen Seitz gal...@seitzassoc.com

Re: [avr-gcc-list] AVR ADC

2007-04-13 Thread Galen Seitz
Bob Paddock wrote: Make sure you look at the 'fine print' in the parameter tables. I found that the 2.56V reference varied from ~2.3V to ~2.7V across devices in the CAN64 parts I have been using. The values still fell within what the table said where acceptable. If you need repeatability from

Re: [avr-gcc-list] C and AS programs - compiled together

2007-03-15 Thread Galen Seitz
Grzegorz !Kubik wrote: Did you look in the avr-libc user manual? avr-libc contains some inline asm explanations while I need more about compiling together C and AS modules. I have just found some interesting guidelines: http://lists.gnu.org/archive/html/avr-gcc-list/2007-02/msg00142.html

Re: [avr-gcc-list] volatile...

2006-12-15 Thread Galen Seitz
One more suggestion... If you are using global volatiles shared between an interrupt and mainline code, interrupt handler performance may be improved by moving the volatile into a temporary variable. galen volatile uint16_t counter; SIGNAL(TMR0_OVERFLOW) { uint16_t tmp; tmp =

Re: [avr-gcc-list] Calling C functions from assembly

2006-10-16 Thread Galen Seitz
Simon Han [EMAIL PROTECTED] wrote: Hi all, This must be the most stupid question of the year. :P Is there a way to call C functions from assembly? Can someone point me an example of this? If you are asking about parameter passing and such, you can find the calling

Re: [avr-gcc-list] Interrupt prologue and epilogue

2006-10-11 Thread Galen Seitz
Simon Han [EMAIL PROTECTED] wrote: Is there any documentation about how interrupt prologue and epilogue are implemented? I am mainly interested in what registers need to be save and why. Please treat me as a person who is trying to implement interrupt handler by hand. :-)

Re: [avr-gcc-list] calling convention used by the avr-gcc compiler

2006-07-15 Thread Galen Seitz
Priyanka Bhardwaj [EMAIL PROTECTED] wrote: Hi there, Can anyone please refer some document or manual where the calling convention used by the avr-gcc compiler is written ? I want to know the calling convention used by the avr-gcc compiler.

Re: [avr-gcc-list] Data Array alignment

2006-06-05 Thread Galen Seitz
Trampas [EMAIL PROTECTED] wrote: I always create my own typedefs, I have been bitten before where a compiler does things funny with variable types. For example is a char a signed or unsigned value. Thus by defining my own typedefs I just eliminate all these problems and make the code the

Re: [avr-gcc-list] Faulty code generation with three uint64_t args to function

2006-05-02 Thread Galen Seitz
Eric Weddington [EMAIL PROTECTED] wrote: Joerg Wunsch wrote: I just created the following bug: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27386 Any suggestions for a fix are welcome. I tried to find the part of GCC responsible for the fault, but have no clues about where to look,

Re: [avr-gcc-list] Glitch on GPIO

2006-02-24 Thread Galen Seitz
Jahagirdar Gopal-AGJ005 [EMAIL PROTECTED] wrote: Yes, first I am configuring the direction register and then writing data in to it. Will this be a problem? will it work, If we write data first and then configure the direction register? I think that is the problem. The data register has

Re: [avr-gcc-list] Adding date/version information to project??

2005-11-28 Thread Galen Seitz
Here's a snippet from my Makefile. I think this is probably close to meeting your needs. I probably lifted this from somewhere off the net but I don't recall where. For all I know, it came from this mailing list. galen OBJS= ${ASRCS:$(S)=$(O)} ${SRCS:.c=$(O)} EXTRA_OBJS = date.o .PHONY:

Re: [avr-gcc-list] After ATMega

2005-10-13 Thread Galen Seitz
Eric Pasquier [EMAIL PROTECTED] wrote: Dear All, I am using an ATMega32, 16MHz to implement a Kalman filter (7 input states). I suceed to run it at 60Hz, but with lots of optimization and compromises, like using fix floating point math for example. ADC, timers, serial, I/O are used. I

Re: [avr-gcc-list] multiplication order effects machine cycles?

2005-10-13 Thread Galen Seitz
intiha Ho gai [EMAIL PROTECTED] wrote: Hello everyone, In one of the programs that I am trying to optimize there is a long multiplication (I am using Atmega128L). Using GPIO toggling across the lines of code I get the following result double skew_; int32_t offset_;//can also be negative

Re: [avr-gcc-list] avrdude.conf section for ATmega168

2005-10-11 Thread Galen Seitz
Manfred Bartz [EMAIL PROTECTED] wrote: Below is a definition for the ATmega168 suitable for incorporation in the avrdude.conf file. I have successfully programmed the ATmega168 flash using the definition and STK200 style hardware (parallel port). It would probably be best to submit

Re: [avr-gcc-list] Makefile Procyon AVRlib vs AVR-libc and ANSI C

2005-10-06 Thread Galen Seitz
Patrick Blanchard [EMAIL PROTECTED] wrote: OK, I'm getting it now. C99 is not included in the current version of KR, which was where my confusion was originating, and there are no immediate plans for a new edition from the authors. If you are already familiar with C, I would recommend getting

[avr-gcc-list] patching info file names for binutils, gcc, gdb?

2005-09-28 Thread Galen Seitz
I'm trying to update Ted Roth's Linux rpms and I've run into an issue with info file naming. Ted's packages for binutils, gcc, and gdb all contain patches to prefix the info file names with 'avr-'. For example, here's is a small piece of his gcc patch: [EMAIL PROTECTED] gcc.info [EMAIL

Re: [avr-gcc-list] Global variables and ISRs ???

2005-09-07 Thread Galen Seitz
Joerg Wunsch [EMAIL PROTECTED] wrote: David Brown [EMAIL PROTECTED] wrote: ..., and it will also change multiply by constant into a series of shifts and adds. The target chip has a hardware multiplier and divider, but they are slower than the shift-and-add sequences. Unfortunately,

Re: [avr-gcc-list] programming SOIC devices.

2005-08-24 Thread Galen Seitz
Hugo González Monteverde [EMAIL PROTECTED] wrote: If you don't want to build an adapter yourself, check in http://www.smt-adapter.com/ Emulation Technology is another option. They are in California. http://www.emulation.com/ galen ___

Re: [avr-gcc-list] output current for ATMega128 on output pins

2005-06-07 Thread Galen Seitz
Torsten Mohr [EMAIL PROTECTED] wrote: Hi, i just browsed the data sheet but could not find in the electrical characteristics how much current i can output on a port. I'd like to drive some LEDs. I wonder, but this value should be in the data sheet, i must have missed it. The spec