I've also managed to get a functional system running completely from nand, though using  slightly different method.  I believe this would have worked earlier were it not for a small typo in my bootargs.

When I replaced rootfs=jffs2 with rootfstype=jffs2 everything seems fat and happy.  This is from the unit with the bad flash - evidently mtd doesn't handle bad blocks, so I had to define the MTD geometry in a bootarg to work around the erase errors, giving me a 64mb rootfs.

BusyBox v1.15.3 (2010-07-07 10:18:36 CDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 Backfire (10.03, r22076) --------------------------
  * 1/3 shot Kahlua    In a shot glass, layer Kahlua
  * 1/3 shot Bailey's  on the bottom, then Bailey's,
  * 1/3 shot Vodka     then Vodka.
 ---------------------------------------------------
root@OpenWrt:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                64.0M      3.5M     60.5M   6% /
tmpfs                    62.3M     24.0K     62.3M   0% /tmp
tmpfs                   512.0K         0    512.0K   0% /dev
root@OpenWrt:~# mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (rw,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=63804k)
tmpfs on /dev type tmpfs (rw,relatime,size=512k)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
none on /proc/bus/usb type usbfs (rw,relatime)
root@OpenWrt:~#

I'll start regressing my work from 'make clean' and flash onto a 'virgin' dockstar while I anxiously await ECC's how-to...

I've posted a first draft of a HOWTO.  Any feedback would be much appreciated.

I also posted a followup that does not require opening the case or attaching a serial cable.

I bought one Seagate Dockstar from Amazon Marketplace. Price was USD 34.88 shipped. Can't wait to hack it to run Backfire.

Hopefully this is not considered off topic, but I just got my GoFlex NET box today and cracked it open.

hooked up the serial console - with the bottom towards you (bottom case clicks off with a small screwdriver or knife) - there's a 10 pin header to the bottom right ( the end where the leds are) the bottom row from the right is:

0V
Txd (output from the GoFlex)
Rxd (input to the goflex)

The usual 115200 baud 8 bits no parity.
I used a cheapy CA42 nokia style cable and the color were (in the same sequence above)
Orange (0v)
Red (txd)
Blue (Rxd)

You get into the console with no password required. (note! I haven't hooked it up to the net yet!)

U-Boot 1.1.4  Cloud Engines 1.1.2 (3.4.22) SATA PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00691750

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: DISCOVERY:0.1

Streaming disabled
Write allocate disabled

USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  3  2  1  0

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x100000 --   0% complete.
Reading data from 0x107800 --   1% complete.
Reading data from 0x10f000 --   2% complete.
Reading data from 0x117000 --   3% complete.
Reading data from 0x11e800 --   4% complete.
Reading data from 0x126000 --   5% complete.
Reading data from 0x12e000 --   6% complete.
Reading data from 0x135800 --   7% complete.
Reading data from 0x13d000 --   8% complete.
Reading data from 0x145000 --   9% complete.
Reading data from 0x14c800 --  10% complete.
Reading data from 0x154000 --  11% complete.
Reading data from 0x15c000 --  12% complete.
Reading data from 0x163800 --  13% complete.
Reading data from 0x16b800 --  14% complete.
Reading data from 0x173000 --  15% complete.
Reading data from 0x17a800 --  16% complete.
Reading data from 0x182800 --  17% complete.
Reading data from 0x18a000 --  18% complete.
Reading data from 0x191800 --  19% complete.
Reading data from 0x199800 --  20% complete.
Reading data from 0x1a1000 --  21% complete.
Reading data from 0x1a8800 --  22% complete.
Reading data from 0x1b0800 --  23% complete.
Reading data from 0x1b8000 --  24% complete.
Reading data from 0x1bf800 --  25% complete.
Reading data from 0x1c7800 --  26% complete.
Reading data from 0x1cf000 --  27% complete.
Reading data from 0x1d7000 --  28% complete.
Reading data from 0x1de800 --  29% complete.
Reading data from 0x1e6000 --  30% complete.
Reading data from 0x1ee000 --  31% complete.
Reading data from 0x1f5800 --  32% complete.
Reading data from 0x1fd000 --  33% complete.
Reading data from 0x205000 --  34% complete.
Reading data from 0x20c800 --  35% complete.
Reading data from 0x214000 --  36% complete.
Reading data from 0x21c000 --  37% complete.
Reading data from 0x223800 --  38% complete.
Reading data from 0x22b800 --  39% complete.
Reading data from 0x233000 --  40% complete.
Reading data from 0x23a800 --  41% complete.
Reading data from 0x242800 --  42% complete.
Reading data from 0x24a000 --  43% complete.
Reading data from 0x251800 --  44% complete.
Reading data from 0x259800 --  45% complete.
Reading data from 0x261000 --  46% complete.
Reading data from 0x268800 --  47% complete.
Reading data from 0x270800 --  48% complete.
Reading data from 0x278000 --  49% complete.
Reading data from 0x27f800 --  50% complete.
Reading data from 0x287800 --  51% complete.
Reading data from 0x28f000 --  52% complete.
Reading data from 0x297000 --  53% complete.
Reading data from 0x29e800 --  54% complete.
Reading data from 0x2a6000 --  55% complete.
Reading data from 0x2ae000 --  56% complete.
Reading data from 0x2b5800 --  57% complete.
Reading data from 0x2bd000 --  58% complete.
Reading data from 0x2c5000 --  59% complete.
Reading data from 0x2cc800 --  60% complete.
Reading data from 0x2d4000 --  61% complete.
Reading data from 0x2dc000 --  62% complete.
Reading data from 0x2e3800 --  63% complete.
Reading data from 0x2eb800 --  64% complete.
Reading data from 0x2f3000 --  65% complete.
Reading data from 0x2fa800 --  66% complete.
Reading data from 0x302800 --  67% complete.
Reading data from 0x30a000 --  68% complete.
Reading data from 0x311800 --  69% complete.
Reading data from 0x319800 --  70% complete.
Reading data from 0x321000 --  71% complete.
Reading data from 0x328800 --  72% complete.
Reading data from 0x330800 --  73% complete.
Reading data from 0x338000 --  74% complete.
Reading data from 0x33f800 --  75% complete.
Reading data from 0x347800 --  76% complete.
Reading data from 0x34f000 --  77% complete.
Reading data from 0x357000 --  78% complete.
Reading data from 0x35e800 --  79% complete.
Reading data from 0x366000 --  80% complete.
Reading data from 0x36e000 --  81% complete.
Reading data from 0x375800 --  82% complete.
Reading data from 0x37d000 --  83% complete.
Reading data from 0x385000 --  84% complete.
Reading data from 0x38c800 --  85% complete.
Reading data from 0x394000 --  86% complete.
Reading data from 0x39c000 --  87% complete.
Reading data from 0x3a3800 --  88% complete.
Reading data from 0x3ab800 --  89% complete.
Reading data from 0x3b3000 --  90% complete.
Reading data from 0x3ba800 --  91% complete.
Reading data from 0x3c2800 --  92% complete.
Reading data from 0x3ca000 --  93% complete.
Reading data from 0x3d1800 --  94% complete.
Reading data from 0x3d9800 --  95% complete.
Reading data from 0x3e1000 --  96% complete.
Reading data from 0x3e8800 --  97% complete.
Reading data from 0x3f0800 --  98% complete.
Reading data from 0x3f8000 --  99% complete.
Reading data from 0x3ff800 -- 100% complete.
3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2010-02-08  23:13:14 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1978884 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................ done, booting the kernel.
[    0.000000] Linux version 2.6.22.18 (bdietrich@brad-ux) (gcc version 4.2.1) #76 Mon Feb 8 15:13:08 PST 2010
[    0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] Machine: Feroceon-KW
[    0.000000] Using UBoot passing parameters structure
[    0.000000] CE: Received CE uboot parameters:
[    0.000000] CE:    BOARDID: DISCOVERY:0.1
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] CPU0: D VIVT write-back cache
[    0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] Built 1 zonelists.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB 0MB 0MB 0MB = 128MB total
[    0.000000] Memory: 125824KB available (3592K code, 253K data, 124K init)
[    0.240000] Mount-cache hash table entries: 512
[    0.240000] CPU: Testing write buffer coherency: ok
[    0.240000] NET: Registered protocol family 16
[    0.240000]
[    0.240000] CPU Interface
[    0.240000] -------------
[    0.240000] SDRAM_CS0 ....base 00000000, size 128MB
[    0.240000] SDRAM_CS1 ....disable
[    0.240000] SDRAM_CS2 ....disable
[    0.240000] SDRAM_CS3 ....disable
[    0.240000] PEX0_MEM ....base e8000000, size 128MB
[    0.240000] PEX0_IO ....base f2000000, size   1MB
[    0.240000] INTER_REGS ....base f1000000, size   1MB
[    0.240000] NFLASH_CS ....base fa000000, size   2MB
[    0.240000] SPI_CS ....base f4000000, size  16MB
[    0.240000] BOOT_ROM_CS ....no such
[    0.240000] DEV_BOOTCS ....no such
[    0.240000] CRYPT_ENG ....base f0000000, size   2MB
[    0.240000]
[    0.240000]   Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG  Soc: 88F6281 A0 LE
[    0.240000]
[    0.240000]  Detected Tclk 200000000 and SysClk 400000000
[    0.240000] MV Buttons Device Load
[    0.240000] Marvell USB EHCI Host controller #0: c0539600
[    0.740000] PEX0 interface detected no Link.
[    0.740000] PCI: bus0: Fast back to back transfers enabled
[    0.740000] SCSI subsystem initialized
[    0.740000] usbcore: registered new interface driver usbfs
[    0.740000] usbcore: registered new interface driver hub
[    0.740000] usbcore: registered new device driver usb
[    0.740000] NET: Registered protocol family 2
[    0.750000] Time: kw_clocksource clocksource has been installed.
[    0.840000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.840000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.840000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.840000] TCP: Hash tables configured (established 4096 bind 4096)
[    0.840000] TCP reno registered
[    0.870000] RTC has been updated!!!
[    0.870000] RTC registered
[    0.870000] Use the XOR engines (acceleration) for enhancing the following functions:
[    0.870000]   o RAID 5 Xor calculation
[    0.870000]   o kernel memcpy
[    0.870000]   o kenrel memzero
[    0.870000] Number of XOR engines to use: 4
[    0.870000] cesadev_init(c00117b0)
[    0.870000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
[    0.870000] MV Buttons Driver Load
[    0.870000] squashfs: version 3.3 (2007/10/31) Phillip Lougher
[    0.870000] squashfs: LZMA suppport for slax.org by jro
[    0.870000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.870000] io scheduler noop registered
[    0.870000] io scheduler anticipatory registered (default)
[    0.880000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[    0.890000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    0.910000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
[    0.910000] Loading Marvell Ethernet Driver:
[    0.920000]   o Cached descriptors in DRAM
[    0.920000]   o DRAM SW cache-coherency
[    0.930000]   o Single RX Queue support - ETH_DEF_RXQ=0
[    0.930000]   o Single TX Queue support - ETH_DEF_TXQ=0
[    0.940000]   o TCP segmentation offload enabled
[    0.940000]   o Receive checksum offload enabled
[    0.950000]   o Transmit checksum offload enabled
[    0.950000]   o Network Fast Processing (Routing) supported
[    0.960000]   o Driver ERROR statistics enabled
[    0.960000]   o Driver INFO statistics enabled
[    0.970000]   o Proc tool API enabled
[    0.970000]   o Rx descripors: q0=128
[    0.970000]   o Tx descripors: q0=532
[    0.980000]   o Loading network interface(s):
[    0.980000]     o eth0, ifindex = 1, GbE port = 0
[    0.990000]
[    0.990000] Warning: Giga 1 is Powered Off
[    0.990000]
[    0.990000] mvFpRuleDb (c7f15000): 1024 entries, 4096 bytes
[    1.000000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[    1.010000] Copyright (c) 1999-2006 Intel Corporation.
[    1.010000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[    1.020000] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.020000] Integrated Sata device found
[    1.050000] scsi0 : Marvell SCSI to SATA adapter
[    1.050000] scsi1 : Marvell SCSI to SATA adapter
[    1.060000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[    1.070000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[    1.080000] Scanning device for bad blocks
[    1.170000] Using static partition definition
[    1.170000] Creating 4 MTD partitions on "nand_mtd":
[    1.180000] 0x00000000-0x00100000 : "u-boot"
[    1.180000] 0x00100000-0x00500000 : "uImage"
[    1.190000] 0x00500000-0x02500000 : "root"
[    1.190000] 0x02500000-0x10000000 : "data"
[    1.200000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[    1.200000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[    1.240000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[    1.260000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    1.260000] usb usb1: configuration #1 chosen from 1 choice
[    1.270000] hub 1-0:1.0: USB hub found
[    1.270000] hub 1-0:1.0: 1 port detected
[    1.390000] USB Universal Host Controller Interface driver v3.0
[    1.390000] usbcore: registered new interface driver usblp
[    1.400000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
[    1.400000] Initializing USB Mass Storage driver...
[    1.410000] usbcore: registered new interface driver usb-storage
[    1.420000] USB Mass Storage support registered.
[    1.420000] mice: PS/2 mouse device common for all mice
[    1.430000] i2c /dev entries driver
[    1.430000] Linux telephony interface: v1.00
[    1.430000] md: linear personality registered for level -1
[    1.440000] md: raid0 personality registered for level 0
[    1.440000] md: raid1 personality registered for level 1
[    1.620000] raid6: int32x1     98 MB/s
[    1.790000] raid6: int32x2    114 MB/s
[    1.960000] raid6: int32x4    122 MB/s
[    2.130000] raid6: int32x8    110 MB/s
[    2.130000] raid6: using algorithm int32x4 (122 MB/s)
[    2.130000] md: raid6 personality registered for level 6
[    2.140000] md: raid5 personality registered for level 5
[    2.140000] md: raid4 personality registered for level 4
[    2.150000] raid5: measuring checksumming speed
[    2.200000]    arm4regs  :  1084.400 MB/sec
[    2.250000]    8regs     :   754.800 MB/sec
[    2.300000]    32regs    :   900.000 MB/sec
[    2.300000] raid5: using function: arm4regs (1084.400 MB/sec)
[    2.310000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[    2.310000] dm_crypt using the OCF package.
[    2.320000] sdhci: Secure Digital Host Controller Interface driver
[    2.320000] sdhci: Copyright(c) Pierre Ossman
[    2.330000] usbcore: registered new interface driver usbhid
[    2.330000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[    2.340000] TCP cubic registered
[    2.340000] NET: Registered protocol family 1
[    2.350000] NET: Registered protocol family 17
[    2.350000] md: Autodetecting RAID arrays.
[    2.360000] md: autorun ...
[    2.360000] md: ... autorun DONE.
[    5.520000] Empty flash at 0x00e54e48 ends at 0x00e55000
[    5.620000] VFS: Mounted root (jffs2 filesystem) readonly.
[    5.630000] Freeing init memory: 124K

init started: BusyBox v1.7.0 (2008-02-26 19:25:17 IST)

starting pid 264, tty '': '/etc/init.d/rcS'
[    7.100000] eth0: started
udhcpc (v1.7.0) started
HWADDR 00 0x10 0x75 0x26 0x17 0x3c
PIP0 23
PIP1 60
Sending discover...
Sending discover...
Sending discover...
HWADDR 00 0x10 0x75 0x26 0x17 0x3c
PIP0 23
PIP1 60
Unexpected Argument: leasefail
interface=eth0
PATH=/sbin:/usr/sbin:/bin:/usr/bin
PWD=/
SHLVL=1
HOME=/
_=/bin/printenv
No lease, forking to background
Loading fs modules:          [   17.080000] fuse init (API version 7.8)
Success
[   17.360000] ufsd: module license 'Commercial product' taints kernel.
[   17.530000] ufsd: driver 8.1 (011_A) LBD=ON with ioctl loaded at bf040000
[   17.530000] NTFS read/write support included
[   17.530000] Hfs+/HfsX read/write support included
Loading tun.ko:              [   17.550000] tun: Universal TUN/TAP device driver, 1.6
[   17.560000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Success
Loading xce.ko:              [   17.580000] Cloud Engines XCE Init [Version: 2.0.5.10]
[   17.590000] XCE: CPU MEMORY MAP:
[   17.590000] XCE:   -- 0x00001000 - 0xbeffffff (3055 MB)  User Space Mappings
[   17.600000] XCE:   -- 0xbf000000 - 0xbfffffff (  16 MB)  Kernel module space
[   17.610000] XCE:   -- 0xc0000000 - 0xc7ffffff ( 128 MB)  Kernel direct-mapped ram
[   17.610000] XCE:   -- 0xc8800000 - 0xe7ffffff ( 504 MB)  Kernel vmalloc space
[   17.620000] XCE:   -- 0xe8000000 - 0xfeffffff ( 367 MB)  Kernel platform space
[   17.630000] XCE: CPU FEATURES:
[   17.630000] XCE:   -- I Cache:         enabled
[   17.640000] XCE:   -- D Cache:         enabled
[   17.640000] XCE:   -- Branch Predict:  disabled
[   17.640000] XCE:   -- MMU:             enabled
[   17.650000] XCE:   -- Alignment Abort: enabled
[   17.650000] XCE:   -- ICache Prefetch: enabled
[   17.660000] XCE:   -- DCache Prefetch: enabled
[   17.660000] XCE:   -- L2 Cache:        enabled
[   17.670000] XCE:   -- L2 Prefetch:     disabled
[   17.670000] XCE:   -- L2 Writethrough: disabled
[   17.680000] XCE:   -- Write Allocate:  disabled
[   17.680000] XCE:   -- Streaming:       disabled
[   17.680000] XCE: BLPARAMS: reading 2048 bytes @ a0000
[   17.690000] XCE: Loaded Property Size: 2048
[   17.700000] XCE:    - 'cesvcid' -> 'FE4BUTMVFW9KWSBBFFFKC258ZE'
[   17.700000] XCE:    - 'ceserialno' -> 'NA1Y05F8'
[   17.710000] XCE:    - 'ceboardver' -> 'DISCOVERY:0.1'
[   17.710000] XCE: Current GPIO State:
[   17.710000] XCE:  GPIO L OUT:    0xeff00000
[   17.720000] XCE:  GPIO L OE:     0xffffffff
[   17.720000] XCE:  GPIO L BLINK:  0x00000000
[   17.730000] XCE:  GPIO L POL:    0x00000000
[   17.730000] XCE:  GPIO L IN:     0xfff00080
[   17.740000] XCE:  GPIO H OUT:    0xfffcc00f
[   17.740000] XCE:  GPIO H OE:     0xfffc000f
[   17.740000] XCE:  GPIO H BLINK:  0x00000000
[   17.750000] XCE:  GPIO H POL:    0x00000000
[   17.750000] XCE:  GPIO H IN:     0x0000c00d
[   17.760000] XCE: Kernel thread starting PID: 332
Success
Starting hbplug:             Success

starting pid 334, tty '': '/bin/sh'
-sh-3.2# [   18.620000] XCE: BLPARAMS: reading 2048 bytes @ a0000
[   18.620000] XCE: BLPARAMS: reading 2048 bytes @ a0800
[   18.630000] XCE: BLPARAMS: reading 2048 bytes @ a1000
[   18.640000] XCE: BLPARAMS: reading 2048 bytes @ a1800
[   23.920000] XCE: XCE: LED -> DISCONNECTED

Linux version is:
-sh-3.2# cat /proc/version
Linux version 2.6.22.18 (bdietrich@brad-ux) (gcc version 4.2.1) #76 Mon Feb 8 15:13:08 PST 2010

-sh-3.2# cat /proc/cpuinfo
Processor       : ARM926EJ-S rev 1 (v5l)
BogoMIPS        : 1192.75
Features        : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1
Cache type      : write-back
Cache clean     : cp15 c7 ops
Cache lockdown  : format C
Cache format    : Harvard
I size          : 16384
I assoc         : 4
I line length   : 32
I sets          : 128
D size          : 16384
D assoc         : 4
D line length   : 32
D sets          : 128

Hardware        : Feroceon-KW
Revision        : 0000
Serial          : 0000000000000000

The hardware looks much the same as the Dockstar except there's two sata ports and only one usb.

Can anyone tell me if the Dockstar build will work on this?

Very likely, although if you use my precompiled images there won't be any SATA support.

Since you already have serial console access, it's easy and non-destructive to try it out: use the tftpboot command to load the image from a TFTP server on your network into RAM, and boot the system from there using the bootm command. But you won't have the OpenWrt rootfs, so it's just a test to see if the kernel makes it that far.

For those late-comers,
I just got myself another one although I would prefer to pay $1 when that other site were clearing them out

http://www.1saleaday.com/

@ecc - the GoFlex happily accepts your build. I haven't tried the sata ports as yet. What I am having problems with is trying to get usb serial devices and video for linux going.

When I install ftdi_sio I get this:
root@OpenWrt:/etc/modules.d# insmod ftdi_sio
ftdi_sio: Unknown symbol kmem_cache_alloc_notrace
ftdi_sio: Unknown symbol __tracepoint_kmalloc
ftdi_sio: Unknown symbol slab_buffer_size

similarly for this:
root@OpenWrt:/etc/modules.d# insmod v4l1-compat.ko
root@OpenWrt:/etc/modules.d# insmod v4l1-compat
v4l1_compat: Unknown symbol kmem_cache_alloc_notrace
v4l1_compat: Unknown symbol __tracepoint_kmalloc
v4l1_compat: Unknown symbol slab_buffer_size

maybe I've just forgotten to load a specific driver, but I don't know which one it would be. Can someone assist?

If you use my precompiled kernel and rootfs, which includes only a minimal selection of modules, then you can't use the official kirkwood module packages (because they're incompatible with my patched kernel).  The only solution currently is to compile your own kernel and build the modules you want.  (See also this thread.)

Seems I'm having a few troubles compiling the kernel. I used the trunk sources to build with that I downloaded on thursday (r22819).

This is what I get:

USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x3ff800 -- 100% complete.
3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.35.3
   Created:      2010-08-28  12:35:08 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1025396 Bytes = 1001.4 kB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.35.3 (root@ubuntu) (gcc version 4.4.4 (GCC) ) #4 Sat Aug 28 22:34:55 EST 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Seagate FreeAgent DockStar
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 127132k/127132k available, 3940k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xc8800000 - 0xfe800000   ( 864 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0022000   ( 104 kB)
      .text : 0xc0022000 - 0xc0297000   (2516 kB)
      .data : 0xc0298000 - 0xc02ac340   (  81 kB)
NR_IRQS:114
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A0, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
SCSI subsystem initialized
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
msgmni has been set to 248
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Creating 4 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000002500000 : "rootfs"
0x000002500000-0x000010000000 : "rootfs_data"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:10:75:26:17:3c
rtc-mv rtc-mv: internal RTC not ticking
i2c /dev entries driver
cpuidle: using governor ladder
TCP westwood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>

and it all stops here.

note: I did have to patch the dockstar-config.c file as the nand partitions didn't seem to line up with what they should've been. Eg: uImage was 64M where it is 32M and there was a secondary uboot partition of 3M - this I deleted. Also note I've enabled SATA support since I'm using a GoFlex NET rather than a Dockstar.

Mazilo - how exactly have you been able to build a usable openwrt?

I configured/built OpenWRT firmware for my DockStar from my local SVN development trunk like you had done, except sans patches. I configured my DockStar device to dual boot using this step-by-step Pogoplug Setboot instructions. I extracted the newly built firmware to a USB memory stick (after creating/formatting the USB memory partition to EXT3) and plugged it into one of the 3 USB ports. When my DockStar is powered up, it will first boot into its original DockStar firmware. I logged into my DockStar and execute a reboot. The device will reboot and boots off from the USB memory stick that contains OpenWRT.

FYI, if you flash the NAND partition with your built OpenWRT firmware, you may want to read posts on this discussion thread. Pay particular attention on this post w.r.t the arcNumber. Just in case you ask, I don't use this approach nor do this on my DockStar. If I change the arcNumber, my DockStar probably will no longer be able to boot the original Seagate DockStar firmware.

If anyone is interested in a Seagate DockStar, currently Fry's Electronics has it for $24.99 as seen here. It is an online purchase with only a store pick up. So, there must be a local Fry's Electronics store nearby your premises.

I'm having trouble getting the u-boot to run on my dockstar. I've compiled from the latest trunk and followed lar's instructions but all it does it sit dead when the 2nd bootloader runs.

I've changed the arcNumber to 2998 - no difference. Has anyone got a working bin file for me to try?

Here's my env from the initial u-boot:

CE>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
run_diag=yes
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
ethaddr=00:10:75:26:17:3C
cesvcid=FE4BUTMVFW9KWSBBFFFKC258ZE
ceserialno=NA1Y05F8
ceboardver=DISCOVERY:0.1
bootcmd_usb=nand read.e 0xc00000 0x2500000 0x80000; go 0xc00000
bootcmd1=setenv bootcmd run bootcmd2; saveenv; run bootcmd_usb
bootcmd2=setenv bootcmd run bootcmd1; saveenv; run bootcmd_original
bootcmd_original=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000
filesize=29078
fileaddr=800000
netmask=255.255.0.0
ipaddr=192.168.1.109
serverip=192.168.1.100
bootcmd=nand read.e 0x800000 0x100000 0x40000; go 0x800000
arcNumber=2998
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=a0000
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
pcieTune=no

Environment size: 1099/131068 bytes
CE>>

(Last edited by Kartman on 7 Sep 2010, 13:02)

I haven't tried to use or debug the version that's checked into OpenWrt. But here are two known working ones:

1. Image built by Jeff Doozan (see installation instructions and LED configuration)

2. Image built by me (available here).  The patches I used are available in the same directory.

My version hard-codes the machine type to 2998, so your kernel must recognize that. It also hard-codes the LED support.  Jeff's version has configurable LED support, and I'm pretty sure requires you to use machine type 2097.  (The arcNumber and mainlineUnix stuff in the environment was pogoplug-specific -- these versions are derived from the official uboot git tree and don't include it.)

Also: I think Jeff's version moves the environment area to 0xC0000 so it doesn't clobber the one used by the pogoplug version (at 0xA0000).  My version keeps it at 0xA0000, since I didn't care about reverting to the the pogoplugs version.  You'll have to configure fw_setenv/fw_printenv accordingly, using /etc/fw_env.config.

Finally, although you might be tempted to test these out by loading them into memory and chainbooting, that won't work, because they  relocate themselves to 0x600000, the same place as the current u-boot.  So you have to just take the plunge and flash them to mtd0.  (Others have been successful using JTAG to restore the u-boot partition, so it's not too risky.)

As explained by ECC on the above post, currently it may be too confusing for any (new) DockStar owners to follow because there are several different approaches that may not be compatible to each one.

What I was hoping is OpenWRT's support will combine the mtd1, mtd2, and mtd3 partitions into a single big chunk parition of a 255MB and use a 1-stage u-boot to replace the existing (original) u-boot on mtd0 parition. Sure this has an after effect for not being able to revert to the original firmware. Heck ain't we all here wanting to hack our DockStar units to boot OpenWRT for good?

Eric, I'm currently using your Openwrt images at the moment. The problem is I need some more drivers and I have no idea how to build these for your kernel. I've tried using the backfire ones as they are built for the same kernel release, but I get complaints when I insmod them - certain functions aren't available. As for your u-boot, I haven't tried that. It could be that if my trunk build of the u-boot doesn't work, then will the kernel work? I tried running the kernel and it faulted. Maybe I've trashed my build environment?

Unfortunately my Linux skills aren't good enough to really dig in to find the problems. Such is life on the bleeding edge! I got a friend to source me a number of Dockstars from the Bay area so hopefully they'll land on my doorstep in a week or so (I'm in Australia). This will give me more to play with. Basically, all I need is the internal nand to store my stuff, so putting Debian on is overkill and having it on a usb stick is do-able, but not something I'd like.

I'm cursing I got the GoFlex net since the Iomega iConnect is the same price here, but gives you more ram,nand and wifi!

(Last edited by Kartman on 8 Sep 2010, 01:28)

If you build from Trunk, then you can do opkg's to your hearts content. You must do an 'opkg update' first of course.
The instructions on the OpenWRT Wiki work fine.

Kartman: can you post the serial console output from the end of the first u-boot? Don't interrupt it....

Also watch which u-boot is active when you edit using 'setenv'. For the Wiki instructions to work, you must be in the second u-boot to install the kernel and jffs2 file system. You use the first u-boot's env only to install the chained u-boot. (I am editing some changes off line to add to the wiki to indicate some of these Notes. Should be ready on Wed.)

Gerrit

(Last edited by z80yyz on 8 Sep 2010, 01:09)

Gerrit, I look forward to your additions. The very reason I used the trunk was the availability of the opkgs. I dread having to manually build stuff!

I'll post the serial output tonight (morning here at the moment).

Thanks to all for their contributions to the cause. I'm sure I'll be finding GoFlex/Dockstar nirvana soon.

The instructions on the Wiki seem a little confusing. I tried loading my images via OpenWrt (Eric's images) and trashed the uboot in the process but I realised this and was able to recover since I had a copy of the original mtd images. So I restored the original images and played around with OpenPogo.

Some of the numbers (addresses,sizes) vary between the instructions for the uboot load (using serial) and loading via linux. Both would give the same result. Interestingly, I made a mistake and the normal bootcmd was activated. This would give me the message "Bad magic number" - I assumed this was referring to the arcNumber, but it gave the same results regardless of 2097 or 2998. In all my fiddling, I forgot to grab the uboot output.

I might just wait for my Dockstars to turn up and do a complete clean build in the meantime.

On a different note, I have a suspicion that the GoFlex net firmware is no different to the Dockstar as there are references to FreeAgent in the boot text. It could be that all the Kirkwood peripherals are supported Linux wise, but not implemented in the hardware.

Well, I got my stash of Dockstars from the US. I've managed to build OpenWrt from trunk and load it successfully as well as build the required drivers and packages.

There's the issue of the left over nand flash named 'data'. Is there any way we can use this? I'm sure the build can be modified to use this as Eric has done, but how to do it? I'd much prefer 200+MB rather than 32MB!

Also the issue of having GCC built for native use on the Dockstar. Is there a means in the normal menuconfig to enable this? I've tried ./scripts/feeds install gcc and couldn't find anything to enable the build.

I am not sure exactly what you meant since I only use OpenWRT firmware on an external USB partition. Can you post here the output of your cat /proc/mtd, cat /proc/mounts, and df? On my DockStar running a self-built OpenWRT booted through an external USB partition, here is the console dump and I don't see any left over space named data from the output of cat /proc/mtd:

root@DockStar:/usr/share/freeswitch/conf# cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 0fb00000 00020000 "rootfs"
root@DockStar:/usr/share/freeswitch/conf# cat /proc/mounts 
rootfs / rootfs rw 0 0
/dev/root / ext2 rw,relatime,errors=continue 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,nosuid,nodev,relatime 0 0
tmpfs /dev tmpfs rw,relatime,size=512k 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
root@DockStar:/usr/share/freeswitch/conf# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root               744552    292568    414164  41% /
tmpfs                    63032         8     63024   0% /tmp
tmpfs                      512         0       512   0% /dev

AFAIK, there is no supports of a native GCC compiler on OpenWRT. With the support of a Seagate DockStar, Sheeve Plug, and/or intel/AMD platform, I open OpenWRT will soon add the support for a native GCC compiler.

If a native GCC compiler is a MUST for you, perhaps you should consider flashing your DockStar with embebian (Debian) and/or Ubuntu.

Mazi, do we have two Erics here? The Eric build I was referring to was ECC's - his build uses the last flash block as an overlay. If ECC or others  can give me a poke in the right direction?

As for gcc, I've yet to raise my psi power to the level required to tackle building gcc. I fear there be dragons lurking. Having gcc isnt a necessity, but it does give a level of convenience.

I originally set things up with a read-only squashfs root image in mtd2 and a writable jffs2 overlay in mtd3.  But I think the version that's now checked in the official OpenWrt tree just uses jffs2 on a single large mtd2 partition (there's no mtd3).  I'd suggest using that version since it's auto-built and all the kernel module packages should work with it.

Kartman, how's it going with the Goflex Net sata driver? Have you managed to mount a sata drive using openwrt? Would be great if it can be done since we can go over 30 MB/s with a sata drive attached.

mazilo, thanks for the hint about putting uImage in /boot to boot openwrt from USB. I got uboot in mtd0 to chainload to uboot (Jeff's version) in mtd3, which loads kernel image /boot/uImage from USB and successfully boots openwrt. This is great since it's safe and works for Debian too.

(Last edited by playdude on 22 Sep 2010, 15:19)

Can anyone confirm this? If so, then the openwrt-kirkwood-dockstar-u-boot.bin should support a 1-stage boot (not a 2-stage boot as mentioned in the OpenWRT Doc for Seagate DockStar).