From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Regarding to eCos on VRC4373
Date: Tue, 09 Jan 2001 23:37:00 -0000 [thread overview]
Message-ID: <010901c07ad8$5ff525c0$0301a8c0@leopard> (raw)
In-Reply-To: <3A5BB04A.38F502F8@redhat.com>
> > <2>. We have some communication application developed on the board,
> > unfortunately the eCos defaultly in Big Endian mode for VRC4373. Since
> > communication application usually in Little Endian mode, I don't know
the
> > rational reason behind the Big Endian choice for this platform, and I
also
> > would like to know the possibility to compile eCos GDB stub and lib in
> > Little Endian mode, can we do it smoothly or need any hacking on the
source
> > code?
>
> You will probably need to make some adjustments in the platform code. But
> I believe the architecture and variant HALs should work because we have a
> v4300-based internal board that used to be little-endian if I remember
> right.
>
Can you disclouse which vr4300 based board is running eCos, I am just
curious since I didn't find any supported platform on eCos website except
the vrc4373 evaluation board.
I briefly checked the platform code, I didn't find any specific point to
modify since the Macro define CYG_LSBFIRST or CYG_MSBFIRST looks to me take
care of a lot of endian issues. I am just wondering why the Little Endian
mode is illegal for VR4300 platform. What I can think of doing first is to
try to enable it and make the monitor, is that doable?
Since I found the PMON comes together with NEC board is Little endian, can I
just complile the eCos lib in Little endian mode and debug it using PMON?
Any comments on this way? Thanks a lot!
-Ling
next prev parent reply other threads:[~2001-01-09 23:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 14:59 Ling Su
2001-01-09 16:44 ` Jonathan Larmour
2001-01-09 23:37 ` Ling Su [this message]
2001-01-10 3:30 ` Nick Garnett
2001-01-10 5:15 ` [ECOS] assertion checks for stack Joerg Rapka
2001-01-10 9:10 ` [ECOS] Regarding to eCos on VRC4373 Jonathan Larmour
2001-01-10 0:19 ` Ling Su
2001-01-10 9:08 ` Jonathan Larmour
[not found] ` <005e01c07ad5$5ba58210$0301a8c0@leopard>
2001-01-10 9:17 ` Jonathan Larmour
2001-01-10 14:08 ` Ling Su
2001-01-10 14:17 ` Jonathan Larmour
2001-01-10 15:45 ` Grant Edwards
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='010901c07ad8$5ff525c0$0301a8c0@leopard' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sources.redhat.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).