Linux on MPC5200 - LITE5200EVAL

Linux on MPC5200 - LITE5200EVAL

[Sylvain Munaut]

Hello,

I've just received the motorola eval board ( one, with 64M SDR and 16Mb
flash). And I'm a little lost.
I've tool u-boot sources from CVS compiled them ( compiled fine exect
for the samples apps ), then took the appropriate kernel sources, build
it ( make uImage ). And .... then ?

On the board currently I have 'dBUG' installed on the flash, it's what
is on the flash by default.

I haven't found any "manual" or so.

Thanks for any pointers,

    Sylvain Munaut

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Wolfgang Denk]

In message <40294AD9.1070407@246tNt.com> you wrote:
>
> I've just received the motorola eval board ( one, with 64M SDR and 16Mb
> flash). And I'm a little lost.
> I've tool u-boot sources from CVS compiled them ( compiled fine exect
> for the samples apps ), then took the appropriate kernel sources, build
> it ( make uImage ). And .... then ?

Either use the default configuration of U-Boot and replace  dBUG,  or
use  the  "LOWBOOT"  configuration and install U-Boot at the start of
the flash area.

Then use U-Boot to load and boot Linux.

> I haven't found any "manual" or so.

There is the DULG - there is no  LITE5200  specific  version  of  the
document (yet), but it should get you started.
See http://www.denx.de/twiki/bin/view/DULG/Manual

Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
If you hear an onion ring, answer it.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Linux on MPC5200 - LITE5200EVAL

[Andrew Dennison]

> In message <40294AD9.1070407@246tNt.com> you wrote:
> >
> > I've just received the motorola eval board ( one, with 64M SDR and 16Mb
> > flash). And I'm a little lost.
> > I've tool u-boot sources from CVS compiled them ( compiled fine exect
> > for the samples apps ), then took the appropriate kernel sources, build
> > it ( make uImage ). And .... then ?
>
> Either use the default configuration of U-Boot and replace  dBUG,  or
> use  the  "LOWBOOT"  configuration and install U-Boot at the start of
> the flash area.
>
> Then use U-Boot to load and boot Linux.
>
> > I haven't found any "manual" or so.
>
> There is the DULG - there is no  LITE5200  specific  version  of  the
> document (yet), but it should get you started.
> See http://www.denx.de/twiki/bin/view/DULG/Manual
>
> Best regards,
>
> Wolfgang Denk
>

I installed and browsed the Montavista BSP for the MPC5200LITE as a starting
point. So far the best documentation I've found is the source for their
deploy script...

You can extract specific examples of dBUG and u-boot command sequences from
there - both for installing u-boot LOW and booting linux.

The following worked for me to get u-boot going:
$cd u-boot
$make MPC5200LITE_LOWBOOT_config
$make CROSS_COMPILE=/path/to/bin/powerpc-linux-
$su -c "cp u-boot.bin /tftpboot"

#dBUG commands to load u-boot via tftp
set mac 00:01:AF:52:01:xx # see MPC5200LITE doco for how to choose xx value
set client lite.ip.address
set server tftpserver.ip.address
set netmask your.netmask
dn -i -o 0x100000 /tftpboot/u-boot.bin
fe 0xff000000 0xff050000
fp 0xff000000 0xff040000 0x100000
#power off and change link to boot low
#power up to u-boot

I've currently configured u-boot to load my kernel via bootp and nfs mount a
root filesystem built with buildroot (see uclibc.org). I did this as follows
(nfsargs line will wrap):

setenv ethaddr 00:01:af:52:01:xx
setenv nfsargs setenv bootargs root=/dev/nfs
nfsroot=\$\(serverip\):/tftpboot/\$\(ipaddr\) console=ttyS0,115200
ip=\$\(ipaddr\):\$\(serverip\):\$\(gatewayip\):\$\(netmask\):\$\(hostname\):
\$\(netdev\):off
setenv bootdelay 2
setenv bootcmd bootp\; run nfsargs\; bootm
saveenv

read u-boot wiki to do it differently:)

