Cloud Engines Pogoplug v4 A3 (Series 4)

From TechInfoDepot
Jump to navigationJump to search
multiple revisions of this device, use caution
NAS
Homepage Product page
WikiDevi.wi-cat.ru Cloud Engines Pogoplug v4 A3 (Series 4)
3rd Party Firmware
dd-wrt Status Unknown
OpenWrt Supported
Tomato any flavor Incompatible
Gargoyle Status Unknown
Platform
BrandModelRev Cloud Engines Pogoplug v4 A3
Type NAS
CPU1 checkY Marvell 88F6192
CPU1 Type ARMv5 Feroceon core
CPU1 Speed 800 MHz
Flash1 Chip SK hynix H27U1G8F2BTR
Flash1 Size 128 MiB 134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br /> (NAND)
RAM1 Size 128 MiB 134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />
RAM1 Chip SK hynix H5PS1G63EFR
ETH chip1 Marvell 88F6192
ETH chip2 Marvell 88E1116R
Ethernet Port Count 1-1GbE-LAN
Wired Standard IEEE 802.3i/3u/3ab

Ethernet OUI: 00:25:31 (4 E, 1 W)

Stock bootloader U-Boot 1.1.4 Cloud Engines
Stock FW OS Linux 2.6.31.8 KW LSP release 5.1.3
Expansion IF types USB 2.0, USB 3.0, SATA, SDHC
USB ports 3
SD/MMC Slots 1
SATA Ports 1
USB Hub Compatible Untested
Power 12 VDC, 2 A
Connector type barrel
Serial Port (UART) yes, 3.3V TTL, 4-pad header (115200 8N1), J11
JTAG Port yes, 6-pin header, J17

Additional chips
4.5V/18V Synchronous Step-Down Three Buck Switcher;Texas Instruments;TPS65251;;1;
30V, 7A N-Channel MOSFET;Fairchild Semiconductor;FDS8984;;1;
5V/12V Synchronous Buck PWM DC/DC Controller;Richtek;RT8105;;1;
USB 3.0 / xHCI Host Controller;Fresco Logic;FL1009;;1;
2A Linear Power, Low Dropout Regulator;uPI Semiconductor;uP0105;;1;

Other
3rd Party Firmware Support Arch Linux ARM • (List | DLs)
, OpenWrt • (List | Dev | DLs)
Retail
Availability common
(Est.) initial retail price (in USD): $99.99
UPC 850877002320
(UPC DB, On eBay)
ASIN B006I5MKZY
Country of manuf China
 CPU1 brandFLA1RAM1
Cloud Engines Pogoplug Classic (POGO-B01)PLX Technology128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />
Cloud Engines Pogoplug E01Marvell512 MiB536,870,912 B <br />4,194,304 Kib <br />524,288 KiB <br />4,096 Mib <br />0.5 GiB <br />256 MiB268,435,456 B <br />2,097,152 Kib <br />262,144 KiB <br />2,048 Mib <br />0.25 GiB <br />
Cloud Engines Pogoplug E02Marvell128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />256 MiB268,435,456 B <br />2,097,152 Kib <br />262,144 KiB <br />2,048 Mib <br />0.25 GiB <br />
Cloud Engines Pogoplug Pro (POGO-P01)PLX Technology128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />
Cloud Engines Pogoplug V3 (POGO-P21)PLX Technology128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />
Cloud Engines Pogoplug v4 A1 (Mobile)Marvell128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />
Cloud Engines Pogoplug v4 A3 (Series 4)Marvell128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />128 MiB134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />

For a list of all currently documented Marvell chipsets with specifications, see Marvell.

Overview

Fresco Logic FL1009 PCI Express to USB 3.0 host controller

provides 2x USB 3.0 ports, remaining port is USB 2.0.

Links of Interest

Arch Arm Linux alternate firmware

Flashing

Flashing OpenWrt

Target: kirkwood
Subtarget: generic
Package architecture: arm_xscale
Supported Since Commit
Support started version: 18.06.0
Current supported version: 24.10.4
WLAN Hardware: none
USB SATA Comment: Serial, see devicepage
Installation method(s):
serial access + bootloader replacement required
Recovery method(s):
see git-commit
Recovery Comment:
serial + kwboot
Comment:
The "eject" button on the back is used as "reset" button

This device supports the (linux-only) kwboot tool to send a new uboot over serial console, so it is easy to unbrick in case the uboot is erased and the device won't boot.

-----
Install instructions:
-----
Since it's not possible to get ssh access to these
devices, the only way to take control is to
solder pins to get TTL serial access.

Case can be opened by removing screws beneath two rubber
feet at back of device, then lifting while prying the
sides of the upper part out to unhook a latch on each
side about 2/3rds of the way toward the front.

Serial connection pins are those labeled "J11", left
of SD as you face SD opening.
Pins are (from left to right, i.e. the first in the list
is the nearest to the SD slot) GND, Rx, Tx.
Do not connect +V pin if you use a USB (self-powered)
TTL-to-USB dongle. Any USB TTL-to-USB converter will work.
Baud rate is 115200, parity "none", databits "8",
flow control "none".

Stock uboot is unable to read ubi partitions (nor usb)
so we will replace it first with our uboot.

Start a TFTP server at IP address 169.254.254.254, and
place the uboot.kwb file in the folder of the server.

Start the serial session and then power up the device.

As soon as you see text on the serial start pressing random
letter keys to stop the boot process.

If you see something like the following line you can proceed:

CE>>

Otherwise if text is still scrolling by you missed the
opportunity, pull the plug and try again.

write

printenv ethaddr

The uboot will write something like this:

ethaddr=00:50:43:00:02:02

This is the device's MAC address, also present in the sticker
under the device.

Write this down as we will need to add it in the
new uboot configuration.

Use the following commands to load the new uboot:

tftp 0x20000 u-boot.kwb

If the uboot confirms that the transfer was successful,
then you can write it to flash with the following commands:

nand erase 0 0x200000
nand write 0x20000 0 0x1c0000

if after the last command the uboot wrote
"xxxx bytes written: OK"
then it was written correctly and we can proceed.

If it did not go well, try again or ask assistence in forums.
Shutting down or rebooting at this time will brick
the device, to unbrick it you will need to use the kwboot
tool from a Linux PC or Virtual Machine.

Now write:

reset

and press enter, the device will reboot and you should see
again text scrolling by.
Press a random key to stop it, and now you should see

pogoplugv4>

We now add the MAC address back, write:

setenv ethaddr '00:50:43:00:02:02'

Confirm that the uboot has understood by writing

printenv ethaddr

If all looks ok, save the setting with

saveenv

At this point the uboot is configured, and we only need to load
the firmware in the flash memory.

Follow the steps below in "Firmware recovery procedure".

----
Firmware recovery procedure
----
The new uboot allows easy recovery from a bad firmware upgrade
where you can't access the device anymore over ssh or luci.

Take a USB flash drive formatted as FAT32, and copy the
initramfs image file in it (it will have "initramfs" in the
file name), then rename it as "initramfs.bin".

Insert the USB drive in the USB 2.0 port of the pogoplug
(the port at the top).

Power up the device, and wait for it to finish booting.

The uboot should find and load the "initramfs.bin"
from usb and if you are connected with serial you should
see the linux kernel boot log (text scrolling by).
Once it is done, press Enter and you will be greeted by
the OpenWRT banner.

If you were not connected with serial just wait a bit and,
you will be able to access it with ssh or luci web interface
(once you find its IP).

The recovery "initramfs" images are run from RAM, so you will
have to do a normal sysupgrade (firmware upgrade) to write
a firmware image to flash memory.