On Sat, Jan 12, 2013 at 10:30:58PM +0100, Jeroen Hofstee wrote:
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
Yep, this is exactly what I have.
no Idea about the guruplug though..
It should work fine (unless you broke something, but that's the whole point of this exercise, isn't it ;-) ). If you get a u-boot command prompt in your serial window after 'resume 0x0600000', then you just successfully tested your u-boot.
hth,
Jason.