[meta-ti] booting 2.6.32 kernel and rootfs

[Pow, Christopher (SWCOE)]

A handy trick I found useful if you have a way to warm-reset the board [ie. RAM content is unaffected]:

In the kernel source directory, type:

grep printk_buf System.map

Then warm-reset your board after it stops outputting, and in u-boot dump the memory at whatever the address is that was reported as printk_buf symbol.

In my situation, integrating Linux onto a mach-davinci derived custom board, I found a printk message indicating it was hung waiting for something that was on the devkit but not on our board.

Christopher S. Pow
Senior Engineer, Systems
Honeywell SWCOE - RTOS
o:612-951-5852 c:612-910-1271

"The number you have dialed is imaginary.  Please rotate your phone 90 degrees and try again."

From: meta-ti-bounces at yoctoproject.org [mailto:meta-ti-bounces at yoctoproject.org] On Behalf Of Frazer, Will
Sent: Monday, July 08, 2013 12:24 PM
To: meta-ti at yoctoproject.org
Subject: Re: [meta-ti] booting 2.6.32 kernel and rootfs

Sounds like it is booting OK but the console is wrong.

Check into why you are getting this message also
** Unable to read "uEnv.txt" from mmc 0:1 **
as the kernel args ought to get read from there:

If they are not loaded then the defaults in the kernel will get used. You might want to check these also.
Not sure about your board/setup however try using /dev/ttyO0. You can test this from U-Boot also by altering the env vars

From: meta-ti-bounces at yoctoproject.org<mailto:meta-ti-bounces at yoctoproject.org> [mailto:meta-ti-bounces at yoctoproject.org] On Behalf Of Sudhangathan B S
Sent: 06 July 2013 05:16
To: meta-ti at yoctoproject.org<mailto:meta-ti at yoctoproject.org>
Subject: [meta-ti] booting 2.6.32 kernel and rootfs

On my way to integrate Leopard imaging camera drivers into the beagle board image, I successfully built a minimal image with necessary camera drivers in the image, this is all after I integrated meta-ti layer with yocto.
I finally put the files in the card and powered up the beagle board.

This is what i'm getting..

U-Boot SPL 2011.09-01172-gfdbe8b9-dirty (Jul 05 2013 - 20:38:26)
Texas Instruments Revision detection unimplemented
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2011.09-01172-gfdbe8b9-dirty (Jul 05 2013 - 20:38:26)

OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

In:    serial
Out:   serial
Err:   serial
Beagle xM Rev C
No EEPROM on expansion board
No EEPROM on expansion board
Die ID #689000029ff80000016842c81202f014
Net:   Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot:  0
The user button is currently NOT pressed.
SD/MMC found on device 0
reading uEnv.txt

** Unable to read "uEnv.txt" from mmc 0:1 **
Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
3148568 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-2.6.32
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3148504 Bytes = 3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................................................................................................ done, booting the kernel.

AND NOTHING AFTER THIS... Any clue how to proceed..?

I posted in this mailing list, just because i'm using the meta-ti layer. Please do let me know if there is another one..!

Best,
---------------------------------
Sudhangathan BS
Ph:(+91) 9731-905-205
---------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20130708/c30a95b7/attachment.html>