public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: zhenhuan <dev_du@163.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Questions about U-boot of customized MPC8315E board
Date: Fri, 26 Apr 2013 12:42:52 +0800	[thread overview]
Message-ID: <517A05CC.60003@163.com> (raw)
In-Reply-To: <20130425193626.0BC7E38489C@gemini.denx.de>

Hi,
About  debug,
Where should I define the macro to enable debug() function definition?
Is there a place in makefile or head file?

On 2013/4/26 3:36, Wolfgang Denk wrote:
> Dear "du zhenhuan",
>
> In message <202dafde.df1f.13e4197224a.Coremail.dev_du@163.com> you wrote:
>> 1, if NAND flash support is enabled,
>> U-boot just print out  "NAND : "  without size info and then print out text like "machine check ...,",
>>   then print out "resetting board ..."
>> So the board keep resetting again and again.
>> Does this  have anything to do with NAND FLASH size change or  NAND PART types?
> It has probably nothing to do with the NAND flash size, but with the
> NAND chip type, and/or with other changes you did for your port.
>
>> 2.if NAND flash support is disabled,
>>   U-boot just go to Ethernet PHY  initialization part and print out that DP83848 is not supported ,
>> Where can I put new driver to support it?
> PHY support is in drivers/net/phy/
>
> Are you sure generic PHY support does not work for you?
>
>> 3.How can I watch more ouput infomation during U-boot boot process to debug these problems ?
> Define DEBUG for the interesting files?
>
> Attach a JTAG debugger und fire up GDB?
>
> Best regards,
>
> Wolfgang Denk
>

  reply	other threads:[~2013-04-26  4:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 14:27 [U-Boot] Questions about U-boot of customized MPC8315E board du zhenhuan
2013-04-25 19:36 ` Wolfgang Denk
2013-04-26  4:42   ` zhenhuan [this message]
2013-04-26  7:05     ` Wolfgang Denk
2013-05-21 22:03 ` Scott Wood

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=517A05CC.60003@163.com \
    --to=dev_du@163.com \
    --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