public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot-ti next updated
Date: Mon, 12 Oct 2009 16:41:44 +0200	[thread overview]
Message-ID: <4AD34028.8010805@googlemail.com> (raw)
In-Reply-To: <5e088bd90910110815h5dbb70f3hafb2867a26bca352@mail.gmail.com>

Steve Sakoman wrote:
> On Sun, Oct 11, 2009 at 7:16 AM, Steve Sakoman <sakoman@gmail.com> wrote:
> 
>> Compile and run test of the Overo build was fine with Tobi card.
>> Later today I will try some of the other daughter cards to make sure
>> it works with all of them.
> 
> Heh, I spoke too soon!
> 
> U-boot appeared to run fine, but it fails in it's main mission in life
> -- to load & execute the linux kernel.
> 
> Overo hangs after the uncompressing kernel message.

Hmm, on beagle it seems to be fine, though.

g78c38ce (see below) is recent head of u-boot-ti/next:

http://git.denx.de/?p=u-boot/u-boot-ti.git;a=commit;h=78c38ce87f7423eedba844e8594cfc5a4fa6051b

Best regards

Dirk

...

U-Boot 2009.08-00514-g78c38ce (Oct 12 2009 - 16:30:03) 

 

OMAP3530-GP ES2.0, CPU-OPP2 L3-165MHz 

OMAP3 Beagle board + LPDDR/NAND 

I2C:   ready 

DRAM:  128 MB 

NAND:  256 MiB 

In:    serial 

Out:   serial 

Err:   serial 

Board revision Ax/Bx 

Die ID #00000000000000000000000000000000 

Hit any key to stop autoboot:  0 

mmc1 is available 

reading uImage 

 

1824144 bytes read 

## Booting kernel from Legacy Image at 80000000 ... 

    Image Name:   Linux-2.6.28-omap1 

    Image Type:   ARM Linux Kernel Image (uncompressed) 

    Data Size:    1824080 Bytes =  1.7 MB 

    Load Address: 80008000 

    Entry Point:  80008000 

    Verifying Checksum ... OK 

    Loading Kernel Image ... OK 

OK 

 

Starting kernel ... 

 

Uncompressing 
Linux....................................................................................................
Linux version 2.6.28-omap1 (kaltsi at kaltsbuntu) (gcc version 4.2.1) #1 
Fri Mar 13 12:58:49 EET 2009
CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=10c5387f 

CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache 

Machine: OMAP3 Beagle Board
...

  parent reply	other threads:[~2009-10-12 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 19:38 [U-Boot] u-boot-ti next updated Paulraj, Sandeep
2009-10-11  7:53 ` Dirk Behme
2009-10-11 14:16 ` Steve Sakoman
2009-10-11 15:15   ` Steve Sakoman
2009-10-11 16:14     ` Paulraj, Sandeep
2009-10-12 14:41     ` Dirk Behme [this message]
2009-10-12 16:14       ` Nishanth Menon
2009-10-11 15:59   ` Tom Rix

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=4AD34028.8010805@googlemail.com \
    --to=dirk.behme@googlemail.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