PogoPlug E02 doesn't boot

It's been a long time since I used Pogoplug, so I wanted to reinstall everything from scratch to update it. I just updated my uBoot, which was a mistake. I think I bricked it. When it boots, I don't get the front light. Tell me from the output if it's bad. I followed all the steps, and that's the only step that didn't give me full writing data. I followed everything else to the letter but I didn't set up rescue. Already rebooted. Do you think I can still fix it with USB to TTL, or would I need to program the CPU directly, Marvell 88F6281. serverip=192.168.65.255 is incorrect, I don't know if that causing a problem.
Also, I just noticed that might be incorrect as well usb_scan_1=usb=0:2=dev=sda1

rescue:/mnt/tmp# flash_erase /dev/mtd0 0 4
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000 done
rescue:/mnt/tmp# nandwrite /dev/mtd0 uboot.2017.07-tld-1.pogo_e02.mtd0.kwb
Writing data to block 0 at offset 0x0

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_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_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
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:04:85:C5
arcNumber=2097
usb_rootfstype=ext3
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_scan_list=1 2 3 4
usb_scan_2=usb=1:1 dev=sdb1
usb_custom_params=zswap.enabled=1
rescue_installed=1
serverip=192.168.65.255
usb_scan_1=usb=0:2=dev=sda1

Edited 6 time(s). Last edit at 05/01/2025 03:43AM by Almaz.

Almaz,

>

> rescue:/mnt/tmp# flash_erase /dev/mtd0 0 4
> Erase Total 4 Units
> Performing Flash Erase of length 131072 at offset
> 0x60000 done
> rescue:/mnt/tmp# nandwrite /dev/mtd0
> uboot.2017.07-tld-1.pogo_e02.mtd0.kwb
> Writing data to block 0 at offset 0x0
> 
>

Looks bad. Looks like it stopped here because of a bad block.

> Already rebooted.

You should not reboot when the behavior is not normal.

> serverip=192.168.65.255 is incorrect, I don't know
> if that causing a problem.
> Also, I just noticed that might be incorrect as
> well usb_scan_1=usb=0:2=dev=sda1

If the serverip is wrong, netconsole would fail to start, but it should not stop the booting process.

> Do you think I can still fix it with
> USB to TTL

This box BootROM does not work with kwboot. So it cannot be rescued with UART booting.

I would still connect serial console just to observe the boot log, if anything coming out of the port. You will need to open the case anyway.

If nothing comes out of serial console, your next best step is using JTAG. See here:

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

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