[U-Boot] Dreamplug v10 uboot

[Steven McGrath]

Jason,

These instructions are great, however they don't work for the newer v10 Dreamplugs.  I would be happy to lend my v10 Dreamplug to the cause to get a workable U-Boot for it. 

-- 
Steven McGrath
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Monday, July 2, 2012 at 1:20 PM, Jason wrote:

> On Fri, Jun 29, 2012 at 10:37:56AM -0500, Steven McGrath wrote:
> > I was recommended to contact you about the possibility un-bricking my
> > dream plug v10. Per the recommendation of some individuals, I
> > attempted to ref lash my boot to a newer version, essentially bricking
> > it. I do have a jtag, however I haven't been able to successfully ref
> > lash any boots to the device. If you can offer any advice on what
> > boot versions I should be using and if you have a known good process
> > for getting the kwb files to stick, i would be very grateful.
> > 
> 
> 
> Steve,
> 
> Sorry to hear about your predicament. Here's how I flash u-boot onto my
> dreamplug:
> 
> 0) read over all instructions before starting this
> 
> 0.5) open a terminal with a serial connect to dp
> 
> screen /dev/ttyUSB0 115200
> 
> -OR-
> 
> minicom -o -w -s # and setup appropriately
> 
> 1) build the latest u-boot tag (2012.04.01)
> 
> cd /path/to/u-boot
> git checkout v2012.04.01
> make CROSS_COMPILE=arm-none-linux-gnueabi- dreamplug_config
> make -j16 CROSS_COMPILE=arm-none-linux-gnueabi- u-boot.kwb
> 
> This yields 'u-boot' and 'u-boot.kwb' in the top of the source tree.
> 
> 2) launch openocd in the same directory
> 
> sudo openocd -f /usr/share/openocd/scripts/board/sheevaplug.cfg
> 
> 3) in another terminal, telnet into openocd
> 
> telnet localhost 4444
> 
> 4) in TELNET session, do the following
> 
> sheevaplug_init
> load_image u-boot
> load_image u-boot.kwb 0x0800000
> resume 0x0600000
> 
> 5) Quick, jump over to SERIAL terminal and hit a key to stop the boot
> 
> 6) In SERIAL session, flash the image
> 
> sf probe 0
> sf erase 0x0 0x100000
> sf write 0x0800000 0x0 0x100000
> # and then test with
> reset
> 
> 7) pause the bootup and configure the u-boot environment
> 
> from there you should be good to go.
> 
> hth,
> 
> Jason.