Problems with POGO-E02 (Black)

Hi there,

I have an POGO-E02 (Black) and wanted to install ArchLinux on it. Hardware-Infos to the device:

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

Hardware        : Feroceon-KW
Revision        : 0000
Serial          : 0000000000000000


Pogoplug:/tmp$ cat /proc/meminfo
MemTotal:       256008 kB
MemFree:        240992 kB
Buffers:            32 kB
Cached:           4304 kB
SwapCached:          0 kB
Active:           2960 kB
Inactive:         2280 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:               0 kB
Writeback:           0 kB
AnonPages:         932 kB
Mapped:           1576 kB
Slab:             8576 kB
SReclaimable:      316 kB
SUnreclaim:       8260 kB
PageTables:         96 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:    128004 kB
Committed_AS:     3560 kB
VmallocTotal:   385024 kB
VmallocUsed:       324 kB
VmallocChunk:   384696 kB

"uName" gives the following result (when now booting without usb-device) :

Pogoplug:~$ uname -a
Linux Pogoplug 2.6.22.18 #81 Tue Oct 19 16:05:00 PDT 2010 armv5tejl unknown

I used the instructions on the ArchLinux pages (http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray) what included the installation of "uBoot". Although there was no error-message in the complete installation-process (uBoot & ArchLinux) the POGO-E02 (Black) does not come up. So I wondered if uBoot was installed properly and tried to install again :

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  --:--:-- 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
## 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
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment    100% |*******************************|   128k 00:00:00 ETA
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Writing data to block 6 at offset 0xc0000

# 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

# uBoot installation has completed successfully.

When I start the Pogo-E02 (with plugged in USB-device with installed ArchLinux) the LED stays off, the LED is working for some seconds, then the LED turns orange and nothing else happens (the device is not shown in the router, so it can't received a new, deiffrent IP).

My questions :
- Did I pick the wrong uBoot ?
- Do you see an errors/mistakes in uBoot ?

Thanx 4 help.


Edit: The command "/usr/sbin/fw_printenv" says:

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_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:00:00:00:00:00 -----> CHANGED ONLY FOR THIS FORUM-POST !
arcNumber=2097

Edited 2 time(s). Last edit at 12/23/2012 05:24PM by JOLA.

It's the correct uBoot. Looks like there was no error in uBoot envs installation, either. Can you boot into Pogo OS (after removing the USB stick and recycle power)? If you can, run the uBoot installation again, and then setup netconsole right away. Then reboot. See if netconsole output says anything out of the ordinary.

I downloaded the netconsole-windows-version, started "nc -l -u -p 6666" on my windows-pc and a black nc-window appears.

The I did the steps as mentioned in the netconsole-manual (http://forum.doozan.com/read.php?3,14), but used the adresses of my LAN-devices (Pogo and PC). After entering the commands line by line without error I rebooted the Pogo with "/sbin/reboot" - but the black windows in the PC stays empty (Firewall turned off before). Also a second windows to communicate from PC to POGO ("nc -u ...") stays black.

You can verify netconsole setup by: on Windows command prompt, start continously pinging the IP address of the Pogo netconsole. Do this before you reboot to Pogo and see if it responds. If the Pogo netconsole IP address was set correctly, then it will respond to the ping for a few seconds. What type of nc/netcat/socat,.... program are you running on Windows?

Thanx 4 helping me with my problem. What I did now was:
- Totally power off Pogo
- Opening CMD-box in Win-PC and entering "ping 192.168.x.y -t" (IP-Adress of Pogo, permanent Ping)
- Powering on Pogo with USB-HDD plugged in
- After some secondfs I now get a response from the Pogo
- Logging in from Win-PC via SSH, now having to use user/pw "root/root" (found by try and error)
- Bash is showing " [root@alarm /]# "

Is this want it should be (ArchLinux installed) ? Please don't ask me why I get this now, I just powered off the Pogo like so many, many, many times before.

Yes! sounds like you've successfully installed Arch. That's the prompt.

Cool ... finally working. ;-)

Hey there, looking for a little help with a E02. I currently am running ALARM on it. When I remove the usb key and try to reboot the pogo os, it never boots, no led on the front. I put the isb stick back in, reboot, ALARM comes up.

Would like to figure out what I did.

Keith

Let see what's in your uBoot environment with the output of

#fw_printenv

Thanks for responding. I have attached the output from fw_printenv as well as the console output with my archlinuxarm usb stick in and without the usb stick.

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_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:25:31:02:EA:4B
arcNumber=2097
serverip=192.168.1.110
ipaddr=192.168.1.132
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


Console output with Archlinuxarm USB stick

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
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 4 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-0x000008000000 : "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: 91 MiB
UBI: number of good PEBs: 728
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: 717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
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)
2856016 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.1.10-13-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2855952 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

