Linux Device Hacking - uBoot

How to revert to factory uboot of Goflex Net (1 reply)

shv — Fri, 17 May 2013 22:20:47 -0400

I want to rerevert to the factory uboot of Goflex Net. How can can I read the factory uboot back from flash rootfs partition and write it to flash? Is it necessary to change the uboot environment variables which were changed during installation of new uboot? I don't have any mtdblock devices in /dev.

I found out how to do that after Debian was booted from a USB Stick:

mknod /dev/mtdblock2 b 31 2
mount -t jffs2 -o ro /dev/mtdblock2 /mnt
cp /mnt/uboot-original-mtd0.kwb /root
umount /dev/mtdblock2
apt-get install mtd-utils

# the next commands could brick the device if something is wrong
cd /root
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot-original-mtd0.kwb
reboot

#after reboot ssh-login shall be possible -> activate hbmgr
mount -o remount,rw / # remount rootfs writeable
vi /etc/init.d/rcS
#uncomment the line with "/etc/init.d/hbmgr.sh start"
reboot

iConnect not boots from Stick when DVB-C Stick plugged in (4 replies)

pr0j3ctx — Wed, 15 May 2013 03:05:19 -0400

Hello.

I will try to explain my problem with my bad english. Sorry for this.

I have an iomega iConnect debianized with this Tutorial: http://www.congenio.de/infos/iconnect.html

All runs good. I will use my iomega als tvheadend Server. For this I need two DVB-C Sticks from Sundtek. First I tried only the USB-Stick and configured all. After this I plugged in one DVB-Card for testing. Since testing I had the problem that after reboot a while nothing happens and then the original firmware loaded.

Yesterday i made some tests and after i plugged out my DVB-C Card the iomega booted from my USB-Stick.

The USB-Sticks plugged in at Port 1 at the back of the iconnect.

