motorola lopec mpc7410

hi!
I'm porting mvista linux 2.1 for the motorola lopec mpc7410 board.And I noticed that there are some differences between the board version described by mvista and motorola.Also,the version of PPCBug is different.I'm wondering why? Does anyone have encounter the problem before?Here is my board starting information:
///////////
Copyright Motorola Inc. 1988 - 2001, All Rights Reserved

PPC5 Debugger/Diagnostics Release Version 1.3 - 04/27/2001 RM01 COLD Start

Local Memory Found =20000000 (&536870912)

MPU Clock Speed =400Mhz

BUS Clock Speed =100Mhz

Reset Vector Location : ROM Bank B
Mezzanine Configuration: Single-MPU
Current 60X-Bus Master : MPU0
Idle MPU(s) : NONE

L2Cache:       2048KB, 200Mhz
System Memory: 512MB, ECC Enabled (ECC-Memory Detected)

PPC5-Bug>CNFG
Board (PWA) Serial Number = "6016204 "

Board Identifier          = "LoPEC-P011      "
Artwork (PWA) Identifier  = "01-W3646F11B    "
MPU Clock Speed           = "400"
BUS Clock Speed           = "100"
Ethernet Address          = 0001AF0996C8
Primary SCSI Identifier   = "07"
System Serial Number      = "0               "
System Identifier         = "0                              "
License Identifier        = "6016204  "

//////////////////

When I port the mvista linux v2.1(motorola lopec 74xx lsp),the starting information is showed below:

//////////////
Copyright Motorola Inc. 1988 - 2001, All Rights Reserved

PPC5 Debugger/Diagnostics Release Version 1.3 - 04/27/2001 RM01 COLD Start

Local Memory Found =20000000 (&536870912)

MPU Clock Speed =400Mhz

BUS Clock Speed =100Mhz

Reset Vector Location : ROM Bank B
Mezzanine Configuration: Single-MPU
Current 60X-Bus Master : MPU0
Idle MPU(s) : NONE

L2Cache: 2048KB, 200Mhz
Initializing System Memory (DRAM)...

L2Cache:       2048KB, 200Mhz
System Memory: 512MB, ECC Enabled (ECC-Memory Detected)

SelfTest/Boots about to Begin... Press <BREAK> at anytime to Abort ALL

NetBoot about to Begin... Press <ESC> to Bypass, <SPC> to Continue

Network Booting from: I82559, Controller 0, Device 0 Device Name: /pci@fec00000/pci8086,1209@e,0:0,0
Loading: vmlinuz-motorola-lopec

Client IP Address      = 192.168.201.3
Server IP Address      = 192.168.201.1
Gateway IP Address     = 0.0.0.0

Subnet IP Address Mask = 255.255.255.0
Boot File Name = vmlinuz-motorola-lopec
Argument File Name =

Network Boot File load in progress... To abort hit <BREAK>

Bytes Received =&784800, Bytes Loaded =&784800
Bytes/Second =&392400, Elapsed Time =2 Second(s)

Residual-Data Located at: $1FED16DC
loaded at:     00005400 000C65BC
relocated to:  00800000 008C11BC
zimage at:     00805A00 008BD53E
avail ram:     00400000 00800000

Linux/PPC load: ip=on
Uncompressing Linux...done.
Now booting the kernel

///////////////////////////////////////////////////////////////////////////

After "Now booting the kernel",there is nothing put on the screen.I don't know why?Can anybody help me? ����������������[email protected]
��������������������2002-11-14

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

For support for an MontaVista product, please contact your mvista sales rep (or perhaps your manager knows) to find out how to contact support.

Having said that, I _believe_ the LoPEC I have running right now has PPC6Bug, so perhaps you should contact Motorola to find out how to upgrade the firmware.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

PPC5Bug is the firmware for Lopec. The last released version for Lopec is PPC5Bug 1.4 RM02 but it is unlikely that upgrading the firmware (from 1.3) would have any effect on the described problem. I don't know much about Linux but my
guess is that something is misconfigured in your kernel (console IO would be the first thing I'd check...).

The PPC6Bug series was for the Hawk based products (MCPN765, MVME5100, PPMC750, etc..). I don't think any version of PPC6Bug will work at all on Lopec.

Tom Armistead

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

Well, if he is using the MVista supplied LSP, the config should be correct, as it was tested on a similar machine at mvista. What changed from PPC5Bug 1.3 to 1.4? There is a general reliance on the lopec for the firmware to have set things up correctly, so if there was some critical fix in 1.4, that might explain it.

My memory has been, and will continue to be wrong on occasions. Thanks.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

Here is the list of changes from 1.3 to 1.4 from the release notes:

Fixed the Symbios 895A SCSI reset problem and corrected the EIDE DMA test so that it doesn't display errant warnings when the test executes on a known good board.

Corrected the PCIBUS REG test to check the PCI bridge device to ensure it supports interrupts. This ensures the Int Line register is not tested if the device does not support interrupts.

Removed the UPDATE command from PPCxBUG and restructured the board feature calls (internal changes only).

Corrected the calculation of the bus speed after having used the PF (Port Format) command to change the baud rate of the serial debug port.

Added support for the Intel 82543 and 82544 ethernet controllers.

Added support for Non-ECC memory (primarily an issue for LoPEC which provides DIMM sockets).

Added ECC error checking during RAM tests to PPC5BUG.

Added Intel 82544 PHY access support.

Corrected an I2C access problem that intermittantly caused the I2C bus to stick in a BUSY state for long periods of time. This resulted in unusually long boot-up times for PPC5BUG, especially for LoPEC boards running at 100MHz (local bus) with certain combinations of DIMMs. Instead of consuming the typical 15 to 30 seconds (depending upon memory size) during the boot process, a period of 70 to 80 seconds would transpire.

Fixed several problems with the I82543 diagnostic tests (the only test available currently is the SPACK test).

Corrected a condition where running the CL1283 diagnostic on a board without the CL1283 generated an error condition instead of simply bypassing the test. The error condition was visible, though, only through invoking either the DE or DEM command.

Tom Armistead

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