From: Cedric VINCENT <cedric.vincent@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Why exceptions are enabled before exception vector code is copied
Date: Wed, 6 Jul 2005 10:53:23 +0200 [thread overview]
Message-ID: <c8f1005070601532cb85bff@mail.gmail.com> (raw)
In-Reply-To: <20050706080402.0E346353A4E@atlas.denx.de>
> No exceptions are supposed to happen until then.
> What do you suggest hoiw such a
> situation should be handled while running from flash?
There is no reason to enable them before exception vector code is
copied. So exceptions should be enabled *after* exception vector code
is copied.
> It does not happen on other systems.
The spurious "Machine Check Excpetion" is well known on Virtex/PPC.
Most Xilinx FPGA boards are affected (tested on Virtex-II Pro and
Virtex 4).
regards, Cedric VINCENT.
next prev parent reply other threads:[~2005-07-06 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 7:45 [U-Boot-Users] Why exceptions are enabled before exception vector code is copied Cedric VINCENT
2005-07-06 8:04 ` [U-Boot-Users] " Wolfgang Denk
2005-07-06 8:53 ` Cedric VINCENT [this message]
2005-07-06 8:59 ` Wolfgang Denk
2005-07-06 9:52 ` Cedric VINCENT
2005-07-06 13:50 ` Cedric VINCENT
2006-03-13 11:24 ` Wolfgang Denk
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=c8f1005070601532cb85bff@mail.gmail.com \
--to=cedric.vincent@gmail.com \
--cc=u-boot@lists.denx.de \
/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