From: Jeff Franks <Jeff.Franks@uson.com>
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: Sun, 30 Sep 2007 14:33:15 -0500 [thread overview]
Message-ID: <46FFF9FB.4060900@uson.com> (raw)
Does anyone have a recipe for debugging u-boot on AT91SAM9263-EK target?
Our proprietary board is very similar, but can't see what goes wrong.
Atmel has a bootstrap that inits SDRAM, and loads u-boot image from
Flash device into SDRAM. It jumps to the proper address in the SDRAM and
dies.
All we have to debug is J-Link from Segger along gdbserver from Segger
which is an application that runs on Windows and talks via Usb to the
J-Link Pod. We can talk to Windows as if it were gdbserver from a Linux
host.
The bootup sequence provided by Atmel looks different from u-boot in
that u-boot does not move itself into SDRAM, this is done by the Atmel
bootstrap.
Don't know how to init SDRAM from J-Link. Has anyone done that?
--jlf
next reply other threads:[~2007-09-30 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 19:33 Jeff Franks [this message]
2007-10-02 18:25 ` [U-Boot-Users] Q) Anyone know how to debug u-boot on AT91SMA9263-EK using J-Link from Segger? Leonid
2007-10-04 14:29 ` Andreas Schweigstill
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=46FFF9FB.4060900@uson.com \
--to=jeff.franks@uson.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.