[meta-ti] booting 2.6.32 kernel and rootfs
Frazer, Will
will.frazer at eurotech.com
Tue Jul 9 07:55:43 PDT 2013
It's still likely that the console is not right. Personally I'd try a few other device nodes. As Robert mentioned, it's probably not using the /dev/ttyO? nodes because of the kernel version, so ttyS0 onwards would be what I would be looking at first.
Another possibility is to network boot Linux (i.e. TFTP the kernel then use NFS for the rootfs) then try to figure it out from that end. At least you may be able to see the serial port device nodes and work backwards.
Worse case try cross reference the serial port addresses on your hardware against what is being setup by UBoot & the kernel.
regards,
Will
Will Frazer | EUROTECH
From: Sudhangathan B S [mailto:sudhangathan at gmail.com]
Sent: 09 July 2013 03:24
To: Frazer, Will; christopher.pow at honeywell.com; robertcnelson at gmail.com
Cc: meta-ti at yoctoproject.org
Subject: Re: [meta-ti] booting 2.6.32 kernel and rootfs
I tried ttyO0 and ttyS2.. for some reason both did not work.. I am getting the same output, i.e. it freezes after "...... done booting the kernel"
I made these changes through the file uEnv.txt, and therefore the error ** Unable to read "uEnv.txt" from mmc 0:1 ** doesn't come anymore..!
I was also reading http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux and also enabled "CONFIG_DEBUG_LL" in the config file using the bitbake -c menuconfig virtual/kernel command, but that did not take much affect.
I have pasted below the console output and the uEnv.txt
******Console Start**********************
********************************************
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
I2C read: I/O error
Unrecognized expansion board: 0
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
826 bytes read
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
reading uImage
3147916 bytes read
Booting from mmc (uEnv.txt configuration) ...
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-2.6.32
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3147852 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.
******Console End
***************************
uEnv.txt
********uEnv.txt start
*************************
usbethaddr=00:E0:4C:53:44:58
ethaddr=00:E0:4C:53:44:58
autoload=no
hostname=BBxM
serverip=192.168.0.41
ipaddr=192.168.0.141
netmask=255.255.255.0
getway=192.168.0.1
console=ttyO2,115200n8 -- had chanhed this to ttyO0 and ttyS2 too...! Everything else appears to be ok.
mpurate=auto
buddy=none
vram=12M
dvimode=640x480MR-16 at 60
defaultdisplay=dvi
loadaddr=0x80200000
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait
ip=192.168.0.141:192.168.0.41:192.168.0.1:255.255.255.0:BBxM:eth0:off
mmcargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} buddy=${buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype} ip=${ip}
mmcboot=echo Booting from mmc (uEnv.txt configuration) ...; run mmcargs; bootm ${loadaddr}
loaduimagefat=fatload mmc ${mmcdev} ${loadaddr} uImage
uenvcmd=run loaduimagefat; run mmcboot
********uEnv.txt end
*************************
How can I proceed..?
Meanwhile i will try the dumping the uboot memory as printed by the grep printk_buf System.map as told by the Christopher Pow.
Thanks so much for looking into this..!!! :) :)
---------------------------------
Sudhangathan BS
Ph:(+91) 9731-905-205
---------------------------------
On Mon, Jul 8, 2013 at 11:28 PM, Robert Nelson <robertcnelson at gmail.com<mailto:robertcnelson at gmail.com>> wrote:
On Fri, Jul 5, 2013 at 11:16 PM, Sudhangathan B S
<sudhangathan at gmail.com<mailto:sudhangathan at gmail.com>> wrote:
> 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..?
Back in the 2.6.32 days, the "omap" serial driver did not exist.. So
if your still setting up console as /dev/ttyO2 change it to
/dev/ttyS2..
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20130709/db921ac3/attachment.html>
More information about the meta-ti
mailing list