From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Porting Result of eCos on NEC DDB-VRC4375
Date: Tue, 27 Feb 2001 11:19:00 -0000 [thread overview]
Message-ID: <010701c0a0f2$303fef00$0201a8c0@raccoon> (raw)
In-Reply-To: <3A9AA7AE.79AC453A@redhat.com>
> > After several weeks porting and testing, eCos finally can run on my new
NEC
> > VRC4375 board in little endian mode. I am not sure if any body need it,
> > anyway, please let me know if you want to use VRC4375 board with eCos.
> > Compared to vrc4373 board, this board is newer, and the porting work
just
> > limits on the platform dependent part.
>
> Congratulations! I'm glad that it's finally worked out for you. Did you
> have to change much from the vrc4373? And what were the solutions to the
> problems you were having?
>
Actually I am still have problem to build a GDB stub based on the new CVS
tree. I worked that out by using the eCos-1.3.1 distribution (adding vrc4375
package) to build a working stub and then using the CVS tree for applicition
library building. I didn't changed much from vrc4373, but since I can not
get PMON source code from NEC after several times asking, I have to find out
the differences from 4375's datasheet. The major difference is the SDRAM
power-up sequence.
Regards,
-Ling
next prev parent reply other threads:[~2001-02-27 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 21:22 [ECOS] porting ecos 김재용
2001-02-24 4:41 ` Gary Thomas
2001-02-24 13:10 ` [ECOS] Porting Result of eCos on NEC DDB-VRC4375 Ling Su
2001-02-26 11:00 ` Jonathan Larmour
2001-02-27 11:19 ` Ling Su [this message]
2001-02-27 11:47 ` Jonathan Larmour
2001-02-28 2:41 ` Jesper Skov
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='010701c0a0f2$303fef00$0201a8c0@raccoon' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@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).