Totally confused with bricked Pogoplug Pro

This forum is for all other ARMv5 devices

Totally confused with bricked Pogoplug Pro

Postby killer666 » Mon Apr 01, 2013 2:53 pm

Hi All,

I'm really confuesd about my Pogoplug Pro behaviour, so I'm currently not sure on which point of "brickness" I'm currently at. I hope you can help me getting the Pogoplug run again.

After receivin my Pogoplug I decided to have it run an alternative firmware then the original. So Idecided to run ArchLinux on it.
Before I startet I made a flash dump of my Pogoplug with a script I found on the net - its name was something like dumpflash or so. The output of the script were the following files:

$this->bbcode_second_pass_code('', 'Pogoplug Flash Dump
│ .ceid
│ mtd0
│ mtd0.oob
│ mtd1
│ mtd1.oob
│ mtd2
│ mtd2.oob

└───.cedata
ceacct
cedb
cefoldersync')

After running the ArchLinux for a while I decided to give the original fimrware one more try. So I started to reestore the dumped Flash Images back to the mtdx partitions. The trouble began ...

My Pogoplug stopped working. I had the situation the front LED flashes and then turnes off. I read about surviveing the Pogoplug with a SATA disk and started to tryout. Nothing changed in the behaveiour. Next step was to build a serial cable.
After I got my own running cable I started reveiving the Pogoplugwith howtos like this: viewtopic.php?f=29&t=1203
Looks my problems get more worse ...
My current situation is the Pogoplug doesn't give any output if the SATA disk isn't connected.
If the SATA disk is connected I got the following output:

$this->bbcode_second_pass_code('', 'Stage-1 Bootloader Mon Nov 14 22:36:34 EST 2011
Attempting to set PLLA to 850MHz ...
plla_ctrl0 : 0x0000020A
plla_ctrl1 : 0x00330000
plla_ctrl2 : 0x0065008B
plla_ctrl3 : 0x000000F1
PLLA Set

Setup memory, testing
Reading disk 0, Image 0
Sector : 0x0000009A
Hdr len: 0x0001FB34
Hdr CRC: 0x2229BDCD
OK
Initialising disks
SATA PHY not ready for device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: FUJITSU MHY2040BH Firm: 0000000B Ser#: K400T8828TU6
Type: Hard Disk
Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)
Device 1: not available
Environment successfully read from disk 0 primary image


U-Boot 1.1.2 (Dec 31 2011 - 15:24:45)

U-Boot code: 60E00000 -> 60E1FB34 BSS: -> 60E5435C
RAM Configuration:
Bank #0: 60000000 128 MB
SRAM Configuration:
64KB at 0x50000000
NAND:128 MiB
In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value

IDE read: device 0 block # 288, count 1 ... 1 blocks read: OK
Hit any key to stop autoboot: 0
## Error: "boot_nand" not defined
$
')

Could anybody give me some hints how to get the original or ArchLinux running again on the system?
I'd love to hear some advice from the experts.
Thank you in advance.

Regards,
killer
killer666
 
Posts: 4
Joined: Mon Apr 01, 2013 2:38 pm

Re: Totally confused with bricked Pogoplug Pro

Postby killer666 » Sat Apr 06, 2013 12:42 pm

Could nobody help me? :?
Should I supply more information?
Just tell me which command output you'll need ...

killer666
killer666
 
Posts: 4
Joined: Mon Apr 01, 2013 2:38 pm

Re: Totally confused with bricked Pogoplug Pro

Postby pepedog » Sat Apr 06, 2013 2:52 pm

You are going to have to do this
viewtopic.php?f=29&t=2146
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Totally confused with bricked Pogoplug Pro

Postby killer666 » Tue Apr 09, 2013 7:04 pm

$this->bbcode_second_pass_quote('pepedog', 'Y')ou are going to have to do this
viewtopic.php?f=29&t=2146

Thank you for your reply. I followed the steps described in the linked post, but I result at the same error messages.
These are the messages from serial console when I boot from the prepared SATA-disk.
$this->bbcode_second_pass_code('', 'Stage-1 Bootloader Mon Nov 14 22:15:13 EST 2011
Attempting to set PLLA to 700MHz ...
plla_ctrl0 : 0x0000000A
plla_ctrl1 : 0x000E0000
plla_ctrl2 : 0x001B01A0
plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading disk 0, Image 0
Sector : 0x0000009A
Hdr len: 0x0001FB34
Hdr CRC: 0x2229BDCD
OK
Initialising disks
SATA PHY not ready for device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: FUJITSU MHY2040BH Firm: 0000000B Ser#: K400T8828TU6
Type: Hard Disk
Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)
Device 1: not available
Environment successfully read from disk 0 primary image


U-Boot 1.1.2 (Dec 31 2011 - 15:24:45)

U-Boot code: 60E00000 -> 60E1FB34 BSS: -> 60E5435C
RAM Configuration:
Bank #0: 60000000 128 MB
SRAM Configuration:
64KB at 0x50000000
NAND:128 MiB
In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value

IDE read: device 0 block # 288, count 1 ... 1 blocks read: OK
Hit any key to stop autoboot: 0
## Error: "boot_nand" not defined
$
')

Looks like the SATA drive is found, but it doesn't boot from it - correct?
killer666
 
Posts: 4
Joined: Mon Apr 01, 2013 2:38 pm

Re: Totally confused with bricked Pogoplug Pro

Postby killer666 » Wed Apr 17, 2013 4:52 pm

I'm searched the web on more time for a solution of my problem.
My current thought is I got the wrong parameters in printenv, thats why the error
$this->bbcode_second_pass_code('', '## Error: "boot_nand" not defined')
appears all the time. Correct?

Could somebody provide a default printenv output, or either a printenv output that should work on my pogoplug?
killer666
 
Posts: 4
Joined: Mon Apr 01, 2013 2:38 pm

Re: Totally confused with bricked Pogoplug Pro

Postby Geoff » Wed Apr 17, 2013 9:43 pm

I was just asking WarheadsSE about it. Unless you futzed with the uboot env on the SATA, which I'm sure you didn't, it's hard to imagine what happened. The only thing I can think of is that maybe you didn't set up the first partition starting at 2048 (assuming 512-byte sectors). If that was wrong, the kernel might have been written over the uboot env.

Edit: WarheadsSE says there's no "boot_nand" variable in the SATA uboot setup, so it must be trying in some bizarre way to access the uboot variables in NAND. He suggested using dd to zero out the contents of the drive and then start over, create a new partition table, etc. I would suggest spinning up the drive before powering up the pogo.
Last edited by Geoff on Thu Apr 18, 2013 12:09 am, edited 1 time in total.
Geoff
 
Posts: 231
Joined: Wed Mar 09, 2011 5:14 pm

Re: Totally confused with bricked Pogoplug Pro

Postby Socaltom » Wed Apr 17, 2013 11:06 pm

I tried four hours to get the direct sata boot to work. I finally got it to work on a 250g drive, but never on my 1TB drive.
It seems everything has to be just so for it to work especially the dos compatible partition table.
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side


Return to Community Supported

Who is online

Users browsing this forum: No registered users and 8 guests