public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andreas Schweigstill <andreas@schweigstill.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Q) Anyone know how to debug u-boot on	AT91SMA9263-EK using J-Link from Segger?
Date: Thu, 04 Oct 2007 16:29:10 +0200	[thread overview]
Message-ID: <4704F8B6.40509@schweigstill.de> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3C0246EBBE@ehost011-3.exch011.intermedia.net>

Hello!

Leonid schrieb:
> I am using BDI2000 with my at91rm9200 board - I think, you can do the
> same for at91rm9263 unless you doesn't get JTAG on your board. I can
> step through code, etc...  

And I am using a Lauterbach ICD for such purposes without any major
problem. I can't see a reason why there should be a problem AFTER
reading the documentation.

In my eyes it doesn't make any sense to use a tool like a JTAG debugger
without understanding how the systems works. So if you get
initialization scripts from someone else and don't understand them you
also won't understand how to debug your bootloader(s). In many cases you
won't be able to find all bugs when just stepping through the code on
C language level. But if you understand how the processor works you
won't need anybody else providing you with further information/files.

Why do so many people think that mailing lists like this are a total
replacement for RTFM?

With best regards
Andreas Schweigstill

-- 
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstra?e 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/

  reply	other threads:[~2007-10-04 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 19:33 [U-Boot-Users] Q) Anyone know how to debug u-boot on AT91SMA9263-EK using J-Link from Segger? Jeff Franks
2007-10-02 18:25 ` Leonid
2007-10-04 14:29   ` Andreas Schweigstill [this message]
2007-10-04 15:11     ` Jeff Franks

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=4704F8B6.40509@schweigstill.de \
    --to=andreas@schweigstill.de \
    --cc=u-boot@lists.denx.de \
    /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