From: jerzy dyrda <jerzy.dyrda@kontron.pl>
To: ecos-discuss@ecos.sourceware.org
Cc: Sujoy Ray <raysujoy@yahoo.com>
Subject: Re: [ECOS] IXP425 Big Endian Mode
Date: Fri, 10 Jun 2005 11:04:00 -0000 [thread overview]
Message-ID: <200506101309.38271.jerzy.dyrda@kontron.pl> (raw)
In-Reply-To: <20050610103437.10287.qmail@web53401.mail.yahoo.com>
Hello All,
> Thanks for your suggestion!
>
> I am still having one doubt -
>
> When I compare the code(pls read elf file) compiled in
> little endian mode with the one in big endian mode
> using objdump - I see that bytes are swapped. E.g a
> code which looks like E6000021 in little endian mode
> becomes 210000E6 in big endian mode. Now, during
> instruction fetch and decode cycle, how processor
> decodes this big endian instruction, when the state of
> the processor is in little endian? Pls note that the
> processor is in little endian mode and trying to
> execute a big-endian instruction. So, byte 0 for it
> will be E6 of the big endian instruction, but the
> correct one should be 21.
>
> I think 'am confused in some way. Please help me to
> come out from this confusion.
#ifdef CYGINT_HAL_ARM_BIGENDIAN
// set big-endian
mrc p15, 0, r0, c1, c0, 0
orr r0, r0, #0x80
mcr p15, 0, r0, c1, c0, 0
CPWAIT r0
#endif
If I can I explain my point of view. Above code regards external bus - before
change this bus works in little endian address coherend mode ( see docu.
regarding address and data cohered mode - this is a Intel "discover"). Core
as I saw always works in big endian mode - to run code you must just swap
code compiled in little endian. Please see to this discuss list - someone ask
how to start window$ CE ( their compiler works only in little endian)
Best Regards,
jerzy
--
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 prev parent reply other threads:[~2005-06-10 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 8:41 Sujoy Ray
2005-06-10 9:51 ` Peter Korsgaard
2005-06-10 10:34 ` Sujoy Ray
2005-06-10 11:04 ` jerzy dyrda [this message]
[not found] <20050918202057.38425.qmail@web53410.mail.yahoo.com>
2005-09-19 4:31 ` Sujoy Ray
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=200506101309.38271.jerzy.dyrda@kontron.pl \
--to=jerzy.dyrda@kontron.pl \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=raysujoy@yahoo.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).