PogoPlug P21/v3 Unable to Boot after U-Boot Update

Hey folks,

New to the forums here, so forgive my ignorance with what I'm doing with my PogoPlug.

Long story short, I've got a box that has the 2013.10-tld-4 U-Boot installed (seems I upgraded it properly at the time), but I believe due to a number of factors that went wrong with everything thereafter (U-Boot envs, amongst others), I can't get the thing to boot.

Initially, I'd extracted a Debian rootfs tar to a flash drive and I'd left this thing on for days with it rebooting itself. The box would start with a solid green light, then flashing green, then solid, then flashing amber and reboot. I've been able to get the box to at least load the kernel on the drive (on it's own now), but it's not going any further.

I'm using a cheapo BTE13-009 (CH340G clone) USB to TTL converter and it's receiving output from the PP just fine, but I'm unable to transmit (using PuTTy, all settings right that I can tell) so it won't accept any keyboard entry. Drivers are the latest I can find for the board, and the board itself has a blue LED that shows when it's transmitting to the PP, but no response from it (for example, when autoboot runs, I can't interrupt).

I've checked all my connections, and I've rebooted the box multiple times, and the output is the same every time as per what's below. Any guidance available would be most appreciated.

Also, I have Windows 7, Windows 10, and Linux Mint to work with for OSes (and possibly more linux flavors via VM).

Quote

