All of lore.kernel.org
 help / color / mirror / Atom feed
* booting 2.6.32 kernel and rootfs
@ 2013-07-06  4:16 Sudhangathan B S
  2013-07-08 17:24 ` Frazer, Will
  2013-07-08 17:58 ` Robert Nelson
  0 siblings, 2 replies; 6+ messages in thread
From: Sudhangathan B S @ 2013-07-06  4:16 UTC (permalink / raw)
  To: meta-ti

[-- Attachment #1: Type: text/plain, Size: 2189 bytes --]

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
---------------------------------

[-- Attachment #2: Type: text/html, Size: 2950 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: booting 2.6.32 kernel and rootfs
  2013-07-06  4:16 booting 2.6.32 kernel and rootfs Sudhangathan B S
@ 2013-07-08 17:24 ` Frazer, Will
  2013-07-08 17:40   ` Pow, Christopher (SWCOE)
  2013-07-08 17:58 ` Robert Nelson
  1 sibling, 1 reply; 6+ messages in thread
From: Frazer, Will @ 2013-07-08 17:24 UTC (permalink / raw)
  To: meta-ti

[-- Attachment #1: Type: text/plain, Size: 2845 bytes --]

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@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Sudhangathan B S
Sent: 06 July 2013 05:16
To: meta-ti@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
---------------------------------

[-- Attachment #2: Type: text/html, Size: 9538 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: booting 2.6.32 kernel and rootfs
  2013-07-08 17:24 ` Frazer, Will
@ 2013-07-08 17:40   ` Pow, Christopher (SWCOE)
  0 siblings, 0 replies; 6+ messages in thread
From: Pow, Christopher (SWCOE) @ 2013-07-08 17:40 UTC (permalink / raw)
  To: Frazer, Will, meta-ti

[-- Attachment #1: Type: text/plain, Size: 3882 bytes --]

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@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Frazer, Will
Sent: Monday, July 08, 2013 12:24 PM
To: meta-ti@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@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Sudhangathan B S
Sent: 06 July 2013 05:16
To: meta-ti@yoctoproject.org<mailto:meta-ti@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
---------------------------------

[-- Attachment #2: Type: text/html, Size: 15711 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: booting 2.6.32 kernel and rootfs
  2013-07-06  4:16 booting 2.6.32 kernel and rootfs Sudhangathan B S
  2013-07-08 17:24 ` Frazer, Will
@ 2013-07-08 17:58 ` Robert Nelson
  2013-07-09  2:23   ` Sudhangathan B S
  1 sibling, 1 reply; 6+ messages in thread
From: Robert Nelson @ 2013-07-08 17:58 UTC (permalink / raw)
  To: Sudhangathan B S; +Cc: meta-ti

On Fri, Jul 5, 2013 at 11:16 PM, Sudhangathan B S
<sudhangathan@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/


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: booting 2.6.32 kernel and rootfs
  2013-07-08 17:58 ` Robert Nelson
@ 2013-07-09  2:23   ` Sudhangathan B S
  2013-07-09 14:55     ` Frazer, Will
  0 siblings, 1 reply; 6+ messages in thread
From: Sudhangathan B S @ 2013-07-09  2:23 UTC (permalink / raw)
  To: will.frazer, christopher.pow, robertcnelson; +Cc: meta-ti

[-- Attachment #1: Type: text/plain, Size: 6339 bytes --]

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_Linuxand
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@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@gmail.com>wrote:

> On Fri, Jul 5, 2013 at 11:16 PM, Sudhangathan B S
> <sudhangathan@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/
>

[-- Attachment #2: Type: text/html, Size: 17660 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: booting 2.6.32 kernel and rootfs
  2013-07-09  2:23   ` Sudhangathan B S
@ 2013-07-09 14:55     ` Frazer, Will
  0 siblings, 0 replies; 6+ messages in thread
From: Frazer, Will @ 2013-07-09 14:55 UTC (permalink / raw)
  To: Sudhangathan B S, christopher.pow, robertcnelson; +Cc: meta-ti

[-- Attachment #1: Type: text/plain, Size: 7124 bytes --]

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@gmail.com]
Sent: 09 July 2013 03:24
To: Frazer, Will; christopher.pow@honeywell.com; robertcnelson@gmail.com
Cc: meta-ti@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@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@gmail.com<mailto:robertcnelson@gmail.com>> wrote:
On Fri, Jul 5, 2013 at 11:16 PM, Sudhangathan B S
<sudhangathan@gmail.com<mailto:sudhangathan@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/


[-- Attachment #2: Type: text/html, Size: 28925 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-07-09 14:56 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-07-06  4:16 booting 2.6.32 kernel and rootfs Sudhangathan B S
2013-07-08 17:24 ` Frazer, Will
2013-07-08 17:40   ` Pow, Christopher (SWCOE)
2013-07-08 17:58 ` Robert Nelson
2013-07-09  2:23   ` Sudhangathan B S
2013-07-09 14:55     ` Frazer, Will

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.