All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Installing U-Boot on target via USB/serial using U-Boot commands
Date: Mon, 26 Sep 2005 12:45:02 -0400	[thread overview]
Message-ID: <4338258E.1060807@smiths-aerospace.com> (raw)
In-Reply-To: <33099.10.0.0.16.1127751442.squirrel@webmail.det3.net>

Disclaimer: I'm not an ARM expert.  I have a hard time even spelling ARM.

Joe Grisso wrote:
> See below.
> 
> 
>>It looks like this is a very simple loader.  It writes to SRAM _only_
>>and then jumps to that program (JTAG loaders typically allow you to
>>write to flash, manipulate registers, and jump anywhere, single step,
>>etc.).  Theoretically you could load u-boot this way, but nobody has
>>volunteered that they have done it so you would likely be blazing a new
>>path.
> 
> 
> Yeah, and with only 16KB of onboard SRAM, I doubt you'd be able to load
> U-Boot in as a single image. I don't know if Atmel's host-side DFU app
> handles downloads larger than the size of SRAM either. So if not, one
> would have to write an app for that on the host as well.

Nope.  U-boot is much more than 16K.  The level of complexity just 
stepped up a notch.

Looking some more at the description, the USB load is done only if no 
"valid" load (the vectors have jump instructions in them) is found in a 
bootable memory.  This means that you would only get one chance to burn 
the vectors - if your load in regular boot memory does not run properly, 
the bootloader doesn't know to go back to USB boot and your hardware 
will turn into a brick (recoverable only with a JTAG loader).

You need a JTAG loader/debugger.  The USB mechanism would work for a low 
budget loader once you have a working program to load, but using the USB 
mechanism to load your initial boot loader will be a one shot failure.

>>Having said all that, this is pretty much off topic for u-boot.  Only
>>after you get u-boot loaded into the target (and at least showing some
>>signs of life) would this become on topic for this list.
> 
> 
> Just out of curiosity, which list would be appropriate then? AT91 Users?

Sorry, I'm just an "idea" man :-/ lots of ideas, very little practice.

> Best Regards,
> 
> Joe Grisso
> Detachment 3 Media, Ltd.

gvb

  reply	other threads:[~2005-09-26 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 12:34 [U-Boot-Users] Re: Installing U-Boot on target via USB/serial using U-Boot commands Koen De Clercq
2005-09-26 13:24 ` Jerry Van Baren
2005-09-26 16:17   ` Joe Grisso
2005-09-26 16:45     ` Jerry Van Baren [this message]
2005-09-26 17:21   ` Andrey P. Vasilyev
2005-09-27  8:25     ` Mathieu Deschamps

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=4338258E.1060807@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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.