Fixing lobotomized B-01

[jbhelfrich]

Figured I'd stop cluttering up the upgrade thread since this is now a rescue operation.

Since I apparently stopped before writing the new Kernel over, is updating/repairing the USB filesystem an option? Or does the absence of a mtd drive mean that I'm in a worse spot?

Presuming that to be the case, what am I looking for in a serial cable? Would https://www.sparkfun.com/products/9893 work, since I can get that locally?

Once I've got a serial connection, is there a simple reset to stock/start over procedure? I'm OK with losing everything on this install (assuming I haven't already) as I've been using it as a dev server, but will probably be picking up a cheap refurbished PC for that and turn this into a network server. (I've decided that using a device that doesn't have a physical terminal as my dev server when I know just enough to really screw things up was...not my brightest idea.)

[WarheadsSE]

One of those plus this: https://www.sparkfun.com/products/9240

You can then tftp in a working uImage, and then go from there.

[jbhelfrich]

OK, I finally got some time to argue with loose wire and my computer until it not only believed it had a serial port, but could actually communicate with the damned thing.

If I let the Pogo boot with the filesystem stick in, I get the following:
$this->bbcode_second_pass_code('', 'Stage-1 Bootloader XCE_STAGE1: 1.1: Tue Feb 8 01:40:26 PST 2011
Attempting to set PLLA to 700MHz ...
plla_ctrl0 : 0x0000000A
plla_ctrl1 : 0x000E0000
plla_ctrl2 : 0x001C01A0
plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading NAND, Image 0
Hdr len: 0x0001C030
Hdr CRC: 0x39F6D832
OK

U-Boot 1.1.2 (Jul 29 2010 - 19:36:07)

U-Boot code: 60D00000 -> 60D1C030 BSS: -> 60D21800
RAM Configuration:
Bank #0: 60000000 128 MB
SRAM Configuration:
64KB at 0x50000000
NAND:128 MiB
In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value
Hit any key to stop autoboot: 0

Loading from device 0: 128MiB 3,3V 8-bit (offset 0x500000)
-- Using 1bit ECC style encoding
Image Name: Linux-2.6.31.6_SMP_820
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2159884 Bytes = 2.1 MB
Load Address: 60008000
Entry Point: 60008000
## Booting image at 60500000 ...
Image Name: Linux-2.6.31.6_SMP_820
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2159884 Bytes = 2.1 MB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................. ......................................................................

crc error

-- System halted')

If I interrupt autoboot, I get a very limited set of commands and no file system. It's got tftpboot in the help menu, and launching that seems to be looking for the ethernet port. Can I plug the ethernet cable in at this point (or, I suppose, before launching tftp)?

Assuming that's the case, my step-daughter has a box upstairs running (ed)ubuntu. So I use these instructions to set up the tftp server on that box, then extract the uimage.nopci file and add it to the server. (Is that one of those things that has to be done as root, not as sudo?) Right so far?

Back on the pogo, I enter tftpboot <ip address> uImage.nopci, correct? (I see lots of examples of tftp commands in a few google searches, but no tftpboot examples.) Will that boot into that image automatically, or do I have to issue another command?

Once that's done, I should have access to the file system on the stick, and network access. Then I can either try to run the update again and get the right files in the right places, or run the revert script and start from scratch? Does the current installer have the most recent files?

Sorry for the step-by-step questions, I just want to make sure I've got it all sorted out before I start. Thanks again!