NOTE: if you have a Version 2.0 board and want 16MiB flash to actually work
you should ensure J24 is in the 2-3 position (J24 is a 0R resistor on the
bottom of the board).
It is stupid for the jumper to be in the 1-3 position when 16MiB is loaded
but that is the way my board was. Seems like a manufacturing error:(

Andrew


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Linux on MPC5200 - LITE5200EVAL

[Gerrit Van de Velde]

<snip>

> #dBUG commands to load u-boot via tftp
> set mac 00:01:AF:52:01:xx # see MPC5200LITE doco for how to choose xx value
> set client lite.ip.address
> set server tftpserver.ip.address
> set netmask your.netmask
> dn -i -o 0x100000 /tftpboot/u-boot.bin
> fe 0xff000000 0xff050000
> fp 0xff000000 0xff040000 0x100000
> #power off and change link to boot low
> #power up to u-boot
>

I followed these instructions and it all worked out fine (left out the
examples directory of U boot though) , but after the reboot in lowboot
jumper configuration, i only see garbage on my minicom screen. I can
figure out some characters that look familiar (like the countdown for
the autostart) so I assume it's working correctly but doesn't get
displayed right. I also can't interrupt the countdown so input doesn't
work. Already tried to change the 115200 8N1 settings of the
communications (but why would they change anyway..) and didn't help.

What could possibly be wrong ??

> read u-boot wiki to do it differently:)
>
> NOTE: if you have a Version 2.0 board and want 16MiB flash to actually work
> you should ensure J24 is in the 2-3 position (J24 is a 0R resistor on the
> bottom of the board).
> It is stupid for the jumper to be in the 1-3 position when 16MiB is loaded
> but that is the way my board was. Seems like a manufacturing error:(
>

checked it and there's a resistor between 2-3 and not 1-3 so i guess
that's right.. (I have version 2.0 Lite)

> Andrew

Regards,
Gerrit


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Linux on MPC5200 - LITE5200EVAL

[Peter Falk]

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

Had the same problem with garbage, apparently a rounding problem in the
baudrate calculation.
The above patch shows the changes suggested by someone on the net, can't
remember his name but it is on the patches page of sourceforge.net.
After application of this it worked fine.
One gotcha, hardware handshake off on your terminal software! U-Boot
wants it off, The motorola DBUG wants it on, this kept me busy for a
day.

Regards,

Peter Falk

-----Original Message-----
From: owner-linuxppc-embedded@lists.linuxppc.org
[mailto:owner-linuxppc-embedded@lists.linuxppc.org] On Behalf Of Gerrit
Van de Velde
Sent: Wednesday, 11 February, 2004 10:19
To: Andrew Dennison
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: RE: Linux on MPC5200 - LITE5200EVAL



<snip>

> #dBUG commands to load u-boot via tftp
> set mac 00:01:AF:52:01:xx # see MPC5200LITE doco for how to choose xx
> value set client lite.ip.address set server tftpserver.ip.address
> set netmask your.netmask
> dn -i -o 0x100000 /tftpboot/u-boot.bin
> fe 0xff000000 0xff050000
> fp 0xff000000 0xff040000 0x100000
> #power off and change link to boot low
> #power up to u-boot
>

I followed these instructions and it all worked out fine (left out the
examples directory of U boot though) , but after the reboot in lowboot
jumper configuration, i only see garbage on my minicom screen. I can
figure out some characters that look familiar (like the countdown for
the autostart) so I assume it's working correctly but doesn't get
displayed right. I also can't interrupt the countdown so input doesn't
work. Already tried to change the 115200 8N1 settings of the
communications (but why would they change anyway..) and didn't help.

What could possibly be wrong ??

> read u-boot wiki to do it differently:)
>
> NOTE: if you have a Version 2.0 board and want 16MiB flash to actually
work
> you should ensure J24 is in the 2-3 position (J24 is a 0R resistor on
the
> bottom of the board).
> It is stupid for the jumper to be in the 1-3 position when 16MiB is
loaded
> but that is the way my board was. Seems like a manufacturing error:(
>

checked it and there's a resistor between 2-3 and not 1-3 so i guess
that's right.. (I have version 2.0 Lite)

> Andrew

Regards,
Gerrit



[-- Attachment #2: serdiff.patch --]
[-- Type: application/octet-stream, Size: 549 bytes --]

Index: serial.c
===================================================================
RCS file: /cvsroot/u-boot/u-boot/cpu/mpc5xxx/serial.c,v
retrieving revision 1.1
diff -r1.1 serial.c
73c73
< 	baseclk = gd->ipb_clk / 32;
---
> 	baseclk = (gd->ipb_clk+16) / 32;
88c88
< 	div = baseclk / gd->baudrate;
---
> 	div = (baseclk+gd->baudrate/2) / gd->baudrate;
157c157
< 	baseclk = gd->ipb_clk / 32;
---
> 	baseclk = (gd->ipb_clk+16) / 32;
161c161
< 	div = baseclk / gd->baudrate;
---
> 	div = (baseclk+gd->baudrate/2) / gd->baudrate;

Re: Linux on MPC5200 - LITE5200EVAL

[Wolfgang Denk]

In message <1076491141.4841.6.camel@nios> you wrote:
>
> I followed these instructions and it all worked out fine (left out the
> examples directory of U boot though) , but after the reboot in lowboot
> jumper configuration, i only see garbage on my minicom screen. I can
> figure out some characters that look familiar (like the countdown for
> the autostart) so I assume it's working correctly but doesn't get
> displayed right. I also can't interrupt the countdown so input doesn't
> work. Already tried to change the 115200 8N1 settings of the
> communications (but why would they change anyway..) and didn't help.

You are using the latest U-Boot (= top of CVS), aren't you?  If  not:
try  it  out.  There  were  some  rounding  errors  in  the  baudrate
calculation.


Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"The question of whether a computer can think is no more  interesting
than the question of whether a submarine can swim"
                                                - Edsgar W.  Dijkstra

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Gerrit Van de Velde]

I patched with sirdeff.patch and it works now, also great tip about the
handshaking, that saved me a day too I guess ;)

