linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Michel Hautbois <jhautbois@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [MPC8272ADS]Cannot start my Linux Kernel
Date: Tue, 20 Jan 2009 11:56:58 +0100	[thread overview]
Message-ID: <8cad0aa0901200256n6122d17eh90f56e9cb8cae775@mail.gmail.com> (raw)
In-Reply-To: <4970CBA9.60809@freescale.com>

2009/1/16 Scott Wood <scottwood@freescale.com>:
> Jean-Michel Hautbois wrote:
>>
>> OK, I just tried a make of my kernel (already compiled yesterday), and
>> it generated a cuImage.mpc8272ads kernel image (which it didn't do
>> yesterday).
>> I don't know why this image was generated, but I tried to reboot using
>> this one.
>
> Use uImage if you are providing a device tree from u-boot.  cuImage is fo=
r
> older u-boots that don't support this, though you could still try using i=
t
> on a modern u-boot with a one- or two-argument bootm command to try to
> isolate the problem.
>
> -Scott
>

OK, I just tried a cuImage and a ramdisk without a FDT. I am starting
to boot, but it freezes. Following is the boot evolution.

Thx & Regards,
JM

bootm 1000000 2000000
## Booting kernel from Legacy Image at 01000000 ...
   Image Name:   Linux-2.6.29-rc1-01197-g5a7b6e7-
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1529877 Bytes =3D  1.5 MB
   Load Address: 00400000
   Entry Point:  00400b94
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02000000 ...
   Image Name:   Sofrel RAM Disk
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    3130063 Bytes =3D  3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
   Loading Ramdisk to 03882000, end 03b7e2cf ... OK
Memory <- <0x0 0x4000000> (64MB)
ENET0: local-mac-address <- 00:04:9f:11:22:33
ENET1: local-mac-address <- 00:00:00:00:00:00
CPU clock-frequency <- 0x17d78400 (400MHz)
CPU timebase-frequency <- 0x17d7840 (25MHz)
CPU bus-frequency <- 0x5f5e100 (100MHz)

zImage starting: loaded at 0x00400000 (sp: 0x03b7ebe8)
Allocating 0x329908 bytes for kernel ...
gunzipping (0x00000000 <- 0x0040d000:0x007591d8)...done 0x308b0c bytes
Using loader supplied ramdisk at 0x3882000-0x3b7e2cf
initrd head: 0x1f8b0800

Linux/PowerPC load: root=3D/dev/ram rw
Finalizing device tree... flat tree at 0x767300
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:setio
MMU:exit
Using Freescale MPC8272 ADS machine description
Linux version 2.6.29-rc1-01197-g5a7b6e7-dirty (dev@gforge) (gcc
version 4.2.2) #2 Thu Jan 15 18:31:04 CET 2009
Found initrd at 0xc3882000:0xc3b7e2cf
console [udbg0] enabled
setup_arch: bootmem
mpc8272_ads_setup_arch()
PCI host bridge /pci@f0010800 (primary) ranges:
 MEM 0x0000000080000000..0x000000009fffffff -> 0x0000000080000000 Prefetch
 MEM 0x00000000a0000000..0x00000000bfffffff -> 0x00000000a0000000
  IO 0x00000000f6000000..0x00000000f7ffffff -> 0x0000000000000000
mpc8272_ads_setup_arch(), finish
arch: exit
Top of RAM: 0x4000000, Total RAM: 0x4000000
Memory hole size: 0MB
Zone PFN ranges:
  DMA      0x00000000 -> 0x00004000
  Normal   0x00004000 -> 0x00004000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00004000
On node 0 totalpages: 16384
free_area_init_node: node 0, pgdat c02ffc90, node_mem_map c0330000
  DMA zone: 128 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 16256 pages, LIFO batch:3
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: root=3D/dev/ram rw
PID hash table entries: 256 (order: 8, 1024 bytes)
time_init: decrementer frequency =3D 25.000000 MHz
time_init: processor frequency   =3D 400.000000 MHz
clocksource: timebase mult[a000000] shift[22] registered
clockevent: decrementer mult[666] sh=EF=BF=BD

  parent reply	other threads:[~2009-01-20 11:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 11:42 [MPC8272ADS]Cannot start my Linux Kernel Jean-Michel Hautbois
2009-01-15 12:52 ` Anatolij Gustschin
2009-01-15 13:10   ` Jean-Michel Hautbois
2009-01-15 14:25     ` Anatolij Gustschin
2009-01-15 15:06       ` Jean-Michel Hautbois
2009-01-16 12:06         ` Jean-Michel Hautbois
2009-01-16 17:29           ` Scott Wood
2009-01-16 17:40             ` Jean-Michel Hautbois
2009-01-16 17:44             ` Jean-Michel Hautbois
2009-01-16 17:53               ` Jean-Michel Hautbois
2009-01-16 18:02                 ` Scott Wood
2009-01-16 18:23                   ` Jean-Michel Hautbois
2009-01-20 10:56                   ` Jean-Michel Hautbois [this message]
2009-01-20 16:27                     ` Jean-Michel Hautbois
2009-01-20 17:51                       ` Scott Wood
2009-01-20 16:31                     ` Scott Wood
2009-01-20 17:05                       ` Jean-Michel Hautbois
2009-01-20 17:16                         ` Scott Wood
2009-01-20 17:32                           ` Jean-Michel Hautbois
2009-01-20 17:35                             ` Scott Wood
2009-01-21 15:42                       ` jeff angielski
2009-01-21 16:15                         ` Jean-Michel Hautbois
2009-01-22  2:15                       ` Daniel Ng99
2009-01-22 17:36                         ` Scott Wood
2009-01-23  0:21                           ` Daniel Ng99
2009-01-23  0:46                             ` Daniel Ng99
2009-01-23 16:17                             ` Scott Wood
2009-01-22  2:17                       ` Daniel Ng99

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=8cad0aa0901200256n6122d17eh90f56e9cb8cae775@mail.gmail.com \
    --to=jhautbois@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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).