linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "yydsr" <yydsr@163.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: About IBM  Walnut405GP  Problem.
Date: Fri, 27 Dec 2002 09:59:35 +0800 (CST)	[thread overview]
Message-ID: <3E0BB407.000043.10611@bj244.163.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2624 bytes --]


Hi,
    hello!
    I'm trying to get a walnut board booted. I'm using linuxppc_2_4_devel pulled from denx yesterday. I'm getting the "Real time clock seems stuck" message then nothing, no messages after that. I found a brief thread about this.

http://lists.linuxppc.org/linuxppc-embedded/200106/msg00113.html

Have the changes suggested been put in the devel tree? If so, can someone offer some advice on how to proceed?

Here's some console output.

PPCBoot 2.0.0
CPU: IBM PowerPC 405GP Rev. D at 200 MHz (PLB=100, OPB=50, EBC=50 MHz)
PCI sync clock at 33 MHz, internal PCI arbiter enabled
16 kB I-Cache 8 kB D-Cache
Board: ### No HW ID - assuming WALNUT405
I2C: ready
DRAM: 32 MB
FLASH: 512 kB
In: serial
Out: serial
Err: serial
KGDB: kgdb ready
ready
BEDBUG:ready

=> tftpboot 400000 p1
ENET Speed is 100 Mbps - FULL duplex connection
ARP broadcast 1
TFTP from server 192.168.1.11; our IP address is 192.168.1.111
Filename 'p1'.
Load address: 0x400000
Loading: #################################################################
############################################
done
Bytes transferred = 557872 (88330 hex)
=> imi 400000

## Checking Image at 00400000 ...
Image Name: Linux-2.4.20-pre11
Created: 2002-10-31 12:17:56 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 557808 Bytes = 544.7 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
=> bootm 400000
## Booting image at 00400000 ...
Image Name: Linux-2.4.20-pre11
Created: 2002-10-31 12:17:56 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 557808 Bytes = 544.7 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.20-pre11 (root@tbdev1) (gcc version 2.95.4 20010319 (prerelease/franzo/20011204)) #12 Thu Oct 31 05:13:53 MST 2002
IBM Walnut port (C) 2000-2002 MontaVista Software, Inc. (source@mvista.com)
On node 0 totalpages: 1295
zone(0): 1295 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0,9600 root=/dev/ram
Warning: real time clock seems stuck!



then nothing after that.

Any ideas? I've searched the archives for walnut boot problems. It seems like most people just get it running and that's that.



thank you.


yydsr@163.com

=============================================================
Ôªµ©¡¢ÇéÈ˽ڲ»ÔÙ×ö¹Â¶ÀÈË!Ä㻹²»¿ìÀ´Ô¼»á£¿	http://dating.163.com/
ÍøÒ×¾ãÀÖ²¿ÎªÄ㽨ÔìÒ»¸ö³¬¼¶µÄ˽ÈËÉçÇø£¡		http://our.163.com
ÐÂÄêÓÐÀñ£¡ VIPÓÊÏäÒ²¿ÉÒÔÃâ·ÑÓã¡		http://vip.163.com/payment/MobilePayment.shtml


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

             reply	other threads:[~2002-12-27  1:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27  1:59 yydsr [this message]
2002-12-27  8:57 ` About IBM Walnut405GP Problem 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=3E0BB407.000043.10611@bj244.163.com \
    --to=yydsr@163.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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).