WITHOUT USB STICK

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
(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... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "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: 91 MiB
UBI: number of good PEBs: 728
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: 717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
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'!
** 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.
### JFFS2 load complete: 18084 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

STOPS HERE

Thanks
Keith

@Keith,

Everything looks good to me except the size of the original uBoot image, it seems too small:

### JFFS2 load complete: 18084 bytes loaded to 0x800000

I would run the uBoot installation again (it won't hurt). And keep the installation log so you an go back to it and verify the installation activities related to pogo_bootcmd

I have rerun the install with no change in results. output below

[root@alarm /]# ./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...
--2013-01-08 05:36:46-- http://jeff.doozan.com/uboot/valid-uboot.md5
Resolving jeff.doozan.com (jeff.doozan.com)... 50.116.34.13
Connecting to jeff.doozan.com (jeff.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://projects.doozan.com/uboot/valid-uboot.md5 [following]
--2013-01-08 05:36:47-- http://projects.doozan.com/uboot/valid-uboot.md5
Resolving projects.doozan.com (projects.doozan.com)... 50.116.34.13
Connecting to projects.doozan.com (projects.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1133 (1.1K) [text/plain]
Saving to: ‘/tmp/valid-uboot.md5’

100%[======================================>] 1,133 --.-K/s in 0s

2013-01-08 05:36:49 (27.1 MB/s) - ‘/tmp/valid-uboot.md5’ saved [1133/1133]

## 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
--2013-01-08 05:37:02-- http://download.doozan.com/uboot/files/environment/uboot.environment.md5
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/tmp/uboot.environment.md5’

[ <=> ] 32 --.-K/s in 0s

2013-01-08 05:37:03 (324 KB/s) - ‘/tmp/uboot.environment.md5’ saved [32]

--2013-01-08 05:37:03-- http://download.doozan.com/uboot/files/environment/uboot.environment
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 131072 (128K) []
Saving to: ‘/tmp/uboot.environment’

100%[======================================>] 131,072 323KB/s in 0.4s

2013-01-08 05:37:05 (323 KB/s) - ‘/tmp/uboot.environment’ saved [131072/131072]

Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Writing data to block 6 at offset 0xc0000

# Verifying uBoot environment
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
--2013-01-08 05:37:05-- http://download.doozan.com/uboot/files/environment/uboot.environment.md5
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/tmp/uboot.environment.md5’

[ <=> ] 32 --.-K/s in 0s

2013-01-08 05:37:06 (326 KB/s) - ‘/tmp/uboot.environment.md5’ saved [32]


# uBoot installation has completed successfully.

Here is my guess (without seeing the original installation log) : there was some problem saving the original uBoot during the first time that you installed ALARM. IIRC, the orginal uBoot image is about 500 KB. Your console output showing the original uBoot image was loaded, but only about 18KB.

Can you stop serial/net console during the countdown, and then try:
run pogo_bootcmd

See what the behavior looks like. I don't expect it to behave differently, but it's worth a try.

Another thought, if you want to have a recovery mechanism so you can boot the Pogo E02 and fix rootfs problem, then you can install rescue system, too. So booting back to Pogo OS is no loger needed for that purpose.

I just bought another pogo-e02 from J&R. It has newer files on it than my first e02 and when I tried to run the current ./install_uboot_mtd0.sh but it failed. Have they changed the uboot? How can I tell? An mtd0 dump does not match the uboot.mtd0.dockstar.original.kwb.

Does anyone know if they Cloudengines has changed the uboot?

I got this (second time I ran install_uboot_mtd0.sh )

# 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: 459cd5082764fc782e204f7de8f4bcca
##
## 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.

Also when I run fw_printenv all I get is.

Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200

blparam shows

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:04:4B:70
cesvcid=EDDCTEPRFJPAP33JXRGKZ2XA36
ceboardver=PPV2
bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root);bootm 0x800000

Suggestions?
Known issues?
How do I check for bad blocks?
Thanks,
TJ

@TJ,

- What's your cat /proc/cpuinfo and uname -a show? ceboardver=PPV2 indicates that it is an E02.
- dmesg will show if there are bad blocks.

If it is indeed a Pogo E02 then if there is no bad block, you can run install_uboot_mtd0 with option "no-uboot-check".

Thanks!
blparams originally showed:

ceboardver=PPV2
bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root);bootm 0x800000



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

Hardware : Feroceon-KW
Revision : 0000
Serial : 0000000000000000

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

Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG Soc: 88F6281 A0 LE

I tried it with the --no-uboot-check -- it failed.

nandwrite /dev/mtd0 uboot.mtd0.kwb
Writing data to block 0
Writing data to block 20000
Writing data to block 40000
Bad block at 40000, 1 block(s) from 40000 will be skipped
Writing data to block 60000
Writing data to block 80000

Can anything be done or should I just scrap it?

TJ

Oh, yes, and now running blparam produces pages of this.
Too many bit errors @ 0xb0800 -- Can't correct!
PAGE DATA:
00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
...
00000590: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
000005a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
000005b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
000005c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
000005d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
000005e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
000005f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
00000600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
00000610: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................

I have a funny feeling that if I turn it off, I'll never see anything again.
Anyone want this jtag project?

TJ

TJ, dont power down or reboot if you don't have serial console.

How far did it go when you run install install_uboot_mtd0 ? do you have the log you can post it here?

Addendum:
I did recover from this before, here is the thread - starting form this post: http://forum.doozan.com/read.php?3,5728,5748#msg-5748. I did a no-uboot-check installation knowing that it could brick the E02, and restamp helped me flashing uBoot around the bad blocks.



Edited 2 time(s). Last edit at 01/08/2013 11:48PM by bodhi.

I tried to interact with the console when running nc but for some reason it didnt respond. I am running Linux Mint and installed the nc.traditional package. Will load up another os and try.

Tried nc with scientific linux and also doesnt allow me to interrupt the boot

@Keith,

Did you set up 2 nc commands per Jeff's instruction? some of us needs to change the 2nd command slightly to get it working:

nc -l -u -p 6666 &
nc -up 6666 192.168.1.100 6666

@bodhi,
Thanks!
I read the other thread. I had a different block bad so had to adjust the parts. Intersting that I did as you indicate before your instructions. I must be "getting" some of this...
But thanks to restamp dump-by-parts, I got a good md5 check. Magically, now fw_printenv now gets results. :-)

FYI what worked...

#/tmp/install_uboot_mtd0.sh --noprompt --no-uboot-check parameter  (log below)
#nanddump -nof /tmp/uBoot1.dump -l 0x40000 /dev/mtd0
#nanddump -nof /tmp/uBoot2.dump -l 0x40000  -s 0x60000 /dev/mtd0
#cat uBoot1.dump uBoot2.dump >uBootbyparts.dump
#md5sum uBootbyparts.dump 
e84a5fd0a0205bb79aed07c3c6fbd145  uBootbyparts.dump
e84a5fd0a0205bb79aed07c3c6fbd145 pinkpogo davygravy-2012-02-20-current .md5 !

#diff -s uboot.mtd0.kwb uBootbyparts.dump
Files uboot.mtd0.kwb and uBootbyparts.dump are identical

Magically, now fw_printenv now gets results. :-)

Now to try to make sure all the important ones are there...


TJ


*****************log file from the install...
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 0x40000
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
Bad block at 40000, 1 block(s) from 40000 will be skipped
Writing data to block 3 at offset 0x60000
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.

@bodhi,

I did enter both commands and tried various attempts. Seems to be non interactive.

Keith

Success! Thanks for the tips and encouragement all.
Reboot into the pogoplug V2 with the new environment in place, in spite of bad block in the middle of the uboot.

This one I'm putting extra stuff on mtd3 as optware. No external drives ... yet.

TJ
Wish we had some wxtofly

@TJ,

Congrats! great to hear a successful recovery :)

I figured out what my issue was. Somehow the uboot-original-mtd0.kwb file that is stored in the root of mtdblock2 was not there. I downloaded one off the web and put it in the root of mtdblock2 and it fixed my issue, I can now boot off pogo os or usb thumbdrive.

Thanks
Keith

Hi Jeff,
I have this same Black Pogo-E02, and the uboot install error at the same 459cd5082764fc782e204f7de8f4bcca
Looking at previous posts with this version, it looks like users have become semi bricked with forcing no-check. Is there any updated info on this uboot version? Thank you for all that you do.
Regards,
Ted