From: "Steven_cheng" <05071@alphanetworks.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: "Andrew Lunn" <andrew@lunn.ch>, <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] What is the different between "ROM" and "ROMRAM" in the Bootup type ??
Date: Mon, 04 Jul 2005 01:01:00 -0000 [thread overview]
Message-ID: <000b01c58034$05ee5f90$016ffea9@stevencheng> (raw)
In-Reply-To: <20050703194145.GL8479@lunn.ch>
Dear Andrew,
I see, I will try it.
Thank you for your help very much.
Steven Cheng
----- Original Message -----
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Steven_cheng" <05071@alphanetworks.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>; <ecos-discuss@sources.redhat.com>
Sent: Monday, July 04, 2005 3:41 AM
Subject: Re: [ECOS] What is the different between "ROM" and "ROMRAM" in the
Bootup type ??
> On Sun, Jul 03, 2005 at 09:41:27AM +0800, Steven_cheng wrote:
> > 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)
>
> No. It should be able to read from any type/vendor. You only need to
> know more when you come to erase/write. But its not the CPU that does
> what, its you application program.
>
>
> > 2) How does the CPU know the memory address which the ROM locates ??
>
> It is hardwired. Read the data sheet for your processor and look at
> the schematics to see what chip select it is using.
>
> 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
prev parent reply other threads:[~2005-07-04 1:01 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
2005-07-03 19:42 ` Andrew Lunn
2005-07-04 1:01 ` Steven_cheng [this message]
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='000b01c58034$05ee5f90$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).