monitor in mpc860fads

monitor in mpc860fads

[gao xiaoguo]

hi,

now i have a mpc860fads board, maybe there is a debug monitor inside it.
but i dont know how to check it. i also dont know what i need on host end to communicate with the monitor. some guide book is appreciated.

I am newbie in this area, hope some expertise point out a way for me.

thanks


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

execve system call question

[Sangmoon Kim]

Hi!
I'm debugging a custom MPC755 board
with linuxppc_devel from montavista rsync,
and /opt/hardhat/devkit/ppc/7xx/target for NFS root.
It booted and stoped after the message.

--------------------------------------------------------
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
IP-Config: Complete:
      device=eth0, addr=203.239.17.200, mask=255.255.255.0, gw=203.239.17.57,
     host=dogoil, domain=, nis-domain=(none),
     bootserver=203.239.17.57, rootserver=203.239.17.57, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 203.239.17.57
Looking up port of RPC 100005/1 on 203.239.17.57
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 76k init
--------------------------------------------------------

I traced the code and the point of stopping is after calling
execve("/sbin/init", argv_init, envp_init)
in init/main.c

I was trying to trace more, but it was impossible
because of the complexity of the code.

Is there any method to debug this?
I'm debugging it for a month.

Please help me.

- Sangmoon Kim -

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

RE: monitor in mpc860fads

[Borracini Evandro-R45188]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 1003 bytes --]


Hi,

Fads boards don't have any native monitor. You need to flash one on your board.
If you intend to run Linux on your fads, I recommend you using ppcboot as bootloader.

You can find ppcboot at http://ppcboot.sourceforge.net
Also, take a look at the "Linux for PowerPC embedded Systems Howto" at http://penguinppc.org/embedded/howto/PowerPC-Embedded-HOWTO.html. That is a very good guide.

regards

Evandro

> -----Original Message-----
> From: gao xiaoguo [mailto:gaoxg@guoguang.com.cn]
> Sent: Terça-feira, 26 de Fevereiro de 2002 06:17
> To: linuxppc-embedded
> Subject: monitor in mpc860fads
>
>
>
> hi,
>
> now i have a mpc860fads board, maybe there is a debug monitor
> inside it.
> but i dont know how to check it. i also dont know what i need
> on host end to communicate with the monitor. some guide book
> is appreciated.
>
> I am newbie in this area, hope some expertise point out a way for me.
>
> thanks
>
>
>

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

Re: execve system call question

[None Atall]

 Well, after that command, the filesystem takes
place. You can't put anything in the kernel. The
procedure for calling and executing init works fine.
Is the root filesystem correct? Have you tried to
upload a ramdisk image in ram? If you are sure that
all these are correct, then do you have a JTAG
Debugger? (OCD Commander ...)

                     D. Meidanis

--- Sangmoon Kim <dogoil@etinsys.com> wrote:
>
> Hi!
> I'm debugging a custom MPC755 board
> with linuxppc_devel from montavista rsync,
> and /opt/hardhat/devkit/ppc/7xx/target for NFS root.
> It booted and stoped after the message.
>
>
--------------------------------------------------------
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 1024 buckets,
> 8Kbytes
> TCP: Hash tables configured (established 8192 bind
> 8192)
> IP-Config: Complete:
>       device=eth0, addr=203.239.17.200,
> mask=255.255.255.0, gw=203.239.17.57,
>      host=dogoil, domain=, nis-domain=(none),
>      bootserver=203.239.17.57,
> rootserver=203.239.17.57, rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Looking up port of RPC 100003/2 on 203.239.17.57
> Looking up port of RPC 100005/1 on 203.239.17.57
> VFS: Mounted root (nfs filesystem).
> Freeing unused kernel memory: 76k init
>
--------------------------------------------------------
>
> I traced the code and the point of stopping is after
> calling
> execve("/sbin/init", argv_init, envp_init)
> in init/main.c
>
> I was trying to trace more, but it was impossible
> because of the complexity of the code.
>
> Is there any method to debug this?
> I'm debugging it for a month.
>
> Please help me.
>
> - Sangmoon Kim -
>
>


