[avr-gcc-list] Code version timestamp

Dear All, I would like to display a code version (date/time or incremental number) during init on an LCD display. Does anybody know if there is any information in the executable (ROM file) that I can use at runtime (updated by the linker for example) ? If no, does anybody know how to implement

Re: [avr-gcc-list] Code version timestamp

[EMAIL PROTECTED] wrote: I would like to display a code version (date/time or incremental number) during init on an LCD display. If you're using CVS, you can get the date of the last checkin of a particular module by const char foo[] = $Date$; CVS will replace that by something like const

Re: [avr-gcc-list] Code version timestamp

[EMAIL PROTECTED] wrote: I am in tunning phase so I am looking for something more dynamic than CVS, i.e. the compilation/link time ... Well, it's up to you to run a cvs commit -f whenever you need. ;-) Anyone, someone pointed out to me offline that of course, the compiler supports the ANSI

Re: [avr-gcc-list] Code version timestamp

From: [EMAIL PROTECTED] (Joerg Wunsch) [EMAIL PROTECTED] wrote: I would like to display a code version (date/time or incremental number) during init on an LCD display. If you're using CVS, you can get the date of the last checkin of a particular module by const char foo[] = $Date$; And

[avr-gcc-list] stdio - how extensible?

I am wrapping up a serial io sample for my rtos (www.barello.net/AvrX) and as a final test I spun up two tasks, one attached to USART0 and one to USART1 (mega128). Well, duh, it didn't work since the second call to fdevopen() (task 2) failed miserably. I knew that, I am just sometimes thick in

[avr-gcc-list] (no subject)

All, Does the toolchain support the AT91RM9200? TIA Bill ___ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc-list

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

Wasn't it 14-Sep-2005, at 07:05PM, when Lars Noschinski said: Speaking of this, if I have an variable which is initialized during startup and only accessed /in/ an ISR, am I on the safe side, if don't declare it as volatile, right? Yes. -- Rich

Re: [avr-gcc-list] (no subject)

William Grigg wrote: All, Does the toolchain support the AT91RM9200? TIA Bill Yes and no. This mailing list is dedicated to the open source toolchain GNU Binutils, GCC, avr-libc, etc. *for the AVR target only*. Any AT91* processor is an ARM based processor. However, GNU Binutils and

Re: [avr-gcc-list] stdio - how extensible?

Larry Barello [EMAIL PROTECTED] wrote: Well, duh, it didn't work since the second call to fdevopen() (task 2) failed miserably. Can you explain `failed miserably' in some more technically descriptive phrase? So, the question is: what would it take to extend the current stdio facility to

Re: [avr-gcc-list] Code version timestamp

On 14 Sep 2005 at 6:21, John Altstadt wrote: [EMAIL PROTECTED] wrote: Dear All, I would like to display a code version (date/time or incremental number) during init on an LCD display. Does anybody know if there is any information in the executable (ROM file) that I can use at

Re: [avr-gcc-list] Code version timestamp

From: Anton Erasmus [EMAIL PROTECTED] On 14 Sep 2005 at 6:21, John Altstadt wrote: [...] %.elf: $(OBJ) @echo @echo $(MSG_LINKING) $@ $(CC) $(ALL_CFLAGS) $^ --output $@ $(LDFLAGS) rm version.o There is a better way to force the recompile of version.c

Re: [avr-gcc-list] AVR-GCC new devices

On Wednesday 14 September 2005 03:39 pm, Uwe Fechner wrote: would like to help to add support for new AVR devices to avr-gcc. http://www.kieltech.de/uweswiki/AVR_2dGCC the diffs I used to build a linux avr toolchain are here