angstrom+omap3503 EVM+beagleboard

[Ben Anderson]

Hello,

I have a TI Omap3503 EVM board and I am trying to get OE up and working
on it.  I am using the angstrom 2008.1  distro with the beagleboard as
machine.  The beagleboard uses the same omap processor (omap3530).  And
it appears as though oe is working for the beagleboard.


Here is my configuration file

======================================================================
BFILES = "/home/projects/oe/stuff/org.openembedded.dev/packages/*/*.bb"
DISTRO = "angstrom-2008.1"
MACHINE = "beagleboard"
IMAGE_FSTYPES="tar.bz2"
======================================================================



I can run bitbake task-base and it appears to build correctly.

======================================================================
NOTE: Tasks Summary: Attempted 1467 tasks of which 0 didn't need to be
rerun and 0 failed.
NOTE: build 200806041351: completed
======================================================================



However when I try to run the kernel (via tftp, or from flash) it does
the following.

======================================================================
OMAP3EVM # run bootcmd
Reseting CHIP... Done
LAN9x18 (0x01150002) detected.
start Auto negotiation... (take ~2sec)
Auto negotiation complete, 100BaseTX, full duplex
Hit any key to stop autoboot:  0
OMAP3EVM # setenv get_kernel run tftp_kernel
OMAP3EVM # run bootcmd
Reseting CHIP... Done
LAN9x18 (0x01150002) detected.
start Auto negotiation... (take ~2sec)
Auto negotiation complete, 100BaseTX, full duplex
TFTP from server 192.168.20.176; our IP address is 192.168.20.201
Filename 'uImage'.
Load address: 0x80000000
Loading:
#################################################################
...
#################################################################
done
Bytes transferred = 2155668 (20e494 hex)
## Booting image at 80000000 ...
   Image Name:   Angstrom/2.6.25+2.6.26-rc4+git24
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2155604 Bytes =  2.1 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
OK

Starting kernel ...
======================================================================


Then it appears to lock up.  Normally, when using the kernel that came
with TI's SDK, the output is the following.

======================================================================
LAN9x18 (0x01150002) detected.
start Auto negotiation... (take ~2sec)
Auto negotiation complete, 100BaseTX, full duplex
TFTP from server 192.168.20.176; our IP address is 192.168.20.201
Filename 'uImage'.
Load address: 0x80000000
Loading:
#################################################################
...
#################################################################
done
Bytes transferred = 1821644 (1bcbcc hex)
## Booting image at 80000000 ...
   Image Name:   Linux-2.6.22.1-omap3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1821580 Bytes =  1.7 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing
Linux...................................................................................................................... done, booting the kernel.
Linux version 2.6.22.1-omap3 (root at BenMain) (gcc version 4.2.3 (Sourcery
G++ Lite 2008q1-126)) #1 Wed May 28 16:58:48 PDT 2008
CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f
.
.
.

======================================================================


Does anyone have any ideas as to what I am doing wrong.  It looks like
uboot recognizes the uImage file and the uboot info displays for the two
kernel match between the TI supplied kernel and the OE built kernel in
all but the Image name.

I realize this question might be better directed to beagleboard
developers but thought I would try here first.

Thanks,


Ben Anderson