Unbrick a Pogoplug Pro (v3/OXNAS?)

Greetings,

After much success with my Pogoplug v4/mobile, I figured I would try to get my larger v3/Oxnas boards working. I seem to have bricked one right out of the gate. I have a sinking suspicion I have misidentified the board and flashed the wrong u-boot. Here's a picture of the board: https://photos.app.goo.gl/kOVyY9wPaZftWUif1

Here's what I've got. The flash went through without errors as far as I can see (nothing that looked out of the ordinary from my first attempts at flashing a board) but now I have no boot, no serial console, no response at boot other than the power LED coming on. Here's the link to the steps I took to flash the board: https://hastebin.com/edoqipelis.makefile

I have the plug fully disassembled now and I've gone hunting for a jtag interface, but I don't see one. Am I SOL here? The board was cheap so if I have to cut my losses that's fine, but I am pretty sure that this should be recoverable. I've got a bus pirate available, but I'm not as well versed in the ways of its use as I'd like to be.

maldridge Wrote:
-------------------------------------------------------
> Greetings,
>
> After much success with my Pogoplug v4/mobile, I
> figured I would try to get my larger v3/Oxnas
> boards working. I seem to have bricked one right
> out of the gate. I have a sinking suspicion I
> have misidentified the board and flashed the wrong
> u-boot. Here's a picture of the board:
> https://photos.app.goo.gl/kOVyY9wPaZftWUif1
>
> Here's what I've got. The flash went through
> without errors as far as I can see (nothing that
> looked out of the ordinary from my first attempts
> at flashing a board) but now I have no boot, no
> serial console, no response at boot other than the
> power LED coming on. Here's the link to the steps
> I took to flash the board:
> https://hastebin.com/edoqipelis.makefile
>
> I have the plug fully disassembled now and I've
> gone hunting for a jtag interface, but I don't see
> one. Am I SOL here? The board was cheap so if I
> have to cut my losses that's fine, but I am pretty
> sure that this should be recoverable. I've got a
> bus pirate available, but I'm not as well versed
> in the ways of its use as I'd like to be.

Yes, you did flash the wrong uboot. Yours is the Pogo V3 OXNAS. But there is no need for JTAG. You can recover with the SATA booting.

Format the HDD using info from this post:

https://forum.doozan.com/read.php?2,32994,33021#msg-33021

And connect this HDD to the internal SATA port (red color). Power up. It will boot into Debian.

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



Edited 1 time(s). Last edit at 11/19/2017 09:41PM by bodhi.

Sounds good, I have ordered an external SATA power supply as I think I lent mine out and never got it back. I'll report back here once I get this working.

maldridge,

In case the link is broken, here is a good one:

https://forum.doozan.com/read.php?3,28162,28313#msg-28313

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

Hmm, I'm having no luck with those directions. Every time I try to run the script I wind up with a corrupt filesystem on the target disk. Perhaps I'm missing something?

maldridge@deepblue:~/Downloads/oxnas/workdir$ sudo ./disk_create 
0+1 records in
0+1 records out
444 bytes copied, 0.00790116 s, 56.2 kB/s
Writing stage 1
14+1 records in
14+1 records out
7576 bytes (7.6 kB, 7.4 KiB) copied, 0.00496056 s, 1.5 MB/s
Writing uboot
253+1 records in
253+1 records out
129852 bytes (130 kB, 127 KiB) copied, 0.0348114 s, 3.7 MB/s
Writing kernel to 
4164+1 records in
4164+1 records out
2132324 bytes (2.1 MB, 2.0 MiB) copied, 0.8046 s, 2.7 MB/s
maldridge@deepblue:~/Downloads/oxnas/workdir$ sudo sync
maldridge@deepblue:~/Downloads/oxnas/workdir$ sudo mount /dev/sdb1 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.

maldridge,

Please post your disk_create script, and the output of

fdisk -l

before running it.

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

Here's the fdisk output:

