From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Running vanilla u-boot v2012.10 on Guruplug
Date: Sat, 12 Jan 2013 22:30:58 +0100 [thread overview]
Message-ID: <50F1D612.7070302@myspectrum.nl> (raw)
In-Reply-To: <20130112204153.GC13433@titan.lakedaemon.net>
On 01/12/2013 09:41 PM, Jason wrote:
> On Sat, Jan 12, 2013 at 08:41:36PM +0100, Dirk Heinrichs wrote:
>> Am Samstag 12 Januar 2013, 16:51:51 schrieb Wolfgang Denk:
>>
>>> Did you read the FAQ? Especially
>>> http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarted
>>> InRAM ?
>> Now I did :) Thanx a lot.
>>
>> Interesting that [1] states it's possible, though...
> With the dreamplug, I often load u-boot into RAM via the JTAG (0x0600000
> and 0x0800000), and then 'resume 0x0600000'. Then use the u-boot
> running from 0x0600000 to burn the image to SPI flash from 0x0800000.
> But that's loaded via the JTAG, not from a running u-boot.
>
> I think I posted instructions to this mailinglist a while ago about
> this. If you have the JTAG (it's only $35US), I would advise trying
> that.
>
For what is worth, I can confirm above for the dreamplug..
I wrote this down a once...:
cd /where/uboot_is
sudo openocd -f /usr/share/openocd/scripts/board/sheevaplug.cfg
# other console
telnet localhost 4444
sheevaplug_init
load_image u-boot
load_image u-boot.kwb 0x0800000
resume 0x0600000
# and hit stop in the serial terminal
no Idea about the guruplug though..
Regards,
Jeroen
next prev parent reply other threads:[~2013-01-12 21:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 8:00 [U-Boot] Running vanilla u-boot v2012.10 on Guruplug Dirk Heinrichs
2013-01-12 15:51 ` Wolfgang Denk
2013-01-12 19:41 ` Dirk Heinrichs
2013-01-12 20:41 ` Jason
2013-01-12 21:30 ` Jeroen Hofstee [this message]
2013-01-12 21:57 ` Jason Cooper
2013-01-12 22:32 ` Jason
2013-01-13 7:44 ` Dirk Heinrichs
2013-01-13 9:25 ` Albert ARIBAUD
2013-01-13 16:25 ` Stefan Herbrechtsmeier
2013-01-13 20:49 ` Dirk Heinrichs
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=50F1D612.7070302@myspectrum.nl \
--to=jeroen@myspectrum.nl \
--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