public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "\"Ilija Kocho [Илија Кочо]\"" <ilijak@siva.com.mk>
To: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Cc: abhishek srivastava <just_abhi22@yahoo.co.in>
Subject: [ECOS] Re: porting ecos on LPC1768
Date: Wed, 28 Aug 2013 14:27:00 -0000	[thread overview]
Message-ID: <521E0550.7010408@siva.com.mk> (raw)
In-Reply-To: <1377690167.73240.YahooMailNeo@web193205.mail.sg3.yahoo.com>

Hi Abhishek.

Yes, LPC1766 can be used with LPC1768, as well as a base for
LPC1768port. For detail and differences between LPC1766 and LPC1768 you
need to consult their LPC17xx documentation that you can find at NXP web
site.

eCos porting process is well described in /eCos reference manual/ and in
/eCos component writer's guide/ that you can find at:
 http://ecos.sourceware.org/docs.html.

The LPC1766 port is available from CVS repository
<http://ecos.sourceware.org/anoncvs.html>

I hope this helps

Ilija

On 28.08.2013 13:42, abhishek srivastava wrote:
> sir
> i am looking to port ecos on mbed LPC1768 but i am not sure where to
> begin with?
> i have ported ecos on i386 (vmware), but i am looking for some
> documentation that may help me in porting process.
> please provide/refer some documentation (not ecos documention), for
> porting on LPC1768
>
> would the same port you have created for LPC1766 work for LPC1768 ?
> where can i found it to look and modify?
>
> looking for reply
>
> thank you
>  
> Abhishek
>         


-- 
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:[~2013-08-28 14:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1377690167.73240.YahooMailNeo@web193205.mail.sg3.yahoo.com>]

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=521E0550.7010408@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=just_abhi22@yahoo.co.in \
    /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).