[resolved] Bricked E02 - restoring with serial

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

[resolved] Bricked E02 - restoring with serial

Postby firefoxPL » Mon Feb 13, 2012 7:26 pm

Hi, I've purchased a second hand Pogo v2 Pink (POGO-E02), since the seller didn't know anything about the pogo he disclosed that the pogo might not by functional, but the price was cheaper than delivery of a new pogo itself therefore I've bought it.
After powering up the E02 flashes green for a short while and then starts to flash yellow/amber, also it doesn't get any ip address therefore I assume it doesn't past uBoot. Tomorrow I'll hook up a serial cable to it at work and see what happens there, but I wanted to ask for some information how to reflash/setup a Arch disto using a usb flash drive, potentially bricked (but hopefully not dead yet Pogo) and a serial cable, from what I've searched there used to be some materials but as someone mentioned in this post viewtopic.php?f=23&t=353&p=11160&hilit=reflashing#p11160 the relevant pages don't exist anymore on the archilinuxarm.org page.
If anyone could point me into direction I should manage to get it up and running in no time :)
All the help much appreciated.
Last edited by firefoxPL on Tue Feb 14, 2012 5:20 pm, edited 2 times in total.
Pogo-P24 (new Pogoplug Classic) - ALARM on SATA (mediatomb, netatalk, avahi, time machine, swap, openvpn)
Pogo-E02 (v2 Pink) - ALARM on USB (netatalk, avahi, cryptodev-linux, getting ready for L2TP)
firefoxPL
 
Posts: 65
Joined: Thu Dec 08, 2011 1:49 pm

Re: Bricked E02 - restoring with serial

Postby BinaryJay » Mon Feb 13, 2012 9:49 pm

I see. "didn't know anything about the pogo" translates into "i know it's broken but want to sell it anyway and give you false hope that perhaps I'm just dumb and it works fine".

I always laugh when I see something underpriced for sale with descriptions like this.
BinaryJay
 
Posts: 87
Joined: Mon Dec 06, 2010 10:27 pm

Re: Bricked E02 - restoring with serial

Postby firefoxPL » Mon Feb 13, 2012 10:05 pm

Basically you got the translation right :)
I was well aware that it might end up like this, but for the price I didn't actually care, I have all the tools and time to try and restore it to proper functioning and I can even find some use for a second device - purely as a hobby.
Only thing I need is some guidance when it comes to uBoot and installing Arch - maybe booting from tftp will work and I will be able to go from there. I design parts of CPUs not program them therefore I didn't yet have to get into uBoot (we have whole lot of programmers to do that ;))
Pogo-P24 (new Pogoplug Classic) - ALARM on SATA (mediatomb, netatalk, avahi, time machine, swap, openvpn)
Pogo-E02 (v2 Pink) - ALARM on USB (netatalk, avahi, cryptodev-linux, getting ready for L2TP)
firefoxPL
 
Posts: 65
Joined: Thu Dec 08, 2011 1:49 pm

Re: Bricked E02 - restoring with serial

Postby firefoxPL » Tue Feb 14, 2012 8:17 am

