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 15:50:47 +0200 [thread overview]
Message-ID: <c8f1005070606506c278f6b@mail.gmail.com> (raw)
In-Reply-To: <c8f10050706025279618920@mail.gmail.com>
Here comes a patch to enable exceptions after exceptions vector code
is copied (i.e after relocation). I tested it with my board (PPC 405),
I also changed 440 and IOP480 target but without testing...
I run the MAKEALL script : there are no errors, warnings was not due
to this patch.
CHANGELOG : * cpu/ppc4xx/start.S : exceptions are enabled after relocation.
About XMD, as I thought the spurious exception comes infinitely... So
there is no easy way to fix it. If you apply this patch (this is an
easy way to detect this spurious exception), you should add at the end
of doc/README.ml300 :
========================
6. Warning
----------
It was reported that XMD makes (sometimes) a spurious "Machine Check Exception".
When debugging, if you are sure that this exception doesn't come from
your system,
comment this line into cpu/ppc4xx/start.S :
addi r7,r0,0x1000 /* set ME bit (Machine Exceptions) */
========================
Regards,
Cedric VINCENT
-------------- next part --------------
A non-text attachment was scrubbed...
Name: u-boot_exception.diff
Type: application/octet-stream
Size: 2467 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20050706/1b1e86c7/attachment.obj
next prev parent reply other threads:[~2005-07-06 13:50 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
2005-07-06 8:59 ` Wolfgang Denk
2005-07-06 9:52 ` Cedric VINCENT
2005-07-06 13:50 ` Cedric VINCENT [this message]
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=c8f1005070606506c278f6b@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