Disk /dev/sdb: 74.5 GiB, 80026361856 bytes, 156301488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00008000

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdb1  *         2048 146802687 146800640   70G 83 Linux
/dev/sdb2       146802688 156301487   9498800  4.5G 82 Linux swap / Solaris

And here's the disk_create script with the correct disk filled in:

#!/bin/sh

# uncomment line below and set to the correct disk
disk=/dev/sdb

if [ -z "${disk}" ] ; then
   echo "You must uncomment/set the 'disk' variable"
   exit -1
fi

workarea="."

stage1File=$workarea/stage1.wrapped
ubootFile=$workarea/u-boot.wrapped
kernelFile=$workarea/uImage

perl <<EOF | dd of="$disk" bs=512
    print "\x00" x 0x1a4;
    print "\x00\x5f\x01\x00";
    print "\x00\xdf\x00\x00";
    print "\x00\x80\x00\x00";
    print "\x00" x (0x1b0 -0x1a4 -12 );
    print "\x22\x80\x00\x00";
    print "\x22\x00\x00\x00";
    print "\x00\x80\x00\x00";
EOF

if [ -f $stage1File ];then
	echo "Writing stage 1"
	dd if=$stage1File    of="$disk" bs=512 seek=34
fi

if [ -f $ubootFile ];then
	echo "Writing uboot"
	dd if=$ubootFile     of="$disk" bs=512 seek=154
fi

if [ -f $kernelFile ];then
	echo "Writing kernel to "
	dd if=$kernelFile of="$disk"1 bs=512 
fi

maldridge,

I did not see anything wrong above.

However, slightly off topic: I would suggest never use sudo while you are doing this. You must be root user to avoid any future complication while hacking.

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

The only thing I can come up with at this point is either a bad disk (seems odd, it takes and retains the partition table) or a bad SATA controller. The second is plausible since I'm going USB-SATA and I could see something getting reset or corrupted in the transfer. I guess I could boot up a system live and build the disk there, then move it over, but ideally I'd like to be able to do this with the USB converter. Getting a whole second system up and running just to use the SATA bus seems like a last ditch effort.



Edited 1 time(s). Last edit at 11/25/2017 07:27PM by maldridge.

maldridge Wrote:
-------------------------------------------------------
> The only thing I can come up with at this point is
> either a bad disk (seems odd, it takes and retains
> the partition table) or a bad SATA controller.
> The second is plausible since I'm going USB-SATA
> and I could see something getting reset or
> corrupted in the transfer. I guess I could boot
> up a system live and build the disk there, then
> move it over, but ideally I'd like to be able to
> do this with the USB converter. Getting a whole
> second system up and running just to use the SATA
> bus seems like a last ditch effort.

If this HDD is 2.5", you can plug it directly to the GF Net. Or plug it directly to the GHHome if 3.5". You have GFHome?

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



Edited 1 time(s). Last edit at 11/25/2017 07:53PM by bodhi.

It is 2.5", but for that I would need a working system right? I'm still stuck at trying to get a rootfs on the drive. As soon as I run the create_disk script I can no longer mount the drive. Perhaps I need a sacrificial partition at the start of the disk?

maldridge,

> It is 2.5", but for that I would need a working
> system right?

Right! so it's too bad you don't have a Pogo V4, Goflex Net/Home, that you can just plug in this HDD. Those are the least expensive plugs that have a SATA interface.

> Perhaps I need a sacrificial partition at
> the start of the disk?

I don't think so. I think probably your USB-SATA interface is the problem. When I use a SATA HDD on the Pogo V4, and ran disk_create, there is no problem mounting it afterward.

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

Meh, its not that bad. I've got a workbench of x86 hardware. Now that we're reasonably confident this is the problem, I can jump off of a live SATA bus and try this from there.

Got it working by offsetting the partition slightly from the start. After dumping the disk with xxd I realized that the first partition was close enough to the start it was being corrupted by the DD commands. I think it depends on how your partitioning software works whether or not you see such corruption.

It still fails to boot though, here is the output:

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
*** Warning - bad CRC, using default environment

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 