I'll rebuild with latest U-boot too.

Thanks Wolfgang & Peter & Andrew :)

On Wed, 2004-02-11 at 11:14, Wolfgang Denk wrote:
> In message <1076491141.4841.6.camel@nios> you wrote:
> >
> > I followed these instructions and it all worked out fine (left out the
> > examples directory of U boot though) , but after the reboot in lowboot
> > jumper configuration, i only see garbage on my minicom screen. I can
> > figure out some characters that look familiar (like the countdown for
> > the autostart) so I assume it's working correctly but doesn't get
> > displayed right. I also can't interrupt the countdown so input doesn't
> > work. Already tried to change the 115200 8N1 settings of the
> > communications (but why would they change anyway..) and didn't help.
>
> You are using the latest U-Boot (= top of CVS), aren't you?  If  not:
> try  it  out.  There  were  some  rounding  errors  in  the  baudrate
> calculation.
>
>
> Best regards,
>
> Wolfgang Denk
>
> --
> See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
> Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
> "The question of whether a computer can think is no more  interesting
> than the question of whether a submarine can swim"
>                                                 - Edsgar W.  Dijkstra
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Wolfgang Denk]

In message <1076495328.4808.2.camel@nios> you wrote:
>
> I patched with sirdeff.patch and it works now, also great tip about the
> handshaking, that saved me a day too I guess ;)

Ummm... Do you think the documentation is not clear enough?

http://www.denx.de/twiki/bin/view/DULG/SystemSetup#Section_4.1.

Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
A Puritan is someone who is deathly afraid that  someone,  somewhere,
is having fun.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Linux on MPC5200 - LITE5200EVAL

[Peter Falk]

The documentation is clear enough, but since the board boots with
Motorola monitor and it's setup it is easy to miss. :-)

Best regards,

Peter Falk

-----Original Message-----
From: owner-linuxppc-embedded@lists.linuxppc.org
[mailto:owner-linuxppc-embedded@lists.linuxppc.org] On Behalf Of
Wolfgang Denk
Sent: Wednesday, 11 February, 2004 14:10
To: Gerrit Van de Velde
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux on MPC5200 - LITE5200EVAL



