linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cal Erickson <cal_erickson@mvista.com>
To: Nguyen Xuan Hoang <hoang_nguyen@smartstors.com>
Cc: linuxppc-embedded@lists.linuxppc.org, support@mvista.com,
	Jeff Maddox <support@hmi.com>
Subject: Re: BDM problem
Date: Mon, 28 Aug 2000 07:51:56 -0700	[thread overview]
Message-ID: <39AA7C8B.F357E8BC@mvista.com> (raw)
In-Reply-To: 011d01c01179$fe249820$0401a8c0@hoangmobile


Hoang,
Did you make sure to move the re-built kernel to where
the downloader expects it? This is a common error
everyone makes at least once. They rebuild the kernel
but forget to move it. Then when they download they
are still downloading the old version and not the new
one.

As for the breakpoint still being set after running. Take
a look at the address where the breakpoint is set. Look
at the system map file . Then you can determine which
code it is  in and turn it off. Why it is doing this is not
easy to determine. There have been problems when
using BDM and the caches and mmu running. Not
being familiar with the HMI BDM solution, I cannot
be sure if this is what you are seeing.

Cal

Nguyen Xuan Hoang wrote:

> Hi,
>
> Thank very much for your info.  I have verified myself and ask one of my
> colleague to double check it, but the Kernel Hacking is already disabled.
> However it seems there's some thing relate to your supposition, I can run
> the kernel without stopping BDM by command:
>          g 100000 (or any random  number).
>
> That's fine for me at this time, but it's still a question : BDM problem or
> kernel problem?????
>
> Another problem I have is:
>
>     - After the kernel initializing and running,  if I stop the BDM to view
> some registers and start again. The BDM will stop and report an breakpoint
> happen if I try to press any key on terminal.  Any advices ???
>
> Thank in advances
> Hoang
>
> ----- Original Message -----
> From: "Cal Erickson" <cal_erickson@mvista.com>
> To: "Nguyen Xuan Hoang" <hoang_nguyen@smartstors.com>
> Cc: <linuxppc-embedded@lists.linuxppc.org>; <support@mvista.com>; "Jeff
> Maddox" <support@hmi.com>
> Sent: Friday, August 25, 2000 2:46 PM
> Subject: Re: BDM problem
>
> >
> > Hoang,
> > When you are trying to use the Avocet Systems HMI BMD device
> > have you built a kernel with Kernel Hacking disabled? It appears
> > from your description the it is still enabled. When kgdb is enabled
> > through kernel hacking, it starts and immediately hits a breakpoint.
> > If you at this time set a breakpoint further on then you should be
> > able to proceed. If you want to use the HMI BMD then you need
> > to un-select kernel hacking and rebuild your kernel.
> > Cal Erickson
> >
> > Nguyen Xuan Hoang wrote:
> >
> > > Hi All, I have problem when running Linux kernel using BDM. It seems
> > > not a new problem, from this mail list I can learn some thing: Before
> > > run the debugger:
> >>        - Set DER to 0 using BDM command:
> > >                         X  DER
> >>                           30002400f
> >>                           0
> >>       -  Set ICTRL to 7 using BDM command:
> >>               X ICTRL
> > >             00000000
> >>              7
> >>        -  Run the debugger: g
> >>    However, the BDM auto stop right after the kernel execute: (perhaps it
> turn on the virtual
> > > mode here)
> >>             execve("/sbin/init",argv_init,envp-init);  in file
> /init/main.c
> >>    The BDM show that an breakpoint occur (the PC = 0xFEEDDA8),but of
> course I didn't set any breakpoint.
>
> >> My system is: RPX LITE + HMI BDM + SOURCE GATE II Could anyone please
> point me a
> > > solution.
> >> Thank in advances
> >>  Hoang
> >
> > --
> >
> ===========================================================================
> > Cal Erickson                 MontaVista Software Inc.
> > Customer Support Engineer    490 Potrero Avenue
> > Phone (408) 328-0304         Sunnyvale CA 94085
> > Fax   (408) 328-9204         e-mail cal_erickson@mvista.com
> > Pager 877-566-2012           support 1-800-759-8888 pin 202-7489
> > web http://www.mvista.com    support e-mail: support@mvista.com
> > eCode: http://cal@work.com.ecode.com
> >
> ===========================================================================
> >
> >
> >

--
===========================================================================
Cal Erickson                 MontaVista Software Inc.
Customer Support Engineer    490 Potrero Avenue
Phone (408) 328-0304         Sunnyvale CA 94085
Fax   (408) 328-9204         e-mail cal_erickson@mvista.com
Pager 877-566-2012           support 1-800-759-8888 pin 202-7489
web http://www.mvista.com    support e-mail: support@mvista.com
eCode: http://cal@work.com.ecode.com
===========================================================================


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

      reply	other threads:[~2000-08-28 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00ba01c00f0c$abd41100$0401a8c0@hoangmobile>
2000-08-25 21:46 ` BDM problem Cal Erickson
2000-08-29  5:28   ` Nguyen Xuan Hoang
2000-08-28 14:51     ` Cal Erickson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39AA7C8B.F357E8BC@mvista.com \
    --to=cal_erickson@mvista.com \
    --cc=hoang_nguyen@smartstors.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=support@hmi.com \
    --cc=support@mvista.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).