U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
(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
4102704 bytes read in 354 ms (11.1 MiB/s)
1953812 bytes read in 253 ms (7.4 MiB/s)
7029 bytes read in 205 ms (33.2 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:16:44 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4102640 Bytes = 3.9 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:18:53 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 67c4b000, end 67e27fd4 ... OK
Loading Device Tree to 67c46000, end 67c4ab74 ... OK

Led: GREEN

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Wrecktify,

>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the
> kernel."]

It seems your u-boot envs are messed up. Connect serial console and power up the Pogo V3. Interrupt serial console at countdown and

printenv

Please post the entire serial console log here.

----
Update:

Quote

I'm using a cheapo BTE13-009 (CH340G clone) USB to TTL converter and it's receiving output from the PP just fine, but I'm unable to transmit (using PuTTy, all settings right that I can tell) so it won't accept any keyboard entry. Drivers are the latest I can find for the board, and the board itself has a blue LED that shows when it's transmitting to the PP, but no response from it (for example, when autoboot runs, I can't interrupt).

It should accept input if the connection is correct. Check the Pogo serial header wire RX and your serial connverter TX.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 01/17/2017 11:00PM by bodhi.

I'll double check my wiring, but I am at least getting data back from the PP, so I'd assume GND and RX on the converter match up to GND and RX on the PP, may just be a loose wire for RX on the PP to TX on the converter. If I can sort that out, I'll get you the envs so we can figure out what's going on. That's been my suspicion, that something got mucked up with them.

Thanks in advance, bodhi.

bodhi Wrote:
-------------------------------------------------------
> It should accept input if the connection is
> correct. Check the Pogo serial header wire RX and
> your serial connverter TX.

So, I've played and played with this thing, such as swapping wiring out and trying a different PC and different terminal emulation software, and I cannot get transmit to work going to the PP. I'm still receiving just fine via terminal, but transmits aren't being picked up by the PP, so I can't interrupt autoboot. I'm not sure if it's my serial converter or the PP, or something I'm doing wrong. I've got the converter configured at a 115200 baud rate, 8 bit data 1 bit stop, no parity or flow control, and can't get anything out of it.

Anybody see anything I'm doing wrong, or maybe I just have a bad converter board somehow. Just odd how I can't seem to find anybody else who's had this particular problem.

Edit:
PP -> Converter
GND -> GND
RX -> TX
TX -> RX



Edited 1 time(s). Last edit at 01/18/2017 09:34AM by Wrecktify.

I think you can try from the most simple one first:

1 Use a new flash drive or usb hard drive.
2 Make a new rootfs on the new usb drive
3 Try to boot with the new drive.


USB flash drive is not reliable. After a few years (maybe one or two, or longer), it will die... and if you format it, you can't see any error!

USB hard drive is much better.

Since you can get

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


I think you simply got a bad rootfs / (maybe due to bad usb drive)



Edited 1 time(s). Last edit at 01/18/2017 10:00AM by daviddyer.

daviddyer Wrote:
-------------------------------------------------------
> I think you can try from the most simple one
> first:
>
> 1 Use a new flash drive or usb hard drive.
> 2 Make a new rootfs on the new usb drive
> 3 Try to boot with the new drive.
>
>
> USB flash drive is not reliable. After a few years
> (maybe one or two, or longer), it will die... and
> if you format it, you can't see any error!
>
> USB hard drive is much better.
>
> Since you can get
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
>
> I think you simply got a bad rootfs / (maybe due
> to bad usb drive)

Hey David,

Flash drive is confirmed good, albeit rootfs is not.

It's a relatively new drive and it works fine for all applications I've applied it to. I've also tried 2 other drives and have the same issue, so it isn't drive specific. Thank you for the suggestion though!

Question though, I have a Linux environment in which to work with the drive to put a proper rootfs on it, but the guides I find are based on commands done locally with the PP. How does one go about building a proper rootfs (at least one that will boot) for the PP when I can't get it to boot due to what is showing up on the bootlogs?

Just download a bootable Linux iso, burn it to usb or CDROM disc, boot linux system with your windows machine, now you can make the rootfs
for your plugs.

It doesn't have to be in Kirkwood / OX820 environment to make rootfs for Kirkwood / OX820.

daviddyer Wrote:
-------------------------------------------------------
> Just download a bootable Linux iso, burn it to usb
> or CDROM disc, boot linux system with your windows
> machine, now you can make the rootfs
> for your plugs.
>
> It doesn't have to be in Kirkwood / OX820
> environment to make rootfs for Kirkwood / OX820.

Right, so to give you some background, I've had Arch Linux running on my PogoPlug before, and made/extracted a rootfs to a flash drive for that to work just fine. I'm somewhat experienced with *nix systems/OSes, so I know how to run Linux (as stated on my original post, I have a laptop dual booting Linux Mint and Windows 7, and I also have a VirtualBox for Lubuntu).

As for extracting/making a proper rootfs for Debian to work with this version of U-Boot, that's where I'm stuck, as I've extracted Debian 3.17 by bodhi to the drive using tar -xjf and it went fine. If there's a guide on how to do this that works from a non-PogoPlug environment, then by all means I'll do that, but I don't know if the steps work regardless of what system I'm running it on.



Edited 2 time(s). Last edit at 01/18/2017 10:41AM by Wrecktify.

Also to add, this is an OXNAS box, not Kirkwood. Rootfs I'd assume would be different between the 2.

I just loaded my converter via Linux Mint and used screen to monitor the output and while I can see everything fine, still no transmit, so I can't interrupt the boot process. Grrr this is so frustrating...

The rootfs I have on the flash drive is brand new, it's never been running on the box and it's a fresh format of ext3.

Do you have net console enabled? You are lucky if you have. That Uboot version has a working NC while the latest version doesn't. Try net console see if you can stop uboot, then set the location for dtb file, saveenv, try to boot the 3.17 kernel debian.

If net console is not enabled, ,maybe you need another serial cable.



Edited 1 time(s). Last edit at 01/18/2017 02:52PM by daviddyer.

Wrecktify,

Quote

As for extracting/making a proper rootfs for Debian to work with this version of U-Boot, that's where I'm stuck, as I've extracted Debian 3.17 by bodhi to the drive using tar -xjf and it went fine. If there's a guide on how to do this that works from a non-PogoPlug environment, then by all means I'll do that, but I don't know if the steps work regardless of what system I'm running it on.

The process to create the OXNAS rootfs is the same on any Linux box. The most important thing to do is to become root, and the commands are the same in Linux for any architecture. So go ahead, do exactly on x86 Mint what you would do on an ARM box.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 01/18/2017 03:05PM by bodhi.

Wrecktify,
>
> So, I've played and played with this thing, such
> as swapping wiring out and trying a different PC
> and different terminal emulation software, and I
> cannot get transmit to work going to the PP. I'm
> still receiving just fine via terminal, but
> transmits aren't being picked up by the PP, so I
> can't interrupt autoboot. I'm not sure if it's my
> serial converter or the PP, or something I'm doing
> wrong. I've got the converter configured at a
> 115200 baud rate, 8 bit data 1 bit stop, no parity
> or flow control, and can't get anything out of
> it.
>

Try loop back your TX and RX on the converter. Type something and it should echo back. This at least solves 1/2 of the problem.

There are too many posts so it is hard for me to keep track of what you have done :) is the serial console log in the 1st post good to use as a reference?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