In message <1076495328.4808.2.camel@nios> you wrote:
>
> I patched with sirdeff.patch and it works now, also great tip about
> the handshaking, that saved me a day too I guess ;)

Ummm... Do you think the documentation is not clear enough?

http://www.denx.de/twiki/bin/view/DULG/SystemSetup#Section_4.1.

Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de A
Puritan is someone who is deathly afraid that  someone,  somewhere, is
having fun.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Sylvain Munaut]

Hello

Thanks for your advices.

I've managed to compile U-Boot in a lowboot configuration :

# make MPC5200LITE_LOWBOOT_config
# <edit the config.mk of the board to set TEXTADDR>
# make

Then flash it with the dBUG ( the defaut motorola stuff on the flash ) :

 > dn -i -o 0x100000 /mpc5200/u-boot.bin
 > fe 0xff000000 0xff050000
 > fp 0xff000000 0xff040000 0x100000

Then, changing the jumpers setting on the board to low-boot, it boots
fine on U-Boot.
 From there I download the freshly downloaded/compiled kernel image (
from denx cvs linux_2_4_devel, configured with icecube_5200_config ) and
try to boot it :

[... Cut ...]

=> tftpboot 200000 mpc5200/uImage
Using FEC ETHERNET device
TFTP from server 192.168.1.1; our IP address is 192.168.1.3
Filename 'mpc5200/uImage'.
Load address: 0x200000
Loading: #################################################################
         ############################################################
