All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: jcherukuri_necc@yahoo.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: problems loading 2.6.25 kernel onto PQ2FADS-VR board
Date: Wed, 12 Nov 2008 15:26:46 -0600	[thread overview]
Message-ID: <491B4A16.5090803@freescale.com> (raw)
In-Reply-To: <204868.67373.qm@web110312.mail.gq1.yahoo.com>

Jyotshna Cherukuri wrote:
> Bytes transferred = 12288 (3000 hex)
> => bootm 400000 - 800000
> ## Booting image at 00400000 ...
>    Image Name:   Linux-2.6.25
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    1624845 Bytes =  1.5 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
>    Booting using the fdt at 0x800000
>    Loading Device Tree to 007fc000, end 007fefff ... OK
> 
> And Then it stops. The board doesn't print anything else. Can anyone 
> please help me to whats going on and to what I need to  enable to see 
> some debug info on the serial port ( minicom in my case ).
> 
> P.S :  I did enable all the early level debugging in the kernel but yet 
> I dont see anything on the console.

Make sure that CONFIG_PPC_EARLY_DEBUG_CPM_ADDR is set properly for 
u-boot; it probably wants 0xf0000088.  The default vaule corresponds to 
cuImage.

If that doens't help, try booting the cuImage (without passing a device 
tree from u-boot); it's what I tested with as there was no device tree 
aware u-boot for this board at the time.  If that works and uImage 
doesn't, then there may be a mismatch between what u-boot is setting up 
in the device tree and what the kernel expects.

-Scott

      reply	other threads:[~2008-11-12 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 21:03 problems loading 2.6.25 kernel onto PQ2FADS-VR board Jyotshna Cherukuri
2008-11-12 21:26 ` Scott Wood [this message]

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=491B4A16.5090803@freescale.com \
    --to=scottwood@freescale.com \
    --cc=jcherukuri_necc@yahoo.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.