Zyxel NSA3x0S u-boot-2014.07-tld-4 for testing

> No - no - yes - OK - OK. ******* HDD2 was not initialized? But boot OK?
Correct

> Yes - no - yes - OK - OK. ****** HDD2 was initilized, and boot OK?
Correct

> > Yes - no - yes - OK - OK. ****** HDD2 was
> initilized, and boot OK?
> Correct

This is good. It means we might put a long sleep period after ide reset and see if it helps.

With 2 HDDs:

poke
ide reset
sleep 60
usb start

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

With 2 HHDs, doing
run poke; ide reset; sleep 60; usb start

Launch Debian (the macro scan_disk includes "ide reset") - looks OK:

root@debian:~# dmesg | grep -i SATA
[    2.626551] sata_mv f1080000.sata: version 1.28
[    2.626885] sata_mv f1080000.sata: slots 32 ports 2
[    2.703914] scsi host0: sata_mv
[    2.723822] scsi host1: sata_mv
[    2.727368] ata1: SATA max UDMA/133 irq 32
[    2.731448] ata2: SATA max UDMA/133 irq 32
[    3.274195] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    3.873696] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)

Nearly there :)

Launch NetBSD with:
run poke; ide reset; sleep 60; usb start; fatload usb 0 0x800000 /netbsd.ub; bootm 0x800000

Boot ok until it detects the USB root drive and then fails as previously:

umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
vfs_mountroot: can't open root device

Full log with emphasis below.
So it can see both HDD's, both pendrives, and chokes when trying to initialise the pen drives (both of them).

run poke; ide reset; sleep 60; usb start; fatload usb 0 0x800000 /netbsd.ub; bootm 0x800000

Reset IDE: Bus 0: OK Bus 1: .......OK
  Device 0: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#:  WD-WCC4MHECYZUX
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
  Device 1: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#:  WD-WCC4MCY6Y4AH
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
       scanning usb for storage devices...
Use USB retry period from the environment: 45 second(s)