done
Bytes transferred = 635394 (9b202 hex)
=> bootm 200000
## Booting image at 00200000 ...
   Image Name:   Linux-2.4.24-pre2
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    635330 Bytes = 620.4 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
Linux version 2.4.24-pre2 (tnt@246tNt-main) (gcc version 3.4.0 20040127
(prerel4On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line:
Calibrating delay loop... 263.78 BogoMIPS
Memory: 62740k available (1096k kernel code, 356k data, 60k init, 0k
highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
PCI: Cannot allocate resource region 0 of device 00:1a.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Oops: kernel access of bad area, sig: 11
NIP: DFFEFDEC XER: 20000000 LR: C0003998 SP: C02CBFD0 REGS: c02cbf20
TRAP: 0400dMSR: 20009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c02ca000[1] 'swapper' Last syscall: 120
last math 00000000 last altivec 00000000
GPR00: DFFEFDED C02CBFD0 C02CA000 00000000 00001032 C03F1F48 00000016
C02CA03C
GPR08: C02CA000 C0150000 C03F003C C0150000 00000000 FFFFEFFF 03FFA000
00000000
GPR16: 00000001 FFFFFFFF 00000000 03FF432C 003FF000 03FA1D80 03FFF1B0
00000002
GPR24: 00000000 007FFEB0 40000000 C012B000 007FFF00 00000000 C014BC00
C014BC04
Call backtrace:
C0003978 C00073F8
Kernel panic: Attempted to kill init!
 <0>Rebooting in 180 seconds..

[... End of cut ...]

But as you can see, it doesn't exactly do what I hoped ;) I was waiting
for an "Unable to mount root" since I didn't put a rootfs yet but it
crashes before that ( i think )
 From what I can see in the System.map, the call backtrace are :

c0003918 t run_init_process
c00073cc T arch_kernel_thread

Any comments ?


    Sylvain Munaut

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Wolfgang Denk]

In message <402A7561.7020105@246tNt.com> you wrote:
>
> I've managed to compile U-Boot in a lowboot configuration :
>
> # make MPC5200LITE_LOWBOOT_config
> # <edit the config.mk of the board to set TEXTADDR>

No such edit is necessary!!!!

>  From there I download the freshly downloaded/compiled kernel image (
> from denx cvs linux_2_4_devel, configured with icecube_5200_config ) and
> try to boot it :
...
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line:

You don't pass any "bootargs" here? Where is your root filesystem?

See http://www.denx.de/twiki/bin/view/DULG/LinuxKernelArgs

> POSIX conformance testing by UNIFIX
> PCI: Probing PCI hardware
> PCI: Cannot allocate resource region 0 of device 00:1a.0

This looks fishy. Is there a PCI card installed? Remove it!!


> But as you can see, it doesn't exactly do what I hoped ;) I was waiting
> for an "Unable to mount root" since I didn't put a rootfs yet but it
> crashes before that ( i think )

Did you modify the kernel configuration? Did you try  passing  useful
kernel boot arguments?

>  From what I can see in the System.map, the call backtrace are :
>
> c0003918 t run_init_process
> c00073cc T arch_kernel_thread
>
> Any comments ?

At the moment my guess is that you have a  PCI  problem.  Remove  any
cards, and retry using useful boot arguments.

Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
A father doesn't destroy his children.
	-- Lt. Carolyn Palamas, "Who Mourns for Adonais?",
	   stardate 3468.1.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Sylvain Munaut]

Hello



>>I've managed to compile U-Boot in a lowboot configuration :
>>
>># make MPC5200LITE_LOWBOOT_config
>># <edit the config.mk of the board to set TEXTADDR>
>>
>>
>
>No such edit is necessary!!!!
>
>
Oh, ok. I've changed it back, and recompiled / reinstalled U-boot just
to be sure ( I don't think it can be of any influence but ... )

>> From there I download the freshly downloaded/compiled kernel image (
>>from denx cvs linux_2_4_devel, configured with icecube_5200_config ) and
>>try to boot it :
>>
>>
>...
>
>
>>zone(1): 0 pages.
>>zone(2): 0 pages.
>>Kernel command line:
>>
>>
>
>You don't pass any "bootargs" here? Where is your root filesystem?
>
>See http://www.denx.de/twiki/bin/view/DULG/LinuxKernelArgs
>
>
>
I had none. I just planned to do it as soon as I got an unable to mount
root error. To be sure it was not the problem, I took
the pRamdisk file from
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/images/ppc_82xx/ as I seen
from another post.

To launch it I use :
tftp 100000 mpc5200/uImage; tftp 200000 mpc5200/pRamdisk; bootm 100000
200000

The environment variable bootargs is set to "root=/dev/ram rw"

The "new" output is included at the end , quite similar.

One other weird things is that I was forced to setenv bootargs, then
saveenv it, then reset to try to boot. If i just set the bootargs before
the bootm, it decompressed the two images, but the kernel was not
(apparently) starting ...

>>POSIX conformance testing by UNIFIX
>>PCI: Probing PCI hardware
>>PCI: Cannot allocate resource region 0 of device 00:1a.0
>>
>>
>
>This looks fishy. Is there a PCI card installed? Remove it!!
>
>
Huh, no. The only things connected to the board are the alim, the serial
cable, and a crossed RJ45 cable ( direct connection to my PC ). Jumper
setting are all default execpt for the low boot settings.

U-Boot seems to 'see' a device too :

U-Boot 1.0.2 (Feb 12 2004 - 00:17:05)


CPU:   MPC5200 (JTAG ID 0001101d) at 396 MHz
       Bus 132 MHz, IPB 66 MHz, PCI 33 MHz
Board: Motorola MPC5200 (IceCube)
I2C:   85 kHz, ready
DRAM:  64 MB
FLASH: 16 MB
PCI:   Bus Dev VenId DevId Class Int
        00  1a  1057  5803  0680  00
In:    serial
Out:   serial
Err:   serial
Net:   FEC ETHERNET

Maybe I'm mistaken, but isn't this the motorola itself ?


>>But as you can see, it doesn't exactly do what I hoped ;) I was waiting
>>for an "Unable to mount root" since I didn't put a rootfs yet but it
>>crashes before that ( i think )
>>
>>
>
>Did you modify the kernel configuration? Did you try  passing  useful
>kernel boot arguments?
>
>
At first, I tried with a kernel I compiled some time ago, when I ordered
the board but didn't yet have it. ( 27 january ), and I had changed some
stuff. When I saw it didn't work, I took a new fresh copy from cvs and
make the default config and compiled it.


Is a default, precompiled kernel image available somewhere ?
Maybe my toolchain is producing weird binaries ....
I'll try to install the toolchain from denx.


Thanks for your help,

    Sylvain Munaut


[ New output ]

Bytes transferred = 1400262 (155dc6 hex)
## Booting image at 00100000 ...
   Image Name:   Linux-2.4.24-pre2
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    635420 Bytes = 620.5 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 00200000 ...
   Image Name:   Simple Embedded Linux Framework
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    1400198 Bytes =  1.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 03e4b000, end 03fa0d86 ... OK
Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
Linux version 2.4.24-pre2 (tnt@246tNt-main) (gcc version 3.4.0 20040127
(prerelease)) #4 Wed Feb 11 19:55:20 CET 2004
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram rw
Calibrating delay loop... 263.78 BogoMIPS
Memory: 61372k available (1096k kernel code, 356k data, 60k init, 0k
highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
PCI: Cannot allocate resource region 0 of device 00:1a.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
floating point used in kernel (task=c3e44000, pc=ffbad4c4)
Oops: kernel access of bad area, sig: 11
NIP: FFF02448 XER: 20000000 LR: FFF00024 SP: C3E45FD0 REGS: c3e45f20
TRAP: 0300    Not tainted
MSR: 0000b032 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
DAR: 00016F88, DSISR: 22000000
TASK = c3e44000[1] 'swapper' Last syscall: 120
last math 00000000 last altivec 00000000
GPR00: FFBAD4C7 C3E45FD0 C3E44000 00000000 00001032 C3FDBF48 00000016
C3E4403C
GPR08: C3E44000 C0150000 C3FDA03C C0150000 00000000 FFE7FFFF 03FFA000
00000000
GPR16: 00000001 FFFFFFFF 00000000 03FF432C C0130000 C014BC00 C0130000
00000001
GPR24: C0110000 00000002 C014BC00 00000000 00352B46 00000000 C014BC00
00016F88
Call backtrace:
C00039B0 C0007498
Kernel panic: Attempted to kill init!
 <0>Rebooting in 180 seconds..

[ End of output ]

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Sylvain Munaut]

Hi

Just drop the matter, the compiler was the problem. I've recompiled it
all with gcc 3.3.2 and it works just fine.

>>>
>>> PCI: Probing PCI hardware
>>> PCI: Cannot allocate resource region 0 of device 00:1a.0
>>>
>>>
>
That still remains though. Not sure if it's of any importance.


Sylvain Munaut

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Wolfgang Denk]

In message <402AC1A4.7070304@246tNt.com> you wrote:
>
> The "new" output is included at the end , quite similar.
>
> One other weird things is that I was forced to setenv bootargs, then
> saveenv it, then reset to try to boot. If i just set the bootargs before
> the bootm, it decompressed the two images, but the kernel was not
> (apparently) starting ...

Did you make any progress? If  not:  are  you  absolutely  sure  your
hardware is OK?


Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
There has been an alarming increase in the number of things you  know
nothing about.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Wolfgang Denk]

