[U-Boot] Debugging uBoot with JTAG/Trace32 ?

[Detlev Zundel <dzu@denx.de>]

Hi Vijay,

>          I am bit new to this field and my query here is understandably a
> bit vague. I am particularly interested in how any of you, who have had
> experience with uBoot and a JTAG debugger (like a Lauterbach), have gone
> about tackling and resolving an issue within uBoot.
>
> Specifically, I would really appreciate if you could describe the
> *problem*encountered within uBoot, and how did the JTAG/Trace32
> debugging help you
> resolve the issue.

Having a BDI at my disposal, I tackle most of U-Boot related problems
with it.  But of course a JTAG debugger is indispensible when doing a
fresh board port for a "traditionally booting"[1] system.  Usually for
such a cycle the JTAG NOR flash capability is used to program the
development U-Boot and debug it.  This continues until U-Boot is able to
flash itself.  From then on it depends on personal taste whether to use
it to debug easier (e.g. driver) problems.

Cheers
  Detlev

[1] Out of reset the CPU starts executing instructions from NOR flash

-- 
Die Mengenlehre in der Schule ist daran gescheitert, dass man sie mit ihrem
Vokabular verwechselt hat.
                                     -- Norbert Treitz
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de