Pogoplug V4 not booting

Greetings,

Please help....
apparently I've made my Pogoplug V4 unable to boot. Front Led always off all the time, not blinking at all, not even the green one.

Serial connection status are connected, but no booting text coming on screen. Only blank screen appear. Also unable to send command on serial.

Ok, so before this thing happen. I'm trying to use my pogoplug as NAS server and media server, but also some other function like download manager, etc. Plan to load OpenWRT/Lede or Arch. This is due to Pogoplug not able to share USB drive. So I decide to switch to Lede/Archlinux.

Right after I register my device on pogoplug website, I'm unable to activate SSH on the pogoplug website, and all USB thumbdrive on all port were not able to shared, like no drive attached even I've attached the drive. I can't read the share folder on Pogoplug.

So, I end up try to get SSH by Serial... And after some gooling I've managed to access to serial and enable dropbear and I'm able to get SSH to pogo. But, it was not permanent, after reboot, dropbear back to disable mode and I've to enable again using serial cable. I can't change root password also, it says /etc/passwd write protected.

Then, I try to upgrade U-boot. And then this happen... I think I'm using wrong command and wrong uboot image. The pogoplug seem unusable for me now after I messed up with Uboot...

Please help guide me how to recover my pogo...


my command log attached...

**) Sorry for my bad english

alphaprime,

I am quite busy so I will look at this in a couple days if no one has helped by that time.

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

Basically, you messed up mtd0 (uboot) and you will need jtag to recover it.

https://wiki.openwrt.org/toh/cloudengines/pogo-v4

also read the jtag info with raspberry pi since this is easy to get, and you can use it for fun later.

https://forum.doozan.com/read.php?3,21789

Hi Bodhi,

Thank you for your response.

If you have free time, please help me to recover my Pogo.

Currently still confuse what method to recover my Pogo.

Thanks

Hi Daviddyer,

Thank you for giving me some light on this.

Currently I don't have Raspi yet. But I will study thread on the link you provided.

My question is:
- Does this the cheapest (easiest) way to recover my pogo?
- Boot using SATA port or USB top port is impossible on this situation?
- My pogo is Pogoplug V4-A3 and the tutorial is for Pogo E2. Which part will be different? can I use the same file as mentioned on the thread?

Thank you

alphaprime,

With the Pogo V4, it does not matter if you have messed up mtd0 or not. You can recover with serial console using kwboot.

Download the Pogo V4 u-boot from the installation thread:
https://forum.doozan.com/read.php?3,12381

Quote

uboot.2017.07-tld-1.pogo_v4.bodhi.tar
md5
e2c2b4927dcd8189f0c97dd81b72ad7e
sha256
18f856d2106aabe6029331358fb06f053ea9257ad896e2d382f4f096f93c46e9

Follow the instruction in this UARTthread by davygravy:
https://forum.doozan.com/read.php?3,7852,7852

Boot the Pogo V4 using the uboot.2017.07-tld-1 with the latest kwboot binary, also from the u-boot installation thread:
https://forum.doozan.com/read.php?3,12381

To download ARM kwboot binary for UART booting at Dropbox

kwboot-2016.05.tar 
md5: 
76977c5a61544a5707dfa17ae832a3ad 
sha256: 
25ee4fa8a94372d2d398cac4704e9ee3ca87585c29e72e18323209b7f163209d 

kwboot (this is an older version) 
md5: 
0efd011bdb244436e432a8de33e639a1

Once you can boot and see u-boot output in kwboot serial console, it is unbricked. Please do that and we'll go from there.

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



Edited 1 time(s). Last edit at 12/17/2017 05:57AM by bodhi.

Hi Bodhi,

I'm trying to follow the guide, I found out that both kwboot that you mention didn't work out on my linux netbook.

This is my linux netbook

$ uname -a
Linux 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 i686 i686 i686 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Linux Lite 3.0
Release:	16.04
Codename:	xenial

File directory:

-rw-rw-r-- 1 alpha alpha 196352036 Des 18 08:46 Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2
-rwxrwxr-x 1 alpha alpha      9448 Des 18 05:26 kwboot
-rwxr-xr-x 1 alpha alpha     15604 Nov 26  2016 kwboot_2016_05
-rw-rw-r-- 1 alpha alpha     20480 Des 18 05:48 kwboot-2016.05.tar
-rw-rw-r-- 1 alpha alpha  31580821 Des 18 08:39 linux-4.14.1-kirkwood-tld-1-bodhi.tar.bz2
-rw-rw-r-- 1 alpha alpha    532480 Des 18 05:24 uboot.2017.07-tld-1.dockstar.bodhi.tar
-rw-rw-r-- 1 alpha alpha    532480 Des 18 05:23 uboot.2017.07-tld-1.pogo_v4.bodhi.tar
-rw-r--r-- 1 alpha alpha    524288 Sep  5 14:37 uboot.2017.07-tld-1.pogo_v4.mtd0.kwb

MD5SUM:

$ md5sum kwboot
0efd011bdb244436e432a8de33e639a1  kwboot
$ md5sum kwboot_2016_05
3d0dd841a94d9d34629a60bb046979ce  kwboot_2016_05

Found this error when running the file

$ ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.pogo_v4.mtd0.kwb
bash: ./kwboot: cannot execute binary file: Exec format error

$ ./kwboot_2016_05 -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.pogo_v4.mtd0.kwb
bash: ./kwboot_2016_05: cannot execute binary file: Exec format error

