Pogoplug E02 Dead after flash

[papoanaya]

Hello:

I have gone through the forums but I could not find this specific problem. At this juncture I am aware that I need to log into the console and see what is going on. Being that I have no access to the serial port available in this unit, it'll be a matter of time until I can go in and look into the problem. Hence, I rather post a message stating what it happened so others can be aware of it.

I attempted to install Arch Linux on a PogoPlug E02 (POGO_E02, Grey) following the directions described in the Arch Linux website. I already performed this procedure on another unit, hence I was expecting it to work without problems.

Well, problems, I got.

• Downloading and configuring the root disk was fine.
• Downloading and flashing the ROM was fine, no errors were seen after flashing completed.
• Reboot was performed and the unit did not boot. The front light never came on.
• The motherboard light and the ethernet port were on and activity was shown on the ethernet connection.
• After leaving the unit for about 15 minutes, the front light never came on.
• There was no connectivity available, ping was not working and the unit was not detected in the newtork using arp, AutoScan and Angry IP Scanner.
• Booting the unit with and without the root disk made no difference. My other unit reverts to the original internal disk when disconnected, this does not happen on the new one.

At this juncture I have to assume that the ROM upgrade did not work and I need to look at the console. Being that I have no console access at this moment I will have to wait until I get the required hardware to do so.

Any ideas are welcome, but from the looks of it the solution is to reflash the unit with a new ROM.

[hydro]

$this->bbcode_second_pass_quote('papoanaya', '
')Booting the unit with and without the root disk made no difference. My other unit reverts to the original internal disk when disconnected, this does not happen on the new one.

[papoanaya]

Well, if it boot or does not boot the stock firmware, I do not know. What I do not know is that on the other unit, I can access the internal drive after it reboots from disconnect. This unit has been running Arch without problems for a couple of years now.

The new one, well, needs to be reflashed. Time for me to explore the net and work on it.

Thanks for providing the link to the original flash ROM.

[hydro]

$this->bbcode_second_pass_quote('papoanaya', 'o')n the other unit, I can access the internal drive after it reboots from disconnect.

[papoanaya]

Hi:

With a bit of ingeunity and luck, I managed to get the console running. This is what it shows on the console:

$this->bbcode_second_pass_code('', '
SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... EHCI timed out on TD - token=0x80008d80

USB device not accepting new address (error=22)
2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

no USB devices available

no USB devices available

no USB devices available

no USB devices available
PogoE02>

')

It is not recognizing any of the USB devices, even though there are at least two, the internal drive and the external. Drive, however it complaints that it does not accept new addresses (?!).

So, what I have seen, I can reflash via tftp. I have not set up a tftp server since the mid 1990s, I hope that it is like riding a bicycle. .

[papoanaya]

Well this is a bit anticlimatic.

This booting image does detect thumbdrives (RAM based) but it does not detect USB hard drives as valid devices. I tried with two hard drive, a generic and a western digital, and they were not recognized. It stll does not fall back to the internal drives. At least I know what's going on. This is what happened after I inserted a thumbdrive.

$this->bbcode_second_pass_code('', '

# preamble omitted

(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 62 3944998 000c72fa-01 83
Attempting to boot from usb 0:1...
** File not found /boot/uEnv.txt **
Checking if uenvcmd is set ...
Running default loadzimage ...
** File not found /boot/zImage **
Running default loaduimage ...
** File not found /boot/uImage **

no USB devices available
')

The error at the end is no surprise being that the thumbdrive has no image, but booting was attempted by Uboot.

Even though this is a way to go, it's not exactly what I was looking for because I wanted to boot directly from a USB hard drive.

Ok, I can get the mtd0 image via nfs (I did not know that I had the option, I already have NFS setup), but I am unsure if this image needs to be flashed from 0 (replace the whole NAND drive) or from the rootfs address.
$this->bbcode_second_pass_code('', '
PogoE02> setenv ipaddr 192.168.10.6
PogoE02> setenv netmask 255.255.255.0
PogoE02> setenv serverip 192.168.10.15
PogoE02> setenv bootfile /opt/home/papo/uboot.mtd0.pinkpogo.original.kwb
PogoE02> nfs
Using egiga0 device
File transfer via NFS from server 192.168.10.15; our IP address is 192.168.10.6
Filename '/opt/home/papo/uboot.mtd0.pinkpogo.original.kwb'.
Load address: 0x810000
Loading: #################################################################
######################################
done
Bytes transferred = 524288 (80000 hex)
PogoE02>
')

So far, so good, but at this juncture I do not know where should I flash.

[papoanaya]

After a lot of thinking and finding a 4GB thumbdrive that I was not really using, I decided not to reflash the unit and go with the thumbdrive approach. It should work for what I need. I use the 1/2 Gig for data after performing the necessary adjustments. I also had enough excitement for a day.

Thanks for your help