public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: sivaji <rameshmrm@gmail•com>
To: linuxppc-dev@ozlabs•org
Subject: RE: 2.6.23-rc3 boot hang on MPC8641D
Date: Wed, 12 Sep 2007 21:52:59 -0700 (PDT)	[thread overview]
Message-ID: <12648696.post@talk.nabble.com> (raw)
In-Reply-To: <46B96294322F7D458F9648B60E15112C85D7FB@zch01exm26.fsl.freescale.net>



Hi,
          I tired to move the dtb to 0x2000000, but the result was same.
uboot version is 1.1.6

by
Sivaji

Zhang Wei-r63237 wrote:
> 
> Hi, 
> 
> Your flat device tree address seems too low. Try to move the dtb to
> higher address such as 0x2000000.
> 
> And which version of your u-boot?
> 
> Cheers!
> - zw
> 
>> -----Original Message-----
>> From: linuxppc-dev-bounces+wei.zhang=freescale.com@ozlabs•org 
>> [mailto:linuxppc-dev-bounces+wei.zhang=freescale.com@ozlabs•or
>> g] On Behalf Of sivaji
>> Sent: Thursday, September 13, 2007 12:18 PM
>> To: linuxppc-dev@ozlabs•org
>> Subject: 2.6.23-rc3 boot hang on MPC8641D
>> 
>> 
>> Hi,
>>         I am try to boot the 2.6.23-rc3 kernel to my custom 
>> board based on
>> 8641D Processor. After uncompressing the kernel it was hang. I got the
>> following messages.
>> 
>>    Uncompressing Kernel Image ... OK
>>    Booting using flat device tree at 0x600000. 
>> 
>>        Then i tried to debug with GDB. In my source path i 
>> given the command
>> ${CROSS_COMPILE}gdb vmlinux, I got GDB Prompt after i tried to set the
>> breakpoint at start_kernel. I got follwing messages
>> 
>> gdb) b start_kernel
>> Cannot access memory at address 0xc02b44ec
>> 
>> Processor Information:
>> 8641D processor and the silicon revision is 2.0.
>> Part : MPC8641D
>> Revision:  2.0
>> e600 Core Revision:  2.2
>> DeviceMarking:  B
>> Processor Version Register Value: 0x8004_0202
>> System Version Register Value:   0x8090_0120
>> 
>>      I don't know how to proceed. Please tell the way how to 
>> start kernel
>> debug in this situation.
>> 
>> By
>> Sivaji
>> -- 
>> View this message in context: 
>> http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf44335
>> 08.html#a12648489
>> Sent from the linuxppc-dev mailing list archive at Nabble.com.
>> 
>> _______________________________________________
>> Linuxppc-dev mailing list
>> Linuxppc-dev@ozlabs•org
>> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 
> 

-- 
View this message in context: http://www.nabble.com/2.6.23-rc3-boot-hang-on-MPC8641D-tf4433508.html#a12648696
Sent from the linuxppc-dev mailing list archive at Nabble.com.

  reply	other threads:[~2007-09-13  4:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13  4:18 2.6.23-rc3 boot hang on MPC8641D sivaji
2007-09-13  4:25 ` Kumar Gala
2007-09-13  4:47   ` sivaji
2007-09-13  5:13     ` Kumar Gala
2007-09-13  5:59       ` Michael Ellerman
2007-09-13  4:38 ` Zhang Wei-r63237
2007-09-13  4:52   ` sivaji [this message]
2007-09-13  5:11     ` Kumar Gala
2007-09-13  5:19       ` Zhang Wei-r63237
2007-09-13  5:32         ` sivaji
2007-09-13  6:46           ` Zhang Wei-r63237
2007-09-14 14:25             ` sivaji
2007-09-13  5:24       ` sivaji
2007-09-13  5:29         ` David Gibson

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=12648696.post@talk.nabble.com \
    --to=rameshmrm@gmail$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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