From: Anatolij Gustschin <agust@denx.de>
To: Jean-Michel Hautbois <jhautbois@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [MPC8272ADS]Cannot start my Linux Kernel
Date: Thu, 15 Jan 2009 15:25:36 +0100 [thread overview]
Message-ID: <496F4760.1010007@denx.de> (raw)
In-Reply-To: <8cad0aa0901150510o7a8146f1m2045e252c5e1cf24@mail.gmail.com>
Jean-Michel Hautbois wrote:
> I just tried. I created a dtb from the file
> arch/powerpc/boot/dst/mpc8272ads.dts file.
> It is not rebboting, but handling (my "run" led is switching off).
>
> => tftp 2000000 mpc8272ads.dtb
> Using FCC1 ETHERNET device
> TFTP from server 10.0.0.1; our IP address is 10.0.0.2
> Filename 'mpc8272ads.dtb'.
> Load address: 0x2000000
> Loading: #
> done
> Bytes transferred = 4442 (115a hex)
> => bootm FF800000 FF980000 2000000
> ## Booting kernel from Legacy Image at ff800000 ...
> Image Name: Linux-2.6.29-rc1-01197-g5a7b6e7-
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size: 1487167 Bytes = 1.4 MB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at ff980000 ...
> Image Name: Simple Embedded Linux Framework
> Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
> Data Size: 1730966 Bytes = 1.7 MB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> ## Flattened Device Tree blob at 02000000
> Booting using the fdt blob at 0x2000000
> Uncompressing Kernel Image ... OK
> Loading Ramdisk to 039d7000, end 03b7d996 ... OK
> Loading Device Tree to 007fb000, end 007ff159 ... OK
> Unable to update property /cpus/cpu@0:bus-frequency, err=FDT_ERR_NOTFOUND
> Unable to update property /cpus/cpu@0:timebase-frequency,
> err=FDT_ERR_NOTFOUND
> Unable to update property /cpus/cpu@0:clock-frequency, err=FDT_ERR_NOTFOUND
try to fix "ft_cpu_setup()" in your u-boot source for mpc8272ads
and use "PowerPC,8272@0" as cpu_path instead of "cpu@0".
Best regards,
Anatolij
next prev parent reply other threads:[~2009-01-15 14:25 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 [this message]
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
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=496F4760.1010007@denx.de \
--to=agust@denx.de \
--cc=jhautbois@gmail.com \
--cc=linuxppc-dev@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).