RE: [avr-gcc-list] use of specifin RAM location

[Matt.VanDeWerken]

That's exactly how I've done it at the moment.

Cheers,
Matthew van de Werken - Electronics Engineer
CSIRO E&M - Rock Mass Characterisation - 1 Technology Court - Pullenvale
- 4069
p: (07) 3327 4142 * f: (07) 3327 4455 * e: address@hidden
"We do not inherit the earth from our ancestors, we borrow it from our
children." 
-- Native American Proverb

> -----Original Message-----
> From: Daniel O'Connor [mailto:address@hidden 
> Sent: Tuesday, 29 November 2005 10:13 AM
> To: address@hidden
> Cc: Van De Werken, Matt (E&M, QCAT)
> Subject: Re: [avr-gcc-list] use of specifin RAM location
> 
> 
> On Tue, 29 Nov 2005 09:05, address@hidden 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.
> 
> You should be able to do..
> char *foo;
> foo = 0x1234;
> 
> for (i = 0; i < 10; i++)
>       putc(foo[0]);
> 
> or similar..
> 
> > I access the FPGA memory at the moment using pointers which I 
> > initialise to the right value. I don't yet have a method mapped out 
> > for the SRAM - it's on the next version of the board (the present 
> > version has no external SRAM).
> >
> > I will have a need to allocate some large-ish arrays in the 
> external 
> > SRAM in the next hardware version.
> 
> I don't think it would be any different to the above unless 
> you are using a 
> malloc routine, in which case you would need to tell it to 
> not allocate 
> memory in certain places.
> 
> -- 
> Daniel O'Connor software and network engineer
> for Genesis Software - http://www.gsoft.com.au
> "The nice thing about standards is that there
> are so many of them to choose from."
>   -- Andrew Tanenbaum
> GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
>