How do i recover from this....... (2 replies)

been given a box from a colleague at work and I think he has messed the box up good and proper!! I got it on the proviso that if i can fix it i can keep it :) I will then use this to build an image for a user on here.....

Good News / Bad News time

Good News
I can serial console to the unit and extract the settings listed below. it appears to be running the later uboot
U-Boot 2014.07-tld-2 (Sep 20 2014 - 00:52:18)
Pogo E02

Bad News
The env settings seem to be all over the place and are attached to this post - what can be seen on the console is the following, which is a good start

U-Boot 2014.07-tld-2 (Sep 20 2014 - 00:52:18)
Pogo E02

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 
Unknown command '‘run' - try 'help'
PogoE02>

can anyone offer a simple solution to input a set of env statements from the console that will allow me to boot a debian stick from which i can then reflash all the settings to get this working again??

I guestimate it will be something like the following, however it doesn't work.
usb reset
setenv bootargs root=/dev/sda1 rw rootwait mtdparts=orion_nand:1M(u-boot),-(rootfs)
load usb 0:1 0x810000 /boot/uImage
bootm 0x810000

The debian stick outputs the following

PogoE02>  usb reset
(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
PogoE02>              setenv bootargs root=/dev/sda1 rw rootwait mtdparts=orion_nand:1M(u-boot),-(rootfs)
PogoE02>  load usb 0:1 0x810000 /boot/uImage
2832460 bytes read in 300 ms (9 MiB/s)
PogoE02>              bootm 0x810000
## Booting kernel from Legacy Image at 00810000 ...
   Image Name:   Linux-3.17.0-kirkwood-tld-1
   Created:      2015-02-23  19:46:09 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2832396 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0xdd6 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Then just sits there doing nothing.

An Arch stick outputs the following before

(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
PogoE02>              setenv bootargs root=/dev/sda1 rw rootwait mtdparts=orion_nand:1M(u-boot),-(rootfs)
PogoE02>  load usb 0:1 0x810000 /boot/uImage
4054464 bytes read in 325 ms (11.9 MiB/s)
PogoE02>  bootm 0x810000
## Booting kernel from Legacy Image at 00810000 ...
   Image Name:   Linux-3.19.0-1-ARCH
   Created:      2015-02-10   4:56:00 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4054400 Bytes = 3.9 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0xdd6 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Then sits there doing nothing

The env settings look to be a mashup of both Arch and Bodhi settings and i dont have the knowledge to correct this on my own, it would be a shame to consign a Pogo to the bin when what looks like an environment variable mashup that COULD be sorted.