=====
-------------------------------------------------
  Dhmhtrios Meidanis
-Degree in Mathematics, University of the Aegean.
-Master in Computer Architecture and Digital
 Systems, University of Crete.
  Greece.
-------------------------------------------------


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

Re: execve system call question

[Wolfgang Denk]

In message <008901c1beb1$409cc7f0$1a11efcb@industrialDiv.hanasys.co.kr> you wrote:
>
> I traced the code and the point of stopping is after calling
> execve("/sbin/init", argv_init, envp_init)
> in init/main.c
>
> I was trying to trace more, but it was impossible
> because of the complexity of the code.

It's not impossible. In fact, it's quite simple.

You're running with root filesystem over NFS,  so  just  start  up  a
network  sniffer  (like  ethereal)  and  check  all  NFS requests and
replys. Probably  something  is  missing  in  your  root  filesystem.
Something essential, like /dev/console or so.

> Is there any method to debug this?

Yes, attach a BDI2000 and check where you are...

> I'm debugging it for a month.

Urghhh...

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Use C++ to confuse your enemies; use C to produce stable code.

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

Re: monitor in mpc860fads

[Magnus Damm]

> If you intend to run Linux on your fads, I recommend you using ppcboot as bootloader.

A more minimalistic approach would be Miniboot. =)

http://opensource.se/projects/miniboot

The FADS board is supported right out of the box.
Just make sure you use the right crystal.

You could then boot PPCBoot from Miniboot if you want network support,
etc.

/ magnus

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

Re: execve system call question

[Christian Pellegrin]

On Tue, 26 Feb 2002, Sangmoon Kim wrote:

>
> and /opt/hardhat/devkit/ppc/7xx/target for NFS root.

> VFS: Mounted root (nfs filesystem).
>
> Is there any method to debug this?
> I'm debugging it for a month.
>

I'll suggest:

1) turn on debugging on the nfs server

2) generate a trivial hello world program and put it instead of
/sbin/init. So to be sure it's a ppc executable. Start with a static
linked one,it's a bit difficult to do dynamic linking right at the first
time ;-)

Bye!


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

Re: execve system call question

[Sangmoon Kim]

Hi None Atall!

I think the root file system is correct because it's from Hard Hat Linux.
I tried some ramdisk images but the result was the same.
And I don't have JTAG debugger.

Thank you for the replay.

----- Original Message -----
From: "None Atall" <linux_meis@yahoo.com>
To: "Sangmoon Kim" <dogoil@etinsys.com>; "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Sent: Tuesday, February 26, 2002 10:11 PM
Subject: Re: execve system call question


> Well, after that command, the filesystem takes
> place. You can't put anything in the kernel. The
> procedure for calling and executing init works fine.
> Is the root filesystem correct? Have you tried to
> upload a ramdisk image in ram? If you are sure that
> all these are correct, then do you have a JTAG
> Debugger? (OCD Commander ...)
>
>                      D. Meidanis
>
> --- Sangmoon Kim <dogoil@etinsys.com> wrote:
> >
> > Hi!
> > I'm debugging a custom MPC755 board
> > with linuxppc_devel from montavista rsync,
> > and /opt/hardhat/devkit/ppc/7xx/target for NFS root.
> > It booted and stoped after the message.
> >
> >
> --------------------------------------------------------
> > NET4: Linux TCP/IP 1.0 for NET4.0
> > IP Protocols: ICMP, UDP, TCP
> > IP: routing cache hash table of 1024 buckets,
> > 8Kbytes
> > TCP: Hash tables configured (established 8192 bind
> > 8192)
> > IP-Config: Complete:
> >       device=eth0, addr=203.239.17.200,
> > mask=255.255.255.0, gw=203.239.17.57,
> >      host=dogoil, domain=, nis-domain=(none),
> >      bootserver=203.239.17.57,
> > rootserver=203.239.17.57, rootpath=
> > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> > Looking up port of RPC 100003/2 on 203.239.17.57
> > Looking up port of RPC 100005/1 on 203.239.17.57
> > VFS: Mounted root (nfs filesystem).
> > Freeing unused kernel memory: 76k init
> >
> --------------------------------------------------------
> >
> > I traced the code and the point of stopping is after
> > calling
> > execve("/sbin/init", argv_init, envp_init)
> > in init/main.c
> >
> > I was trying to trace more, but it was impossible
> > because of the complexity of the code.
> >
> > Is there any method to debug this?
> > I'm debugging it for a month.
> >
> > Please help me.
> >
> > - Sangmoon Kim -
> >
> >
>
>
> =====
> -------------------------------------------------
>   Dhmhtrios Meidanis
> -Degree in Mathematics, University of the Aegean.
> -Master in Computer Architecture and Digital
>  Systems, University of Crete.
>   Greece.
> -------------------------------------------------
>
>

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

