public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] need your help
Date: Tue, 15 Feb 2011 18:43:33 +0100	[thread overview]
Message-ID: <20110215174333.7C05F151B54@gemini.denx.de> (raw)
In-Reply-To: <44e92e.98dc.12e2a003bb1.Coremail.huan_t@163.com>

Dear nice,

In message <44e92e.98dc.12e2a003bb1.Coremail.huan_t@163.com> you wrote:
>
> Please help.I have a custom board with a mpc8641d processer,
> I compiled the u-boot using the configuration of sbc8641d board ,

You cannot use one configuration for a completely different bord - not
even when you think they are pretty similar. This does not work.

> then I flashed the u-boot.bin into flash, everything seems to
> be fine so far. Then I compiled the kernel image and dts file with

Everything seems to be fine, but only because you close both your eyes
and ignore all the errors.

> U-Boot 2010.12-rc1 (Jan 30 2011 - 09:32:35)

This is old code. Why don't you use current one.

> CPU:   8641D, Version: 2.1, (0x80900121)
> Core:  E600 Core 0, Version: 2.2, (0x80040202)
> Clock Configuration:
>        CPU:1200 MHz, MPX:400  MHz
>        DDR:200  MHz (400 MT/s data rate), LBC:25   MHz
> L1:    D-cache 32 KB enabled
>        I-cache 32 KB enabled
> L2:    512 KB enabled
> Board: Wind River SBC8641D
> I2C:   ready
> DRAM:      DDR: 512 MiB
> FLASH: ERROR: too many flash sectors

Here is a clear error message. Why do you say "everything seems to be
fine" ?

> Net:   eTSEC2: No support for PHY id ffffffff; assuming generic
> eTSEC3: No support for PHY id ffffffff; assuming generic
> eTSEC4: No support for PHY id ffffffff; assuming generic

Here are more errors.

> ## Flattened Device Tree blob at 00400000

This is a pretty low address. Eventyally the device tree blob gets
overwritten during uncompression.

> Call backtrace:
> 001A001A 1FECD4D0 1FEE9E98 1FEE9FC4 1FED9600 1FED99E4 1FEE5AB0
> 1FEE51C4 1FEE5410 1FEE59EC 1FEE51C4 1FEE53E4 1FEE6AF0 1FEE5AB0
> 1FEE51C4 1FEE5334 1FEE6F80 1FED0CC8 1FEC957C Machine check in kernel mode.

Did you attempt to decode the backtrace?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"This isn't brain surgery; it's just television."   - David Letterman

  reply	other threads:[~2011-02-15 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 15:46 [U-Boot] need your help nice
2011-02-15 17:43 ` Wolfgang Denk [this message]
2011-02-16  4:02   ` Zang Roy-R61911
     [not found] <EC921D4B77C99B4EB3CEDAFFCF17D5F72F2949D4A2@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
2010-07-09 13:29 ` [U-Boot] Need Your Help Marek Vasut

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=20110215174333.7C05F151B54@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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