aboutsummaryrefslogtreecommitdiffstats
path: root/freedom-maker/flashing-notes
diff options
context:
space:
mode:
authorficus <ficus@robocracy.org>2012-10-04 16:13:54 +0200
committerficus <ficus@robocracy.org>2012-10-04 16:29:05 +0200
commit60eb2616ed83209b8e46aba14c19814ab4f4c1c6 (patch)
treea17d4c26d47148cb2b2c96470ecc22c993fcf7be /freedom-maker/flashing-notes
parentfcf6a8630b7ae818e7719d6e811d01d9359388c3 (diff)
downloadtorouter-60eb2616ed83209b8e46aba14c19814ab4f4c1c6.tar.gz
torouter-60eb2616ed83209b8e46aba14c19814ab4f4c1c6.zip
sd card refactor
Diffstat (limited to 'freedom-maker/flashing-notes')
-rw-r--r--freedom-maker/flashing-notes28
1 files changed, 0 insertions, 28 deletions
diff --git a/freedom-maker/flashing-notes b/freedom-maker/flashing-notes
deleted file mode 100644
index def3f61..0000000
--- a/freedom-maker/flashing-notes
+++ /dev/null
@@ -1,28 +0,0 @@
-Jason <u-boot@lakedaemon.net> says:
-
- 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.
-