Now I don`t know what todo next. It isn´t a nice solution to unplug the DVB-C Card each reboot. I often works remotly some miles away on the iconnect.

I´m not a specialistin uBoot etc. so I don´t know what to do. Is there anyone out there who can help me or push me in the right direction.

Sorry if there are to less information. If you need one, tell me and i will bring it.

Thanks for reading till here.

Greats
pr0

PogoPlug Mobile SD Boot Troubles (4 replies)

sosuke — Thu, 16 May 2013 05:58:39 -0400

Hello, I am having some issues getting my Pogoplug mobile to boot from an SD card. I'll say up front that I am no linux expert so if there is anything unclear or additional information needed please let me know.

I followed bodhi's guide for getting this setup (http://forum.doozan.com/read.php?2,11663,page=1)
I've tried 2 different images for the SD card. One from a file called Debian.Wheezy.20130407.Pogoplug.tar (sorry I can't remember where I found this and I can't find it searching) and the other currently on the SD card from Davy's Zyxel thread here (http://forum.doozan.com/read.php?2,7806).

The SD card is fromated ext2 3gb for partition 1 and 1gb swap for partition 2.

I think the uboot install worked out ok because I get feedback from netconsole as follows

** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
SDHC found. Card desciption is:
Manufacturer:       0x1b, OEM "SM"
Product name:       "FBA4B", revision 1.1
Serial number:      171337637
Manufacturing date: 11/2012
CRC:                0x00, b0 = 0
mmc1 is available
SDHC found. Card desciption is:
Manufacturer:       0x1b, OEM "SM"
Product name:       "FBA4B", revision 1.1
Serial number:      171337637
Manufacturing date: 11/2012
CRC:                0x00, b0 = 0
mmc1 is available
Loading file "/boot/uImage" from mmc device 0:1 (xxa1)
2279256 bytes read
Loading file "/boot/uInitrd" from mmc device 0:1 (xxa1)
7004538 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2279192 Bytes = 2.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.3.2-kirkwood-dg
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7004474 Bytes = 6.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

At this point it seems to hang and drops off my network (no longer in device table on router).

I took a look at the logs on the SD card and they all say

(Nothing has been logged yet.)

Which seems to be the default for them on a fresh install.

Here is my printenv output. Maybe I have a mistake somewhere in here?

Pogov4> printenv
arcNumber=2097
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdpar
ts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd;
 usb stop; run mmc_bootcmd
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=02:50:43:52:d1:04
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /
rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd
; fi
if_netconsole=ping $serverip
ipaddr=192.168.10.46
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_bootcmd=mmc init; mmc init; ext2load mmc 0:1 0x00800000 /boot/uImage; if ext
2load mmc 0:1 0x01100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else boot
m 0x800000; fi
mtddevname=uImage2
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M
(root)
ncip=192.168.10.38
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; na
nd read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.10.38
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se
tenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && u
bifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm
0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0
:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext
2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; el
se bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if t
est $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_
scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; se
tenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_
rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2955/131068 bytes

So is it my SD card? Is it my kernel? Is it my env? I'm not really sure how to proceed to fix this. Any help would be apprciated. Thank you.

Semi-bricked GoFlex Home in need of fixing (2 replies)

CrimsonKnight13 — Tue, 07 May 2013 07:21:23 -0400

I semi-bricked my GoFlex Home a while ago by trying out a new u-boot. It appears that it knocked out the ethernet connectivity & killed the ability to boot properly. I do realize that I tried the GoFlex Net u-boot & I believe that I jacked up the process for using it with a GoFlex Home. What's the best way to go about fixing this?

It is currently connected via serial, which is where I copied the log from.

U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Using egiga0 device
ping failed; host 10.10.10.5 is not alive
Hit any key to stop autoboot:  0

Reset IDE: ide_preinit failed
** Bad partition 1 **
** Bad partition 1 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:  done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:

Edit: I am able to gain access to the command prompt. U-Boot checks as 1.21.

U-Boot for Device-Tree Kernel (3 replies)

bodhi — Sun, 12 May 2013 15:13:15 -0400

I'm starting this thread to gather info about getting newer u-Boot builds to enable booting Flattened Device Tree (FDT) kernel (3.5 and later).

U-Boot 2013.01 has most of the board definitions, except for GoFlex Net/Home and Pogoplug Mobile/V4.

So we do have supports for these Kirkwood boxes (perhaps also other Kirkwwod boxes)
- Goflex Net/Home (with patch)
- iConnect
- Dockstar
- Pogo E02
- Sheevaplug

Status:

1. GoFlex Net/Home:

So far I got a patched version of U-Boot 2013.01 running with FDT-enabled kernel 3.6.11 on a GoFlex Net. This was using the patch that rpress post here.
Currently I'm having problem with netconsole. The 2nd character in a command always got dropped, and working around it by repeating the 2nd char in a command (e.g. seetnv) enabled it to execute correctly. However, kernel just hang after executing boot command.

2. Pogoplug E02:

So far I got a patched version of U-Boot 2013.01 running with non-FDT kernel 3.6.11 on a Pogo E02. We don't have Debian FDT board patch for Pogo E02 yet.
It exibits the same netconsole problem as in GoFlex Net version.

Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB (11 replies)

cpe — Fri, 10 May 2013 00:44:12 -0400

Hi all,

I have dockstars which in some point in time didn't get back up again.
Using a Nokia USB-cable with some test hooks, tftp'ed mtd0, 1, 2 and installed rescue from USB stick.
Unfortunately, they don't boot the USB stick which installed without error messages (wheezy-script)

I attached my environment.
uname -a
Linux pogo02-rescue 3.3.2-kirkwide #1 Mon Oct 29 17:52:07 CDT 2012 armv5tel GNU/Linux

Please help me making the devices work again.

#update#
######start boot-log ########

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1752
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1606576 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
6883383 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: kernel 3.2.0-4-kirkwood
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1606512 Bytes = 1.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: ramdisk 3.2.0-4-kirkwood
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6883319 Bytes = 6.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

######## end bootlog ###########

Thanks in advance and greetings
CP

Boot from USB while SATA disks connected (2 replies)

Marcel — Sun, 28 Apr 2013 16:34:27 -0400

Hi,

i'm using a GoFlexHome with 3.1.10-17-ARCH. The OS is installed on a USB-Stick (ext2). For the databackup, I want to use two 3,5" hd-drives as raid 1, too.

Cause i use 3,5" disk, i use a extra power supply for the disks. So i can switch the disks, during the boot process on! After i set the disks into the raid1, i must use for a working bootprocess, the following steps:
* Switch off the power supply for the disks
* Reboot/switch on the GoFlex
* Wait for finished uboot (the led becomes on)
* Switch on the power supply for the disks

If i don't switch the power supply of the disks during the boot process on, the boot fails. See the log! If the disks on the beginning of the bootprocess on, the boot fails too!

My google search told me, that i must use disklabel for working booting. I used tunefs to give my stick the label "rootfs" and changed the usb_init entry in my env!

fw_setenv usb_init "run usb_scan; setenv usb_root LABEL=rootfs"

But the booting problem is still alive.

The boot log is always the same:

Quote

U-Boot 2010.09 (Feb 16 2011 - 18:42:02)
UBIT v0.6 by Jeff Doozan and Peter Carmichael
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot: 0
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fast", error -19
Error reading superblock on volume 'ubi:fast'!
UBIFS not mounted, use ubifs mount to mount volume first!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2869732 bytes read
Loading file "/uInitrd" from usb device 0:1 (usbda1)
** File not found /uInitrd
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00680000 ...
Image Name: Linux-3.1.10-17-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2869668 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ..

The kernel-startup messages a different:

Quote
SATA switched on, after uboot finished
[ 22.838797] rtc-mv rtc-mv: internal RTC not ticking
[ 23.374057] sd 2:0:0:0: [sda] No Caching mode page present
[ 23.379619] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 23.388181] sd 2:0:0:0: [sda] No Caching mode page present
[ 23.393883] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 23.425058] sd 2:0:0:0: [sda] No Caching mode page present
[ 23.430610] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 23.643752] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 23.651250] ata1: edma_err_cause=00000010 pp_flags=00000000, dev connect
[ 23.657985] ata1: SError: { PHYRdyChg DevExch }
[ 23.662630] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 23.670092] ata2: edma_err_cause=00000010 pp_flags=00000000, dev connect
[ 23.676829] ata2: SError: { PHYRdyChg DevExch }
[ 25.949158] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 35.960322] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities

Quote
SATA always off
[ 22.852634] rtc-mv rtc-mv: internal RTC not ticking
[ 23.388068] sd 2:0:0:0: [sda] No Caching mode page present
[ 23.393631] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 23.402193] sd 2:0:0:0: [sda] No Caching mode page present
[ 23.407893] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 23.421194] sd 2:0:0:0: [sda] No Caching mode page present
[ 23.426894] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 25.842956] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 35.854835] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[ 126.882998] systemd[1]: Timed out waiting for device dev-md0.device.
[ 126.912981] systemd[1]: Dependency failed for /media/dddrive.
[ 126.942985] systemd[1]: Dependency failed for Local File Systems.

Quote
SATA always on
[ 25.847139] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 35.893260] EXT4-fs (sda1): ext4_check_descriptors: Block bitmap for group 0 not in group (block 2838187772)!
[ 35.903272] EXT4-fs (sda1): group descriptors corrupted!
[ 35.927178] EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
[ 35.964621] EXT4-fs (sda1): ext4_check_descriptors: Block bitmap for group 0 not in group (block 2838187772)!
[ 35.974624] EXT4-fs (sda1): group descriptors corrupted!
[ 36.056765] Unable to handle kernel paging request at virtual address 00303030
[ 36.064043] pgd = c0004000
[ 36.066801] [00303030] *pgd=00000000
[ 36.070418] Internal error: Oops: 5 [#1] PREEMPT
[ 36.075056] Modules linked in:
[ 36.078135] CPU: 0 Not tainted (3.1.10-17-ARCH #1)
[ 36.083303] PC is at mount_block_root+0x200/0x280
[ 36.088033] LR is at mount_block_root+0x1e0/0x280
[ 36.092761] pc : [] lr : [] psr: 40000013
[ 36.092766] sp : c7829f80 ip : 00000000 fp : 00000000
[ 36.104303] r10: c049f470 r9 : c7812150 r8 : 00008000
[ 36.109554] r7 : 00000000 r6 : c0551e7c r5 : c7812021 r4 : 00303030
[ 36.116112] r3 : c7829eb0 r2 : c7829f74 r1 : c049f448 r0 : 00000039
[ 36.122669] Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 36.130020] Control: 0005397f Table: 00004000 DAC: 00000017
[ 36.135791] Process swapper (pid: 1, stack limit = 0xc7828270)
[ 36.141651] Stack: (0xc7829f80 to 0xc782a000)
[ 36.146043] 9f80: 00000000 00000000 00006180 c74a4c80 00006000 c00d3508 c78190a0 c7497300
[ 36.154266] 9fa0: c049f470 00000001 c0593380 c0551e91 c000945c 00000013 00000000 00000000
[ 36.162489] 9fc0: 00000000 c052ff3c fffffffe 00000002 00000000 c0558ee4 c0558ee4 c052f8c8
[ 36.170711] 9fe0: 00000000 00000000 00000000 00000000 c052f7ac c000945c ffffffff ffffffff
[ 36.178942] [] (mount_block_root+0x200/0x280) from [] (prepare_namespace+0x160/0x1c0)
[ 36.188565] [] (prepare_namespace+0x160/0x1c0) from [] (kernel_init+0x11c/0x14c)
[ 36.197758] [] (kernel_init+0x11c/0x14c) from [] (kernel_thread_exit+0x0/0x8)
[ 36.206682] Code: e1a00004 ebf3b5e7 e2800001 e0844000 (e5d43000)
[ 36.212882] ---[ end trace 2f254dfb3bd44332 ]---
[ 36.217644] Kernel panic - not syncing: Attempted to kill init!
[ 36.223632] [] (unwind_backtrace+0x0/0xe0) from [] (panic+0x58/0x198)
[ 36.231898] [] (panic+0x58/0x198) from [] (do_exit+0x88/0x7a0)
[ 36.239548] [] (do_exit+0x88/0x7a0) from [] (die+0x1d4/0x200)
[ 36.247106] [] (die+0x1d4/0x200) from [] (__do_kernel_fault.part.2+0x54/0x74)
[ 36.256051] [] (__do_kernel_fault.part.2+0x54/0x74) from [] (do_page_fault.part.3+0x274/0x2b0)
[ 36.266489] [] (do_page_fault.part.3+0x274/0x2b0) from [] (do_page_fault+0x2c/0x94)
[ 36.275965] [] (do_page_fault+0x2c/0x94) from [] (do_DataAbort+0x34/0x98)
[ 36.284570] [] (do_DataAbort+0x34/0x98) from [] (__dabt_svc+0x38/0x60)
[ 36.292896] Exception stack(0xc7829f38 to 0xc7829f80)
[ 36.297998] 9f20: 00000039 c049f448
[ 36.306231] 9f40: c7829f74 c7829eb0 00303030 c7812021 c0551e7c 00000000 00008000 c7812150
[ 36.314474] 9f60: c049f470 00000000 00000000 c7829f80 c052fbdc c052fbfc 40000013 ffffffff
[ 36.322729] [] (__dabt_svc+0x38/0x60) from [] (mount_block_root+0x200/0x280)
[ 36.331597] [] (mount_block_root+0x200/0x280) from [] (prepare_namespace+0x160/0x1c0)
[ 36.341241] [] (prepare_namespace+0x160/0x1c0) from [] (kernel_init+0x11c/0x14c)
[ 36.350448] [] (kernel_init+0x11c/0x14c) from [] (kernel_thread_exit+0x0/0x8)

Does anybody, what i must do, for a working boot, with the connected SATA disks?

Can uboot boot in to an ext3 patition (1 reply)

richard-g8jvm — Wed, 24 Apr 2013 20:38:58 -0400

Sorry newbie type question, but
Is it possible to boot into an ext3 partition ?,
I've noticed a few posts about failing to reboot after a power outage/failure. I assume using an ext2 partition.

I've only just got my pogoE02 and it wouldn't take long to reload Debian , although I found that loading wheezy failed, I had to install squeeze and then upgrade.

Or could I clone the drive reformat it and load the cloned image ????, a link to a howto on that would help

Thanks
Richard

Boot your Dockstar by TFTP/NFS (1 reply)

tsunulukai — Sat, 20 Apr 2013 10:22:46 -0400

Hi there!

A few month ago, I was trying to boot my dockstar by TFTP & NFS... but did not succeed.
I've left my dockstar on the side for a time, and I recently tried again successfully !

My deep gratitude to this fellow community who made it all possible by their numerous contributions !

Here's my modest contribution...

I tried this with a newly-installed debian wheezy distribution on my dockstar, the latest uboot, and a unmodified debian kernel.

This guide assumes that you already have a functionnal NFS, TFTP and DHCP server on your network.
In my example, I'm running the TFTP and NFS server on a NAS running Debian, and the DHCP server on a router running OpenWRT.

Here's how I proceeded

1. Install latest uboot on the Dockstar:

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

2. Install a fresh debian on the Dockstar using the well known Jeff's script, or try to use your existing dockstar installation.

3. Copy the dockstar rootfs on the NFS Server:

mkdir -p /mnt/usbdockstar
mkdir -p /srv/nfs/hosts/dockstar
mount /dev/ /mnt/usbdockstar
cp -av /mnt/usbdockstar/* /srv/nfs/hosts/dockstar/
umount /mnt/usbdockstar

4. Copy the dockstar boot files on the TFTP Server:

mkdir -p /mnt/usbdockstar
mkdir -p /srv/nfs/hosts/dockstar
mount /dev/ /mnt/usbdockstar
cp -av /mnt/usbdockstar/boot/u* /srv/tftp/nfs/dockstar/
umount /mnt/usbdockstar

5. Add the dockstar folder as shared folder on the NFS server:

if ! cat /etc/exports | grep /srv/nfs/hosts/dockstar >/dev/null; then
cat <>/etc/exports
/srv/nfs/hosts/dockstar                 192.168.0.0/255.255.0.0(rw,sync,no_root_squash,no_subtree_check)
EOF
fi
exportfs -av

6. Make changes onto the dockstar rootfs hosted on the NFS server to allow it to properly boot by NFS:

# Define Dockstar RootFS location on NFS Server
ROOTFS=/srv/nfs/hosts/dockstar

#Change Root entry in /etc/fstab
sed -i 's;^/dev/root.*;/dev/root       /               nfs    noatime,errors=remount-ro 0 1;' $ROOTFS/etc/fstab

#Disable eth0 auto-configuration
sed -i 's;auto eth0;#auto eth0;' $ROOTFS/etc/network/interfaces

#Disable eth0 auto-configuration (ifplugd)
sed -i 's;eth0;;' $ROOTFS/etc/default/ifplugd;
sed -i 's;^\(INTERFACES\)="auto";\1="";' $ROOTFS/etc/default/ifplugd
sed -i 's;^\(HOTPLUG_INTERFACES\)="all";\1="";' $ROOTFS/etc/default/ifplugd

7. Create NetBoot variables in uboot on the Dockstar from the running Linux:
This will not yet alter the Dockstar startup configuration. All the following commands create non-existing variables into uBoot.

#NetBoot variables
# -User-Serviceable
fw_setenv net_dhcp_c '1'
fw_setenv net_dhcp_s '0'
fw_setenv net_c_ipaddr ''
fw_setenv net_c_netmask ''
fw_setenv net_c_gatewayip ''
fw_setenv net_tftp_server '192.168.1.1'
fw_setenv net_tftp_kernel 'nfs/dockstar/uImage'
fw_setenv net_tftp_initrd 'nfs/dockstar/uInitrd'
fw_setenv net_nfs_server '192.168.1.1'
fw_setenv net_nfs_path '/srv/nfs/hosts/dockstar'

# -Fixed
fw_setenv net_bootcmd 'run net_check_dhcp_c; run net_check_dhcp_s; run net_set_bootargs; run net_boot'
fw_setenv net_boot 'tftp 0x800000 $net_tftp_kernel; echo; echo ** Kernel Boot Arguments: $bootargs; echo;if tftp 0xe00000 $net_tftp_initrd; then bootm 0x800000 0xe00000;else bootm 0x800000;fi'
fw_setenv net_set_bootargs 'setenv serverip $net_tftp_server; setenv bootargs console=$console root=/dev/nfs rootfstype=nfs rootwait nfsroot=$net_nfs_server:$net_nfs_path ip=$ipaddr:$net_nfs_server:$gatewayip:$netmask:dockstar:eth0:off $mtdparts'
fw_setenv net_check_dhcp_c 'if test $net_dhcp_c -eq 1 ; then run net_set_c_ip_dhcp; else run net_set_c_ip_stat; fi;echo ** IP Address: $ipaddr; echo ** Subnet Mask: $netmask; echo ** Def Gateway: $gatewayip'
fw_setenv net_set_c_ip_dhcp 'dhcp; echo; echo ** net_dhcp_c = 1 --> Getting IP Settings by DHCP'
fw_setenv net_set_c_ip_stat 'setenv ipaddr $net_c_ipaddr; setenv netmask $net_c_netmask; setenv gatewayip $net_c_gatewayip; echo; echo ** net_dhcp_c = 0 --> Using static IP Settings'
fw_setenv net_check_dhcp_s 'if test $net_dhcp_s -eq 1 && test $net_dhcp_c -eq 1 ; then run net_set_s_ip_dhcp; else run net_set_s_ip_stat; fi;echo ** TFTP Boot Server: $net_tftp_server; echo ** NFS Boot Server: $net_nfs_server; echo'
fw_setenv net_set_s_ip_dhcp 'setenv net_tftp_server $serverip; setenv net_nfs_server $serverip;echo; echo ** net_dhcp_s and net_dhcp_c = 1 --> Getting TFTP and NFS Boot Server by DHCP'
fw_setenv net_set_s_ip_stat 'echo; echo ** net_dhcp_s or net_dhcp_c = 0 --> Using static TFTP and NFS Boot Server'

#NetBoot variables End

8. Now you need access to uBoot to test the TFTP/NFS boot.
You can either plug a serial adapter on your Dockstar or configure uBoot to send the information by netconsole
I used the first option, but here's the procedure for the second one, assuming your NetCat client runs on 192.168.1.250.

On the dockstar, enter:

fw_setenv netcatip 192.168.1.250
fw_setenv if_netconsole 'ping $netcatip'
fw_setenv start_netconsole 'setenv ncip $netcatip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;'
fw_setenv preboot 'dhcp; run if_netconsole start_netconsole'

To receive the console on your computer, run:

nc -l -u -p 6666

9. Reboot the dockstar, interrupt the autoboot and execute

run net_bootcmd

It should boot your dockstar by TFTP and NFS.

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
u-boot>> run net_bootcmd
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 28
*** Unhandled DHCP Option in OFFER/ACK: 28
DHCP client bound to address 192.168.222.239
Using egiga0 device
TFTP from server 192.168.222.1; our IP address is 192.168.222.239
Filename 'boot/gpxelinux.0'.
Load address: 0x800000
Loading: #######
done
Bytes transferred = 89432 (15d58 hex)

** net_dhcp_c = 1 --> Getting IP Settings by DHCP
** IP Address: 192.168.1.239
** Subnet Mask: 255.255.255.0
** Def Gateway: 192.168.1.254

** net_dhcp_s or net_dhcp_c = 0 --> Using static TFTP and NFS Boot Server
** TFTP Boot Server: 192.168.1.1
** NFS Boot Server: 192.168.1.1

Using egiga0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.239
Filename 'nfs/dockstar/uImage'.
Load address: 0x800000
Loading: #################################################################
         #############################################
done
Bytes transferred = 1606576 (1883b0 hex)

** Kernel Boot Arguments: console=ttyS0,115200 root=/dev/nfs rootfstype=nfs rootwait nfsroot=192.168.1.1:/srv/nfs/hosts/dockstar ip=192.168.1.239:192.168.1.1:192.168.1.254:255.255.255.0:dockstar:eth0:off mtdparts=orion_nand:1M(u)

Using egiga0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.239
Filename 'nfs/dockstar/uInitrd'.
Load address: 0xe00000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########
done
Bytes transferred = 6817161 (680589 hex)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.2.0-4-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1606512 Bytes = 1.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 00e00000 ...
   Image Name:   initramfs-3.2.0-4-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6817097 Bytes = 6.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.2.0-4-kirkwood (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 Debian 3.2.41-2

 ...

IP-Config: eth0 hardware address 00:10:75:27:3e:f3 mtu 1500
IP-Config: eth0 guessed broadcast address 192.168.1.255
IP-Config: eth0 complete:
 address: 192.168.1.239  broadcast: 192.168.1.255    netmask: 255.255.255.0
 gateway: 192.168.1.254  dns0     : 0.0.0.0          dns1   : 0.0.0.0
 host   : dockstar
 rootserver: 192.168.1.1 rootpath:
 filename  :
Begin: Running /scripts/nfs-premount ... done.

 ...

[....] Starting OpenBSD Secure Shell server: sshd. ok

Debian GNU/Linux 7.0 dockstar ttyS0

dockstar login:

10. If your boot attempt was successful, alter the dockstar boot sequence to try to boot by NFS with the following command:

fw_setenv bootcmd 'usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run net_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset'

It's a copy of the original boot command, altered to try to boot by NFS after it fails to boot by USB, but before it tries to boot the rescue_system.

Next time you reboot, your dockstar will boot by NFS if it cannot find a bootable USB storage.

EnJoY !

N.B.
In the current configuration, the dockstar will get an IP address by DHCP, but will boot from the statically defined TFTP & NFS server. If you want the dockstar to get the IP address of the TFTP & NFS server by DHCP, just change this:

fw_setenv net_dhcp_s '1'

The DHCP server should then provide the server address with the dhcp option 66
(known as 'TFTP server name' or 'next-server')

Alternatively, if there's no DHCP server on your network or the DHCP server gives faulty information (I had the case with a cable modem that returned an inexisting boot file in option 67), You can statically define your client IP settings with the following changes:

fw_setenv net_dhcp_c '0'
fw_setenv net_c_ipaddr '192.168.1.5'
fw_setenv net_c_netmask '255.255.255.0'
fw_setenv net_c_gatewayip '192.168.1.254'

In this case, you also MUST statically define the IP address for

fw_setenv net_tftp_server '192.168.1.1'
fw_setenv net_nfs_server '192.168.1.1'

uBoot does not count down in Serial Console (Pogo E02) [SOLVED] (17 replies)

bodhi — Sun, 05 May 2013 16:37:17 -0400

I'm running davy's uBoot on my Pogo E02:

Netconsole:

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 10

I have serial console connected to this E02 and it is strange that I don't see the count down.

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Using egiga0 device
host 192.168.0.220 is alive

uBoot env for boot delay:

bootdelay=3

Anybody knows why? if you have serial console on Pogo E02, does yours have a countdown?

POGO-E02 Debian installation broken (2 replies)

zAM — Thu, 09 May 2013 04:16:00 -0400

Hi,
my deabian installation crashed recently.
my usb stick is broken and all data on it is lost.
i am stuck with an POGO-E02(black) looping arround without an usb stick.

i have no idear on gettin it runnig again,
i tested a ARCHLINUX usb boot stick which worked,
but there was no access to the mtdblock1 to reset it to original Pogoplug.

is there any solution for my problem,
for example an image of another usb stick to boot in the system again?

Altered Uboot env, PPV4, need to revert to initial env (3 replies)

t3ch42 — Thu, 11 Apr 2013 18:29:49 -0400

Hi, with the help of bodhi and shv, I was able to get my pogoplug series 4 to flash the custom uboot. I was unable to boot with a second usb drive plugged in and attempted to change some of the usb_boot env and usb_root settings in uboot.

I was hoping that someone might be able to help identify what command I would need to revert my env back to normal. I've tried, but I don't think that I am chaining them together right. Every time I make a change, it seems to get worse.

Follows is my printenv listing.

rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2966/131068 bytes
Pogov4> printenv
printenv

arcNumber=3960
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdpar
ts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd;
 usb stop; run mmc_bootcmd
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=02:50:43:5c:3f:bd
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /
rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd
; fi
if_netconsole=ping $serverip
ipaddr=192.168.1.99
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=F78
mainlineLinux=yes
mmc_bootcmd=mmc init; mmc init;ext2load mmc 0:1 0x00800000 /boot/uImage; if ext2
load mmc 0:1 0x01100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm
 0x800000; fi
mtddevname=uImage2
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M
(root)
ncip=192.168.1.252
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; na
nd read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.1.252
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se
tenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && u
bifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm
0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0
:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext
2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; el
se bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if t
est $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_
scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; se
tenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_
rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2966/131068 bytes
Pogov4>

My other exploits were listed here

here is my boot log.

U-Boot 2011.12 (Apr 08 2012 - 19:03:41)
Cloud Engines-Pogoplug v4/Mobile:MMC version
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
incorrect device type in data
Partition data not found!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2185768 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
6938844 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2-kirkwood-shv
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2185704 Bytes = 2.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.3.2-kirkwood-shv
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6938780 Bytes = 6.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Using machid 0xf78 from environment

Starting kernel ...

edit...I edited my post as I had not had a successful boot after last night, but tried again today from a different computer and was successful.

GoFlex Home: booting the original firmware (6 replies)

teosoft — Wed, 10 Apr 2013 17:42:12 -0400

I have installed the new u-boot using Jeff's install_uboot_mtd0.sh in my Seagate GoFlex Home without any problems. I have also installed Debian following davygravy's instructions in http://forum.doozan.com/read.php?2,7806. However I only have a few moments everyday to work in the unit (while is not serving files to the family) and hence, I need to boot the original firmware until my Debian installation is fully configured and working. According to http://projects.doozan.com/uboot/, it can be done by simply unplugging the USB drive and rebooting. But it doesn't work in my case. I plugged a serial cable to the GFH and here is the output:

U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  3 ??? 2 ??? 1 ??? 0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:   ?? done.

find_inode failed for name=uboot-original-mtd0.kwb

load: Failed to find inode

### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:

The printenv output is

ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:10:75:29:73:32
arcNumber=3338

I was able to boot the original kernel by running the original uboot environment commands:

GoFlexNet> setenv bootargs_root 'ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc'
GoFlexNet> setenv console2 'console=ttyS0,115200'
GoFlexNet> setenv bootcmd 'nand read.e 0x800000 0x100000 0x600000; setenv bootargs $(console2) $(bootargs_root); bootm 0x800000'
GoFlexNet> run bootcmd 

NAND read: device 0 offset 0x100000, size 0x600000
 6291456 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2095148 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................................................................................... done, booting the kernel.

but then it hangs. I tried setting all the original environment variables before running those commands without any success.

I can revert to the original uboot but I would like to have a way to boot the original firmware from the updated uboot.

Does you have any idea on what is going wrong?

Thanks and sorry for this long post.

Cant update uboot: wget: content-length 337 is garbage (2 replies)

janptak — Tue, 02 Apr 2013 04:00:29 -0400

Hi,
Thank You for Your great support and a way to unlock power in my Pogoplug.

I have Pogoplug E02. Brand new, just activated. Ive gain asscess to SSH and I am trying to update uboot to be able to use alternative linux distro like Debian or Archlinux.

I am struggling with the update procedutre. Simply - It cant install new uboot.

Ive tried few times - at first it downloaded some files and it took some operations but unfortunaletty I dont have log for this. But anyway - it stops in the same way as at first run: rm: "cannot remove '/tmp/valid-uboot.md5': No such file or directory"
Heres terminal output:

Using username "root".
-bash-3.2# cd /tmp
-bash-3.2# wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh
Connecting to projects.doozan.com (50.116.34.13:80)
install_uboot_mtd0.s 100% |*******************************| 18406  --:--:-- ETA
-bash-3.2# chmod +x install_uboot_mtd0.sh
-bash-3.2# ./install_uboot_mtd0.sh


!!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER  !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
 Seagate Dockstar
 Seagate GoFlex Net
 Seagate GoFlex Home
 Pogoplug v1
 Pogoplug Pink (v2)
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
wget: content-length 337       is garbage
grep: /tmp/valid-uboot.md5: No such file or directory
## Unknown uBoot detected on mtd0: c7b77a049725096d83db958f39b2c0c3
##
## The installer could not detect the version of your current uBoot
## This may happen if you have installed a different uBoot on
## /dev/mtd0 or if you have bad blocks on /dev/mtd0
##
## If you have bad blocks on mtd0, you should not try to install uBoot.
##
## Installation cancelled.
rm: cannot remove '/tmp/valid-uboot.md5': No such file or directory

It looks like wget cant download proper files (?)
I have some new files in /etc like : fw_env.config
Pogoplug restarts without any problems and work flawlessly but still I d like to play with full linux distro...
Pleae help me.

Please help with uboot compiling on dockstar (2 replies)

mr_evil — Tue, 12 Mar 2013 14:46:41 -0400

Hi

Cutting a long story short:
I can compile uboot without errors, but as soon as i try to load the new kwb from the already installed uboot, the dockstar hangs.

i have a dockstar, i am currently running the latest uboot installed with jeffs installer.
It is version 2011.12 compiled by davygravy if i am not completely mistaken.
This version works fine, it does not support mmc however. Since i modded my dockstar to have the sd slot, i would reallz like to use it.
I am running a gentoo on this dockstar (gcc 4.6.3), i thought i could just download the 2011.12 sources, apply the patches (which i found in other threads) and compile. Compiling went fine, the dd command for aligning aswell, but as soon as i try to "go" after ther tftp, the dockstar hangs.
To make sure that it wasnt the patches, i tried a 2011.12 and 2013.01 vanilla compile, 2011.12 with the dockstar patches but withou the mmc patch ... none did work. i also tried aligned/non aligned and bin/kwb. As you can see i do not have much experience in this area, thats why i tried all combinations.

I read the forums for quite a while, and in another thread it was suggeste to use the codesourcery 2009q3 for compiling. Thing is: cant find that software anymore, and maybe i dont need it.

questions:
do i maybe miss compiler options ?
do i need a different compiler/toolchain ? i could setup a vm with the eldk ...
maybe somebody has a build environment?
maybe there is a uboot already that can boot current kernels (3.8.2) and has mmc/sd support for the dockstar?

any hints are really appreciated.
many thanks in advance

Hello, pbs with Uboot/Nand... :( (2 replies)

troupier — Sat, 02 Mar 2013 07:33:57 -0500

First of all, thanks to all contributors for helping people !!

Then.. sorry for my scholar english (and maybe incorrect) I'm french ;)

ok let's talks about my problem(s) :

I've two GFH. One is fine, running Arch.. The second one is running.. almost..

I've installed a jeff's u-boot through the script.

I can boot from USB on the Rescue System. (thanks !)

But when I want to upgrade the Uboot :

nandwrite /dev/mtd1 uImage-mtd1.img
Writing data to block 0 at offset 0x0
Bad block at 0, 1 block(s) from 0 will be skipped
Writing data to block 1 at offset 0x20000
Bad block at 20000, 1 block(s) from 20000 will be skipped
Writing data to block 2 at offset 0x40000
Bad block at 40000, 1 block(s) from 40000 will be skipped
Writing data to block 3 at offset 0x60000
Bad block at 60000, 1 block(s) from 60000 will be skipped
Writing data to block 4 at offset 0x80000
Bad block at 80000, 1 block(s) from 80000 will be skipped
Writing data to block 5 at offset 0xa0000
Bad block at a0000, 1 block(s) from a0000 will be skipped
Writing data to block 6 at offset 0xc0000
Bad block at c0000, 1 block(s) from c0000 will be skipped
Writing data to block 7 at offset 0xe0000
Bad block at e0000, 1 block(s) from e0000 will be skipped
Writing data to block 8 at offset 0x100000
Bad block at 100000, 1 block(s) from 100000 will be skipped
Writing data to block 9 at offset 0x120000
Bad block at 120000, 1 block(s) from 120000 will be skipped
Writing data to block 10 at offset 0x140000
Bad block at 140000, 1 block(s) from 140000 will be skipped
Writing data to block 11 at offset 0x160000
Bad block at 160000, 1 block(s) from 160000 will be skipped
Writing data to block 12 at offset 0x180000
Bad block at 180000, 1 block(s) from 180000 will be skipped
Writing data to block 13 at offset 0x1a0000
Bad block at 1a0000, 1 block(s) from 1a0000 will be skipped
Writing data to block 14 at offset 0x1c0000
Bad block at 1c0000, 1 block(s) from 1c0000 will be skipped
Writing data to block 15 at offset 0x1e0000
Bad block at 1e0000, 1 block(s) from 1e0000 will be skipped
Writing data to block 16 at offset 0x200000
Bad block at 200000, 1 block(s) from 200000 will be skipped
Writing data to block 17 at offset 0x220000
Bad block at 220000, 1 block(s) from 220000 will be skipped
Writing data to block 18 at offset 0x240000
Bad block at 240000, 1 block(s) from 240000 will be skipped
Writing data to block 19 at offset 0x260000
Bad block at 260000, 1 block(s) from 260000 will be skipped
Writing data to block 20 at offset 0x280000
Bad block at 280000, 1 block(s) from 280000 will be skipped
Writing data to block 21 at offset 0x2a0000
Bad block at 2a0000, 1 block(s) from 2a0000 will be skipped
Writing data to block 22 at offset 0x2c0000
Bad block at 2c0000, 1 block(s) from 2c0000 will be skipped
Writing data to block 23 at offset 0x2e0000
Bad block at 2e0000, 1 block(s) from 2e0000 will be skipped
Writing data to block 24 at offset 0x300000
Bad block at 300000, 1 block(s) from 300000 will be skipped
Writing data to block 25 at offset 0x320000
Bad block at 320000, 1 block(s) from 320000 will be skipped
Writing data to block 26 at offset 0x340000
Bad block at 340000, 1 block(s) from 340000 will be skipped
Writing data to block 27 at offset 0x360000
Bad block at 360000, 1 block(s) from 360000 will be skipped
Writing data to block 28 at offset 0x380000
Bad block at 380000, 1 block(s) from 380000 will be skipped
Writing data to block 29 at offset 0x3a0000
Bad block at 3a0000, 1 block(s) from 3a0000 will be skipped
Writing data to block 30 at offset 0x3c0000
Bad block at 3c0000, 1 block(s) from 3c0000 will be skipped
Writing data to block 31 at offset 0x3e0000
Bad block at 3e0000, 1 block(s) from 3e0000 will be skipped
Writing data to block 32 at offset 0x400000
ioctl(MEMGETBADBLOCK): Invalid argument
Data was only partially written due to error
: Invalid argument

nandtest /dev/mtd0
ECC corrections: 0
ECC failures   : 0
Bad blocks     : 8
BBT blocks     : 0
Bad block at 0x00000000
Bad block at 0x00020000
Bad block at 0x00040000
Bad block at 0x00060000
Bad block at 0x00080000
Bad block at 0x000a0000
Bad block at 0x000c0000
Bad block at 0x000e0000

Finished pass 1 successfully

try everything i've found to clean this and had a proper uboot..

the GFH boots on archlinux, rescue system, get a DHCP address, be accessed through ssh but i can't see anything on netconsole..

Serial adapter is on the way..

Any ideas ?

Problems with Pogoplug E02 (2 replies)

bernd99 — Wed, 27 Feb 2013 15:23:13 -0500

Hi,

First: sorry for my english :-)

I have 3 identical Pogoplugs E02 buy in December.

One i have installing Debian with the script of December, all fine.

Yesterday i want isntall the other 2, all ok boot no boot.

Led ist ornage but no network connection. I take the image of the 1, but no running too.

I see that there are changes in the script, perhaps a new bootlader?

Can i backup the bootlader partition from my first running pogo und flash the other 2?
How?

Thx for your help

[Pogoplug] Booting with multiple USB devices plugged in (12 replies)

Clark — Sat, 02 Mar 2013 09:56:01 -0500

Apologies if this has already been answered before - I looked but didn't find it.

I have Debian Squeeze running on my Pogoplug per the instructions here: http://projects.doozan.com/debian/

My boot device is a thumb drive. When just the thumb drive is plugged in, it boots up great. However, if I have an external USB drive plugged in, it doesn't boot up. If I plug the USB drive in after it is booted up, everything works fine.

How do I tell the bootloader to boot from a specific USB drive?

[Pogoplug Series 4] Booting Debian with Arch Linux ARM uBoot (15 replies)

bodhi — Mon, 04 Mar 2013 04:57:35 -0500

Here I want to describe how I modified uBoot envs in the Pogoplug V4 to boot Debian. This is done for booting with SATA or USB drive. To boot with SD card or USB, see Davygravy's instruction at http://forum.doozan.com/read.php?3,7477 (Davygravy's uBoot is of newer version and much more flexible in that we can use netconsole and other newer uBoot features, however it does not boot with SATA).

As usual, the warning: if you don't have serial console, and have no mean of installing serial console in the future, to recover from potential problems in messing with uBoot envs, then perhaps you should not do it. Arch uBoot does not have netconsole capability, so serial console is needed to recover from bad uBoot envs.

These steps were copied from my installation log. Again, please study the uBoot envs below and make sure that it makes sense to you before modifying them.

This procedure will allow for SATA drive booting first and then USB drive booting.

- Boot into Pogo OS, and save CloudEngines (CE) bin directory /usr/local/cloudengines/bin to a USB drive. We need blparam in this direcotry to change uBoot envs later 
- Install Arch Linux ARM on USB. See instruction at http://archlinuxarm.org/platforms/armv5/pogoplug-series-4
- Boot into Arch, copy saved CE bin directory to /usr/local/bin/cloudengines/bin/

- To list uBoot envs
/usr/local/bin/cloudengines/bin/blparam

- Add uBoot envs to boot Debian

cd /usr/local/bin/cloudengines/bin/

./blparam debian_usb='if ext2load usb 0:1 0x800000 /boot/uImage; then run alarm_which; run alarm_args; fi; if ext2load usb 0:1 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'

./blparam isDisk='no'

./blparam debian_ide='if ext2load ide 0:1 0x800000 /boot/uImage; then setenv device /dev/sda1; run alarm_args; if ext2load ide 0:1 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi; else setenv isDisk yes; fi'

./blparam debian_boot='ide reset; run alarm_revert; if ide part 0; then run debian_ide; else setenv isDisk no; fi; run debian_usb'

- Modify bootcmd env 

./blparam bootcmd='if usb start; then run debian_boot; else nand read 0x800000 0x100000 0x73d0c; go 0x800000; fi'

- Shutdown and cold start with you Debian SATA or USB drive.

Pogoplug boot problem (4 replies)

timmypro — Sun, 31 Mar 2013 12:54:20 -0400

I have a Pogoplug E02. I mess around with uboot with fw_setenv and it does not boot up anymore. (no response to SSH, no status light on the device, IP assigned to pogoplug) I could netconsole to it and it shows the following when i reboot.

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0 
u-boot>>

fw_printenv output:

Pogoplug:ß$  /usr/sbin/fw_printenv                                             
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 öö ext2load usb 0:1 0x1700000 /rescueme 1 öö fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_device=0:1
usb_root=/dev/sda1
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
ethaddr=00:25:31:03:04:9C
arcNumber=2097
serverip=192.168.0.102
ipaddr=192.168.0.103
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
usb_rootfstype=ext3
usb_init=usb stop; usb start; run usb_scan
bootcmd=usb=start

How can I restore to normal pogoplug prompt?

uBoot install Error (no replies)

AcidFir — Mon, 11 Feb 2013 10:44:23 -0500

i try to istall uBoot on my goFlex Home but every time i start the script i say´s 404 Not Found! IS there a Bug in the Script or the downloadserver moved?

!!!!!! DANGER DANGER DANGER DANGER DANGER DANGER !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
Seagate Dockstar
Seagate GoFlex Net
Seagate GoFlex Home
Pogoplug v1
Pogoplug Pink (v2)
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

-n If you agree, type 'ok' and press ENTER to continue:
ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
valid-uboot.md5 100% |********************************************************************************************************************************************************************************************| 1133 --:--:-- ETA
./install_uboot_mtd0.sh: line 250: head: not found
## Unknown uBoot detected on mtd0: 907809c6d628dd10b143a36d9b3f57ca
##
## --no-uboot-check flag detected, continuing installation

############################################
Your device could not be auto-detected.

You must be using a device listed below to run this installer.

What device are you using? Type the number of your device and press ENTER.
1 - Seagate Dockstar
2 - Seagate GoFlex Net
3 - Seagate GoFlex Home
4 - Pogoplug v1
5 - Pogoplug v2 - Pink
6 - Other
3
Selected Seagate GoFlex Home
./install_uboot_mtd0.sh: line 342: head: not found
./install_uboot_mtd0.sh: line 342: sed: not found

# Installing uBoot
## Installing goflexhome
Connecting to download.doozan.com (50.116.34.13:80)
wget: server returned error: HTTP/1.1 404 Not Found
Connecting to download.doozan.com (50.116.34.13:80)
wget: server returned error: HTTP/1.1 404 Not Found
## uBoot could not be downloaded, or the MD5 does not match.
## Exiting. No changes were made to mtd0.
ubit0-6:/tmp#

Greeting
AcidFire

getting the dockstar into arm mode with jtag (no replies)

murpf — Thu, 07 Feb 2013 05:16:29 -0500

hey everyone,

managed to brick my dockstar (accidently erased 0x0...). got a bus pirate with seeedstudio connect cable.
i connected the bus pirate to the jtag using the info at: http://translate.google.de/translate?hl=de&sl=fr&tl=en&u=http%3A%2F%2Fpsolyca.free.fr%2Fwiki%2Fdoku.php%3Fid%3Ddockstar%3Ajtag
i connected a cheap usb ttl converter like the one varkey used for the goflex net.

i think i got jtag running, but everytime i try to halt the cpu, it freezes in thumb mode :(
target state: halted
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x400000f3 pc: 0xffff0a42
MMU: enabled, D-Cache: enabled, I-Cache: enabled

how can i get that damn thing into arm mode to get a new uboot?

thanks

uboot installs, but not environment. [Inactive] (15 replies)

chackoc — Sun, 03 Mar 2013 22:03:01 -0500

I have a black E02. The install script appears to install uboot ok but fails when trying to install the environment.

...
If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5 100% |***************************************************************| 1133 --:--:-- ETA
## Valid uBoot detected: [pinkpogo davygravy-2012-02-20-current]
## The newest uBoot is already installed on mtd0.

You are already running the latest uBoot.
Your current uBoot environment should be reasonable. However, if you're having
any probems booting, you can reset the environment variables to know good values.
Would you like to reset the uBoot environment? [N/y] y

# Installing uBoot environment
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |***************************************************************| 32 --:--:-- ETA
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000
MTD Erase failure: Input/output error
Writing data to block 6 at offset 0xc0000
Bad block at c0000, 1 block(s) from c0000 will be skipped
Writing data to block 7 at offset 0xe0000

# Verifying uBoot environment
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |***************************************************************| 32 --:--:-- ETA
## VERIFICATION FAILED!
## uBoot environment was not properly written to mtd0. Please re-run this installer.

From that output it almost looks like the installer may have succesfully id'ed the bad block and written the env to block 7 instead of 6. Is that correct?

It looks like the script does it's verification against the hardcoded block 6 so that might explain why the verification failed. I edited the script as follows to see if the env was succesfully written to block 7:

Pogoplug:/tmp$ !diff
diff install_uboot_mtd0.sh install_uboot_mtd0_mod.sh 
--- install_uboot_mtd0.sh	Sat Jan  1 00:01:45 2000
+++ install_uboot_mtd0_mod.sh	Sat Jan  1 00:56:45 2000
@@ -527,7 +527,7 @@
   echo "# Verifying uBoot environment"
 
   # Verify the uBoot environment
-  $NANDDUMP --noecc --omitoob -f "/tmp/uboot.environment" -s 0xc0000 -l 0x20000 /dev/mtd0
+  $NANDDUMP --noecc --omitoob -f "/tmp/uboot.environment" -s 0xe0000 -l 0x20000 /dev/mtd0
   wget -O "$UBOOT_ENV.md5" "$UBOOT_ENV_URL.md5"
   verify_md5 "/tmp/uboot.environment" "$UBOOT_ENV.md5"
   if [ "$?" -ne "0" ]; then
Pogoplug:/tmp$

But when I ran the modified script it still failed verification.

# Installing uBoot environment
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |***************************************************************|    32  --:--:-- ETA
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000
MTD Erase failure: Input/output error
Writing data to block 6 at offset 0xc0000
Bad block at c0000, 1 block(s) from c0000 will be skipped
Writing data to block 7 at offset 0xe0000

# Verifying uBoot environment
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000e0000 and ending at 0x00100000...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |***************************************************************|    32  --:--:-- ETA
## VERIFICATION FAILED!
## uBoot environment was not properly written to mtd0.  Please re-run this installer.

In any case rebooting with a USB drive doesn't work. The LED just lights up orange and my routers device table never shows the rebooting box. I'm also unable to use fw_printenv. I get the following:

Pogoplug:/tmp$ /usr/sbin/fw_printenv 
Too few good blocks within range
Pogoplug:/tmp$

Does anyone have any ideas on how to move forward? It seems like others who have had problems were able to skip a bad block and write the objects to the next blocks. Should I try doing that by manually having my modded script write to block 7 (which I assume is 0xe0000)? Perhaps the issue is that block 7 isn't erased before being written to?

For the record, the proposed changes to the script are shown below, but I'm pretty terrified that if I run this I'll brick the box since I don't really know anything about any of this hardware.

Pogoplug:/tmp$ !diff
diff install_uboot_mtd0.sh install_uboot_mtd0_mod.sh 
--- install_uboot_mtd0.sh	Sat Jan  1 00:01:45 2000
+++ install_uboot_mtd0_mod.sh	Sat Jan  1 01:11:18 2000
@@ -520,14 +520,14 @@
     echo "## Could not install uBoot environment, exiting"
     exit 1
   fi
-  $FLASH_ERASE /dev/mtd0 0xc0000 1
-  $NANDWRITE -s 786432 /dev/mtd0 "$UBOOT_ENV"
+  $FLASH_ERASE /dev/mtd0 0xe0000 1
+  $NANDWRITE -s 917504 /dev/mtd0 "$UBOOT_ENV"
 
   echo ""
   echo "# Verifying uBoot environment"
 
   # Verify the uBoot environment
-  $NANDDUMP --noecc --omitoob -f "/tmp/uboot.environment" -s 0xc0000 -l 0x20000 /dev/mtd0
+  $NANDDUMP --noecc --omitoob -f "/tmp/uboot.environment" -s 0xe0000 -l 0x20000 /dev/mtd0
   wget -O "$UBOOT_ENV.md5" "$UBOOT_ENV_URL.md5"
   verify_md5 "/tmp/uboot.environment" "$UBOOT_ENV.md5"
   if [ "$?" -ne "0" ]; then
Pogoplug:/tmp$

Also, in case it's not blindingly obvious, while I'm comfortable on the software side of linux, messing around with this sort of stuff is completely new to me.

Minor "glitch" in install_uboot_mtd0.sh (no replies)

sed — Wed, 30 Jan 2013 17:55:59 -0500

Hello there,

this is actually a post directed to Jeff.

I just noticed a minor "glitch" in the install_uboot_mtd0.sh script. I think line 144 should read:

      local is_readonly=1

So that a read-only file system is later remounted read-only. The debian installer script (kirkwood.debian-wheezy.sh) is correct in this regard.

Keep up the good work
sed

Pogoplug E02 completely dead - no ssh, www and serial (2 replies)

chiefdome — Tue, 05 Feb 2013 04:08:53 -0500

Hi there I have got a Pogoplug which is completetly dead - cant get access to it?
I think the only solution would be to recover via jtag?
Since pogoplugged.com is dead there is not much information about how to realize this with an ftdi chip or with the bus pirate?
Thanks for your replys!

Goflex Net fail -need help to unbrick (4 replies)

daveeeee — Thu, 31 Jan 2013 03:39:40 -0500

Hello,

i have an almost new Goflex Net device, that i wanted to run debian. After trying different solutions (installing debian and rescue), i have problem with my device.

I cannot install a new uboot, and the only way i can access it is through the serial port with uart boot. I tried some of the suggestions in the forum, but i am stuck with it.
It seems the first nand block is bad. I want to ask the experts, what to do to get it running, if somebody could help me with unbricking. I hope there is some light chance to use it :)

I can boot it by uart to the dns-320 image on the usb, but i cannot install uboot. The script ends with verification failed. I tried writing with nandwrite (found in this forum that somebody managed to repair it with the same symptoms) with no success.

I cannot get further. Here is my log:

##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.

root@debian-kirkwood-wide:/tmp# /usr/sbin/flash_erase /dev/mtd0 0 5
Erase Total 5 Un[ 748.998066] nand_erase_nand: attempt to erase a bad block at page 0x00000000
its
Performing Flash Erase of length 131072 at offset 0x0
MTD Erase failure: Input/output error
root@debian-kirkwood-wide:/tmp# /usr/sbin/nandwrite /dev/mtd0 uboot.mtd0.kwb
Writing data to block 0 at offset 0x0
Bad block at 0, 1 block(s) from 0 will be skipped
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
td0t@debian-kirkwood-wide:/tmp# nanddump -bnof /tmp/uBoot.dump -l 0x80000 /dev/m
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
root@debian-kirkwood-wide:/tmp# diff -s uboot.mtd0.kwb uBoot.dump
Binary files uboot.mtd0.kwb and uBoot.dump differ
root@debian-kirkwood-wide:/tmp#

Any help is much appreciated.

uBoot install canceled with Pogo E02(Black) (10 replies)

ploks — Sat, 02 Feb 2013 13:02:14 -0500

Hello

I have a Pogoplug E02Black)

I want to install Debian uboot on my Pogoplug E02(Black). but I can't install on my device

Can you help me to solve my problem?

My pogo's nand flash has a 1 bad blocks at 60000. Maybe, Is this a my problem?

I don't know about it

I hope to resolve my problems and install on my Pogoplug E02(Black)

I'll take iinfomations about my pogoplug E02(Black) below

My Pogo's cpu info is

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

uname -a is

Linux Pogoplug 2.6.22.18 #81 Tue Oct 19 16:05:00 PDT 2010 armv5tejl unknown

version is

Linux version 2.6.22.18 (bdietrich@buildman) (gcc version 4.2.1) #81 Tue Oct 19 16:05:00 PDT 2010

meminfo is

MemTotal:       256008 kB
MemFree:        154968 kB
Buffers:            12 kB
Cached:          84940 kB
SwapCached:          0 kB
Active:          18712 kB
Inactive:        67140 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:               0 kB
Writeback:           0 kB
AnonPages:         928 kB
Mapped:           1588 kB
Slab:            13472 kB
SReclaimable:     1368 kB
SUnreclaim:      12104 kB
PageTables:         96 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:    128004 kB
Committed_AS:    83048 kB
VmallocTotal:   385024 kB
VmallocUsed:       324 kB
VmallocChunk:   384696 kB

blparam is

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
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
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
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
bootargs=console=ttyS0,115200 root=/dev/mtdblock2 ro
serverip=169.254.254.252
ipaddr=169.254.254.253
ethaddr=00:25:31:02:D6:74
cesvcid=LE9FW64CV8GHU3Z46W8Q2S3Z7N
ceboardver=PPV2
bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000

fw_printenv is

ethact=egiga0
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset

dmesg is

[    0.000000] Linux version 2.6.22.18 (bdietrich@buildman) (gcc version 4.2.1) #81 Tue Oct 19 16:05:00 PDT 2010
[    0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
[    0.000000] Machine: Feroceon-KW
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 65536
[    0.000000]   DMA zone: 512 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 65024 pages, LIFO batch:15
[    0.000000]   Normal zone: 0 pages used for memmap
[    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: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
[    0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.010000] Memory: 256MB 0MB 0MB 0MB = 256MB total
[    0.010000] Memory: 255872KB available (3592K code, 253K data, 124K init)
[    0.010000] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
[    0.250000] Mount-cache hash table entries: 512
[    0.250000] CPU: Testing write buffer coherency: ok
[    0.250000] NET: Registered protocol family 16
[    0.250000]
[    0.250000] CPU Interface
[    0.250000] -------------
[    0.250000] SDRAM_CS0 ....base 00000000, size 256MB
[    0.250000] SDRAM_CS1 ....disable
[    0.250000] SDRAM_CS2 ....disable
[    0.250000] SDRAM_CS3 ....disable
[    0.250000] PEX0_MEM ....base e8000000, size 128MB
[    0.250000] PEX0_IO ....base f2000000, size   1MB
[    0.250000] INTER_REGS ....base f1000000, size   1MB
[    0.250000] NFLASH_CS ....base fa000000, size   2MB
[    0.250000] SPI_CS ....base f4000000, size  16MB
[    0.250000] BOOT_ROM_CS ....no such
[    0.250000] DEV_BOOTCS ....no such
[    0.250000] CRYPT_ENG ....base f0000000, size   2MB
[    0.250000]
[    0.250000]   Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG  Soc: 88F6281 A0 LE
[    0.250000]
[    0.250000]  Detected Tclk 200000000 and SysClk 400000000
[    0.250000] MV Buttons Device Load
[    0.250000] Marvell USB EHCI Host controller #0: c0652600
[    0.750000] PEX0 interface detected no Link.
[    0.750000] PCI: bus0: Fast back to back transfers enabled
[    0.750000] SCSI subsystem initialized
[    0.750000] usbcore: registered new interface driver usbfs
[    0.750000] usbcore: registered new interface driver hub
[    0.750000] usbcore: registered new device driver usb
[    0.750000] NET: Registered protocol family 2
[    0.760000] Time: kw_clocksource clocksource has been installed.
[    0.850000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.850000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.850000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.850000] TCP: Hash tables configured (established 8192 bind 8192)
[    0.850000] TCP reno registered
[    0.880000] RTC has been updated!!!
[    0.880000] RTC registered
[    0.880000] Use the XOR engines (acceleration) for enhancing the following functions:
[    0.880000]   o RAID 5 Xor calculation
[    0.880000]   o kernel memcpy
[    0.880000]   o kenrel memzero
[    0.880000] Number of XOR engines to use: 4
[    0.880000] cesadev_init(c00117b0)
[    0.880000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
[    0.880000] MV Buttons Driver Load
[    0.880000] squashfs: version 3.3 (2007/10/31) Phillip Lougher
[    0.880000] squashfs: LZMA suppport for slax.org by jro
[    0.880000] JFFS2 version 2.2. (NAND) Ã‚Â© 2001-2006 Red Hat, Inc.
[    0.880000] io scheduler noop registered
[    0.880000] io scheduler anticipatory registered (default)
[    0.900000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[    0.900000] 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.920000] 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.990000]     o eth0, ifindex = 1, GbE port = 0
[    0.990000]     o eth1, ifindex = 2, GbE port = 1
[    1.000000]
[    1.000000] mvFpRuleDb (cfdf6000): 2048 entries, 8192 bytes
[    1.000000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[    1.010000] Copyright (c) 1999-2006 Intel Corporation.
[    1.020000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[    1.020000] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.030000]
[    1.030000] Warning Sata is Powered Off
[    1.030000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[    1.040000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[    1.050000] Scanning device for bad blocks
[    1.050000] Bad eraseblock 3 at 0x00060000
[    1.110000] Using static partition definition
[    1.110000] Creating 4 MTD partitions on "nand_mtd":
[    1.120000] 0x00000000-0x00100000 : "u-boot"
[    1.120000] 0x00100000-0x00500000 : "uImage"
[    1.130000] 0x00500000-0x02500000 : "root"
[    1.130000] 0x02500000-0x08000000 : "data"
[    1.140000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[    1.140000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[    1.180000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[    1.200000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    1.200000] usb usb1: configuration #1 chosen from 1 choice
[    1.210000] hub 1-0:1.0: USB hub found
[    1.210000] hub 1-0:1.0: 1 port detected
[    1.330000] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.330000] USB Universal Host Controller Interface driver v3.0
[    1.610000] usb 1-1: new high speed USB device using ehci_marvell and address 2
[    1.760000] usb 1-1: configuration #1 chosen from 1 choice
[    1.760000] hub 1-1:1.0: USB hub found
[    1.770000] hub 1-1:1.0: 4 ports detected
[    1.880000] usbcore: registered new interface driver usblp
[    1.880000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
[    1.890000] Initializing USB Mass Storage driver...
[    1.890000] usbcore: registered new interface driver usb-storage
[    1.900000] USB Mass Storage support registered.
[    1.910000] mice: PS/2 mouse device common for all mice
[    1.910000] i2c /dev entries driver
[    1.910000] Linux telephony interface: v1.00
[    1.920000] md: linear personality registered for level -1
[    1.920000] md: raid0 personality registered for level 0
[    1.930000] md: raid1 personality registered for level 1
[    2.100000] raid6: int32x1     97 MB/s
[    2.270000] raid6: int32x2    114 MB/s
[    2.440000] raid6: int32x4    122 MB/s
[    2.610000] raid6: int32x8    110 MB/s
[    2.610000] raid6: using algorithm int32x4 (122 MB/s)
[    2.610000] md: raid6 personality registered for level 6
[    2.620000] md: raid5 personality registered for level 5
[    2.620000] md: raid4 personality registered for level 4
[    2.630000] raid5: measuring checksumming speed
[    2.680000]    arm4regs  :  1084.000 MB/sec
[    2.730000]    8regs     :   754.800 MB/sec
[    2.780000]    32regs    :   899.600 MB/sec
[    2.780000] raid5: using function: arm4regs (1084.000 MB/sec)
[    2.790000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[    2.790000] dm_crypt using the OCF package.
[    2.800000] sdhci: Secure Digital Host Controller Interface driver
[    2.800000] sdhci: Copyright(c) Pierre Ossman
[    2.810000] usbcore: registered new interface driver usbhid
[    2.810000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[    2.820000] TCP cubic registered
[    2.820000] NET: Registered protocol family 1
[    2.830000] NET: Registered protocol family 17
[    2.830000] md: Autodetecting RAID arrays.
[    2.840000] md: autorun ...
[    2.840000] md: ... autorun DONE.
[    4.600000] Empty flash at 0x009ac208 ends at 0x009ac800
[    8.800000] VFS: Mounted root (jffs2 filesystem) readonly.
[    8.800000] Freeing init memory: 124K
[   10.940000] eth0: link down
[   10.950000] eth0: started
[   12.530000] eth0: link up, full duplex, speed 100 Mbps

Install is

Pogoplug:/$ cd /tmp
Pogoplug:/tmp$ wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh
Connecting to jeff.doozan.com (50.116.34.13:80)
install_uboot_mtd0.s 100% |*******************************| 18406  00:00:00 ETA
Pogoplug:/tmp$ chmod +x install_uboot_mtd0.sh
Pogoplug:/tmp$ ./install_uboot_mtd0.sh


!!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER  !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
 Seagate Dockstar
 Seagate GoFlex Net
 Seagate GoFlex Home
 Pogoplug v1
 Pogoplug Pink (v2)
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |*******************************|  1133  --:--:-- ETA
## Unknown uBoot detected on mtd0: ec3fadd50ae24760b035b0afe9ac6018
##
## The installer could not detect the version of your current uBoot
## This may happen if you have installed a different uBoot on
## /dev/mtd0 or if you have bad blocks on /dev/mtd0
##
## If you have bad blocks on mtd0, you should not try to install uBoot.
##
## Installation cancelled.

Install(no prompt no uboot check parameter) is

Pogoplug:/tmp$ ./install_uboot_mtd0.sh --noprompt --no-uboot-check parameter
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |*******************************|  1133  --:--:-- ETA
## Unknown uBoot detected on mtd0: ec3fadd50ae24760b035b0afe9ac6018
##
## --no-uboot-check flag detected, continuing installation

############################################
Your device could not be auto-detected.

You must be using a device listed below to run this installer.

What device are you using? Type the number of your device and press ENTER.
1 - Seagate Dockstar
2 - Seagate GoFlex Net
3 - Seagate GoFlex Home
4 - Pogoplug v1
5 - Pogoplug v2 - Pink
6 - Other
5
Selected Pogoplug v2 - Pink

# Installing uBoot
## Installing pinkpogo davygravy-2012-02-20
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5   100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb       100% |*******************************|   512k 00:00:00 ETA
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000
MTD Erase failure: Input/output error
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Bad block at 60000, 1 block(s) from 60000 will be skipped
Writing data to block 4 at offset 0x80000
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5   100% |*******************************|    32  --:--:-- ETA
##
##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.

I was wrong: installed uboot on B04 (1 reply)

zampara — Sun, 27 Jan 2013 14:06:20 -0500

Hi,

I used the command --force, but my pogo is pro and not pink v2, so i have now a bricked pogoplug .
I bought the cable C-42, so I have a serial connection. Befor installing,
i made backups with

# nanddump -nof mtd0.backup /dev/mtd0
# nanddump -nf mtd0.backup.oob

Using the boot sata: i used these commands:

flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 mtd0.backup
reboot

The Pogoplug does not start. With serial connection i see this in terminal

# screen /dev/ttyUSB0 115200 8N1
Reading NAND, Image 0
Uncorrectable error(s) encountered in page with starting address 0x00040000.

Uncorrectable error(s) encountered in page with starting address 0x00040000.

Hdr len: 0xA1A2A3A4
Hdr CRC: 0xB1B2B3B4
read failed
Reading NAND, Image 1
Uncorrectable error(s) encountered in page with starting address 0x00100000.

Uncorrectable error(s) encountered in page with starting address 0x00100000.

Hdr len: 0xA1A2A3A4
Hdr CRC: 0xB1B2B3B4
read failed
Reading NAND, Image 0
Uncorrectable error(s) encountered in page with starting address 0x00040000.

Is it possible to reset the nand correctly. ? :S

Thanks

Dockstar - now way to boot (1 reply)

satjuice — Tue, 22 Jan 2013 16:28:25 -0500

Hi all,

I have a dockstar on which I installed a couple of years ago Debian Squeeze.
Yesterday I tried to do a dist-upgrade.
Something went wrong.

No way to reboot via usb key.

I can boot using v3 rescue USB key.

Without USB key this is what I see via serial cable.

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:

thanks to all
Satjuice

Swap boot disks with between two dock (1 reply)

Andre Chantme — Thu, 10 Jan 2013 05:01:28 -0500

Hello

Forgive me if it's not the right place to post, I'am a newbie with this subject, I just presume it's the appropriate forum..

I own two docks, on each I attached an USB disk, and I installed Debian squeeze following http://projects.doozan.com/debian/, it works fine, thank you Jeff :-)

If I try to swap disks and put disk 2 on dock 1 (and vice versa), none of them boots.

Do I miss something ? is this normal ? does it mean that the pair can't be separate and only the parts installed conjointly work ?

Thanks for your reply

Andre