Looks like I might have found something on debian forum (http://forum.doozan.com/) in Rescue and uBoot sections, I'll manage to get it up and running I'll post my steps maybe someone will have a similar problem (with theirs or second hand devices) in future.
In any case if anyone had a similar experience and was successful in the past I definitely wouldn't mind a word of advice :)
Pogo-P24 (new Pogoplug Classic) - ALARM on SATA (mediatomb, netatalk, avahi, time machine, swap, openvpn)
Pogo-E02 (v2 Pink) - ALARM on USB (netatalk, avahi, cryptodev-linux, getting ready for L2TP)
firefoxPL
 
Posts: 65
Joined: Thu Dec 08, 2011 1:49 pm

Re: Bricked E02 - restoring with serial

Postby firefoxPL » Tue Feb 14, 2012 11:13 am

Hi, I've managed to hook up a serial cable to my pogo, and as I've suspected I get bad CRC error and CE prompt:
$this->bbcode_second_pass_code('', '
U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Flash: 0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV2

Streaming disabled
Write allocate disabled

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x100000, size 0x200000

Reading data from 0x2ff800 -- 100% complete.
2097152 bytes read: OK
## Booting image at 00800000 ...
Image Name: Linux-2.6.22.18
Created: 2009-08-10 19:57:40 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1977716 Bytes = 1.9 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... Bad Data CRC
CE>>
')

I found what seems to be a solution for me but originally ment for Dockstar. From what I've read the dockstar is fairly similar to Pogo v2, so I belive that if I use:
- ce_kernel_v2.0.img
instead of
- ce_kernel_redstone_v63.img
from http://archlinuxarm.org/mirror/ce/
to boot from tftp I should be ok, am I right?
Pogo-P24 (new Pogoplug Classic) - ALARM on SATA (mediatomb, netatalk, avahi, time machine, swap, openvpn)
Pogo-E02 (v2 Pink) - ALARM on USB (netatalk, avahi, cryptodev-linux, getting ready for L2TP)
firefoxPL
 
Posts: 65
Joined: Thu Dec 08, 2011 1:49 pm

Re: Bricked E02 - restoring with serial

Postby Philoo » Tue Feb 14, 2012 11:34 am

well I guess your next move is to untar an armv5 rootfs to a freshly ext2 formatted flash drive, plug it to the device, restart.
Interrupt the autoboot process when given the option.
in the uboot prompt check (help) for extload or fatload command, that would allow you to load a kernel and an initrd from flash drive rather than from nand also check the environment variables as it *might* (don't get high hopes) be setup to boot from usb.

check in the script http://jeff.doozan.com/debian/uboot/ins ... ot_mtd0.sh at what address the kernel needs to be loaded

if or once you've got that a bootm or boot 0x<address> will fire up your linux environment where you should be able to reflash Jeff Doozan's improved firmware

if you're lucky you might find that it's just a matter of uboot environment variables that need fixing (setenv , once you've got the right mix saveenv makes it persistent through reboots)
Philoo
 
Posts: 102
Joined: Wed Aug 10, 2011 9:20 pm

Re: Bricked E02 - restoring with serial

Postby firefoxPL » Tue Feb 14, 2012 12:11 pm

Thank You I'll try that later today and post my result, hopefully everything will work out just fine.
Pogo-P24 (new Pogoplug Classic) - ALARM on SATA (mediatomb, netatalk, avahi, time machine, swap, openvpn)
Pogo-E02 (v2 Pink) - ALARM on USB (netatalk, avahi, cryptodev-linux, getting ready for L2TP)
firefoxPL
 
Posts: 65
Joined: Thu Dec 08, 2011 1:49 pm

Re: Bricked E02 - restoring with serial

Postby WarheadsSE » Tue Feb 14, 2012 1:26 pm

Looks to me like the CE kernel image in NAND got screwy, and that is all that is needed to be fixed.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Bricked E02 - restoring with serial

Postby firefoxPL » Tue Feb 14, 2012 2:25 pm

@WarheadsSE so just to confirm, to reflash NAND I could do something like this:
$this->bbcode_second_pass_code('', '
setenv ipaddr <some_pogo_ip>
setenv serverip <tftp_server_ip>
nand erase 0x100000 0x300000
tftp 0x800000 ce_kernel_v2.0.img
nand write.e 0x800000 0x100000 0x1e30f0
tftp 0x1000000 ce_ramdisk_v2.0b.img.gz
setenv bootargs $(console) root=/dev/mtdblock2 initrd=0x1000000,0xb39a59
bootm 0x800000
')
and I should have a stock Pogo v2?

edit: this is current uBoot environment:
$this->bbcode_second_pass_code('', '
CE>> printenv
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
serverip=169.254.254.252
ipaddr=169.254.254.253
ethaddr=00:25:31:00:57:AA
cesvcid=<i've erased this for the forum>
ceboardver=PPV2
bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root);bootm 0x800000
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

Environment size: 786/131068 bytes
')
Pogo-P24 (new Pogoplug Classic) - ALARM on SATA (mediatomb, netatalk, avahi, time machine, swap, openvpn)
Pogo-E02 (v2 Pink) - ALARM on USB (netatalk, avahi, cryptodev-linux, getting ready for L2TP)
firefoxPL
 
Posts: 65
Joined: Thu Dec 08, 2011 1:49 pm

Re: Bricked E02 - restoring with serial

Postby firefoxPL » Tue Feb 14, 2012 4:05 pm

Hi, I went ahead and flashed only kernel image, didn't touch ramdisk, and Pogo is alive and well, SSH is also alive with default CE password, now I just need to instal ALARM according to normal install guide. For me topic solved and ready to be closed. Thank You all for help.
Pogo-P24 (new Pogoplug Classic) - ALARM on SATA (mediatomb, netatalk, avahi, time machine, swap, openvpn)
Pogo-E02 (v2 Pink) - ALARM on USB (netatalk, avahi, cryptodev-linux, getting ready for L2TP)
firefoxPL
 
Posts: 65
Joined: Thu Dec 08, 2011 1:49 pm

Next

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 4 guests