I figured out the issue.  It turns out that terraterm has a bug in its Kermit transfers.  It will corrupt files, which explains why no images were working.

The warning is absent from this wiki page, but fortunately I noticed the warning on another site.

 

http://docwiki.gumstix.org/Replacing_the_filesystem_image

 

I have to say I’m disappointed with the documentation on gumstix.com.  Lots of dead-ends with “coming soon” on pretty basic tasks.

 

 


From: gumstix-users-bounces@lists.sourceforge.net [mailto:gumstix-users-bounces@lists.sourceforge.net] On Behalf Of Alan Brumley
Sent: Sunday, March 09, 2008 2:30 PM
To: gumstix-users@lists.sourceforge.net
Subject: [Gumstix-users] Reloading a filesystem, what did I miss?

 

 

I flashed my own root file system onto a verdex.  I was getting bad CRC on the kernel, so I wanted to replace with “good” images.

Following this procedure:

http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using-a-serial-connection/111.html

I went to the feeds site here:

http://gumstix.net/feeds/current/glibc/images/gumstix-custom-verdex/

 

and used this filesystem:

Angstrom-gumstix-basic-image-glibc-ipk-2007.9-test-20080229-gumstix-custom-verdex.rootfs.jffs2 

 

And this kernel

uImage-2.6.21-r1-gumstix-custom-verdex.bin     

 

I didn’t see any errors during the procedure.

 

 

now I get a hang on boot:

U-Boot 1.2.0 (Dec 21 2007 - 13:34:50) - PXA270@400 MHz - 1578M

 

*** Welcome to Gumstix ***

 

DRAM:  64 MB

Flash: 16 MB

Using default environment

 

Hit any key to stop autoboot:  0

Instruction Cache is ON

Copying kernel to 0xa2000000 from 0x00f00000 (length 0x00100000)...done

## Booting image at a2000000 ...

   Image Name:   Angstrom/2.6.21/gumstix-custom-v

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1028172 Bytes = 1004.1 kB

   Load Address: a0008000

   Entry Point:  a0008000

OK

 

Starting kernel ...

 

 

Can anybody give me a pointer here?  Is my UBoot too old? Was there something wrong with the instructions?

 

It takes a while to upload a filesystem via serial so I’m going to try an image dating closer to the Uboot build date if I can find one. 

I figured I’d ask if somebody sees something glaring I missed.

 

If it matters, I’m using a Verdex board, (non Bluetooth) with a robostix and a tweener.  I modified the tweener (serial cut-trace) and it was working fine before I installed my own filesystem on it.  That was the image from the factory (dated sometime in December). 

Due to glibc dependency issues (one I’m building with is newer than the image that came from the factory), I was forced to static link my packages so I was trying to put my own image on there.  That’s what got my trying my own filesystem.

 

 

Thanks for any help.

 

 

Alan

 

 


No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.518 / Virus Database: 269.21.7/1322 - Release Date: 3/9/2008 12:17 PM


No virus found in this incoming message.
Checked by AVG.
Version: 7.5.518 / Virus Database: 269.21.7/1322 - Release Date: 3/9/2008 12:17 PM


No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.518 / Virus Database: 269.21.7/1322 - Release Date: 3/9/2008 12:17 PM