Loading from IDE device 0, partition 2: Name: hda2
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: ST980817AS Firm: 3.CMF  Ser#: 5RE1XNLE
            Type: Hard Disk
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
  Device 1: not available
Failed to read valid environment from disk, using built-in default


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
*** Warning - bad CRC, using default environment

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 

Loading from IDE device 0, partition 2: Name: hda2
  Type: U-Boot

** Bad Magic Number **
Unknown command 'lightled' - try 'help'

I'm inclined to think this is a result of the bad flash, here's the output of printenv:

$ printenv
bootcmd=run dload1 boot || run dload2 boot || lightled
bootdelay=2
baudrate=115200
ethaddr=00:30:e0:00:00:01
ipaddr=172.31.0.128
serverip=172.31.0.100
autoload=n
netmask=255.255.0.0
bootfile="uImage"
lightled=ledfail 1
extinguishled=ledfail 0
boot=bootm 60500000
dload1=diskboot 60500000 0:1
dload2=diskboot 60500000 0:2
root_dev1=/dev/sda2
root_dev2=/dev/sda1
root_dev=/dev/sda2
stdin=serial
stdout=serial
stderr=serial
bootargs=root=/dev/sda2 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 rootwait ubi.mtd=2,512 mem=128M poweroutage=yes

Environment size: 565/8188 bytes

Any thoughts?

maldridge,

Quote

> 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
> *** Warning - bad CRC, using default environment
>
> 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

>
> Loading from IDE device 0, partition 2: Name:
> hda2
> 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: ST980817AS Firm: 3.CMF Ser#:
> 5RE1XNLE
> Type: Hard Disk
> Capacity: 76319.0 MB = 74.5 GB
> (156301488 x 512)
> Device 1: not available

Cool! it's now unbricked. Even though you did not get it to boot into Debian, it is now unbrickable. You can always go back to this SATA booting and start recovery.


> Failed to read valid environment from disk, using
> built-in default

This indicated a wrong u-boot envs file in the HDD.

> I'm inclined to think this is a result of the bad
> flash, here's the output of printenv:

The printenv now shows what in u-boot internal envs setting. So it is not usable. Note that when you boot with HDD this way, NAND is not read at all. So it is not the previous bad flash.


You can do either:

1. Check and make sure this file on your HDD /boot is OK. Try recopy that file from the tarball.

/boot/u-boot.env

2. If it still fails to boot after you've tried number 1, you can flash the new uboot.2015.10-tld-2 SPL image and U-boot image to NAND at serial console prompt and completely unbrick it. After that, you can boot the rootfs Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 on USB drive. Adn then move on to Void Linux booting.

-----

