CloudEngine marketed different devices under the name “Pogoplug”, some of which even share the same outward appearance. This page is for the devices using the Oxnas/PLXtech SoC.
The “V3 Pro” version is marked “P01” or “P02” on the bottom, the non-“pro” “V3” version is marked “B01”, “B02”, “B03”, “B04”, “P21”, “P24”, or “P25”.
Devices marked “E02” share the same case but not the hardware, they can be found at their own target: Kirkwood Pogoplug E02
|Model||Version||Current Release||Firmware OpenWrt Install||Firmware OpenWrt Upgrade|
|Pogoplug V3||B0*, P2*||19.07.0||http://downloads.openwrt.org/releases/19.07.0/targets/oxnas/ox820/||http://downloads.openwrt.org/releases/19.07.0/targets/oxnas/ox820/openwrt-19.07.0-oxnas-ox820-cloudengines_pogoplug-series-3-squashfs-sysupgrade.tar|
|Pogoplug V3 Pro||P01, P02||19.07.0||http://downloads.openwrt.org/releases/19.07.0/targets/oxnas/ox820/||http://downloads.openwrt.org/releases/19.07.0/targets/oxnas/ox820/openwrt-19.07.0-oxnas-ox820-cloudengines_pogoplugpro-squashfs-sysupgrade.tar|
Support for the OXNAS Pogoplugs has been added with OpenWrt 15.05. OpenWrt 15.05 and LEDE 17.01 required a u-boot version more capable than the vendor u-boot that comes with the Pogoplug. This required a rather convoluted installation process, resulting in either loading a suitably capable u-boot from the less capable vendor u-boot (a “2nd stage u-boot”) or outright replacing the vendor u-boot (which is rather dangerous).
With 18.06, the OXNAS target has been overhauled, one of the results is that it can now be booted from the vendor u-boot, no additional or replacement u-boot required anymore. One of the consequences of those significant changes is that you cannot upgrade from an older version than 18.06 to 18.06 or later using sysupgrade. If you try to force it, you will render your device unable to boot, you will need to go through the installation process outlined below.
As of 2020-01-14, all versions of 18.06, 19.07 and snapshot contain a bug that prevents a proper boot after a reset. If you reset the device from OpenWrt it will hang at the subsequent boot and requires a physical power cycle.
In versions 18.06.0 through 18.06.2, pre-compiled “official” images did not contain a kernel image, resulting in an unbootable Pogoplug even if you followed the correct install process. Pre-built OpenWrt 18.06.0 to 18.06.2 images are broken and can not be used. This has been fixed in OpenWrt 18.06.3 and newer versions.
You will need the following:
prodepending on your Pogoplug hardware. For brevity of this guide, the files are only referenced by the last part of the filename)
Danger - live voltage!
A Pogoplug contains its own unenclosed power supply in the lower part of the case. When connected to power, parts inside the case are live at mains voltage and must be handled with extreme care!
Seriously, this could kill you if you're not careful. Please completely disconnect the Pogoplug from power before opening the case and working inside, and make really sure to not touch anything inside as long as the Pogoplug is powered.
Open the serial connection and power on your Pogoplug. Once you see
Hit any key to stop autoboot: … hit any key to stop autoboot. You will be on the vendor u-boot command line, prompting you with
Permanently change the bootloader's boot configuration to boot OpenWrt:
setenv bootcmd 'nboot 60500000 0 440000; bootm' saveenv
U-Boot expects to download files from a TFTP server located at the IP address configured in the U-Boot variable
serverip, and it will appear on the network with its own IP configured in “ipaddr”.
Set appropriate IP addresses for the server and the Pogoplug:
setenv serverip 192.168.1.2 setenv ipaddr 192.168.1.1
Set your PC's ethernet connection to the static address 192.168.1.2 and start the tftp server.
initramfs-uImage to uboot and start it:
tftp 64000000 initramfs-uImage bootm 64000000
OpenWrt will start up, but only in memory.
Contrary to other devices, in the OpenWrt build for the Pogoplug the ethernet interface is configured as DHCP. This may change in the future, but for now it is not quite ideal for our flashing process. Set it to a static IP using:
uci set network.lan.proto=static uci set network.lan.ipaddr=192.168.1.1 uci set network.lan.netmask=255.255.255.0 uci commit service network restart
and leave your PC's ethernet interface configured to the same address (192.168.1.2).
Using SCP applications like WinSCP, transfer the OpenWrt firmware image to OpenWrt's
/tmp directory, and flash it with sysupgrade.
xxxxxxxxxxx-squashfs-sysupgrade.tar file and flash it using:
The Pogoplug will reboot, and you should be able to observe it booting into your complete OpenWrt installation. Again, the default LAN configuration is DHCP, so either plug it into a router serving DHCP or, while you are still connected, change the network configuration to a static IP.
Transfer first the
squashfs-ubinized.bin image, and then install it by using
sysupgrade -F /tmp/squashfs-ubinized.bin
(This sysugprade step requires
This will create the necessary partitions on your Pogoplug, but this step will not flash the kernel yet. Once the Pogoplug reboots, we need to go through the process a second time.
Repeat “Step 2” above, but instead of
squashfs-ubinized.bin, transfer the
squashfs-sysupgrade.tar and flash it using:
-F necessary this time.)
This will finally write the kernel to flash. Your Pogoplug is now running OpenWrt.
Pogoplugs come with a serial header, populated with a Molex 70107 connector (as used with CD-ROM audio cables).
The settings for accessing the serial console are as follows:
Bits per second: 115200
Data bits: 8
Stop bits: 1
Flow control: None