public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Steven_cheng" <05071@alphanetworks.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] What is the different between  "ROM" and "ROMRAM" in the Bootup type ??
Date: Sun, 03 Jul 2005 17:08:00 -0000	[thread overview]
Message-ID: <000101c57ff2$07c6cf10$016ffea9@stevencheng> (raw)
In-Reply-To: <20050701124913.GK5563@lunn.ch>

Dear Andrew,

    Thank you for you reply, but I still confuse about the following
questions.

1) When the board  powers on, does the CPU need to know which type and
vendor
of ROM flash?? (ex. AMD 29LV040B)

2) How does the CPU know the memory address which the ROM locates ??
because the files (xxx_romram.ldi/xxx_romram.h) only define the
RAM address and size.

Thnak you very much.

// Steven


----- Original Message ----- 
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Steven_cheng" <05071@alphanetworks.com>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Friday, July 01, 2005 8:49 PM
Subject: Re: [ECOS] What is the different between "ROM" and "ROMRAM" in the
Bootup type ??


> On Fri, Jul 01, 2005 at 05:48:45PM +0800, Steven_cheng wrote:
> > Hi All,
> >
> >     What is the different between  "ROM" and "ROMRAM" in the Bootup type
??
> >
> > Reference to the description of the configure tool :
> >
> >     This option is used to control where the application program will
run,
> > either from RAM or ROM (flash) memory. ROM based applications must be
self
> > contained, while RAM applications will typically assume the existence of
a
> > debug environment, such as GDB stubs.
> >
> >
> >
> > But What is the different between "ROM" and "ROMRAM"  ??
>
> ROMRAM starts in ROM, but copies itself into RAM.
>
>         Andrew
>
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>


-- 
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:[~2005-07-03 17:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 12:30 Steven_cheng
2005-07-01 12:49 ` Andrew Lunn
2005-07-03 17:08   ` Steven_cheng [this message]
2005-07-03 19:42     ` Andrew Lunn
2005-07-04  1:01       ` Steven_cheng

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='000101c57ff2$07c6cf10$016ffea9@stevencheng' \
    --to=05071@alphanetworks.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@sources.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).