Re: execve system call question

[Sangmoon Kim]

Hi Cristian Pellegrin!

I tried the 'hello world' thing.
but it didn't worked.

Thank you for the reply.

----- Original Message -----
From: "Christian Pellegrin" <chri@infis.univ.trieste.it>
To: "Sangmoon Kim" <dogoil@etinsys.com>
Cc: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Sent: Tuesday, February 26, 2002 10:27 PM
Subject: Re: execve system call question


> On Tue, 26 Feb 2002, Sangmoon Kim wrote:
>
> >
> > and /opt/hardhat/devkit/ppc/7xx/target for NFS root.
>
> > VFS: Mounted root (nfs filesystem).
> >
> > Is there any method to debug this?
> > I'm debugging it for a month.
> >
>
> I'll suggest:
>
> 1) turn on debugging on the nfs server
>
> 2) generate a trivial hello world program and put it instead of
> /sbin/init. So to be sure it's a ppc executable. Start with a static
> linked one,it's a bit difficult to do dynamic linking right at the first
> time ;-)
>
> Bye!
>
>

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

Re: execve system call question

[Sangmoon Kim]

Hi Wolfgang Denk.

> You're running with root filesystem over NFS,  so  just  start  up  a
> network  sniffer  (like  ethereal)  and  check  all  NFS requests and
> replys. Probably  something  is  missing  in  your  root  filesystem.
> Something essential, like /dev/console or so.

The root file system is from Hardhat Linux. I think it's correct because so many people use it without complain. and the /dev/console exist.
I tried ramdisk. But the result was same.

Thank you for the reply.

----- Original Message -----
From: "Wolfgang Denk" <wd@denx.de>
To: "Sangmoon Kim" <dogoil@etinsys.com>
Cc: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Sent: Tuesday, February 26, 2002 10:21 PM
Subject: Re: execve system call question


>
> In message <008901c1beb1$409cc7f0$1a11efcb@industrialDiv.hanasys.co.kr> you wrote:
> >
> > I traced the code and the point of stopping is after calling
> > execve("/sbin/init", argv_init, envp_init)
> > in init/main.c
> >
> > I was trying to trace more, but it was impossible
> > because of the complexity of the code.
>
> It's not impossible. In fact, it's quite simple.
>
> You're running with root filesystem over NFS,  so  just  start  up  a
> network  sniffer  (like  ethereal)  and  check  all  NFS requests and
> replys. Probably  something  is  missing  in  your  root  filesystem.
> Something essential, like /dev/console or so.
>
> > Is there any method to debug this?
>
> Yes, attach a BDI2000 and check where you are...
>
> > I'm debugging it for a month.
>
> Urghhh...
>
> Wolfgang Denk
>
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
> Use C++ to confuse your enemies; use C to produce stable code.
>
>
>

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

Re: execve system call question

[Wolfgang Denk]

In message <005e01c1bf2d$101798e0$1a11efcb@industrialDiv.hanasys.co.kr> you wrote:
>
> I think the root file system is correct because it's from Hard Hat Linux.

Not necessarily so. You may have made some  mistakes  when  selecting
and installing the packages.

> I tried some ramdisk images but the result was the same.
> And I don't have JTAG debugger.

Get yourself a BDI2000 then.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
If something is different, it's either better or worse,  and  usually
both.                                                    - Larry Wall

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