public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Ethernet POST freeze on 440EPx boards (PMC440, sequoia)
Date: Wed, 04 Jun 2008 12:03:29 +0200	[thread overview]
Message-ID: <m2lk1lbjpq.fsf@ohwell.denx.de> (raw)
In-Reply-To: <200806021101.16979.matthias.fuchs@esd-electronics.com> (Matthias Fuchs's message of "Mon, 2 Jun 2008 11:01:16 +0200")

Hi Matthias,

> I noticed some strange issues with our PMC440 (PPC440PEx based) board and
> also with the sequoia eval platform.
>
> In a certain configuration these boards stuck during the Ethernet POST tests.
> When they got stuck, it is even not possible to attach with a BDI2000.

Oh, this hints to some deeper problems, so maybe one should check all
erratas (again).

> On the console you only see this:
>
> U-Boot 1.3.1 (May 30 2008 - 17:01:42)
>
> CPU: ? AMCC PowerPC 440EPx Rev. A at 533.333 MHz (PLB=133, OPB=66, EBC=66 MHz)
> ? ? ? ?Security/Kasumi support
> ? ? ? ?Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
> ? ? ? ?Internal PCI arbiter enabled, PCI async ext clock used
> ? ? ? ?32 kB I-Cache 32 kB D-Cache
> Board: Sequoia - AMCC PPC440EPx Evaluation Board, Rev. F, PCI=33 MHz
> I2C: ? ready
> DTT: ? 1 is 38 C
> DRAM: ?256 MB
> FLASH: 64 MB
> NAND: ?32 MiB
> PCI: ? Bus Dev VenId DevId Class Int
> ? ? ? ? 00 ?0c ?168c ?0013 ?0200 ?43
> In: ? ?serial
> Out: ? serial
> Err: ? serial
> USB: ? Host(int phy) Device(ext phy)
> Net: ? ppc_4xx_eth0, ppc_4xx_eth1
>

[...]

> Did anybody else see this behavior? 

The last time I had problems looking similar to what you see, these two
commits from Anatolij solved my problems:

commit 5e3dca577b7c1bf58bd2b48449b18b7e7dcd8e04
Author: Anatolij Gustschin <agust@denx.de>
Date:   Thu Apr 17 18:18:00 2008 +0200

    Fix crash on sequoia in ppc_4xx_eth_init
    
    Currently U-Boot crashes in ppc_4xx_eth_init on sequoia
    with cache enabled (TLB Parity exeption). This patch
    fixes the problem.
    
    Signed-off-by: Anatolij Gustschin <agust@denx.de>

commit accf7355767dc7f6b85d88bb1c75c9d95e84ba5b
Author: Anatolij Gustschin <agust@denx.de>
Date:   Thu Apr 17 18:15:27 2008 +0200

    ppc4xx: Fix crash on sequoia with cache enabled
    
    Currently U-Boot crashes on sequoia board in CPU POST if
    cache is enabled (CONFIG_4xx_DCACHE defined). The cache
    won't be disabled by change_tlb before CPU POST because
    there is an insufficient adress range check since
    CFG_MEM_TOP_HIDE was introduced. This patch tries to fix
    this problem.
    
    Signed-off-by: Anatolij Gustschin <agust@denx.de>

Cheers
  Detlev

-- 
But in terms of creative  information, information that people can use
or enjoy, and that will be  used and enjoyed more  the more people who
have it, always we should encourage the copying.
	                                    -- Richard M. Stallman
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

      reply	other threads:[~2008-06-04 10:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02  9:01 [U-Boot-Users] Ethernet POST freeze on 440EPx boards (PMC440, sequoia) Matthias Fuchs
2008-06-04 10:03 ` Detlev Zundel [this message]

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=m2lk1lbjpq.fsf@ohwell.denx.de \
    --to=dzu@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