From: Stefan Rosinger <stefan.rosinger@cesys.com>
To: ecos-devel@sources.redhat.com, "v2p@mind.be" <v2p@mind.be>
Subject: Problem with Virtex II Pro PowerPC 405 in 'hal_cpu_int_merge'
Date: Thu, 28 Oct 2004 17:27:00 -0000 [thread overview]
Message-ID: <opsglb3ydzwdnz90@www.cesys.com> (raw)
Hi all!
I have the same problem described here
http://ecos.sourceware.org/ml/ecos-discuss/2004-01/msg00080.html
I am working with an adaption of the Mind port of eCos for the Virtex II
Pro on an own developed hardware. I am building a ROM startup
configuration and don't use Redboot. I debug with GDB over a JTAG
connection.
I read the mail above and also disabled the MMU and Data/Instruction
caches. That brought no effect.
I also unchecked the 'use seperate interrupt stack'...
The instruction where the stack crashes:
.macro hal_cpu_int_merge sr
mfmsr r0
rlwimi r0,\sr,0,16,16
sync
mtmsr r0
sync
.endm
at the mtmsr r0.
the content of r0 at runtime is 0x9000
I have no idea why!
Who knows shomething about this problem.?
For more informations about hardware or something else, write me a mail!
Thx for help
Stefan
reply other threads:[~2004-10-28 17:27 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=opsglb3ydzwdnz90@www.cesys.com \
--to=stefan.rosinger@cesys.com \
--cc=ecos-devel@sources.redhat.com \
--cc=v2p@mind.be \
/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).