[ELDK] Want to build a ebc.ko object

[Price, John @ SDS]

>> I am able to build a uImage from your repository.  When I install the
>This statement is obviously wrong - it seems you can build new uImage
>files just fine, but they just don't run as expected...

I did say I could build a uImage from the repository.

>Unfortunately you fail to show us your boot command, 

I also said the last output on the console was;
	" Loading Ramdisk to 0ecf5000, end 0ff1f8df ... OK"

Nothing more came out on the console.

The command line passed to Linux works for the original version.  I
would expect it to also work for the newer version.

>but to me it seems as if you did not load (and pass to Linux) a device
tree >blob?

Hmm, is there somewhere else to look when the kernel misbehaves, that is
other than the console?

Regards,

---
John Price  <john.p.price at l-3com.com> 781-970-1743
L-3 Communications
Security & Detection Systems Division, 
10E Commerce Way, Woburn, MA 01801
 

-----Original Message-----
From: wd at denx.de [mailto:wd at denx.de] 
Sent: Monday, March 24, 2008 6:29 PM
To: Price, John @ SDS
Cc: eldk at lists.denx.de
Subject: Re: [ELDK] Want to build a ebc.ko object

Dear John,

in message
<B9639434CFA424438117913649CDB78704E3750A at MA_EXCHANGE.corp.sds.l-3com.co
m> you wrote:
> I am able to build a uImage from your repository.  When I install the

This statement is obviously wrong - it seems you can build new uImage
files just fine, but they just don't run as expected...

> new uImage file on the Kilauea evaluation board the last output says
> loading "ramdisk to xxx, end yyy ...OK" and that's it.
> 
> Are there some other dependencies that I am not aware of???  For
> instance is eldkv 4.2 ok or the original ramdisk image ok?

Yes, both have been tested and are known to work, at least in earlier
versions of the source tree.

>   WRAP    arch/powerpc/boot/uImage
> Image Name:   Linux-2.6.25-rc6-01253-gca0a328

Here you use a very recent (Sun Mar 23 16:34:41 2008 +0100) Linux
kernel over a ...

> U-Boot 1.3.1-g5dd372a2 (Jan 14 2008 - 11:01:38)

...not so recent (Mon Jan 14 10:48:28 2008 +0100) version of U-Boot.

> Hit any key to stop autoboot:  5 \0x08\0x08\0x08 4 \0x08\0x08\0x08 3
> \0x08\0x08\0x08 2 \0x08\0x08\0x08 1 \0x08\0x08\0x08 0 
> Using ip address 192.168.1.50
> ## Booting image at fc000000 ...
>    Image Name:   Linux-2.6.25-rc6-01253-gca0a328
>    Created:      2008-03-24  19:18:59 UTC
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    1555953 Bytes =  1.5 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> ## Loading RAMDisk Image at fc200000 ...
>    Image Name:   kilauea Ramdisk Rev 002
>    Created:      2008-01-15   0:20:02 UTC
>    Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
>    Data Size:    19048671 Bytes = 18.2 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Loading Ramdisk to 0ecf5000, end 0ff1f8df ... OK

Unfortunately you fail to show us your boot command, but to me it
seems as if you did not load (and pass to Linux) a device tree blob?

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
The joys of love made her human and the  agonies  of  love  destroyed
her.
	-- Spock, "Requiem for Methuselah", stardate 5842.8