* Debug ppclinux with BDI2000
@ 2001-05-10 18:55 Kirk Lee
2001-05-10 19:44 ` Wolfgang Denk
0 siblings, 1 reply; 2+ messages in thread
From: Kirk Lee @ 2001-05-10 18:55 UTC (permalink / raw)
To: linuxppc-embedded
Dear All:
I am trying to debug ppclinux running on TQM8xxL
with BDI2000.
I followed the procedure mentioned in BDI's manual
(Sec3.3.4, P29).
I just type 'load' on BDI's telnet terminal to load
target zImage file(arch/ppc/mbxboot/zImage).
After that BDI shows:
"File offset 0x00010000 to address 0x00210000 size
514200"
Then I type "go 0x00210000" on BDI's telnet terminal.
However, nothing happened!!
I can not get any responce from serial console.
Did I lose something?
Thanks
kirk
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Debug ppclinux with BDI2000
2001-05-10 18:55 Debug ppclinux with BDI2000 Kirk Lee
@ 2001-05-10 19:44 ` Wolfgang Denk
0 siblings, 0 replies; 2+ messages in thread
From: Wolfgang Denk @ 2001-05-10 19:44 UTC (permalink / raw)
To: mpc; +Cc: linuxppc-embedded
In message <989520948.8638.mpc@mail2000.com.tw> you wrote:
>
> I followed the procedure mentioned in BDI's manual
> (Sec3.3.4, P29).
> I just type 'load' on BDI's telnet terminal to load
> target zImage file(arch/ppc/mbxboot/zImage).
> After that BDI shows:
> "File offset 0x00010000 to address 0x00210000 size
> 514200"
> Then I type "go 0x00210000" on BDI's telnet terminal.
> However, nothing happened!!
Of course something happened: your kernel crashed.
> I can not get any responce from serial console.
> Did I lose something?
Yes. The Linux kernel, even with the mbxboot bootstrap stuff
attached, is not a standalone program. It expects a lot of
initialization to be done by the firmware, and some information
passed, too.
I don't see why you go such a difficult route.
Both PPCboot and Linux are running out of the box on the TQM8xxL.
Just install and run.
If you want to debug your own kernel modifications, you can still use
PPCBoot to load and start the kernel - but remember that PPCBoot does
not use zImage files, it uses it's own image format instead.
A simple but efficient way to enter the debugger _after_ Linux has
started and the MMU has been turned on is to set an instruction
breakpoint for the address range 0xC0000000 ... 0xC1000000 (use the
"BI" command at the telnet prompt to do so).
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
panic: kernel trap (ignored)
** 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:[~2001-05-10 19:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-05-10 18:55 Debug ppclinux with BDI2000 Kirk Lee
2001-05-10 19:44 ` 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).