[ELDK] Want to build a ebc.ko object

[Price, John @ SDS]

I printed out the bootcmd and arguments.  Not sure what an device tree
blob is?

 

=> print bootcmd

bootcmd=run flash_self

 

=> print flash_self

flash_self=run ramargs addmtd setip addip addtty;bootm ${kernel_addr}
${ramdisk_addr}

 

=> print ramargs

ramargs=setenv bootargs ramdisk=65536 root=/dev/ram rw

 

=> print addmtd

addmtd=setenv bootargs ${bootargs}
mtdparts=physmap-flash.0:2M(linux),20M(ramdisk),4M(jffs2),38272k(user),2
56k(env),384k(uboot)

 

=> print setip

setip=echo Using ip address ${ipaddr}

 

=> print addip

addip=setenv bootargs ${bootargs}
ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:o
ff panic=1

 

=> print addtty

addtty=setenv bootargs ${bootargs} console=ttyS0,${baudrate}

 

=> print kernel_addr

kernel_addr=fc000000

 

=> print ramdisk_addr

ramdisk_addr=fc200000

 

=> imls

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

Image at FC200000:

   Image Name:   Simple Embedded Linux Framework

   Created:      2008-02-22  11:58:24 UTC

   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)

   Data Size:    1856970 Bytes =  1.8 MB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

=>

 

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: Tuesday, March 25, 2008 12:30 PM
To: Price, John @ SDS
Cc: eldk at lists.denx.de
Subject: Re: [ELDK] Want to build a ebc.ko object

 

In message
<B9639434CFA424438117913649CDB78704E37823 at MA_EXCHANGE.corp.sds.l-3com.co
m> you wrote:

> 

> >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"

 

Yes, you said that, and I wrote that you did not show us yoru boot

command.

 

And I tell you that nobody will be able you when you fail to provide

the information we ask for.

 

> Nothing more came out on the console.

 

Then you might try to interrupt the boot process by  pressing  a  key

and then print the bootcmd variable?

 

> The command line passed to Linux works for the original version.  I

> would expect it to also work for the newer version.

 

I have no idea what "original version" might be, but no - if that was

a arch/ppc kernel and now it's arch/powerpc, then it will NOT work.

 

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

> tree lob?

> 

> Hmm, is there somewhere else to look when the kernel misbehaves, that
is

> other than the console?

 

It would help if you answered the question.

 

Also, you did not comment if you loaded and passed a device tree blob?

 

> -----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

 

And please, don't full-quote / top-post.

 

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

A mouse is an elephant built by the Japanese.