Use USB retry period from the environment: 45 second(s)
2 Storage Device(s) found
reading /netbsd.ub
4452292 bytes read in 181 ms (23.5 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   NetBSD/ 7.99.26
   Created:      2016-01-31  11:16:27 UTC
   Image Type:   ARM NetBSD Kernel Image (uncompressed)
   Data Size:    4452228 Bytes = 4.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
## Transferring control to NetBSD stage-2 loader (at address 00008000) ...

NetBSD/evbarm (Marvell) booting ...
[ Kernel symbol table missing! ]
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 7.99.26 (NSA320s) #1: Sun Jan 31 11:15:46 GMT 2016
        michael@odroid:/home/michael/src/netbsd/sys/arch/evbarm/compile/obj/NSA320s
total memory = 256 MB
avail memory = 245 MB
sysctl_createv: sysctl_create(machine_arch) returned 17
mainbus0 (root)
cpu0 at mainbus0 core 0: Sheeva 88SV131 rev 1 (ARM9E-S V5TE core)
cpu0: DC enabled IC enabled WB enabled EABT branch prediction enabled
cpu0: 16KB/32B 4-way L1 VIVT Instruction cache
cpu0: 16KB/32B 4-way write-back-locking-C L1 VIVT Data cache
mvsoc0 at mainbus0: Marvell 88F619x Rev. A1  Kirkwood
mvsoc0: CPU Clock 1000.000 MHz  SysClock 400.000 MHz  TClock 166.666 MHz
mvsoctmr0 at mvsoc0 unit 0 offset 0x20300-0x203ff irq 65: Marvell SoC Timer
mvsocgpp0 at mvsoc0 unit 0 offset 0x10100-0x101ff irq 35: Marvell SoC General Purpose I/O Port Interface
mvsocgpp0: 36 gpio pins
mvsocgpp0: interrupts 96..103, intr 35
mvsocgpp0: interrupts 104..111, intr 36
mvsocgpp0: interrupts 112..119, intr 37
mvsocgpp0: interrupts 120..127, intr 38
mvsocgpp0: interrupts 128..135, intr 39
mvsocgpp0:   Data Out:                  0x00200000
mvsocgpp0:   Data Out Enable Control:   0xc70e0ffd
mvsocgpp0:   Data Blink Enable:         0x10000000
mvsocgpp0:   Data In Polarity:          0x00000000
mvsocgpp0:   Data In:                   0x13020080
mvsocgpp0:   Interrupt Cause:           0x00000000
mvsocgpp0:   Interrupt Mask:            0x00000000
mvsocgpp0:   Interrupt Level Mask:      0x00000000
mvsocgpp0:   High Data Out:             0x00000002
mvsocgpp0:   High Data Out Enable Ctrl: 0xfffffff9
mvsocgpp0:   High Blink Enable:         0x00000000
mvsocgpp0:   High Data In Polarity:     0x00000000
mvsocgpp0:   High Data In:              0x00000002
mvsocgpp0:   High Interrupt Cause:      0x00000000
mvsocgpp0:   High Interrupt Mask:       0x00000000
mvsocgpp0:   High Interrupt Level Mask: 0x00000000
gpio0 at mvsocgpp0: 36 pins
mvsocrtc0 at mvsoc0 unit 0 offset 0x10300-0x10317: Marvell SoC Real Time Clock
com0 at mvsoc0 unit 0 offset 0x12000-0x1201f irq 33: ns16550a, working fifo
com0: console
com1 at mvsoc0 unit 1 offset 0x12100-0x1211f irq 34: ns16550a, working fifo
ehci0 at mvsoc0 unit 0 offset 0x50000-0x50fff irq 19: Marvell USB 2.0 Interface
usb0 at ehci0: USB revision 2.0
gtidmac0 at mvsoc0 unit 0 offset 0x60000-0x60fff: Marvell IDMA Controller/XOR Engine
gtidmac0: XOR Engine 4 channels, intr 5...8
gttwsi0 at mvsoc0 unit 0 offset 0x11000-0x110ff irq 29: Marvell TWSI controller
iic0 at gttwsi0: I2C bus
mvcesa0 at mvsoc0 unit 0 offset 0x3d000-0x3dfff irq 22: Marvell Cryptographic Engines and Security Accelerator
mvgbec0 at mvsoc0 unit 0 offset 0x70000-0x73fff: Marvell Gigabit Ethernet Controller
mvgbe0 at mvgbec0 port 0 irq 11
mvgbe0: Ethernet address 5c:f4:ab:df:0a:e0
makphy0 at mvgbe0 phy 1: Marvell 88E1116R Gigabit PHY, rev. 0
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
mvgbec1 at mvsoc0 unit 1 offset 0x74000-0x77fff: Marvell Gigabit Ethernet Controller
mvgbe at mvgbec1 port 0 not configured
mvpex0 at mvsoc0 unit 0 offset 0x40000-0x41fff irq 9: Marvell PCI Express Interface
pci0 at mvpex0
vendor 11ab product 6281 (miscellaneous memory, revision 0x03) at pci0 dev 0 function 0 not configured
mvsata0 at mvsoc0 unit 0 offset 0x80000-0x87fff irq 21: Marvell Serial-ATA Host Controller (SATAHC)
mvsata0: GenIIe, 1hc, 2port/hc
atabus0 at mvsata0 channel 0
atabus1 at mvsata0 channel 1
mvsdio at mvsoc0 unit 0 not configured
uhub0 at usb0: Marvell EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
mvsata0 port 0: device present, speed: 3.0Gb/s
mvsata0 port 1: device present, speed: 3.0Gb/s
wd0 at atabus0 drive 0
wd0: <WDC WD20EZRX-00D8PB0>
wd0: 1863 GB, 3876021 cyl, 16 head, 63 sec, 512 bytes/sect x 3907029168 sectors
wd1 at atabus1 drive 0
wd1: <WDC WD20EZRX-00D8PB0>
wd1: 1863 GB, 3876021 cyl, 16 head, 63 sec, 512 bytes/sect x 3907029168 sectors
uhub1 at uhub0 port 1: Genesys Logic USB2.0 Hub, class 9/0, rev 2.00/85.32, addr 2
uhub1: single transaction translator
umass0 at uhub1 port 2 configuration 1 interface 0
umass0: Kingston DataTraveler 2.0, rev 2.00/2.00, addr 3
scsibus0 at umass0: 2 targets, 1 lun per target
sd0 at scsibus0 target 0 lun 0: <Kingston, DataTraveler 2.0, 0000> disk removable
sd0: fabricating a geometry
sd0: 14782 MB, 14782 cyl, 64 head, 32 sec, 512 bytes/sect x 30273600 sectors
sd0: fabricating a geometry
umass1 at uhub1 port 3 configuration 1 interface 0
umass1: HP v210w, rev 2.00/0.00, addr 4
scsibus1 at umass1: 2 targets, 1 lun per target
sd1 at scsibus1 target 0 lun 0: <hp, v210w, 1.00> disk removable
sd1: 15300 MB, 3936 cyl, 16 head, 32 sec, 512 bytes/sect x 31334400 sectors
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
(repeat until)
umass1: BBB reset failed, IOERROR
umass1: BBB bulk-in clear stall failed, IOERROR
umass1: BBB bulk-out clear stall failed, IOERROR
(repeat until)
boot device: <unknown>
root on sd0a dumps on sd0b
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
(repeat until)
vfs_mountroot: can't open root device
cannot mount root, error = 5
root device (default sd0a):

Micky Wicky,

Quote

> With 2 HHDs, doing
> run poke; ide reset; sleep 60; usb start
>
> Launch Debian (the macro scan_disk includes "ide
> reset") - looks OK:

> root@debian:~# dmesg | grep -i SATA
> [ 2.626551] sata_mv f1080000.sata: version
> 1.28
> [ 2.626885] sata_mv f1080000.sata: slots 32
> ports 2
> [ 2.703914] scsi host0: sata_mv
> [ 2.723822] scsi host1: sata_mv
> [ 2.727368] ata1: SATA max UDMA/133 irq 32
> [ 2.731448] ata2: SATA max UDMA/133 irq 32
> [ 3.274195] ata1: SATA link up 3.0 Gbps
> (SStatus 123 SControl F300)
> [ 3.873696] ata2: SATA link up 3.0 Gbps
> (SStatus 123 SControl F300)

So did it boot all the way to the Debian prompt here?

Quote

> Boot ok until it detects the USB root drive and
> then fails as previously:

> umass0: BBB reset failed, IOERROR
> umass0: BBB bulk-in clear stall failed, IOERROR
> umass0: BBB bulk-out clear stall failed, IOERROR

Have you tried a different USB flash drive? what brand are you using?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Quote
So did it boot all the way to the Debian prompt here?

Yes it did

Quote
Have you tried a different USB flash drive? what brand are you using?

umass0 is a Kingston DataTraveler 2.0, rev 2.00/2.00, addr 3
16GB with NetBSD installation on it

umass1 is a (sloooooooooowwwww) HP v210w, rev 2.00/0.00, addr 4
16GB with Debian installation on it

I've got a 1GB stick lying around somewhere I'll try, if I can find it.
Although the fact that it fails to reset both devices doesn't bode well, esp. as both worked flawlessly in tld-1.

Micky Wicky,

> esp. as both worked flawlessly in tld-1.

tld-1 and tld-2 code are identical, except for the HDD2 power trigger (2 lines of code in GPIO configuration). The problem with initializing WD HDDs has always been in u-boot. You could only used 1 HDD in tld-1 so that is not really a good comparison, IMO.

I think the power draw of the WD HDDs must be causing problem (in that the WD HDDs are not settled in when the EHCI driver needs to spin up the USB drive). The facts: 1 WD HDD in the 2nd slot was OK without sleep period, and 2 WD HDDs work with 60 seconds sleep was OK.

I have a USB connected 2TB WD HDD with its own power source, and saw this problem every time during boot. This is the configuration that always boots OK for me:

GoFlex Home:

- USB flash 8GB Sandisk Ultra Fit rootfs.
- Seagate Goflex Desk 2TB SATA.
- WD Element 2TB USB 2.0 with its own power source.
- usb_ready_retry=40

During boot, the EHCI timeout on TD errors ocurs several time. But eventually, it stops and u-boot loads the kernel from the Sandisk USB rootfs.

I would consider this issue being worked around successfully for Debian. But is not for NetBSD issue. I think we should try to find a workaround for this. Improvement in u-boot for SATA is not easy (they are using a ported Marvell driver and it is not close to Linux driver).

Other thought, perhaps we should look at sata_mv and ehci versions between Debian and NetBSD to see if they are from different baseline?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 03/01/2016 04:20PM by bodhi.

I think that's the explanation I needed!
Esp wrt the code changes in tld-2 and the WD (likely) power draw issue.

So the difference between Linux and NetBSD in this is either how they initialise USB (NetBSD is asking too quickly, drawing too much power), or how the two OSes can control the power draw on SATA (if that is possible...)
I'll see what I can make out of the USB stuff in NetBSD first

I think this may be beyond my C skills... but let's see.

The src/sys/dev/marvell/ehci_mv.c NetBSD driver is here: http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sys/dev/marvell/ehci_mv.c?rev=1.5&content-type=text/plain&only_with_tag=MAIN
Based on an import from 2008.

It probably needs the umass driver as well (this is the one generating the error messages):
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/usb/umass.c?rev=1.149&content-type=text/x-cvsweb-markup&only_with_tag=MAIN


The Linux driver for that is at http://lxr.free-electrons.com/source/drivers/usb/host/ehci-mv.c

As expected they are very different. The Linux driver is from a Marvell import, I'm pretty sure the NetBSD driver cannot be for a couple of reasons (the HAL and possible licence conflicts)

Which function am I looking for here, I wonder?

I'll also compile a kernel with EHCI_DEBUG to see whether that yields anything more.



Edited 1 time(s). Last edit at 03/04/2016 11:57AM by Micky Wicky.

Micky Wicky,

> As expected they are very different. The Linux
> driver is from a Marvell import, I'm pretty sure
> the NetBSD driver cannot be for a couple of
> reasons (the HAL and possible licence conflicts)
>
> Which function am I looking for here, I wonder?

HAL? wow! that's just ancient. I really don't have any idea.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

You're not thinking about the HAL in 2001: A Space odyssey, are you? :)
It's a generic acronym,
The driver was first created in 2008 but received regular updates, the last one only a few weeks ago.
Maybe Linux used to have a later under the same acronym, I'm not sure.

Micky Wicky,

> It's a generic acronym,
> The driver was first created in 2008 but received
> regular updates, the last one only a few weeks
> ago.
> Maybe Linux used to have a later under the same
> acronym, I'm not sure.

Yes I meant this HAL :) if you noticed, most the latest Debian packages do not require HAL, iirc.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Looking at my options... what can you tell me about u-boot and WD drives, Google wasn't terribly informative.
Second Q - does this mean that a Seagate drive such as this one would work without any issues?

Micky Wicky,

> Looking at my options... what can you tell me
> about u-boot and WD drives, Google wasn't terribly
> informative.

I've already did above!

And it does not hurt to try different brand if you can get a hold of one such as Seagate or Hitachi.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

So I picked up an old (damaged) Seagate disk and did a couple of tests with NetBSD...

HDD1 = WD, HDD2=Seagate --> no change, errors crop up the first time NetBSD tries to initialise USB
HDD1 = Seagate, HDD2=WD --> NetBSD boots to a login prompt, having started all services, etc... Then the same errors happen within a couple of seconds with no intervention on my part. Note that the OS hasn't tried accessing the WD drive at that point.
Looks promising though...

This points to 3 options:
1. Trying to fix it on the NetBSD side
2. Testing with 2 seagate HDDs
3. Switching to Debian

Ordered by ease of implementation!
#1 is out of the way, at least for now.

Micky Wicky,

When I have time, I will build another version to try so we don't have to do the poke.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Happy to test, as always.

Micky Wicky Wrote:
-------------------------------------------------------
> Happy to test, as always.


Do you have madmin's explanation which GPIO was poke in the poke command? I forgot the number.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Wasn't it GPIO 33?

Micky Wicky Wrote:
-------------------------------------------------------
> Wasn't it GPIO 33?

I forgot how chrlee come up with that mask. GPIO 33 might not be correct, but I'll put that in the code and see what'll happen.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Micky,

Try kwboot with this image. And do "ide reset" without the poke.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks for this.
It makes no difference however - without the poke, ide reset only sees the first disk (and the same booting issues occur with or without poke)

Micky Wicky Wrote:
-------------------------------------------------------
> Thanks for this.
> It makes no difference however - without the poke,
> ide reset only sees the first disk (and the same
> booting issues occur with or without poke)

Thanks Micky.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Micky,

There are 3 versions rc1, rc2, rc3. Please try 6 tests: each without poke, and each then with poke.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

No luck...

RC1 with poke: Reset IDE: Bus 0: OK Bus 1: OK --- usb start (no errors) --- sleep 60; NetBSD fails to boot with umass errors as previous
RC1 without poke: Reset IDE: Bus 0: OK Bus 1: not available
--> RC1 = no difference

RC2 with poke: Reset IDE: Bus 0: OK Bus 1: OK --- usb start (no errors) --- sleep 60; NetBSD fails to boot with umass errors as previous
RC2 without poke:Reset IDE: Bus 0: OK Bus 1: not available
--> RC2 = no difference

RC3 with poke: Reset IDE: Bus 0: OK Bus 1: OK --- usb start (no errors) --- sleep 60; NetBSD fails to boot with umass errors as previous
RC3 without poke: Reset IDE: Bus 0: OK Bus 1: not available
--> RC3 = no difference

Note that I didn't try booting without the poke, just "ide reset".

Micky,

> Note that I didn't try booting without the poke,
> just "ide reset".

How about booting without the poke?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Without poke, all 3 RC builds yield:

U-Boot 2015.10-tld-2-rc3 (Mar 13 2016 - 17:12:52 -0700)
ZyXEL NSA310S/320S 1/2-Bay Power Media Server

SoC:   Kirkwood 88F6702_A1
DRAM:  256 MiB (ECC not enabled)
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0
running scan_disk ...
Scan device usb
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices...
Use USB retry period from the environment: 45 second(s)
1 Storage Device(s) found
device usb 0:1
reading /boot/uImage
** Unable to read file /boot/uImage **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: WDC WD20EZRX-00D8PB0 Firm: 80.00A80 Ser#:  WD-WCC4MHECYZUX
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
device ide 0:1
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
reading /netbsd.ub
4452292 bytes read in 181 ms (23.5 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   NetBSD/ 7.99.26
   Created:      2016-01-31  11:16:27 UTC
   Image Type:   ARM NetBSD Kernel Image (uncompressed)
   Data Size:    4452228 Bytes = 4.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
## Transferring control to NetBSD stage-2 loader (at address 00008000) ...

NetBSD/evbarm (Marvell) booting ...
[ Kernel symbol table missing! ]
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 7.99.26 (NSA320s) #1: Sun Jan 31 11:15:46 GMT 2016
	michael@odroid:/home/michael/src/netbsd/sys/arch/evbarm/compile/obj/NSA320s
total memory = 256 MB
avail memory = 245 MB
sysctl_createv: sysctl_create(machine_arch) returned 17
mainbus0 (root)

[...]

sd0 at scsibus0 target 0 lun 0: <Kingston, DataTraveler 2.0, 0000> disk removable
sd0: fabricating a geometry
sd0: 14782 MB, 14782 cyl, 64 head, 32 sec, 512 bytes/sect x 30273600 sectors
sd0: fabricating a geometry
umass0: BBB reset failed, IOERROR
umass0: BBB bulk-in clear stall failed, IOERROR
umass0: BBB bulk-out clear stall failed, IOERROR
umass0: BBB reset failed, IOERROR

[...]

vfs_mountroot: can't open root device
cannot mount root, error = 5
root device (default sd0a):

Micky,

> sd0 at scsibus0 target 0 lun 0: <Kingston,
> DataTraveler 2.0, 0000> disk removable

This could be your problem. I think if you can, stay away from Kingston brand for booting disk. Try a Sandisk USB instead.

So for now we know that the last stable version uboot.2015.10-tld-2.nsa310s.mtd0.kwb works:
http://forum.doozan.com/read.php?3,23331,26068#msg-26068

Let keep this version and do the poke to get the 2nd HDD working. With WD HDDs, use a really long sleep period. With other brand, I think it should be shorter.

When I have time to release new version, I'll revisit this.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

So I've tried with my Debian pendrive:

umass0: HP v210w, rev 2.00/0.00, addr 4

and did

run poke; sleep 120; ide reset; sleep 120; usb start; sleep 120

followed by fatload and bootm

but it's made no difference at all.