Hello all,
I'm working on avr-gcc (GCC) 3.4.3 compiler and target MCU is Atmega 16
i want to declare some variables, such that hey
will take specific ram locations...
for ex:
as we do in assembly code as,
org(ramend-4)
date:.byte
1month:.byte 1
how to achieve this in c?
Thank you,
On Mon, 28 Nov 2005, varsha wrote:
I'm working on avr-gcc (GCC) 3.4.3 compiler and target MCU is Atmega 16
i want to declare some variables, such that hey will take specific ram
locations...
how to achieve this in c?
What's the point of using the abstraction of the C language, then? The
I have the same problem, and the point is that part of my external
memory is inside an FPGA, basically under control of the FPGA (It's
high-speed ADC data), while another part is external SRAM which I use
for my heap etc.
I access the FPGA memory at the moment using pointers which I initialise
Joerg Wunsch wrote:
Günter Dannoritzer [EMAIL PROTECTED] wrote:
Not sure whether it was the additional switch --program-prefix that
was not shown in the installation instructions ...
That option is normally not needed. It defaults to ${prefix}/bin,
for whatever prefix you gave with
On Tue, 29 Nov 2005 11:11, [EMAIL PROTECTED] wrote:
That's exactly how I've done it at the moment.
Heh, sorry, I sort of was replying to the original poster's email via yours :)
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about
Eric Weddington wrote:
You need to use the -mmcu= option for the link stage too, and specify
your microcontroller type.
I actually used that Makefile with WinAVR before and it always worked. I
tried it with the broken installation and it did not make any difference.
Now I am always a bit
On Tue, Nov 29, 2005 at 08:35:05AM +1000, [EMAIL PROTECTED]
wrote:
I have the same problem, and the point is that part of my external
memory is inside an FPGA, basically under control of the FPGA (It's
high-speed ADC data), while another part is external SRAM which I use
for my heap etc.
I
Hi all:
I am looking for an automated way to update a static string in program
space when my project is built. Is there an easy way to do this, either
by adding an extra target to the makefile, or some other way? I'd prefer
not to manually have to change the information, and I'd also prefer for
[EMAIL PROTECTED] wrote:
Hi all:
I am looking for an automated way to update a static string in program
space when my project is built. Is there an easy way to do this, either
by adding an extra target to the makefile, or some other way? I'd prefer
not to manually have to change the
On Nov 28, 2005, at 10:20 PM, [EMAIL PROTECTED] wrote:
Hi all:
I am looking for an automated way to update a static string in program
space when my project is built. Is there an easy way to do this,
either
by adding an extra target to the makefile, or some other way? I'd
prefer
not to
Hi David/avr-gcc list:
The __DATE__ and __TIME__ macros as mentioned by others in this thread
are useful for timestamps.
However, I'm having a problem getting my head around the following:
Suppose I create a version.c file, that contains those macros as progmem
strings, like this:
const
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:
On Tue, Nov 29, 2005 at 03:35:19PM +1100, Russell Shaw wrote:
In the makefile rule that calls the linker, a shell command could get
the current date and then edit the resulting binary to replace a special
marker string with the current date. There might be a way to edit the
linker script to
Günter Dannoritzer [EMAIL PROTECTED] wrote:
I should have also tried without the -program-prefix option. Anyhow,
another difference I noticed is that for the libc configuration no
--prefix is given on the avr libc page. Is that a possible
difference?
Yes, you need to run it with a consistent
14 matches
Mail list logo