In message <402E0D8C.4080801@246tNt.com> you wrote:
>
> The weird problem with u-boot ( not booting If I set bootargs manually )
> and the kernel crash are both solved. It was a compiler issue. I used a
> toolchain I used to build binaries for a "normal" mac based on gcc 3.4 (
> cvs ) and it was a really bad idea.

I see.

>  - The PCI slot is 3.3 v and apparently I don't have a single PCI card
> that seems to work on it ... When I plug one ( that I thought was 3.3v
> ), nothing boot, sometimes even the led don't power on ...

Be careful to put it correctly. The slot bracket has  to  be  on  the
side where the UART / USB / CAN connctors are. Do not insert the card
with the slot bracket pointing to the IDE connector.

Also be VERY carefully  which  card  you  insert.  make  sure  it  is
_really_ a 3.3V compatible card. [I fried a board by trying a Digitus
"DC  SER2 Rev. 2.0 Serial PCI I/O Card" - this card has the key slots
for a 3.3/5V combi card, but the V_I/O pins are connected to  the  5V
rail. The RAM chips didn't like to see 5V ...]

>  - When I change options in the kernel to support new stuff I need, like
> activating USB host & IDE controller, the kernel don't boot at all ( or
> at least, I don't see on the serial console it does ). It's the same
> problem with activating drivers for the PCI bus ... What is weird is
> that it's not an error on boot, it's just that after u-boot messages,
> there is nothing at all.

Can you attach a debugger? Or even try  a  post-mortem  dump  of  the
logbif area? Both PCI and USB are working fine for me.

> I'm not sure my hardware is fully OK, but I did mtest on u-boot  for
> about 10 hours and it didn't complained. It's a fresh new board from
> motorola...

Maybe you can ask for a replacement. Your problems don't look  normal
to me.

Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Being schizophrenic is better than living alone.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Sylvain Munaut]

