public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Elad Yosef <elad.yosef@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re-use RedBoot RAM segment in the application
Date: Sun, 03 Jul 2011 07:49:00 -0000	[thread overview]
Message-ID: <CAOFa9c0mkaQLx04V0GAG0JcUkg0uWDKFMPy9CLTG=QB00NmJug@mail.gmail.com> (raw)
In-Reply-To: <4E0DBFE0.2070502@mlbassoc.com>

But My RedBoot code is running directly from the ROM.
What you are saying is that when the application is calling "UART
write" for example
The code which runs is the RedBoot code from the ROM, which I agree about it.
But all the parameters I think they are located on the calling
Thread's stack, Am I wrong here?

Elad


On Fri, Jul 1, 2011 at 3:38 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> On 07/01/2011 06:28 AM, Elad Yosef wrote:
>>
>> Hi all,
>> My Target is short with RAM and I want to use the RedBoot RAM in the
>> application as well.
>> Is it possible? it is a waste of RAM if not.
>
> It's only a waste if your application does not use RedBoot for
> runtime services.  By default, your code will call functions in
> RedBoot for such things as console I/O, network debug support,
> GDB support, etc.  You can only reuse RedBoot's RAM section if
> you are not using any of those (CYGSEM_HAL_USE_ROM_MONITOR == 0)
>
> --
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
>

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2011-07-03  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 12:28 Elad Yosef
2011-07-01 12:39 ` Gary Thomas
2011-07-03  7:49   ` Elad Yosef [this message]
2011-07-03 11:33     ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOFa9c0mkaQLx04V0GAG0JcUkg0uWDKFMPy9CLTG=QB00NmJug@mail.gmail.com' \
    --to=elad.yosef@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).