From: Wolfgang Denk <wd@denx.de>
To: "Mustafa Çayır" <mustafa.cayir@bte.mam.gov.tr>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: u-boot debugging
Date: Fri, 20 Jan 2006 14:40:23 +0100 [thread overview]
Message-ID: <20060120134023.57E2F353A3F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 20 Jan 2006 08:51:04 +0200." <008501c61d8d$e35ff9f0$9e01120a@bilisim.local>
In message <008501c61d8d$e35ff9f0$9e01120a@bilisim.local> you wrote:
>
> Which tool must i use to debuggin u-boot codes. BDI2000 or windriver
> visionclick, which one do you prefer? is step by step code tracing
> possible?
I know that the BDI2000 works fine, and some people have been
successfully using the vision* tools, too (often after some
struggeling).
My personal tool of choice is the BDi2000.
Use the tool you know best...
And yes, single stepping is possible if your tool allows it.
Note that this question is off topic on this list; you should post
such questions on the U-Boot mailing list. But please ntoe that...
> Content-Type: text/html;
> charsetÿso-8859-9"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
...HTML code is strictly forbidden there!
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
If programming was easy, they wouldn't need something as complicated
as a human being to do it, now would they?
- L. Wall & R. L. Schwartz, _Programming Perl_
next prev parent reply other threads:[~2006-01-20 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 6:51 u-boot debugging Mustafa Çayır
2006-01-20 13:40 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 17:56 atul.sabharwal
2006-01-20 19:46 ` Wolfgang Denk
2006-01-21 6:34 ` Atul Sabharwal
2006-01-23 9:32 ` David Jander
2006-01-23 13:44 ` Atul Sabharwal
2006-01-23 22:32 ` Wolfgang Denk
2006-01-20 18:00 atul.sabharwal
2006-01-20 18:06 atul.sabharwal
2006-01-20 19:48 ` Wolfgang Denk
2006-01-20 20:40 ` bennett78
2006-01-20 18:13 atul.sabharwal
2006-01-20 21:13 atul.sabharwal
2006-01-23 9:25 ` Alexandre BASTOS
[not found] <mailman.3.1137805202.13229.linuxppc-embedded@ozlabs.org>
2006-01-21 14:20 ` Glenn Burkhardt
2006-01-22 8:28 ` Frank
2006-01-22 10:10 Albert David
2006-01-23 14:10 ` Atul Sabharwal
2006-01-23 7:48 Paula Saameño
2006-01-23 18:42 sri.dharmasanam
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=20060120134023.57E2F353A3F@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mustafa.cayir@bte.mam.gov.tr \
/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).