daviddyer Wrote:
-------------------------------------------------------
> Do you have net console enabled? You are lucky if
> you have. That Uboot version has a working NC
> while the latest version doesn't. Try net console
> see if you can stop uboot, then set the location
> for dtb file, saveenv, try to boot the 3.17 kernel
> debian.
>
> If net console is not enabled, ,maybe you need
> another serial cable.

David,

Netconsole is not enabled, my envs are jacked so I never got around to implementing it's configuration.

As for the serial cable swap, I confirmed that my converter is transmitting, but the PogoPlug isn't receiving it. I did a loopback test and characters are being transmitted.

I did find an article that outlines what may be wrong with the serial, or at least shows that the issue can exist. Check this link, specifically the 2nd to last post.

https://archlinuxarm.org/forum/viewtopic.php?f=29&t=3344

bodhi Wrote:
-------------------------------------------------------
>
> Try loop back your TX and RX on the converter.
> Type something and it should echo back. This at
> least solves 1/2 of the problem.
>
> There are too many posts so it is hard for me to
> keep track of what you have done :) is the serial
> console log in the 1st post good to use as a
> reference?


Bodhi,

Loopback tested good, so my converter seems to be fine.

My console log in the first post is what I'm seeing consistently when I have a rootfs with Debian 3.17 on it (freshly formatted). I see the following when I don't have a flash drive in, and I can't get the serial console to respond to any key inputs.

Quote
U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command

Led: ORANGE (Failed)
ERROR: can't get kernel image!
stopping USB..
resetting ...

Edited 2 time(s). Last edit at 01/18/2017 03:35PM by Wrecktify.

Wrecktify,

Ok this problem should be easy! plug in your USB rootfs to the port in the back (next to the ethernet port), boot up and post serial log.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Wrecktify,
>
> Ok this problem should be easy! plug in your USB
> rootfs to the port in the back (next to the
> ethernet port), boot up and post serial log.


Freshly formatted Linux Mint 18.1 (had to reinstall completely, I was using 14 and it was WAY outdated), freshly formatted flash drive (ext3), freshly extracted tar rootfs (3.17.0), followed this guide to the T in terms of drive preparation.

Here are my results, same as before.

Quote

