public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot for AMCC Sequoia Board (PPC440EPX) fails to boot for version 2009.11-rc1 onwards
Date: Fri, 9 Sep 2011 08:30:21 +0200	[thread overview]
Message-ID: <201109090830.22072.sr@denx.de> (raw)
In-Reply-To: <39A385F269A9E349AA6606AD4E327D76021F857B2D@BEL1EXCH02.amer.sfnt.local>

Hi Doug,

On Thursday 08 September 2011 22:24:51 Hayes,Doug wrote:
> Has anyone tried the latest U-Boot on the above board lately?  I am
> building the U-Boot image with "sequoia_config" option and have found it
> stops booting after version 2009_08.  I get no text output for the
> versions that I have tried:  2009.11-rc1, 2009.11, 2010.03. latest
> (2011.06).  There were a lot of "4xx" changes in 2009.11-rc1 so perhaps
> one of those has changed how my board comes up.  I am just starting to
> compare code files for differences in order to track it down.
> 
> I am compiling with this ELDK "gcc version 4.0.0 (DENX ELDK 4.1.4.0.0)".
> 
> I anyone has an idea why my U-Boot hangs please let me know.  Thanks for
> any info.

I do test on Sequoia from time-to-time. No problems here:

U-Boot 2011.06-00588-g49ea2e3 (Sep 09 2011 - 08:20:40)

CPU:   AMCC PowerPC 440EPx Rev. A at 330 MHz (PLB=132 OPB=66 EBC=66 PCI=33 
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-Async=33 MHz
I2C:   ready
DRAM:  256 MiB
Flash: 64 MiB
NAND:  32 MiB
PCI:   Bus Dev VenId DevId Class Int
USB:   Host(int phy) Device(ext phy)
Net:   ppc_4xx_eth0, ppc_4xx_eth1

Type run flash_nfs to mount root filesystem over NFS

Hit any key to stop autoboot:  0 
=> 


This is with ELDK 4.2 (GCC 4.2.2).


On Thursday 08 September 2011 23:31:18 Hayes,Doug wrote:
> Some extra info.  U-Boot dies in get_async_pci_freq() (new feature) called
> from board_early_init_f() when trying to read a byte from 0xC0000005
> (CONFIG_SYS_BCSR_BASE + 5).

Perhaps your board is too old and doesn't support reading these CPLD 
registers. On mine I get:

=> md.b c0000000 20
c0000000: 0f 00 c0 07 00 00 00 80 00 20 00 00 00 00 00 00    ......... ......
c0000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

What do you get on your "old", working U-Boot?


Best regards,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2011-09-09  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 20:24 [U-Boot] U-Boot for AMCC Sequoia Board (PPC440EPX) fails to boot for version 2009.11-rc1 onwards Hayes, Doug
2011-09-09  6:30 ` Stefan Roese [this message]
     [not found]   ` <39A385F269A9E349AA6606AD4E327D76021F857DD1@BEL1EXCH02.amer.sfnt.local>
2011-09-09 14:37     ` Stefan Roese
2011-09-09 20:04       ` Hayes, Doug
2011-09-13  8:10         ` Stefan Roese
2011-09-15 15:08           ` Hayes, Doug
  -- strict thread matches above, loose matches on Subject: below --
2011-09-08 21:31 Hayes, Doug

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=201109090830.22072.sr@denx.de \
    --to=sr@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