kernel 2.6.37 hangs on C4

GoogleGroups
1

After updating OE, linux kernel version is changed to 2.6.37 from
2.6.32 (from linux-omap-psp_2.6.32.bb to linx-omap_2.6.37) in terms of
angstrom-2010.x.conf. By building console-image, I got u-boot and
uImage. Here
are two problems,
1. u-boot doesn't work on C4 except orange screen (it has much smaller
size than built out
side of OE using codesourcery).
2. use previous u-boot built out side of OE, but the uImage hangs on

Loading u-boot.bin from
mmc

U-Boot 2010.06-00704-gcd67422-dirty (Aug 22 2010 - 13:38:03)

OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Board revision C4
Die ID #1978000400000000040365fa1700e01a
Hit any key to stop autoboot: 0
OMAP3 beagleboard.org # AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
syntax error
OMAP3 beagleboard.org # boot
mmc1 is available
reading uImage.bin

2850272 bytes read
## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Angstrom/2.6.37/beagleboard
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 2850208 Bytes = 2.7 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

I have tried to build 2.6.37 before updating OE, I got the same
problem. Did I miss something or
change version to 2.6.32 from angstrom-2010.x.conf?

2

Hi Kai,

1. Enable "Early printk" support in your kernel:

Kernel hacking --->
    [*] Kernel low-level debugging functions
    [*] Early printk

2. Add "earlyprintk" parameter to your U-Boot bootargs.

Cheers,
Max.

3

Did you change the kernel boot options to use console=ttyO2,115200 ?

4

Hi Kai,

It sounds like you ran into the new version of u-boot. The newest
version of u-boot requires a different script format. Most of the
wiki's and blog posts are decoys. Follow the instructions listed
under the sticky post titled "New SD Image to Test".

BTW --- I am so stoked that I can now change my uboot environment
settings with only a text editor, woot! Just kidding. I wasted most
of the weekend sorting thru the BS to fix something that was never
broken in the first place.

The sticky would be better titled "LOOK -- NEW version of UBOOT hoses
EVERYTHING!!"

Mark

5

Yes, this could be problem. I managed to login. But I got omapfb
problem in terms of message.

[ 3.307556] OMAPFB: omapfb_init
[ 3.307678] OMAPFB: omapfb_probe
[ 3.307708] omapfb omapfb: no displays
[ 3.307708] OMAPFB: free_resources
[ 3.307739] OMAPFB: free all fbmem
[ 3.307739] omapfb omapfb: failed to setup omapfb
[ 3.307769] omapfb: probe of omapfb failed with error -22
[ 3.308166] regulator_init_complete: incomplete constraints,
leaving VDVI on
[ 3.308441] regulator_init_complete: incomplete constraints,
leaving VDAC on

Here is my omapfb config