* Ppcboot & kernel upgrade problem(2.4.x kernel does not work)
@ 2002-01-15 6:50 ByungGiBaek
2002-01-15 7:33 ` Wolfgang Denk
0 siblings, 1 reply; 2+ messages in thread
From: ByungGiBaek @ 2002-01-15 6:50 UTC (permalink / raw)
To: linuxppc-embedded@lists.linuxppc.org
Dear all,
Now I'm trying to upgrade linux kernel from 2.2.14 to 2.4.x on our own MPC860T board(50MHz).
I successfully download and boot linux-2.2.14 kernel with ppcboot-0.9.3.
But when I tried to boot linux-2.4.x kernel with same ppcboot and same board,I have some problem.
I just see under messages then the board is auto resetted.
I adjusted IMMR and bd_t of include/asm/my_board.h as ppcboot.h of ppcboot.
Thanks in advance.
=> bootm
## Booting image at 00100000 ...
Image Name: 2.4.8 for MPC860T Board
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 535804 Bytes = 523 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Transferring control to Linux (at address 00000000) ...
ByungGi Baek.
weapon100@hanmail.net
===========================================================================
우리 인터넷, Daum http://www.daum.net
- 2002 대입 1:1상담,원서접수,합격자발표 ☞ http://hmm.daum.net/daeip_0112
- 인터넷에서 '토정비결' 보세요~ ☞ http://hmm.daum.net/fortune_0112
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Ppcboot & kernel upgrade problem(2.4.x kernel does not work)
2002-01-15 6:50 Ppcboot & kernel upgrade problem(2.4.x kernel does not work) ByungGiBaek
@ 2002-01-15 7:33 ` Wolfgang Denk
0 siblings, 0 replies; 2+ messages in thread
From: Wolfgang Denk @ 2002-01-15 7:33 UTC (permalink / raw)
To: ByungGiBaek; +Cc: linuxppc-embedded@lists.linuxppc.org
Dear ByungGi Baek,
in message <20020115155001.HM.60000000003dHZi@www7.hanmail.net> you wrote:
>
> Now I'm trying to upgrade linux kernel from 2.2.14 to 2.4.x on our own MPC860T board(50MHz).
> I successfully download and boot linux-2.2.14 kernel with ppcboot-0.9.3.
You must update PPCBoot to a newer version:
Q:
I am using PPCBoot version X (X >= 1.0.5) with a Linux kernel
version Y (Y < 2.4.5-pre5), but the last message I see is
Uncompressing Kernel Image ... OK
Then the system hangs.
A:
Most probably you pass bad parameters to the Linux kernel.
There are several possible reasons:
Bad definition of the bd_info structure
You must make sure that your machine specific header file
(for instance include/asm-ppc/tqm8xx.h) includes the same
definition of the Board Information structure as we
define in include/ppcboot.h, and make sure that your
definition of IMAP_ADDR uses the same value as your
PPCBoot configuration in CFG_IMMR.
Bad clock information
Before kernel version 2.4.5-pre5 (BitKeeper Patch
1.1.1.6, 22MAY2001) the kernel expected the clock
information in MHz, but recent kernels expect it in Hz
instead. Starting with version 1.0.5, PPCBoot passes the
clock information in MHz by default. To switch to the old
behaviour, you can set the environment variable
"clocks_in_mhz" in PPCBoot:
=> setenv clocks_in_mhz 1
=> saveenv
In your case it's most probably the clock frequency: the kernel
expects Hz, but the old PPCBoot passes MHz.
Hope this helps,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
He'd heard her use that sweet, innocent tone of voice before. It
meant that, pretty soon, there was going to be trouble.
- Terry Pratchett, _Truckers_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-01-15 7:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-15 6:50 Ppcboot & kernel upgrade problem(2.4.x kernel does not work) ByungGiBaek
2002-01-15 7:33 ` Wolfgang Denk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).