Pogoplug POGO-E02 u-boot broken?

This forum is for topics dealing with problems with software specifically in the ARMv5 repo.

Pogoplug POGO-E02 u-boot broken?

Postby woynitt » Sat Aug 15, 2020 4:23 pm

Hi,

on the internet auction I've bought few untested electronic parts and one of them was Pogoplug POGO-E02.

I turned it on and ethernet port blinks, so I started digging and founded information about console inside.

After connect console and power up I've got below text and looks like u-boot is broken, because it's restarting all the time.

It's possible to repair or only destination is trash?

$this->bbcode_second_pass_code('', '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.1.2 is alive')
woynitt
 
Posts: 2
Joined: Sat Aug 15, 2020 4:13 pm

Re: Pogoplug POGO-E02 u-boot broken?

Postby moonman » Sat Aug 15, 2020 5:47 pm

If you are seeing something it's not broken.
Interrupt U-Boot process and enter "printenv" and post it here.

Most likely somebody booted up 3rd party OS on it, like ArchLinux ARM and now since there is no external storage with the OS attached, it won't boot up. It should be recoverable with, most likely, installing ArchLinuxARM on a USB flash drive/hdd.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3387
Joined: Sat Jan 15, 2011 3:36 am

Re: Pogoplug POGO-E02 u-boot broken?

Postby woynitt » Sat Aug 15, 2020 9:41 pm

I've got below respond.

So if I good understand - now I should update u-boot and install OS?


$this->bbcode_second_pass_code('', '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

Abort
ping failed; host 192.168.1.2 is not alive
Hit any key to stop autoboot: 0
u-boot>> <INTERRUPT>
u-boot>>
u-boot>>
u-boot>>
u-boot>> printenv
arcNumber=2097
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=3
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:04:9D:A8
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.5
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
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; nand 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.2
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc
stderr=serial
stdin=serial
stdout=serial
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
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 ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else 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 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_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: 2559/131068 bytes
u-boot>>
')
woynitt
 
Posts: 2
Joined: Sat Aug 15, 2020 4:13 pm

Re: Pogoplug POGO-E02 u-boot broken?

Postby moonman » Sun Aug 16, 2020 3:14 am

This looks like Jeff's old U-Boot. I think it had a problem booting kernels >=3.1 or something like that :| But you can try it anyway. Create a bootable USB flash drive on a PC running any kind of Linux:

Create a single partition and format it ext3
download http://os.archlinuxarm.org/os/ArchLinux ... est.tar.gz
extract ArchLinuxARM-kirkwood-latest.tar.gz as root (not sudo) to the flash drive.

Plug this flash drive into pogoplug and see if it boots up. If it does, you are golden as you will be able to update U-Boot from withing ArchLinuxARM
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3387
Joined: Sat Jan 15, 2011 3:36 am


Return to ARMv5

Who is online

Users browsing this forum: No registered users and 8 guests