U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
4102704 bytes read in 408 ms (9.6 MiB/s)
1953812 bytes read in 301 ms (6.2 MiB/s)
7029 bytes read in 237 ms (28.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.3.17.0-oxnas-tld-1
Created: 2017-01-19 0:31:05 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4102640 Bytes = 3.9 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:18:53 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 67c4b000, end 67e27fd4 ... OK
Loading Device Tree to 67c46000, end 67c4ab74 ... OK

Led: GREEN

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Wrecktify,

> Freshly formatted Linux Mint 18.1 (had to
> reinstall completely, I was using 14 and it was
> WAY outdated), freshly formatted flash drive
> (ext3), freshly extracted tar rootfs (3.17.0),
> followed
> this
> guide to the T in terms of drive
> preparation.
>
> Here are my results, same as before.

Not the same as before. Last boot, the drive was not even recognized by u-boot. This boot, the kernel has loaded and attempted to run.

Probably the reason it could not run was because the u-boot env for bootargs was wrong. So we are back to the orginal starting point. And to solve this:

1. Connect serial console.
or
2. Prepare a special formatted HDD, connect it to the internal SATA port and boot directly to it. This approach should work as well as serial console.

I'de recommend to go with number 1. Because this serial converter will help you in a big way when you might acquire more plugs in the future.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
------------------------------------------------------
>
> Not the same as before. Last boot, the drive was
> not even recognized by u-boot. This boot, the
> kernel has loaded and attempted to run.
>
> Probably the reason it could not run was because
> the u-boot env for bootargs was wrong. So we are
> back to the orginal starting point. And to solve
> this:
>
> 1. Connect serial console.
> or
> 2. Prepare a special formatted HDD, connect it to
> the internal SATA port and boot directly to it.
> This approach should work as well as serial
> console.
>
> I'de recommend to go with number 1. Because this
> serial converter will help you in a big way when
> you might acquire more plugs in the future.

Bodhi, sorry for the confusion. My first post is nearly identical to this last post in regards to the serial output. They both get stuck at the kernel part. I've posted 3 serial console outputs and the 2nd was different as I knowingly had the USB drive disconnected.

As for the serial console, that's how I'm getting the output. Problem is, the PogoPlug is not accepting/receiving anything transmitted to it via serial. I can receive fine but no transmit, and I've confirmed my converter isn't the problem nor connections.

So plan b may be my only option. Is there another forum post with preparing a SATA drive for this, or how should I go about doing this?

SATA booting is in the uboot for OX820 sticky thread. About page 6

Here is a summary


http://forum.doozan.com/read.php?3,16017,19763#msg-19763

Wrecktify,

> As for the serial console, that's how I'm getting
> the output. Problem is, the PogoPlug is not
> accepting/receiving anything transmitted to it via
> serial. I can receive fine but no transmit, and
> I've confirmed my converter isn't the problem nor
> connections.

Let's try one last time on Linux Mint. Use picocom to run serial console, don't use any thing else.

>
> So plan b may be my only option. Is there another
> forum post with preparing a SATA drive for this,
> or how should I go about doing this?

This take more works than serial console:

- open the box
- buy matching SATA cable
- Buy HDD if not having one
- connect to an eSATA enclosure with the HDD inside (the cable you bought above must be male SATA- female eSATA ). Or instead of an enclosure, buy an extension cable that has both a SATA connector and a USB connector (for power).
- Format the HDD in a special way that (instruction was posted in the forum). I''ll have to find the post that has a good link (most of them are very old and seem to be dead).

So I'd consider the HDD approach is the last resort.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

> - Format the HDD in a special way that
> (instruction was posted in the forum). I''ll have
> to find the post that has a good link (most of
> them are very old and seem to be dead).

Hold on. I recalled one of our veteran forum members has sent me link to his tarball for the HDD booting.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
>
> Let's try one last time on Linux Mint. Use picocom
> to run serial console, don't use any thing else.
>
>
> This take more works than serial console:
>
> - open the box
> - buy matching SATA cable
> - Buy HDD if not having one
> - connect to an eSATA enclosure with the HDD
> inside (the cable you bought above must be male
> SATA- female eSATA ). Or instead of an enclosure,
> buy an extension cable that has both a SATA
> connector and a USB connector (for power).
> - Format the HDD in a special way that
> (instruction was posted in the forum). I''ll have
> to find the post that has a good link (most of
> them are very old and seem to be dead).
>
> So I'd consider the HDD approach is the last
> resort.

With picocom

Quote
picocom -b 115200 /dev/ttyUSB0
picocom v1.7

port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv
imap is :
omap is :
emap is : crcrlf,delbs,

Terminal ready

U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
4102704 bytes read in 408 ms (9.6 MiB/s)
1953812 bytes read in 301 ms (6.2 MiB/s)
7029 bytes read in 237 ms (28.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.3.17.0-oxnas-tld-1
Created: 2017-01-19 0:31:05 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4102640 Bytes = 3.9 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:18:53 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 67c4b000, end 67e27fd4 ... OK
Loading Device Tree to 67c46000, end 67c4ab74 ... OK

Led: GREEN

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

I don't know if my PogoPlug is legitimately broken in terms of serial connectivity or what, but I can receive fine from it, but when transmitting, no luck.

I did a loopback test to ensure that send/receive are communicating properly, and it echoed as it should (local echo shows 2 characters for every 1 typed). I've undone and redone the connectors to the converter and the PogoPlug and ensured they were good, but still nothing.

While it may be inconvenient to do the SATA method (I don't have a spare SATA drive laying around that works, and I'll have to bust the side of my computer open to get a cable and power for the drive), I don't know that this thing is recoverable with serial not working, unless I'm missing something.

Wrecktify Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> >
> > Let's try one last time on Linux Mint. Use
> picocom
> > to run serial console, don't use any thing
> else.
> >
> >
> > This take more works than serial console:
> >
> > - open the box
> > - buy matching SATA cable
> > - Buy HDD if not having one
> > - connect to an eSATA enclosure with the HDD
> > inside (the cable you bought above must be male
> > SATA- female eSATA ). Or instead of an
> enclosure,
> > buy an extension cable that has both a SATA
> > connector and a USB connector (for power).
> > - Format the HDD in a special way that
> > (instruction was posted in the forum). I''ll
> have
> > to find the post that has a good link (most of
> > them are very old and seem to be dead).
> >
> > So I'd consider the HDD approach is the last
> > resort.
>
> With picocom
>
>

Quote
picocom -b 115200 /dev/ttyUSB0
> picocom v1.7
>
> port is : /dev/ttyUSB0
> flowcontrol : none
> baudrate is : 115200
> parity is : none
> databits are : 8
> escape is : C-a
> local echo is : no
> noinit is : no
> noreset is : no
> nolock is : no
> send_cmd is : sz -vv
> receive_cmd is : rz -vv
> imap is :
> omap is :
> emap is : crcrlf,delbs,
>
> Terminal ready
>
> U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
>
> Boot device: NAND
> Attempting to set PLLA to 850 MHz ...
> plla_ctrl0 : 0000020a
> plla_ctrl1 : 00330000
> plla_ctrl2 : 0065008b
> plla_ctrl3 : 000000f1
>
> PLLA Set
>
>
> U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for
> OXNAS
>
> DRAM: 128 MiB
> NAND: 128 MiB
> In: serial
> Out: serial
> Err: serial
> Net:
> Led: GREEN
> mii0
> Main Loop
> Hit any key to stop autoboot: 0
> (Re)start USB...
> USB0: USB EHCI 1.00
> scanning bus 0 for devices... 3 USB Device(s)
> found
> scanning usb for storage devices... 1 Storage
> Device(s) found
> 4102704 bytes read in 408 ms (9.6 MiB/s)
> 1953812 bytes read in 301 ms (6.2 MiB/s)
> 7029 bytes read in 237 ms (28.3 KiB/s)
> ## Booting kernel from Legacy Image at 60500000
> ...
> Image Name: Linux-3.3.17.0-oxnas-tld-1
> Created: 2017-01-19 0:31:05 UTC
> Image Type: ARM Linux Kernel Image (uncompressed)
>
> Data Size: 4102640 Bytes = 3.9 MiB
> Load Address: 60008000
> Entry Point: 60008000
> Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at
> 60e00000 ...
> Image Name: initramfs-3.17.0-oxnas-tld-1
> Created: 2014-11-01 7:18:53 UTC
> Image Type: ARM Linux RAMDisk Image (gzip
> compressed)
> Data Size: 1953748 Bytes = 1.9 MiB
> Load Address: 60000000
> Entry Point: 60000000
> Verifying Checksum ... OK
> ## Flattened Device Tree blob at 62c00000
> Booting using the fdt blob at 0x62c00000
> Loading Kernel Image ... OK
> Loading Ramdisk to 67c4b000, end 67e27fd4 ... OK
> Loading Device Tree to 67c46000, end 67c4ab74 ...
> OK
>
> Led: GREEN
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
>

>
> I don't know if my PogoPlug is legitimately broken
> in terms of serial connectivity or what, but I can
> receive fine from it, but when transmitting, no
> luck.
>
> I did a loopback test to ensure that send/receive
> are communicating properly, and it echoed as it
> should (local echo shows 2 characters for every 1
> typed). I've undone and redone the connectors to
> the converter and the PogoPlug and ensured they
> were good, but still nothing.
>
> While it may be inconvenient to do the SATA method
> (I don't have a spare SATA drive laying around
> that works, and I'll have to bust the side of my
> computer open to get a cable and power for the
> drive), I don't know that this thing is
> recoverable with serial not working, unless I'm
> missing something.

There is a really easy way to recover (uEnv.txt). But you are running an older unreleased version of my uboot, so I forgot if I have added this capability to this version (the 2015.10 version has this).

See the instruction for my uboot 2015.10 about uEnv.txt. And try that approach:
http://forum.doozan.com/read.php?3,16017

Summary: copy the content of uboot.2013.10-tld-5.ox820.environment to the uEnv.txt and pkace it in /boot folder of the rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 01/19/2017 08:05AM by bodhi.

bodhi Wrote:
-------------------------------------------------------
>
> There is a really easy way to recover (uEnv.txt).
> But you are running an older unreleased version of
> my uboot, so I forgot if I have added this
> capability to this version (the 2015.10 version
> has this).
>
> See the instruction for my uboot 2015.10 about
> uEnv.txt. And try that approach:
> http://forum.doozan.com/read.php?3,16017
>
> Summary: copy the content of
> uboot.2013.10-tld-5.ox820.environment to the
> uEnv.txt and pkace it in /boot folder of the
> rootfs.


Hey Bodhi,

I copied the entire contents of uboot.2013.10-tld-5.ox820.environment from the U-Boot forum post download for updating U-boot, and placed it in uEnv.txt under /boot on my drive. I did so as root, and confirmed the file existed. Booting the PogoPlug up, I receive the same serial log as before, no difference whatsoever (stops at booting the kernel).

Wrecktify

I remember now I created this U-Boot 2013.10-tld-4 version to recover from a bad block where the u-boot envs stored (meaning there is no envs that can be used, even worse than your situation). If I recalled this correctly then it would save you some hassle and money. I think it was for LeggoMyEggo. Can you search the forum for his posts? or the post where this u-boot version was attached.

Other than that, what David posted above (thanks David!) is where the good instruction for HDD preparation: http://forum.doozan.com/read.php?3,32092,32142#msg-32142.
But that download link is dead, so I'll find and post the link to LeggoMyEggo uploaded HDD rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Here you go: starting from this post, see if any good info.

http://forum.doozan.com/read.php?3,16017,20204#msg-20204

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 01/19/2017 06:51PM by bodhi.

bodhi Wrote:
-------------------------------------------------------
> Here you go: starting from this post, see if any
> good info.
>
> http://forum.doozan.com/read.php?3,16017,20204#msg
> -20204


Thank you Bodhi, I wasn't even paying attention to the revision of U-Boot I was running (I thought I was on 1 and not 4), so that may put me in a better spot than I thought. I will attempt to copy the uEnv.txt Leggo posted and see if that helps me boot.

Crossing my fingers it will work, but otherwise, I may need to find a spare working SATA drive and boot it that way. I have what I need to do that, but it's gonna be a royal pain in the behind. I will post my findings when I get a chance.

Wrecktify,

> Crossing my fingers it will work, but otherwise, I
> may need to find a spare working SATA drive and
> boot it that way. I have what I need to do that,
> but it's gonna be a royal pain in the behind.

:))

Acoording to my post (above that post), uEnv.txt should work with tld-4 version.
http://forum.doozan.com/read.php?3,16017,20193#msg-20193

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> :))
>
> Acoording to my post (above that post), uEnv.txt
> should work with tld-4 version.
> http://forum.doozan.com/read.php?3,16017,20193#msg
> -20193


I can't make out why this isn't working......I have uEnv.txt located at /boot/uEnv.txt, and I've created it as root, and copied verbatim what LME posted on what you linked. The only thing different is I specified the proper MAC address, which I don't believe was necessary, but that's all I did.

I attempt to boot the PogoPlug, and I get the same serial output, that I can tell....

Quote

U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
4102704 bytes read in 406 ms (9.6 MiB/s)
1953812 bytes read in 301 ms (6.2 MiB/s)
7029 bytes read in 237 ms (28.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.3.17.0-oxnas-tld-1
Created: 2017-01-19 0:31:05 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4102640 Bytes = 3.9 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:18:53 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 67c4b000, end 67e27fd4 ... OK
Loading Device Tree to 67c46000, end 67c4ab74 ... OK

Led: GREEN

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

I've attached the configuration of my uEnv.txt file, as well as screenshots showing where I have everything located.