u-boot debugging
Wolfgang Denk
wd at denx.de
Sat Jan 21 00:40:23 EST 2006
In message <008501c61d8d$e35ff9f0$9e01120a at 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 at 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_
More information about the Linuxppc-embedded
mailing list