From: E Robertson <e.robertson.svg@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] loading via jtag
Date: Sat, 4 Jul 2009 10:21:03 -0500 [thread overview]
Message-ID: <200907041021.03465.e.robertson.svg@gmail.com> (raw)
In-Reply-To: <1ba63b520907021357h7b9d4205vbde0700ea4533847@mail.gmail.com>
On Thursday 02 July 2009 03:57:38 pm Frank Svendsb?e wrote:
> On Thu, Jul 2, 2009 at 3:32 PM, E Robertson<e.robertson.svg@gmail.com>
wrote:
> > On Thursday 02 July 2009 02:22:16 am Frank Svendsb?e wrote:
> >> On Thu, Jul 2, 2009 at 6:10 AM, E Robertson<e.robertson.svg@gmail.com>
> >
> > wrote:
> >> > Hi All,
> >> > Has anyone used the JTAG like the BDI2000 to load u-boot onto a
> >> > at91sam9263? I've done it on other boards but some some reason the
> >> > code will not execute
> >> > from on board SDRAM. To avoid initializing the external memory via
> >> > jtag, I use the bootstrap code to do the setup then load u-boot and
> >> > run it.
> >> > For reason(s) I haven't figured out yet, the code will not external
> >> > memory. Has anyone done this before and can provide some help?
> >> > Thanks.
> >>
> >> How come you want to execute it from RAM? Is the board without flash?
> >> Could you instead replace the "bootstrap" loader with U-Boot?
> >>
> >> It the SDRAM controller is already setup, I guess you must recode U-Boot
> >> and tell it not to touch/re-initialize the memory controller...
> >>
> >> Btw, look at
> >> http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeSta
> >>rte dInRAM
> >>
> >> - Frank
> >
> > In this case, I believe things are a bit different. U-boot is not
> > relocated because the bootstrap already does this and the bootstrap does
> > all the init needed to set up ram (among other things). I'm tracking a
> > problem which is why I'm trying to run it from ram. I've done quite a bit
> > of modifications to the point where I believe this should work, but
> > apparently I may have overlooked something.
>
> Ok. The BDI makes it possible to debug U-Boot so that you can pinpoint
> where the problem occur. Have you tried that yet, and what exactly is the
> problem you observe?
>
> Try to be more specific, then some of the Gurus here may be able to help
> you. Good luck!
>
> - Frank
Thanks. I finally figured out what the problem is. I have s signal integrity
problem on my SDRAM bus.
prev parent reply other threads:[~2009-07-04 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 4:10 [U-Boot] loading via jtag E Robertson
2009-07-02 7:22 ` Frank Svendsbøe
2009-07-02 13:32 ` E Robertson
2009-07-02 20:42 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-02 20:57 ` Frank Svendsbøe
2009-07-04 15:21 ` E Robertson [this message]
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=200907041021.03465.e.robertson.svg@gmail.com \
--to=e.robertson.svg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox