linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: shanta@india.tek.com
Cc: "'Wolfgang Denk'" <wd@denx.de>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Basic questions about PPC embedded developement under Linux
Date: Tue, 11 Apr 2000 10:58:58 +0200	[thread overview]
Message-ID: <200004110858.KAA05916@denx.local.net> (raw)
In-Reply-To: Your message of "Tue, 11 Apr 2000 12:30:07 +0530." <000601bfa383$92e508b0$4f689ec0@w-shanta.india.tek.com>


In message <000601bfa383$92e508b0$4f689ec0@w-shanta.india.tek.com> you wrote:
>
> I have a small question regarding the "bdiGDB".
> I need to first flash the kernel image into the flash memory. Can this be
> done with the debugger??

Yes. Using the telnet interface, you can  use  the  LOAD  command  to
download an image to RAM, and the PROG command to write it to FLASH:

LOAD   [<offset>] [<file> [<format>]] load program file to target memory
...
PROG   [<offset>] [<file>]   program flash memory

> Also the boot monitor needs to load the kernel image from the flash memory
> to the RAM and start executing it.
> Can this be traced with "bdiGDB"??

You can use a "target remote" command in GDB to attach to the  BDI200
debugger;  then  you  can use GDB; or you can do everything "by hand"
using the telnet interface and commands like these:

...
GO    [<pc>]                 set PC and start target system
TI    [<pc>]                 trace on instuction (single step)
TC    [<pc>]                 trace on change of flow
HALT                         force target to enter debug mode
BI  <from> [<to>] [<count>]  set instruction breakpoint
CI  [<id>]                   clear instruction breakpoint(s)
BD  [R|W] <addr> [<count>] [<data>] set data breakpoint (32bit access)
BDH [R|W] <addr> [<count>] [<data>] set data breakpoint (16bit access)
BDB [R|W] <addr> [<count>] [<data>] set data breakpoint ( 8bit access)
BDR <from> <to> [<count>]    set data breakpoint on a range
CD [<id>]                    clear data breakpoint(s)
...

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
The game of life is a game of boomerangs.  Our  thoughts,  deeds  and
words return to us sooner or later with astounding accuracy.

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

       reply	other threads:[~2000-04-11  8:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000601bfa383$92e508b0$4f689ec0@w-shanta.india.tek.com>
2000-04-11  8:58 ` Wolfgang Denk [this message]
     [not found] <38EA0716.47AA17BA@sympatico.ca>
2000-04-04 16:53 ` Basic questions about PPC embedded developement under Linux Wolfgang Denk
2000-04-05  9:02   ` Marcus Sundberg
     [not found] <38E7EFD4.F77B945B@ict.ac.cn>
2000-04-03 14:08 ` Ron Flory
2000-04-03 15:03   ` Wolfgang Denk

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=200004110858.KAA05916@denx.local.net \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=shanta@india.tek.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).