* linux booting
@ 2002-08-23 9:11 leeyang
2002-08-23 14:23 ` Wolfgang Denk
0 siblings, 1 reply; 8+ messages in thread
From: leeyang @ 2002-08-23 9:11 UTC (permalink / raw)
To: linuxppc-embedded
hi,all!
These days I am trying to upgrade kernel from
2.2.14 to 2.4.20-pre2 in my 860T custom board.
The old 2.2.14 kernel and ppcboot do work,and
I add some custom board file to the 2.4.20-pre2
soure tree from linuxppc_2_4_devel,and comile
it successfully.(no any warn or error in my modify)
When I "bootm 0x10000"in ppcboot,it runs to
"Transferring control to linux kernel",then hangs
there,and I see nothing in the console.:(
In the PPCBoot guide(FAQ section),it mentioned
2 possible causes,wrong bdinfo and clocks_in_mhz
I do check it and feel nothing wrong,however
nothing yet.
I have a BDI2000,but I think I should debug the bootm
part of ppcboot,however someone says it is quite
difficult to do so( at least for me).
so I am seeking errors in blind.
hope some light!
leeyang
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux booting
2002-08-23 9:11 linux booting leeyang
@ 2002-08-23 14:23 ` Wolfgang Denk
2002-08-24 0:07 ` leeyang
0 siblings, 1 reply; 8+ messages in thread
From: Wolfgang Denk @ 2002-08-23 14:23 UTC (permalink / raw)
To: leeyang; +Cc: linuxppc-embedded
In message <000b01c24a85$0596a620$cc00a8c0@ycigrnd.ycig.com> you wrote:
>
> When I "bootm 0x10000"in ppcboot,it runs to
> "Transferring control to linux kernel",then hangs
> there,and I see nothing in the console.:(
This will never work. I bet it didn't work with your old kernel
either. 0x10000 is just 64 kB - this is _never_ enough for an
uncompressed Linux kernel. You will overwrite your kernel while
uncompressing it, which crashes the system. Use a higher load address, somthing like 0x200000.
> In the PPCBoot guide(FAQ section),it mentioned
> 2 possible causes,wrong bdinfo and clocks_in_mhz
> I do check it and feel nothing wrong,however
> nothing yet.
You have to _unset_ clocks_in_mhz for a 2.4.20-pre2 kernel.
> I have a BDI2000,but I think I should debug the bootm
> part of ppcboot,however someone says it is quite
> difficult to do so( at least for me).
Well, it's not _that_ difficult. Try it out, so you get used to is ;-)
> so I am seeking errors in blind.
Just open your eyes, and thou shalt see :-)
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Always leave room to add an explanation if it doesn't work out.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux booting
2002-08-23 14:23 ` Wolfgang Denk
@ 2002-08-24 0:07 ` leeyang
2002-08-25 18:35 ` Wolfgang Denk
0 siblings, 1 reply; 8+ messages in thread
From: leeyang @ 2002-08-24 0:07 UTC (permalink / raw)
To: Wolfgang Denk; +Cc: linuxppc-embedded
> > When I "bootm 0x10000"in ppcboot,it runs to
> > "Transferring control to linux kernel",then hangs
> > there,and I see nothing in the console.:(
>
> This will never work. I bet it didn't work with your old kernel
> either. 0x10000 is just 64 kB - this is _never_ enough for an
> uncompressed Linux kernel. You will overwrite your kernel while
> uncompressing it, which crashes the system. Use a higher load address,
somthing like 0x200000.
Sorry! I lost a zero here,I mean 0x100000,so old kernel can boot there.
>
> > In the PPCBoot guide(FAQ section),it mentioned
> > 2 possible causes,wrong bdinfo and clocks_in_mhz
> > I do check it and feel nothing wrong,however
> > nothing yet.
>
> You have to _unset_ clocks_in_mhz for a 2.4.20-pre2 kernel.
>
> > I have a BDI2000,but I think I should debug the bootm
> > part of ppcboot,however someone says it is quite
> > difficult to do so( at least for me).
>
> Well, it's not _that_ difficult. Try it out, so you get used to is ;-)
I wish it is not that hard,however I can not debug the kernel or
ppcboot according the brief introduction in BDI manual.:(
I want to watch r3,r4,r5,r6,r7 register when ppcboot transferring
to kernel.Could you tell me how to get that? thanks a lot!
>
> > so I am seeking errors in blind.
>
> Just open your eyes, and thou shalt see :-)
>
> Wolfgang Denk
>
> --
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
> Always leave room to add an explanation if it doesn't work out.
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux booting
2002-08-24 0:07 ` leeyang
@ 2002-08-25 18:35 ` Wolfgang Denk
2002-08-26 12:40 ` leeyang
0 siblings, 1 reply; 8+ messages in thread
From: Wolfgang Denk @ 2002-08-25 18:35 UTC (permalink / raw)
To: leeyang; +Cc: linuxppc-embedded
Hi,
in message <002301c24b03$038024f0$fc4bb73d@leeyang> you wrote:
>
> > > I have a BDI2000,but I think I should debug the bootm
> > > part of ppcboot,however someone says it is quite
> > > difficult to do so( at least for me).
> >
> > Well, it's not _that_ difficult. Try it out, so you get used to is ;-)
>
> I wish it is not that hard,however I can not debug the kernel or
> ppcboot according the brief introduction in BDI manual.:(
There are some more hints at
http://www.denx.de/doc/TQM8xxL/debugging.html
> I want to watch r3,r4,r5,r6,r7 register when ppcboot transferring
> to kernel.Could you tell me how to get that? thanks a lot!
Start PPCBoot, setup bootargs etc., load the kernel image. Before
finally typing the "bootm" command set a (hardware) breakpoint at the
kernel entry point (= physical address 0x0000).
When hitting the breakpoint, print the registers...
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
You don't have to worry about me. I might have been born yesterday...
but I stayed up all night.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux booting
2002-08-25 18:35 ` Wolfgang Denk
@ 2002-08-26 12:40 ` leeyang
2002-08-26 15:12 ` Wolfgang Denk
0 siblings, 1 reply; 8+ messages in thread
From: leeyang @ 2002-08-26 12:40 UTC (permalink / raw)
To: Wolfgang Denk; +Cc: linuxppc-embedded
hi,WD
> There are some more hints at
> http://www.denx.de/doc/TQM8xxL/debugging.html
I have read it before,but only for module or application,
not for kernel and ppcboot,someone told me because of
ppcboot's relocation,so it is difficult in some externd.
Anyway it helps some:)
> > I want to watch r3,r4,r5,r6,r7 register when ppcboot transferring
> > to kernel.Could you tell me how to get that? thanks a lot!
>
> Start PPCBoot, setup bootargs etc., load the kernel image. Before
> finally typing the "bootm" command set a (hardware) breakpoint at the
> kernel entry point (= physical address 0x0000).
>
> When hitting the breakpoint, print the registers...
Yes,it works:),and I can check thoes regs when entering kernel.
and I am sure ppcboot handle correct value to kernel now.
the kernel can boot and I can see some in the console now.
I replaced the ppcboot.h in the 1.1.6 with one in old version
so I think it is still bdinfo problem.
However,new ones come:
kernel can not find init in the ramdisk!
the initrd had been tested in the old kernel and can mount fs
and entering system.so a little strange:(
the only reason I am wondering is the compiler!
the file in the initrd were compiled with HHL1.2 ppc compiler.
and the kernel was created with eldk.
Is that make sense?
leeyang
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux booting
2002-08-26 12:40 ` leeyang
@ 2002-08-26 15:12 ` Wolfgang Denk
0 siblings, 0 replies; 8+ messages in thread
From: Wolfgang Denk @ 2002-08-26 15:12 UTC (permalink / raw)
To: leeyang; +Cc: linuxppc-embedded
Hi,
in message <000901c24cfd$de617140$0141b73d@leeyang> you wrote:
>
> > http://www.denx.de/doc/TQM8xxL/debugging.html
>
> I have read it before,but only for module or application,
> not for kernel and ppcboot,someone told me because of
> ppcboot's relocation,so it is difficult in some externd.
See the Q+A section
> However,new ones come:
> kernel can not find init in the ramdisk!
> the initrd had been tested in the old kernel and can mount fs
> and entering system.so a little strange:(
>
> the only reason I am wondering is the compiler!
> the file in the initrd were compiled with HHL1.2 ppc compiler.
> and the kernel was created with eldk.
> Is that make sense?
That should be no problem.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The nice thing about standards is, there are so many to choose from.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* linux booting
@ 2002-05-28 7:48 zhongqx
2002-05-28 8:23 ` Wolfgang Denk
0 siblings, 1 reply; 8+ messages in thread
From: zhongqx @ 2002-05-28 7:48 UTC (permalink / raw)
To: linuxppc-embedded
Hi,
I use ppcboot to booting linux ,but linux cann't go on when malloc some memory.My board is FADS860T,
it has 4M DRAM(in physical 0---3fffff) and 4M SDRAM(in physical address is 03000000-033fffff),when ppcboot
run up,i use bdi command find it tell me total memory is 8M which is from 0 to 7fffff.i think ppcboot maped
two memory block into one continuous memory block(are i right?).when ppcboot boot linux it pass bdi to linux,
so i don't know whether linux kernel understand the memory 0---7fffff is actualy two memory block which
is 0----3fffff and 03000000 -033fffff.who can tell me how to understand this.sorry for my bad english.thank
you!
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: linux booting
2002-05-28 7:48 zhongqx
@ 2002-05-28 8:23 ` Wolfgang Denk
0 siblings, 0 replies; 8+ messages in thread
From: Wolfgang Denk @ 2002-05-28 8:23 UTC (permalink / raw)
To: zhongqx; +Cc: linuxppc-embedded
In message <002901c2061c$1d564840$7301a8c0@zhongqx> you wrote:
>
> I use ppcboot to booting linux ,but linux cann't go on when malloc some memory.My board is FADS860T,
> it has 4M DRAM(in physical 0---3fffff) and 4M SDRAM(in physical address is 03000000-033fffff),when ppcboot
> run up,i use bdi command find it tell me total memory is 8M which is from 0 to 7fffff.i think ppcboot maped
> two memory block into one continuous memory block(are i right?).when ppcboot boot linux it pass bdi to linux,
> so i don't know whether linux kernel understand the memory 0---7fffff is actualy two memory block which
> is 0----3fffff and 03000000 -033fffff.who can tell me how to understand this.sorry for my bad english.thank
The Linux boot messages contain information about how much memory it
found; search for a line like this:
...
Memory: 62604k available (1164k kernel code, 540k data, 52k init, 0k highmem)
...
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"There are three principal ways to lose money: wine, women, and engi-
neers. While the first two are more pleasant, the third is by far the
more certain." - Baron Rothschild, ca. 1800
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2002-08-26 15:12 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-08-23 9:11 linux booting leeyang
2002-08-23 14:23 ` Wolfgang Denk
2002-08-24 0:07 ` leeyang
2002-08-25 18:35 ` Wolfgang Denk
2002-08-26 12:40 ` leeyang
2002-08-26 15:12 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 7:48 zhongqx
2002-05-28 8:23 ` 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).