Limiting program RAM addresses

[Joel Sherrill]

Is there a LD linker script "include next" or include file but may not be present?, if so, the generic linker script might be able to include a custom extension.

Random thought and probably not a great one but finding a way to support this use case without duplicating the entire linkcmds set would be good.

--joel

On Dec 1, 2013 7:29 PM, Mohammed Khoory <mkhoory at eiast.ae> wrote:
I see, thanks. This makes sense.

I assume in order to make sure that ramdisk_buffer is located in the memory
region that I need, I would have to modify the linker script. Time to
research that I suppose.

>-----Original Message-----
>From: Sebastian Huber [mailto:sebastian.huber at embedded-brains.de]
>Sent: Friday, November 29, 2013 6:17 PM
>To: Mohammed Khoory
>Cc: rtems-users at rtems.org
>Subject: Re: Limiting program RAM addresses
>
>This doesn't work, but you can use this:
>
>static char ramdisk_buffer[12288][512];
>
>rtems_ramdisk_config rtems_ramdisk_configuration[] = {
>       {
>               sizeof(ramdisk_buffer[0]),
>               sizeof(ramdisk_buffer) / sizeof(ramdisk_buffer[0]),
>               &ramdisk_buffer[0][0]
>       }
>};
>

_______________________________________________
rtems-users mailing list
rtems-users at rtems.org
http://www.rtems.org/mailman/listinfo/rtems-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20131201/3bc86a21/attachment-0001.html>