I think you should get number 1 working and boot into Debian 2.6.31.14 (that's what in the HDD rootfs partition right now). And then flash u-boot. It is much easier.

But if you must do option 2 above, let me know if you are not sure what the flash-erase and nand-write commands should be at serial console prompt.

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



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

All the critical files look to be intact. I do find ext4 to be just a tad suspicious though for the format. Can the spl u-boot really read an ext4 volume?

Here are the sha256sums of the important files.

maldridge@deepblue:~$ sha256sum /mnt/boot/u-boot-spl.bin 
70d359b639d28b8b6c701f1aea1ef47f849c3b7922ba92809afece99ff76f431  /mnt/boot/u-boot-spl.bin
maldridge@deepblue:~$ sha256sum Downloads/oxnas/ox820-sata-uboot/u-boot-spl.bin 
70d359b639d28b8b6c701f1aea1ef47f849c3b7922ba92809afece99ff76f431  Downloads/oxnas/ox820-sata-uboot/u-boot-spl.bin
maldridge@deepblue:~$ sha256sum /mnt/boot/u-boot.env 
763f5290ec8fb0beea5fbfaa9c10c8452d6d21949d3011d2af2abf692ac88d30  /mnt/boot/u-boot.env
maldridge@deepblue:~$ sha256sum Downloads/oxnas/ox820-sata-uboot/u-boot.env
763f5290ec8fb0beea5fbfaa9c10c8452d6d21949d3011d2af2abf692ac88d30  Downloads/oxnas/ox820-sata-uboot/u-boot.env
maldridge@deepblue:~$ sha256sum /mnt/boot/u-boot.img
095821b1a9877c26d31c08f6af3d238a846c67fce7f3a6dbf96dab48d74441bd  /mnt/boot/u-boot.img
maldridge@deepblue:~$ sha256sum Downloads/oxnas/ox820-sata-uboot/u-boot.img
095821b1a9877c26d31c08f6af3d238a846c67fce7f3a6dbf96dab48d74441bd  Downloads/oxnas/ox820-sata-uboot/u-boot.img

maldridge,

> All the critical files look to be intact. I do
> find ext4 to be just a tad suspicious though for
> the format. Can the spl u-boot really read an
> ext4 volume?

Yes it can. Ext4 was ported to this SPL. If shv has compiled this SPL with the right option, it should work.

Besides, when you see this

Hit any key to stop autoboot:  0 

Loading from IDE device 0, partition 2: Name: hda2
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: ST980817AS Firm: 3.CMF  Ser#: 5RE1XNLE
            Type: Hard Disk
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
  Device 1: not available
Failed to read valid environment from disk, using built-in default

it means SPL has booted successfully, and it tried to find the u-boot.env file from disk.

OTOH, when in doubt, you can use Ext2 file system to format the HDD.

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

Hmm, well the files appear intact and the system loads to this point. Would it be possible to just load the files from disk by hand without the environment? Unless there was a separate environment file from the one linked in the first linked thread, I am confident it is on the drive and not corrupt.

maldridge,

Which tarball did you use? does it look like this?

ls -l oxnasboottarball/ox820-sata-uboot/boot/

total 8404
drwxr-xr-x 3 root root    4096 Nov 28 21:59 .
drwxr-xr-x 3 root root    4096 Jun  1  2016 ..
drwxr-xr-x 2 root root    4096 Aug  3  2014 dts
-rwxr-xr-x 1 root root   16384 Dec 31  1969 u-boot.env
-rw-r--r-- 1 root root  525880 Aug  3  2014 u-boot.img
-rwxr-xr-x 1 root root   32120 Aug  3  2014 u-boot-spl.bin
-rw-r--r-- 1 root root 3676848 Aug  3  2014 uImage
-rw-r--r-- 1 root root 2212156 Aug  3  2014 uImage_2.6.31.14_OX820_1.2_shv.Pro
-rw-r--r-- 1 root root 2103272 Aug  3  2014 uInitrd

And did you use this download link?

https://forum.doozan.com/read.php?3,28162,28313#msg-28313

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



Edited 1 time(s). Last edit at 11/29/2017 04:11AM by bodhi.

I used the tarball that was linked above, this is what mine contains. They appear to be identical:

maldridge@deepblue:~$ ls -l Downloads/oxnas/ox820-sata-uboot/
total 8380
drwxr-xr-x 2 maldridge maldridge    4096 Aug  3  2014 dts
-rwxr-xr-x 1 maldridge maldridge   32120 Aug  3  2014 u-boot-spl.bin
-rwxr-xr-x 1 maldridge maldridge   16384 Dec 31  1969 u-boot.env
-rw-r--r-- 1 maldridge maldridge  525880 Aug  3  2014 u-boot.img
-rw-r--r-- 1 maldridge maldridge 3676848 Aug  3  2014 uImage
-rw-r--r-- 1 maldridge maldridge 2212156 Aug  3  2014 uImage_2.6.31.14_OX820_1.2_shv.Pro
-rw-r--r-- 1 maldridge maldridge 2103272 Aug  3  2014 uInitrd

maldridge,

1. This is OT, but weird looking attributes:

maldridge@deepblue:~$ ls -l Downloads/oxnas/ox820-sata-uboot/
total 8380
drwxr-xr-x 2 maldridge maldridge    4096 Aug  3  2014 dts
-rwxr-xr-x 1 maldridge maldridge   32120 Aug  3  2014 u-boot-spl.bin
-rwxr-xr-x 1 maldridge maldridge   16384 Dec 31  1969 u-boot.env
-rw-r--r-- 1 maldridge maldridge  525880 Aug  3  2014 u-boot.img
-rw-r--r-- 1 maldridge maldridge 3676848 Aug  3  2014 uImage
-rw-r--r-- 1 maldridge maldridge 2212156 Aug  3  2014 uImage_2.6.31.14_OX820_1.2_shv.Pro
-rw-r--r-- 1 maldridge maldridge 2103272 Aug  3  2014 uInitrd

Why were they not created by root?

2. Also, perhaps you should try various options like shv described:

Quote
https://forum.doozan.com/read.php?3,16017,17297#msg-17297
But if you put the right stage1 bootloader and the right uboot to your SATA drive it might boot with them. You can't use the files which are provided here for Flash install. Moreover you must put the stage1 bootloader to your drive as it is done by OXNAS-SATA-Boot skript from ALARM forum. The uboot can be put to the filesystem of the first partition (Fat32 or ext4 depends on the stage1 loader).

I tested the following setups:
sda1: just für boot files like u-boot.img, u-boot.env, uImage, uInitrd (ext4 or fat32)
sda2: rootfs (ext3 or ext4)
sda3: linux swap partition
sda4: data (ext4)

or
sda1: rootfs including boot files (ext4)
sda2: linux swap partition
sda3: data (ext4)

For both setups you can use the same stage1 bootloader (u-boot-spl.bin) which reads the boot files from and stores boot environment to the first ext4 partition of the SATA drive. The device must support 512 Byte sector size either natively or by simulation.

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

To your first point, the files are owned by me because I expanded the archive for the express purpose of checking the shasums. The ones on the boot volume are, naturally, owned by root.

As far as the information you linked to below it occurs to me that the partition in question is actually the second partition on the disk, but it is labelled 'rootfs'. I wonder if some things are hard coded to find the first partition.

I will rebuild the disk and try this assertion.

maldridge,

> I wonder if some things are
> hard coded to find the first partition.
>

Ah. That makes a lot of sense now. If you posted this in fdisk output then I've missed it! the /boot folder must be on the 1st partition, always. This is by convention.

If somehow the rootfs is on a 2nd partition, then /boot must be copied to the 1st partition to make it work.

For any newer u-boot that I released, this convention also applies, too.

This is just something I have not have time to work on, so that /boot can reside on any partition.

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



Edited 1 time(s). Last edit at 11/29/2017 09:29PM by bodhi.

Fair enough, I usually will put /boot on the first partition, though in this case I cannot get the disk to work without putting a 2M partition on the front of the disk which is inevitably corrupted after running the disk_create script. I've been trying to put a sufficient offset on the disk so this doesn't happen, but I haven't succeeded yet.

> front of the disk which is inevitably corrupted
> after running the disk_create script.

This corruption should only occurs on a non-512-bytes-sector HDD. But you do have a 512-bytes sector HDD!

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

Ok, if you can't make it 1st partition then we can modify the u-boot.env file to make it 2nd partition, too.

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

I've tried everything I can think of with formatting and partitioning and I can't make it work as the first partition. Is there a way to get it to see the 2nd partition for the env file?

Alternatively can I load the correct flash image to a USB key and just flash it from the spl u-boot?

> Alternatively can I load the correct flash image
> to a USB key and just flash it from the spl
> u-boot?

Let me see if I can work out the flashing commands at serial console prompt (I don't have my old notes with me, atm).

In prepare, interrupt the countdown here:

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
*** Warning - bad CRC, using default environment

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

And list the commands available

help

Basically we are looking for:

ide reset
ide part
usb start
usb part
source
nand erase
ext2load 
nand write

And then see what are in the envs, as well:

printenv

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

maldridge,

Were you able to interrupt serial console like I post above?

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

Things have been busy at work, I'll be able to try this tonight (Pacific Time).