Looking for kwboot on my linux

$ whereis kwboot
kwboot: /usr/bin/kwboot /usr/share/man/man1/kwboot.1.gz

Rename original kwboot to kwboot.orig and put kwboot_2016_05 to /usr/bin/kwboot

$ sudo mv /usr/bin/kwboot /usr/bin/kwboot.orig

Execution on the new kwboot after renaming, found below error:

# /usr/bin/kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.pogo_v4.mtd0.kwb
bash: /usr/bin/kwboot: cannot execute binary file: Exec format error

Using old original kwboot:

# /usr/bin/kwboot.orig -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.pogo_v4.mtd0.kwb
Sending boot message. Please reboot the target...|^C

And finally after dozen time try to get the handshake, finally loading..........

# /usr/bin/kwboot.orig -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
  5 % [......................................................................]
........
 95 % [......................................................................]
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]


U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   MVEBU_MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0 

Pogov4> printenv
arcNumber=3960
baudrate=115200
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm$load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
console=ttyS0,115200
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4
ethact=egiga0
ethaddr=00:3b:20:9c:11:44
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 2907/131068 bytes
Pogov4>

Please help how to proceed from this point.

Thank you...



Edited 1 time(s). Last edit at 12/18/2017 05:44PM by alphaprime.

alphaprime,

Quote

> U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01
> -0700)
> Pogoplug V4
>
> SoC: Kirkwood 88F6192_A1
> DRAM: 128 MiB
> WARNING: Caches not enabled
> NAND: 128 MiB
> MMC: MVEBU_MMC: 0
> *** Warning - bad CRC, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Net: egiga0
> Hit any key to stop autoboot: 0

Cool! It is unbricked now!


So now you can proceed and boot with the Debian rootfs. Follow the instruction in the 1st post to create a USB rootfs:
https://forum.doozan.com/read.php?2,12096

Scroll dow to section:

Quote

Updated 24 Jul 2017:

Basic Debian stretch Kirkwood rootfs for most Kirwood plugs:

- tarball size: 188M
- install size: 488M
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

md5:
bf3d29569943875df348fb5ca03b348c
sha256:
4ed5714fdb123cdb40e973f3d0754e91cd199b75a9874018f2b5dc9cfa8ae8bb

Since you are booting with the new u-boot using kwboot, you only need to do step 1 and 2. Use your Ubuntu spacerobotics box to create the USB rootfs..

Rember to follow the instruction very closely, and execute sync command before you umount the rootfs.

And boot the Pogo V4 with this new rootfs. After it booted, you will need to install new u-boot. However, let's get it booting consistently and post your result here, before worrying about new u-boot.

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



Edited 1 time(s). Last edit at 12/17/2017 11:05PM by bodhi.

Hi Bodhi,

I've follow step 1 & 2. There was below error after attaching my SD card to Pogo

loading envs from mmc 0 ...
** File not found /boot/uEnv.txt **
running scan_disk ...

Then I create my own /boot/uEnv.txt file

After loding again, then it says that having bad CRC

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   MVEBU_MMC: 0
*** Warning - bad CRC, using default environment

Below error appear due to uEnv bad CRC

root@debian:~/tmp# fw_printenv ethaddr
Warning: Bad CRC, using default environment
ethaddr=00:00:11:22:33:44

Please help to build uEnv file for PogoV4

Btw, I've flash u-boot with latest u-boot

But still having this error when boot using mtd0 NAND

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   MVEBU_MMC: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
## Error: "if_netconsole" not defined
## Error: "if_netconsole" not defined
## Error: "if_netconsole" not defined
## Error: "if_netconsole" not defined
## Error: "if_netconsole" not defined
Pogov4> printenv
arch=sandbox
baudrate=115200
board=sandbox
board_name=sandbox
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf
boot_net_pci_enum=pci enum
boot_net_usb_start=usb start
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_targets=host1 host0 
bootcmd_host0=setenv devnum 0; run host_boot
bootcmd_host1=setenv devnum 1; run host_boot
bootdelay=2
bootm_size=0x10000000
cpu=sandbox
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
eth1addr=00:00:11:22:33:45
eth3addr=00:00:11:22:33:46
eth5addr=00:00:11:22:33:47
ethact=egiga0
ethaddr=00:00:11:22:33:44
fdt_addr_r=0xc00000
host_boot=if host dev ${devnum}; then setenv devtype host; run scan_dev_for_boot_part; fi
ipaddr=192.168.1.117
kernel_addr_r=0x1000000
nc_ready=0
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
pxefile_addr_r=0x2000
ramdisk_addr_r=0x2000000
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scriptaddr=0x1000
serverip=192.168.1.2
stderr=serial
stdin=serial
stdout=serial
usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi

Environment size: 2349/131068 bytes
Pogov4>

Edited 3 time(s). Last edit at 12/19/2017 03:29AM by alphaprime.

Hi Bodhi,

Now my pogo boot with U-boot & Debian so far running normally on MMC drive.
Thank you for your support

I'll play a while with this, I'll ask again if I don't know how to solve it
I'm sorry if I disturb you

Thank you

alphaprime Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> Now my pogo boot with U-boot & Debian so far
> running normally on MMC drive.
> Thank you for your support
>
> I'll play a while with this, I'll ask again if I
> don't know how to solve it
> I'm sorry if I disturb you
>
> Thank you


Cool!

I have been very busy so I forgot respond to some posts. Glad you got it working:)

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