Pogoplug v4 potentially bricked

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

Re: Pogoplug v4 potentially bricked

Postby beyondbuxton » Fri Oct 26, 2012 3:17 am

Freaqy:

I'm also waiting on the usb-ttl adapter- I expect it in the next few days. I figured I'd do a brief write up on what I bought, how I connected it and how I repaired the damage I'd done to the filesystem.

Good luck getting the solder out of the serial port pin holes on the board! <g>

BB
beyondbuxton
 
Posts: 20
Joined: Tue Oct 16, 2012 7:08 pm

Re: Pogoplug v4 potentially bricked

Postby FreaqyGeeq » Fri Oct 26, 2012 3:26 am

$this->bbcode_second_pass_quote('beyondbuxton', 'G')ood luck getting the solder out of the serial port pin holes on the board! <g>


I'm in an ever-so-slightly better situation than you—turns out the Classic V3 (aka B01), which I have, has a proper serial header on-board: http://www.flickr.com/photos/45932617@N06/6703823181 (this is not my photo, by the way).

Hopefully I don't have to solder a thing and can just plug in the pins. But I'm really interested to see what you get up to as well, and the restoration procedure, software-wise, will likely be the same for both models.

My USB>TTL probably won't turn up until the end of next week for me, so you're certainly going to be in the lead here!

Cheers beyondbuxton!
FreaqyGeeq
 
Posts: 23
Joined: Mon Oct 22, 2012 9:29 am

Re: Pogoplug v4 potentially bricked

Postby WarheadsSE » Fri Oct 26, 2012 5:48 pm

Get yourself a 4-pin JST for the V3/B03/Pro/P21 connector. :) $1.50 at sparkfun.

https://plus.google.com/photos/11697247 ... 6721880769
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Pogoplug v4 potentially bricked

Postby FreaqyGeeq » Sat Oct 27, 2012 1:31 am

$this->bbcode_second_pass_quote('WarheadsSE', 'G')et yourself a 4-pin JST for the V3/B03/Pro/P21 connector. :) $1.50 at sparkfun.

https://plus.google.com/photos/11697247 ... 6721880769


Nice one WarheadsSE, cheers... oh, and look at that eSATA mod! Wow!! :D
FreaqyGeeq
 
Posts: 23
Joined: Mon Oct 22, 2012 9:29 am

Re: Pogoplug v4 potentially bricked

Postby beyondbuxton » Fri Nov 02, 2012 3:02 pm

$this->bbcode_second_pass_quote('FreaqyGeeq', '
')My USB>TTL probably won't turn up until the end of next week for me, so you're certainly going to be in the lead here!


I think my order fell off the slow boat. Is impatience for a part coming from the other side of the planet a tad ridiculous?
beyondbuxton
 
Posts: 20
Joined: Tue Oct 16, 2012 7:08 pm
Top

Re: Pogoplug v4 potentially bricked

Postby karog » Fri Nov 02, 2012 5:27 pm

$this->bbcode_second_pass_quote('beyondbuxton', '')$this->bbcode_second_pass_quote('FreaqyGeeq', '
')My USB>TTL probably won't turn up until the end of next week for me, so you're certainly going to be in the lead here!


I think my order fell off the slow boat. Is impatience for a part coming from the other side of the planet a tad ridiculous?

My USB-TTL from Hong Kong took 31 days from ship date to arrive on US east coast. But it works great and was cheap: $2.64 w/free shipping. I still can't believe free shipping from Hong Kong on such a cheap item even if it does take a month to arrive.
karog
 
Posts: 305
Joined: Thu Jan 05, 2012 7:55 pm
Top

Re: Pogoplug v4 potentially bricked

Postby moonman » Fri Nov 02, 2012 8:32 pm

Mine took about 1 month and 1 week to arrive. When it arrived I already forgot I ordered one :) and already made one myself from USB to serial adapter that I already had before. It would take less time if you ordered one from US, but it would cost you x10 what you paid and they probably just resell this stuff and order it from HongKong anyway.
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: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Pogoplug v4 potentially bricked

Postby FreaqyGeeq » Thu Nov 08, 2012 1:24 pm

Okay, well I'm back again. I have successfully connected via serial to my V3, and am now looking at a CE>> prompt. It would appear that I actually need to reflash to stock in order to recover from the changes I've made to the /etc/init.d/rcS which prevent it from booting. At least uBoot is looking good, though.

This guide looks like the one to refer to: viewtopic.php?t=1323

The only question is... which images should I be using for the V3? Are the Pro images from here the ones I should be using?
http://archlinuxarm.org/mirror/ce/

Any guidance would be greatly appreciated. Thanks a lot guys!
FreaqyGeeq
 
Posts: 23
Joined: Mon Oct 22, 2012 9:29 am

Re: Pogoplug v4 potentially bricked

Postby WarheadsSE » Thu Nov 08, 2012 3:34 pm

I believe that they will work. You will want to make sure the process is correct before loading anything to NAND.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Pogoplug v4 potentially bricked

Postby FreaqyGeeq » Thu Nov 08, 2012 11:10 pm

Hi WarheadsSe, thanks once again for the reply.

I've done a printenv, and this is what it displayed:

$this->bbcode_second_pass_code('', 'CE>> printenv
bootcmd=run boot_nand
bootdelay=2
baudrate=115200
autoload=n
netmask=255.255.0.0
bootfile="uImage"
kernflmode=s
load_nand=nboot 60500000 0 200000
load_nand2=nboot 60500000 0 800000
boot=bootm 60500000
boot_nand=run load_nand boot || run load_nand2 boot
ethaddr=00.00.00.00.00.00
cesvcid=0000000000000000000000000000
ceboardver=PPV3
serverip=192.168.1.20
ipaddr=192.168.1.122
stdin=serial
stdout=serial
stderr=serial
bootargs=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes

Environment size: 568/131068 bytes')

(Note that I've zero'd out the ethaddr and cesvcid for privacy.)

When referring to the described reflashing method here: http://archlinuxarm.org/forum/viewtopic.php?t=1323, can you see anything in my setup that I need to be aware of, such as the memory address locations for the NAND?

I'm still very much a *nix noob, but I'm slowly coming to grips with it and pushing through. I really appreciate your help, and the assistance of the ArchLinuxARM community here—you guys are great, thank you!
FreaqyGeeq
 
Posts: 23
Joined: Mon Oct 22, 2012 9:29 am

PreviousNext

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 13 guests