On Sun, Jul 24, 2011 at 03:56:57PM +0000, Clint Adams wrote: > On Sun, Jul 24, 2011 at 01:12:01AM +0000, u-b...@lakedaemon.net wrote: > > rewrite of the not-merged code from Globalscale Technologies. This RTC is > > known to exist in the DreamPlug platform and is accessed via two registers. > > If I apply this on top of your v4 patch on top of 2011.06, I only need two > tweaks to build: MACH_TYPE_DREAMPLUG which will obviously sort itself out, > and s/MPP7_GP0/MPP7_GPO/ in board/Marvell/dreamplug/dreamplug.c .
Yes, what an embarrassing typo, that shouldn't even build. :-( Well, it was RFC... > It has not yet been tested on a plug. Do you have a working OpenOCD config > for flash/ram? Sort of. The openocd config for the sheevaplug/guruplug is what I use, and is distributed on the dreamplug download page [1]. It does _not_ have support for the SPI flash. You can also use the sheevaplug.cfg shipped with openocd. So, I use openocd or tftp to transfer to RAM, then use u-boot to write to flash. To test images, or to reflash, I load the known-good u-boot into RAM via openocd, then I'll either reflash it or load a new testing one from there. To write a u-boot.kwb test image to flash, here is what I do: openocd$ sheevaplug_init openocd$ load_image u-boot # known good from Marvell openocd$ load_image u-boot.kwb 0x00800000 # monster I created openocd$ resume 0x00600000 # run the known good then, in u-boot u-boot$ sf probe 0 u-boot$ sf erase 0x0 0x100000 u-boot$ sf write 0x00800000 0x0 0x100000 If time allows, I'd like to add SPI flash support to OpenOCD. Unfortunately, time is short and the above process works. hth, Jason. [1] http://code.google.com/p/dreamplug/downloads/detail?name=dream_burn_spi.tar.bz2&can=2&q= _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
