From: anupbehare at gmail.com <anupbehare@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot Crashes with Dumps
Date: Wed, 13 Jan 2010 17:43:31 +0000 [thread overview]
Message-ID: <0016e64cac800d1bb3047d0f4f29@google.com> (raw)
In-Reply-To: <201001130838.50003.sr@denx.de>
I am using board having ppc440x5 core with customized chip and not a
standard 440Gx.
Board is using Denali controller, as the register are completely different
we can not use the standard u-boot initialization.
We performed board specific initialization and training for DDR2.
When the code enter into board_init_r() console shows following messages:
Top of RAM usable for U-Boot at: 20000000
Reserving 178k for U-Boot at: 1ffd3000
Reserving 1040k for malloc() at: 1fecf000
Reserving 128 Bytes for Board Info at: 1fecef80
Reserving 64 Bytes for Global Data at: 1fecef40
New Stack Pointer is: 1fecef28
Now running in RAM - U-Boot at: 1ffd3000
Bus Fault @ 0x1ffd5764, fixup 0x00000000
Machine Check Exception.
NIP: 1FFD5764 XER: 00000000 LR: 1FFD5764 REGS: 1fecee20 TRAP: 0200 DEAR:
00000000
MSR: 00021000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
GPR00: 1FFD5338 1FECEF10 1FECEF40 1FFD3000 1FFD6814 00000034 00000034
1FFD5764
GPR08: 00000600 00002098 00000030 2FAF07FE FFFFFFFF C000B330 20002A00
20013000
GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
GPR24: 00000000 1FECEF40 1FFD3000 1FED3000 1FFD3000 1FECEF80 20002B10
20013000
Call backtrace:
1FFD680C 1FFD56D8 A462C4EC
machine check
We tried to debug it with BDI as per steps given @
http://www.denx.de/wiki/view/DULG/DebuggingUBoot#Section_10.1.2.
We have verified by using BDI that uboot code is placed in DDR, but getting
an exception and u-boot is in continuously reboot mode.
Will it ok if we disable the MSR for ME,EE,CE? Or still it looks DDR
initialization issue ?
~Anup B
next prev parent reply other threads:[~2010-01-13 17:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001636d351d9aa42b7047d069e1b@google.com>
2010-01-13 7:38 ` [U-Boot] U-Boot Crashes with Dumps Stefan Roese
2010-01-13 17:43 ` anupbehare at gmail.com [this message]
2010-01-14 7:30 ` Stefan Roese
2010-01-14 9:39 ` anupbehare at gmail.com
2010-01-14 10:15 ` Wolfgang Denk
2010-01-16 9:53 ` anup behare
2010-01-14 10:24 ` Stefan Roese
2010-01-16 9:48 ` anup behare
2010-01-18 8:00 ` Stefan Roese
2010-01-12 7:02 anupbehare at gmail.com
2010-01-12 7:26 ` Stefan Roese
2010-01-12 9:09 ` anupbehare at gmail.com
2010-01-12 9:50 ` Stefan Roese
2010-01-12 10:07 ` anupbehare at gmail.com
2010-01-12 10:20 ` Stefan Roese
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=0016e64cac800d1bb3047d0f4f29@google.com \
--to=anupbehare@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