From: "Bhanu Prakash Adhikari" <bhanua@aztecsoft.com>
To: <ecos-discuss@sources.redhat.com>
Cc: "Gary Thomas" <gary@mlbassoc.com>
Subject: RE: [ECOS] to find whether my board uses redboot_RAM.ecm or redboot_ROM.ecm
Date: Fri, 23 Feb 2007 13:47:00 -0000 [thread overview]
Message-ID: <93F0E3CFC1ABB646B8808894FC7CDD2509E61B1F@azindbaex01.aztec.soft> (raw)
Thanks for clarification, Gary.
In case of redboot_RAM.ecm where will the image be stored? I'm afraid if
it stores in RAM it will be wiped off for power down. How does this
works?
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Gary Thomas
Sent: Friday, February 23, 2007 7:12 PM
To: Bhanu Prakash Adhikari
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] to find whether my board uses redboot_RAM.ecm or
redboot_ROM.ecm
Bhanu Prakash Adhikari wrote:
>
> Hi,
>
> How would I know whether uses redboot_RAM.ecm or redboot_ROM.ecm? How
can I find it?
>
> Unable to decrypt it in
http://ecos.sourceware.org/ecos/docs-latest/redboot/ixdp425.html
>
> It's a brand new board directly from manufacturer.
>
> Board details -
>
> 1. Avila GW2348
> 2. IXP 425
> 3. RedBoot 2.02
>
>
> RedBoot> fis list
>
> Name FLASH addr Mem addr Length Entry point
>
> RedBoot 0x50000000 0x50000000 0x00080000 0x00000000
>
> ramdisk 0x50080000 0x50080000 0x00800000 0x00800000
>
> zimage 0x50880000 0x50880000 0x00120000 0x00D40000
>
> FIS directory 0x50FE0000 0x50FE0000 0x0001F000 0x00000000
>
> RedBoot config 0x50FFF000 0x50FFF000 0x00001000 0x00000000
>
> RedBoot>
ROM - look at the addresses :-)
--
------------------------------------------------------------
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
The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
www.aztecsoft.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2007-02-23 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 13:47 Bhanu Prakash Adhikari [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-23 13:33 Bhanu Prakash Adhikari
2007-02-23 13:42 ` Gary Thomas
2007-02-26 4:40 ` tejas pawaskar
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=93F0E3CFC1ABB646B8808894FC7CDD2509E61B1F@azindbaex01.aztec.soft \
--to=bhanua@aztecsoft.com \
--cc=ecos-discuss@sources.redhat.com \
--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).