I've updated the mtd0 uBoot again with some fixes for some USB devices. If you're having any troubles getting things too boot, this upgrade is the first place to start.

To upgrade (from the instructions for installing mtd0 uBoot):

cd /tmp
wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh

-- Jeff

You say that it is only tested with Pogoplug v2. How do I know which version of the Pogoplug I have?

This is how my Seagate DockStar looks like:
http://i.zdnet.com/blogs/seagate_dockstar_01.jpg

There's only one type of Dockstar, so you're fine. The Pogoplugs are completely different devices and very easy to tell apart (one is bright Pink, the other is not).

-- Jeff

Thank you Jeff, its working fine.

I have two drives connected, one flash drive with debian and another USB hard disk for storage. Do I have to make any changes so that it boots always from the flash drive, like you had posted earlier while using the old uboot?

If you want to have multiple storage devices connected, you still need to use the USB Scanner script.

-- Jeff

^ Thank you so much. Everything is working perfectly now. :)

Jeff, I went through the install, on the pink pogoplug, everything seems to be working although, I did see errors when I run the script (related to blparam I'm guessing), plus I had to specify my device since it couldn't detect.

Should I be worry? script finished with "# uBoot installation has completed successfully."

Some of the errors:

...
# Verifying uBoot environment
ECC failed: 1
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.environment.md 100% |*******************************| 52 --:--:-- ETA
Too many bit errors @ 0xa0000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa0800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa1000 -- Can't correct!
...
-- Invalid CRC32 on parameters: 0xffffffff != 0x619d86db


Thanks

You're correct, the errors you're seeing are coming from a corrupted blparam environment. That's one of the errors that the new uBoot fixes so you should be fine now. The installer is very careful and would have given you a big scary warning if it couldn't install properly.

-- Jeff

i've tried using below code


fw_setenv usb_init 'usb start; if ext2load usb 0:1 0x800000 /boot/uImage; then setenv usb_device 0:1; setenv usb_root /dev/sda1; elif ext2load usb 1:1 0x800000 /boot/uImage; then setenv usb_device 1:1; setenv usb_root /dev/sdb1; elif ext2load usb 2:1 0x800000 /boot/uImage; then setenv usb_device 2:1; setenv usb_root /dev/sdc1; elif ext2load usb 3:1 0x800000 /boot/uImage; then setenv usb_device 3:1;setenv usb_root /dev/sdd1;fi;'

since then i'm unable to load debian...

can you give me the default value of usb_init...

fw_setenv usb_init 'usb start'

hi...i've tried the default value, but its still not booting....please help me...

Just re-run the uBoot installer, it will reset the environment.

i've tried re-running uboot installer...and even couldn't boot into debian...

so, i've again reinstalled debian into another usb and now its fine...

i want to know if in case of power loss while using it, will i get the same problem again...

also, as with the boot order problem...

what i've noticed it..

case1) when i use the usb with debian on any of the 3 usb's on sides:

it will boot into debian properly, but if there is any other usb device then it wont boot....

case 2) i've newly installed debian on freeagent go, and now i can boot into debian no matter how many other devices are connected at sides...

so i think there is default usb1-usb2-usb3-usb4 thing...

and if i use freeagent go on stock port, it always takes it as sda1...

did you notice it...

You should connect a serial cable or configure netconsole to watch the boot process. When you can see what it's doing, it much easier to figure out what's going wrong.

I'm not able to run this version of u-boot from RAM -- should I be able to? The CPU resets as soon as I use the "go" command:

CE>> tftpboot 0x800000 uboot.mtd0.kwb
Using egiga0 device
TFTP from server 10.0.0.20; our IP address is 10.0.0.250
Filename 'uboot.mtd0.kwb'.
Load address: 0x800000
Loading: #################################################################
         ######################################
done
Bytes transferred = 524288 (80000 hex)
CE>> go 0x800200
## Starting application at 0x00800200 ...


U-Boot 2010.06-00695-gbd23130-dirty (Aug 25 2010 - 01:20:45)
Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
NAND:  prefetch abort
pc : [<00000160>]          lr : [<00000064>]
sp : 005006d0  ip : 004fff08     fp : 004fff04
r10: ffffffff  r9 : 00000000     r8 : 004fffe0
r7 : 000000ff  r6 : 00000000     r5 : 00000000  r4 : 00000000
r3 : 0003f112  r2 : 00000083     r1 : 5458f40f  r0 : 00051078
Flags: Nzcv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

resetting ...

Hey Jeff, thanks for your shiny new uboot which I've just installed. I tried to configure netconsole with the fw_setenv command but I'm getting

fw_setenv: command not found

Did is missed something?

The uBoot installer puts fw_setenv/printenv utils in /usr/sbin of your Pogoplug installation. The Debian uboot-envtools package will put them in the same place. If you're running something else, you can just reboot into Pogoplug and run or copy them from there.

Is there a way of integrate the commands on my usb plugbox-os?