Hi

>> - The PCI slot is 3.3 v and apparently I don't have a single PCI card
>>that seems to work on it ... When I plug one ( that I thought was 3.3v
>>), nothing boot, sometimes even the led don't power on ...
>>
>>
>
>Be careful to put it correctly. The slot bracket has  to  be  on  the
>side where the UART / USB / CAN connctors are. Do not insert the card
>with the slot bracket pointing to the IDE connector.
>
>Also be VERY carefully  which  card  you  insert.  make  sure  it  is
>_really_ a 3.3V compatible card. [I fried a board by trying a Digitus
>"DC  SER2 Rev. 2.0 Serial PCI I/O Card" - this card has the key slots
>for a 3.3/5V combi card, but the V_I/O pins are connected to  the  5V
>rail. The RAM chips didn't like to see 5V ...]
>
>
Yeah I can only imagine ...
I don't think my only test fried the card, it show the same behavior
before and after so I guess ( hope ? ) I'm lucky.

The slot does indeed work, I just came across a Intel EEPro100 card,
like the one I used on other dev kit. I'm sure it's 3.3v/5v compatible
and it's recognized without problems.

>> - When I change options in the kernel to support new stuff I need, like
>>activating USB host & IDE controller, the kernel don't boot at all ( or
>>at least, I don't see on the serial console it does ). It's the same
>>problem with activating drivers for the PCI bus ... What is weird is
>>that it's not an error on boot, it's just that after u-boot messages,
>>there is nothing at all.
>>
>>
>
>Can you attach a debugger? Or even try  a  post-mortem  dump  of  the
>logbif area? Both PCI and USB are working fine for me.
>
>
I don't have a debugger ... But I think I'll invest in one soon ! ;)
How can I dump the logbuf area ? I saw a discussion on this ml about
this buffer, is it fixed in memory ? How to find it's address ?

>>I'm not sure my hardware is fully OK, but I did mtest on u-boot  for
>>about 10 hours and it didn't complained. It's a fresh new board from
>>motorola...
>>
>>
>
>Maybe you can ask for a replacement. Your problems don't look  normal
>to me.
>
>
>
Could you send me a kernel image you compiled with the config at
http://www.246tNt.com/mpc5200_config ?
Maybe my compiler is wrong again. The ELDK binaries didn't work ( I
don't have the good glibc version on my machine ). I'm downloading what
I need to try to compile it right now ...
I've also put http://www.246tNt.com/uImage wich is not bootable on my
board ...

Basically the config is default + USB + IDE ( HD & CDRom ) + SCSI disk
support ( for memory sticks on USB ) + Misc filesystems and partition
support.

On http://www.246tNt.com/mpc5200_config  is a sample .config file that
makes the kernel to not boot at all.


Sylvain Munaut


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL

[Dale Farnsworth]

