RE: Simple experiment with, ML403, running 2.6 kernel , kernel.org source

RE: Simple experiment with, ML403, running 2.6 kernel , kernel.org source

[Mohammad Sadegh Sadri]

[-- Attachment #1: Type: text/plain, Size: 302 bytes --]


Peter This is my config file hope help. ... let me know if i can do any thing more for you.

_________________________________________________________________
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline

[-- Attachment #2: mvista-config.gz --]
[-- Type: application/x-gzip, Size: 3292 bytes --]

RE: Unable to Boot 2.6.19.2 from ELDK 4.1 on MPC8349E MDS

[Gary Kenaley]

I have been evaluating Freescale 2.6.11, Wind River 2.6.14, and am now
attempting Denx 2.6.19 (from ELDK 4.1) - running on the Rev 1.0 MPC8349E
MDS (V1.1 CPU). I boot 2.6.19.2 using the factory u-boot 1.1.3 and the
kernel immediately hangs:
Uncompressing Kernel Image ... OK {hangs forever}

The following boot arguments work when I swap in a Wind or Freescale
uImage in /tftpboot, so I know that the ELDK filesystem and devnodes are
okay:

bootargs=3Droot=3D/dev/nfs rw
nfsroot=3D10.2.11.175:/home/gkenaley/ELDK4.1/ppc_6xx
ip=3D10.2.11.184:10.2.11.175:10.2.0.1:255.255.128.0:83493mds2:eth0:off
console=3DttyS0,115200

I installed the ELDK 4.1 as per the instructions (including running the
FIX scripts) on a Red Hat 4 U4(2.6.9-42) PC host. I then ran these
commands on the host:
export
PATH=3D/home/gkenaley/ELDK4.1/usr/bin:/home/gkenaley/ELDK4.1/bin:$PATH
export CROSS_COMPILE=3Dppc_6xx-
export ARCH=3Dpowerpc
cd /home/gkenaley/ELDK4.1/ppc_6xx/usr/src/linux-2.6.19.2
${CROSS_COMPILE}make clean
${CROSS_COMPILE}make V=3D1 mpc834x_mds_defconfig
${CROSS_COMPILE}make V=3D1 all

cp -p
/home/gkenaley/ELDK4.1/ppc_6xx/usr/src/linux-2.6.19.2/arch/powerpc/boot/
uImage /tftpboot/

${CROSS_COMPILE}make V=3D1 =
INSTALL_MOD_PATH=3D/home/gkenaley/ELDK4.1/ppc_6xx
modules_install

Since the host depmod is not a cross version and segfaults, and the ELDK
versions refuse to run, I also ran:
perl /home/gkenaley/ELDK4.1/usr/bin/depmod.pl -v -F System.map -b
/home/gkenaley/ELDK4.1/ppc_6xx/lib/modules/2.6.19.2

At that point I u-boot the target and it hangs forever as shown above.
I did a lot of comparisons to the Wind and Freescale .config files and
also tried turning off CONFIG_PCI (since I have only the MDS processor
board), but it did not help solve the problem. I also tried running
xconfig and producing a more complete configuration, but the boot
process fails exactly the same way with that larger uImage.

I also tried a "full source rebuild from scratch" for the ELDK 4.1, but
I found that these SRPMS were originally misnamed (could not be found in
CVS, rpmfind, or the ELDK source CD-ROM) in
/home/gkenaley/ELDK/V4.1/build/SRPMS.lst:

#rpm-4.4.1-22_4.src.rpm
#httpd-2.0.54-10.2_2.src.rpm
#libtool-1.5.16.multilib2-2_2.src.rpm
#module-init-tools-3.1-4_1.src.rpm
#nfs-utils-1.0.7-12_3.src.rpm
#pam-0.79-9.5_2.src.rpm
#procps-3.2.5-6.3_2.src.rpm
#tar-1.15.1-10_2.src.rpm
#util-linux-2.12p-9.12_3.src.rpm

After correcting (?) SRPMS.lst to contain the names shown above, the
build ran for about 1/2 hour and then failed in rpm-4.4.1-22_4 with
various undefined references to ELF parameters.

Questions, please:
------------------
1. Should I expect this kernel to boot on the MPC8349E MDS, or do I need
to find and apply a variety of patches?

2. Any idea why I have problems doing the "ELDK 4.1 full source rebuild
from scratch"?

3. Do you see anything else important that I should change in my
process?

Since I am a bit of a newbie, I'll be grateful to get a lot of specific
advice.

Thanks, Gary

RE: Unable to Boot 2.6.19.2 from ELDK 4.1 on MPC8349E MDS

[Ben Warren]

Gary,

--- Gary Kenaley <gkenaley@echelon.com> wrote:

> I have been evaluating Freescale 2.6.11, Wind River
> 2.6.14, and am now
> attempting Denx 2.6.19 (from ELDK 4.1) - running on
> the Rev 1.0 MPC8349E
> MDS (V1.1 CPU). I boot 2.6.19.2 using the factory
> u-boot 1.1.3 and the
> kernel immediately hangs:
> Uncompressing Kernel Image ... OK {hangs forever}

This version of U-boot is very old.  It is too old to 
boot a Linux kernel that was built using ARCH=powerpc.
 
On to your questions...  
<snip>

> Questions, please:
> ------------------
> 1. Should I expect this kernel to boot on the
> MPC8349E MDS, or do I need
> to find and apply a variety of patches?
> 
This kernel will boot on this board (I have the same
board), but you need to do a few things:

1. Get the latest U-boot.  It's available via git
from:
git://www.denx.de/git/u-boot.git.
2. Get 'dtc', the device tree compiler.  It's
available at www.jdl.com
3. Compile the device tree file for your board, which
is in /arch/powerpc/boot/dts/mpc8349emds.dtc of the
Linux source.
4. From U-boot, load the .dtb file that was generated
in step 3 either into memory or flash.
5. Modify whatever U-boot command you're using to boot
Linux to call 'bootm <kernel address> - <dtb address>
6. Try to not get frustrated about this device tree
stuff.  It's not very well documented, but several
people recognize this and are working to remedy it.

> 2. Any idea why I have problems doing the "ELDK 4.1
> full source rebuild
> from scratch"?
> 
Can't comment.  I'm still on ELDK 4.0.
> 3. Do you see anything else important that I should
> change in my
> process?
> 
> Since I am a bit of a newbie, I'll be grateful to
> get a lot of specific
> advice.
> 
> Thanks, Gary

Feel free to ping the U-boot list if you need help. 
It's very possible that I missed something here or
wrote something incorrectly.  Please ask again if you
still have difficulty.

regards,
Ben

Re: Unable to Boot 2.6.19.2 from ELDK 4.1 on MPC8349E MDS

[David Hawkins]

Gary Kenaley wrote:
> I have been evaluating Freescale 2.6.11, Wind River 2.6.14, and am now
> attempting Denx 2.6.19 (from ELDK 4.1) - running on the Rev 1.0 MPC8349E
> MDS (V1.1 CPU). I boot 2.6.19.2 using the factory u-boot 1.1.3 and the
> kernel immediately hangs:

Hey Gary,

I'm working with the same board (and have a rev 3.0 EA board too).
Here are my notes for the ELDK 4.0;

http://www.ovro.caltech.edu/~dwh/powerpc_mpc8349e.pdf

I setup the board so the software developers could start working
with it, so haven't touched it for a while ... (the instructions
use the arch/ppc version) ...

So, try repeating via the arch/ppc method, and follow Ben's
arch/powerpc advice and let us know how things went.

If you're having trouble, then I hope to get back to working
with the board soon, so I can also take a crack at repeating
Ben's arch/powerpc method.

Cheers,
Dave

Re: Unable to Boot 2.6.19.2 from ELDK 4.1 on MPC8349E MDS

[Wolfgang Denk]

In message <DDBD7B17DB2ECE48BCD94C593F7255B4046E9F23@monk.echelon.echcorp.com> you wrote:
>
...
[Comments on questions already answered by Ben Warren omitted.]
> 
> I also tried a "full source rebuild from scratch" for the ELDK 4.1, but
> I found that these SRPMS were originally misnamed (could not be found in
> CVS, rpmfind, or the ELDK source CD-ROM) in
> /home/gkenaley/ELDK/V4.1/build/SRPMS.lst:

You misunderstand. Please read the documentation. The SRPMs listed in
SRPMS.lst are the original Fedora Core SRPMs which are used as  input
to  the  ELDK  build  process.  The SRPMs on the Source CDROM are the
source RPMs created by the ELDK build, i. e. it's output.

> After correcting (?) SRPMS.lst to contain the names shown above, the

You did not correect it, you corrupted it instead.

> 2. Any idea why I have problems doing the "ELDK 4.1 full source rebuild
> from scratch"?

Because you did not follow the documentation.

Note that you should use either RedHat Linux 7.3  or  Fedora  Core  5
(both  with  all  updates  installed) as build environment - at least
these are the only officially supported build environments.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Power is danger.
	-- The Centurion, "Balance of Terror", stardate 1709.2

RE: Unable to Boot 2.6.19.2 from ELDK 4.1 on MPC8349E MDS

[Gary Kenaley]

Thanks for the guidance, Ben, David, and Wolfgang.

The root ELDK 4.1 build problem seems to be that Fedora has further
updated their core 4 SRPMs without saving the old SRPMs on their ftp
site. Plus I need to use an FC5 build PC instead of RHEL 4.

For example, if I turn on echo in ELDK_BUILD script, here is an example
of one of the failures that led me to look elsewhere for SRPMS:
+ rm -f rpm-4.4.1-22.src.rpm
+ ncftpget -v
ftp://download.fedora.redhat.com/pub/fedora/linux/core/4/SRPMS/rpm-4.4.1
-22.src.rpm
ncftpget: server said: Failed to open file.
+ ncftpget -v
ftp://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/SRPMS/r
pm-4.4.1-22.src.rpm
ncftpget: server said: Failed to open file.

But if I MANUALLY try to get the current build 23, it works:
cd /home/gkenaley/ELDK/V4.1/SRPMS
ncftpget -v
ftp://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/SRPMS/r
pm-4.4.1-23.src.rpm
rpm-4.4.1-23.src.rpm:                                   10.97 MB  106.61
kB/s

So I Googled around and finally found all of the missing FC4 SRPMS
except for "util-linux-2.12p-9.12.src.rpm". The best sites that I could
find to obtain the SRPMS were:
http://download.stmc.edu.hk/fedora/linux/core/updates/4/SRPMS/
http://www.distro-cd.org/PatchCD/Fedora/Core4/SRPMS/

I had to change SRPMS.lst to use the closest available SRPM,
"util-linux-2.12p-9.13.src.rpm"

I also set up and updated an FC5 build machine, and it looks like the
ELDK 4.1 build is going through okay.

Next I will try updating to u-boot 1.1.6 on the MPC8349E MDS.

Thanks, Gary


> -----Original Message-----
> From: wd@denx.de [mailto:wd@denx.de]
> Sent: Tuesday, April 10, 2007 10:17 AM
> To: Gary Kenaley
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: Unable to Boot 2.6.19.2 from ELDK 4.1 on MPC8349E MDS
>=20
> In message
> <DDBD7B17DB2ECE48BCD94C593F7255B4046E9F23@monk.echelon.echcorp.com>
you
> wrote:
> >
> ...
> [Comments on questions already answered by Ben Warren omitted.]
> >
> > I also tried a "full source rebuild from scratch" for the ELDK 4.1,
but
> > I found that these SRPMS were originally misnamed (could not be
found in
> > CVS, rpmfind, or the ELDK source CD-ROM) in
> > /home/gkenaley/ELDK/V4.1/build/SRPMS.lst:
>=20
> You misunderstand. Please read the documentation. The SRPMs listed in
> SRPMS.lst are the original Fedora Core SRPMs which are used as  input
> to  the  ELDK  build  process.  The SRPMs on the Source CDROM are the
> source RPMs created by the ELDK build, i. e. it's output.
>=20
> > After correcting (?) SRPMS.lst to contain the names shown above, the
>=20
> You did not correect it, you corrupted it instead.
>=20
> > 2. Any idea why I have problems doing the "ELDK 4.1 full source
rebuild
> > from scratch"?
>=20
> Because you did not follow the documentation.
>=20
> Note that you should use either RedHat Linux 7.3  or  Fedora  Core  5
> (both  with  all  updates  installed) as build environment - at least
> these are the only officially supported build environments.
>=20
>=20
> Best regards,
>=20
> Wolfgang Denk
>=20
> --
> DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
> Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> Power is danger.
> 	-- The Centurion, "Balance of Terror", stardate 1709.2