From: <Zhang.Sonys@INVENTEC-inc.com>
To: <puneetgoel77@yahoo.co.uk>, <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] 答复: [ECOS] Suggestion needed for the support of ecos for my philips ARM board
Date: Mon, 02 Aug 2004 07:56:00 -0000 [thread overview]
Message-ID: <A373CBAE0333A4409D517DA697F41D83363C99@inc-mx6.inc.iac> (raw)
Why not try run RedBoot in Flash? You can load the eCos + Application with http/tftp or X-modem/Y-modem protocol into RAM.
Brs
Sonys
-----原始邮件-----
发件人: Puneet [mailto:puneetgoel77@yahoo.co.uk]
发送时间: 2004年8月2日 13:35
收件人: ecos-discuss@ecos.sourceware.org
主题: Re: [ECOS] Suggestion needed for the support of ecos for my philips ARM board
one small doubt.
I am able to get one more ARM9 board with 256KB Flash and 128MB RAM.
will that work?
soppose i have an OS+Application with the image size of 1MB, where is that
stored? In Flash?
RAM comes in picture only when i need to run the OS?
am i right?
regards,
Puneet
----- Original Message -----
From: "Robert Cragie" <rcc@jennic.com>
To: "Puneet Goel" <puneetgoel77@yahoo.co.uk>
Sent: Friday, July 30, 2004 2:16 PM
Subject: RE: [ECOS] Suggestion needed for the support of ecos for my philips
ARM board
> If it is not listed here, it won't be supported:
>
> http://ecos.sourceware.org/hardware.html
>
> However, I would say a good starting point would be the HAL for the the
ARM
> PID, ARM AEB or ARM Evaluator E7T, as these all use chips based on the
> ARM7TDMI. Anthony Massa's book (available online here
> http://www.informit.com/content/downloads/perens/0130354732.pdf) has a
> section on porting.
>
> HTH
>
> Robert Cragie, Design Engineer
> _______________________________________________________________
> Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK
> http://www.jennic.com Tel: +44 (0) 114 281 2655
> _______________________________________________________________
>
> > -----Original Message-----
> > From: ecos-discuss-owner@ecos.sourceware.org
> > [mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of Puneet Goel
> > Sent: 29 July 2004 09:43
> > To: ecos-discuss@ecos.sourceware.org
> > Subject: [ECOS] Suggestion needed for the support of ecos for my philips
> > ARM board
> >
> >
> > Hi all,
> >
> > I am new to embedded linux and wiling to learn it. I
> > have a board Philips LPC2119/LPC2129 with 16/32 bit
> > ARM7TDMI-S core. Can you please let me know ecos
> > supports this board or not.
> >
> > http://www.semiconductors.philips.com/pip/LPC2119FBD64.html
> >
> >
> > regards,
> > Puneet
> >
> >
> >
> >
> >
> >
> > ___________________________________________________________ALL-NEW
> > Yahoo! Messenger - all new features - even more fun!
> > http://uk.messenger.yahoo.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
> >
> >
>
--
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:[~2004-08-02 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=A373CBAE0333A4409D517DA697F41D83363C99@inc-mx6.inc.iac \
--to=zhang.sonys@inventec-inc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=puneetgoel77@yahoo.co.uk \
/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).