On Sat, Feb 14, 2004 at 02:53:03PM +0000, Wolfgang Denk wrote:
>
> In message <402E0D8C.4080801@246tNt.com> you wrote:
> >
> > The weird problem with u-boot ( not booting If I set bootargs manually )
> > and the kernel crash are both solved. It was a compiler issue. I used a
> > toolchain I used to build binaries for a "normal" mac based on gcc 3.4 (
> > cvs ) and it was a really bad idea.
>
> I see.
>
> >  - The PCI slot is 3.3 v and apparently I don't have a single PCI card
> > that seems to work on it ... When I plug one ( that I thought was 3.3v
> > ), nothing boot, sometimes even the led don't power on ...
>
> Be careful to put it correctly. The slot bracket has  to  be  on  the
> side where the UART / USB / CAN connctors are. Do not insert the card
> with the slot bracket pointing to the IDE connector.
>
> Also be VERY carefully  which  card  you  insert.  make  sure  it  is
> _really_ a 3.3V compatible card. [I fried a board by trying a Digitus
> "DC  SER2 Rev. 2.0 Serial PCI I/O Card" - this card has the key slots
> for a 3.3/5V combi card, but the V_I/O pins are connected to  the  5V
> rail. The RAM chips didn't like to see 5V ...]
>
> >  - When I change options in the kernel to support new stuff I need, like
> > activating USB host & IDE controller, the kernel don't boot at all ( or
> > at least, I don't see on the serial console it does ). It's the same
> > problem with activating drivers for the PCI bus ... What is weird is
> > that it's not an error on boot, it's just that after u-boot messages,
> > there is nothing at all.
>
> Can you attach a debugger? Or even try  a  post-mortem  dump  of  the
> logbif area? Both PCI and USB are working fine for me.
>
> > I'm not sure my hardware is fully OK, but I did mtest on u-boot  for
> > about 10 hours and it didn't complained. It's a fresh new board from
> > motorola...
>
> Maybe you can ask for a replacement. Your problems don't look  normal
> to me.

I've seen the same symptoms Sylvain described on the five Lite5200
boards that I have tried.  Eepro100 network cards work fine, but the 3
brands of IDE cards I tried are not even visible in PCI config space.
U-boot doesn't see them and Linux doesn't see them, booted either from
dBUG or U-boot.

Actually, one Lite5200/IDE combo comes close.  Parts of the IDE cards
PCI config info do read correctly sometimes.  Different parts each time.
I think this is likely a hardware issue with Lite5200 boards.

-Dale Farnsworth

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Linux on MPC5200 - LITE5200EVAL & New bestcomm code ?

[Sylvain Munaut]

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

Hi every one.


A little update on my problems. Apparently the problem was the u-boot
command I used to boot :

I used :
     tftp 100000 mpc5200/uImage; tftp 300000 mpc5200/pRamdisk;bootm
100000 300000

And now I use :
     tftp 200000 mpc5200/uImage; tftp 400000 mpc5200/pRamdisk;bootm
200000 400000

and it works just fine ... Apparently when the kernel was too big, the
area near 100000 is probably used by u-boot in some way, maybe during
decompression and it doesnt work. I've check with multiple different
memory tests that the concerned memory region is fine. So it is a
software issue. Maybe u-boot should give some warning about that ( if
it's the cause, not yet sure ). But that's off topic here.



Now, I'm just looking forward for new BestComm code, to get AC97 and IDE
DMA running ( quite slow and CPU intensive right now ... ).



Sylvain Munaut



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: Linux on MPC5200 - LITE5200EVAL & New bestcomm code ?

[Wolfgang Denk]

In message <40458A8C.8020009@246tNt.com> you wrote:
>
> and it works just fine ... Apparently when the kernel was too big, the
> area near 100000 is probably used by u-boot in some way, maybe during

Well, it is not used by U-Boot itself, but when you have a big  Linux
kernel it starts overwriting itself when you uncompress it to address
0.

> software issue. Maybe u-boot should give some warning about that ( if
> it's the cause, not yet sure ). But that's off topic here.

U-Boot does not know the uncompressed size in advance. And  anyway  -
it's  a  pilot  error  :-)  In modification of anmother famous quote:
"U-Boot was not designed  to  stop  you  from  doing  stupid  things,
because that would also stop you from doing clever things."

> Now, I'm just looking forward for new BestComm code, to get AC97 and IDE
> DMA running ( quite slow and CPU intensive right now ... ).

:-(

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Q:  How many DEC repairman does it take to fix a flat ?
A:  Five; four to hold the car up and one to swap tires.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/