Here we go again;

 

First of all.

 

YES I TRIED RE-SEATING THE COM BOARD.

NO. I DIDN’T WORK. OK !!

 

What I did do was try something suggested earlier.

I used a previously built console image using Steve Sakoman’s script.

I re-named the “70-Persistent-net.rules” file, to “70-Persistent-net.old_rules” and re-booted.

 

root@omap3-multi:/etc/udev/rules.d# ls

50-udev-default.rules           78-sound-card.rules

60-persistent-alsa.rules        80-drivers.rules

60-persistent-input.rules       90-hal.rules

60-persistent-serial.rules      95-udev-late.rules

60-persistent-storage-tape.rules  local.rules

60-persistent-storage.rules     permissions.rules

70-persistent-net.old_rules     run.rules

75-net-description.rules        udev.rules

75-tty-description.rules

 

Here are the results:

 

Texas Instruments X-Loader 1.4.4ss (Mar  6 2011 - 20:53:08)

OMAP3503-GP ES3.1

Board revision: 2

Reading boot sector

Loading u-boot.bin from mmc

 

 

U-Boot 2010.12 (Mar 06 2011 - 20:54:20)

 

OMAP3503-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz

Gumstix Overo board + LPDDR/NAND

I2C:   ready

DRAM:  512 MiB

NAND:  512 MiB

MMC:   OMAP SD/MMC: 0

*** Warning - bad CRC, using default environment

 

In:    serial

Out:   serial

Err:   serial

Board revision: 2

Direct connection on mmc2

No EEPROM on expansion board

Die ID #18e400040000000004037d0710020008

Net:   smc911x: Invalid chip endian 0x4765c321

No ethernet found.

Hit any key to stop autoboot:  0

 

*** Note that I seem to be getting the same results as Sean and others …

*** This is the result of ‘lsmod’:

 

Module                  Size  Used by

ipv6                  222207  18

ads7846                 8867  0

 

Does anyone have any suggestions?

Could it be that the manufacturer has made changes to the IC ??

 

Bill

 

A prisoner of war is a man who tries to kill you and fails, and then asks you not to kill him.

Winston Churchill