From: "Chris Down" <chris@alcor.co.uk>
To: <linuxppc-embedded@ozlabs.org>
Subject: Problem bringing up Linux on Custom MPC522 Board
Date: Fri, 12 Nov 2004 11:00:44 -0000 [thread overview]
Message-ID: <004201c4c8a6$db904cd0$0101a8c0@alcor1> (raw)
I am trying to bring up Linux (latest linuxppc-2.4 tree) on a custom =
MPC852
Board. The board has 8MByte SDRAM and 8MByte Flash.=20
I have ported u-boot, modified Linux to add a new board config and added =
the
board specific definitions in arch/ppc/platforms.=20
U-Boot and Linux were built using the ppc_8xx compiler from ELDK 3.0.
When I boot Linux I get the following:-
## Booting image at 00100000 ...
Image Name: Linux-2.4.28-pre3-cdd1
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 664920 Bytes =3D 649.3 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.28-pre3-cdd1 (chris@alioth) (gcc version 3.2.2 =
20030217 (Yello
w Dog Linux 3.0 3.2.2-2a_1)) #3 Fri Nov 12 09:46:59 GMT 2004
On node 0 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line:
Decrementer Frequency =3D 187500000/60
Calibrating delay loop... 49.76 BogoMIPS
Memory: 6508k available (1176k kernel code, 344k data, 56k init, 0k =
highmem)
Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
POSIX conformance testing by UNIFIX
At this point it stops executing in arch_kernel_thread.
As I am new to this I could do with some pointers as to what to do next. =
Any
help would be gratefully appreciated.
Regards
Chris Down
reply other threads:[~2004-11-12 11:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='004201c4c8a6$db904cd0$0101a8c0@alcor1' \
--to=chris@alcor.co.uk \
--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 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).