public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@redhat.com>
To: Jesper Skov <jskov@redhat.com>
Cc: ecos-discuss@sourceware.cygnus.com, jlarmour@redhat.com,
	Andreas.Karlsson@combitechsystems.com
Subject: Re: [ECOS] Modifying memory layout, possible?
Date: Tue, 31 Oct 2000 06:39:00 -0000	[thread overview]
Message-ID: <XFMail.20001031080629.gthomas@redhat.com> (raw)
In-Reply-To: <otlmv5qe1t.fsf@thinktwice.zoftcorp.dk>

On 31-Oct-2000 Jesper Skov wrote:
>>>>>> "Andreas" == Andreas Karlsson <Andreas.Karlsson@combitechsystems.com> writes:
> 
> Andreas> Hello, I'm wondering if it is possible to run eCos after
> Andreas> adding more memory, in any case it seems to be hard to edit
> Andreas> the memory layout, which is a bad feature for eCos.
> 
> There is a GUI for doing this, but it is only available on WinDOS.
> 
> Editing the .ldi and .h files should be quite simple though. But I
> guess I'm slightly biased.
> 
> Andreas> Then I compile my testprogram and I expect to see some
> Andreas> changes in the start and stop registers but no.
> 
> Changes in the memory layout has to be matched with appropriate
> changes to the startup code. Arguably, it should be automatic, but I
> suspect we didn't have the .h file when the AEB HAL was written.
> 
> I'll put it on my TODO list, but of course I'd be happy to accept a
> patch fixing that.
> 
> Andreas> How can I tell eCos that there are more memory available so I
> Andreas> can get rid of those ".bss is not within region RAM"?
> 
> Maybe the linker map doesn't have the right dependencies. Did you try
> creating a new build directory after updating the .ldi and .h files?
> 
> Andreas> I thought that it was in hal_platform_setup.h but this script
> Andreas> (PLATFORM_SETUP1)just runs when
> Andreas> CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS is defined and it is not
> 
> This is wrong. The startup code should allow the target to run with
> ROM startup, doing all the necessary initializations - regardless of
> the inclusion/exclusion of the GDB stubs.
> 

Sorry, but on this and some other platforms, no can do :-(  The startup
code moves memory around, and in some cases at least, it would be very
difficult to allow this code to run after this remap had taken place.

> The condition should probably be something like:
> 
>#if !defined(CYG_HAL_STARTUP_RAM) \
>     defined(CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS)
> 
> That is, always init the MMU mapping for non-RAM startups, of if the
> stubs are included.
> 
> Jesper

  reply	other threads:[~2000-10-31  6:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-31  2:46 Andreas.Karlsson
2000-10-31  6:29 ` Jesper Skov
2000-10-31  6:39   ` Gary Thomas [this message]
2000-10-31  6:54     ` Jesper Skov
2000-10-31  6:48 Andreas.Karlsson
2000-10-31  6:56 ` Jesper Skov
2000-10-31  7:06 Andreas.Karlsson
2000-10-31  7:11 ` Jesper Skov
2000-10-31  7:16 Andreas.Karlsson
2000-11-01  1:48 Andreas.Karlsson
2000-11-01  2:15 ` Jesper Skov
2000-11-01  2:15 Andreas.Karlsson
2000-11-01  2:22 ` Jesper Skov
2000-11-01  5:16 ` Jonathan Larmour
2000-11-01  5:28 Andreas.Karlsson
2000-11-01  5:40 ` Jonathan Larmour
2000-11-01  7:50 Andreas.Karlsson
2000-11-01  8:05 ` Jonathan Larmour

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=XFMail.20001031080629.gthomas@redhat.com \
    --to=gthomas@redhat.com \
    --cc=Andreas.Karlsson@combitechsystems.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@redhat.com \
    --cc=jskov@redhat.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).