linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Yuji Nishimura <yujin@pp.iij4u.or.jp>
Cc: emanuel stiebler <emu@ecubics.com>,
	linux-emb <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: kernel boot on mpc8245
Date: Wed, 05 Mar 2003 10:17:57 -0700	[thread overview]
Message-ID: <3E663145.7060605@mvista.com> (raw)
In-Reply-To: <3E662D79.9030904@pp.iij4u.or.jp>


My recommendation for a first step is to look at your printk data. You
didn't miss a flag, you're simply crapping out before the console is set
up to dump out the printk data.

Go into the System.map file associated with the kernel your running,
search for 'log_buf', subtract 0xc0000000 to get the physical addr of
'log_buf', hook up a BDI or something similar (and hopefully, your board
has an appropriate connector), and dump the [printk] data at that address.

Mark
--

Yuji Nishimura wrote:

>Hi,
>
>I was some experience for similar problem on past time. It was happened
>on kernel porting process (to other board).
>For my problem, It caused by ppc_md.calibrate_decr =
>todc_calibrate_decr; . i forgot to initialize external real time clock(
>so rtc was stopped). that means it does not work and stop on same
>point.... If you use another calibrate_decr (based on bus clock or
>another clock), maybe it caused by other problem...
>
>Best Regards,
>Yuji Nishimura - Tokyo, Japan.
>
>
>
>
>emanuel stiebler wrote:
>
>
>
>>Hi,
>>I have a board which is close to Sandpoints mpc8245 cpu board.
>>(using internal DUARTs, EPIC_MODE_SERIAL)
>>
>>Trying to get it working, I got until:
>>
>>Filename 'pImage'.
>>Load address: 0x1000000
>>Loading: ################################T ###################T
>>##############
>>###T
>>##############################################################
>>##T #########################
>>done
>>Bytes transferred = 801369 (c3a59 hex)
>>=> bootm 1000000
>>## Booting image at 01000000 ...
>>Image Name: Linux-2.4.20
>>Created: 2003-03-04 23:57:29 UTC
>>Image Type: PowerPC Linux Kernel Image (gzip compressed)
>>Data Size: 801305 Bytes = 782 kB = 0 MB
>>Load Address: 00000000
>>Entry Point: 00000000
>>Verifying Checksum ... OK
>>Uncompressing Kernel Image ... OK
>>id mach(): done
>>MMU:enter
>>MMU:hw init
>>MMU:mapin
>>MMU:mapin_ram done
>>MMU:setio
>>MMU:exit
>>setup_arch: enter
>>setup_arch: bootmem
>>mpc10x:enter
>>mpc10x:exit
>>arch: exit
>>openpic: enter
>>openpic: timer
>>openpic: external
>>openpic: spurious
>>openpic: exit
>>
>>
>>then it stops. Any idea what it is waiting for ?
>>
>>And another question, I don't see any of the "printk ()" outputs I put
>>in the code, did I missed a flag ?
>>
>>Cheers & thanks for any help
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-03-05 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05  0:25 kernel boot on mpc8245 emanuel stiebler
2003-03-05 17:01 ` Yuji Nishimura
2003-03-05 17:17   ` Mark A. Greer [this message]
2003-03-05 18:04     ` emanuel stiebler
2003-03-05 21:35   ` kernel boot on mpc8245, internal UART emanuel stiebler

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=3E663145.7060605@mvista.com \
    --to=mgreer@mvista.com \
    --cc=emu@ecubics.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=yujin@pp.iij4u.or.jp \
    /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;
as well as URLs for NNTP newsgroup(s).