Kernel does not emit any boot-up messages

Kernel does not emit any boot-up messages

[Hartmut Behrens]

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

Hi All,

A newbie question:

After creating a new bsp for an Overo using the yocto-bsp script and
modifying some kernel config's using menuconfig, I successfully created and
loaded the image (core-image-minimal) onto an SD card and booted it.

However, I do not see the kernel emitting any boot messages. Am I
forgetting to include some recipes?




> OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  512 MiB
> NAND:  512 MiB
> MMC:   OMAP SD/MMC: 0
> *** Warning - bad CRC, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Beagle Rev Ax/Bx
> No EEPROM on expansion board
> Die ID #36be00029ff80000016071640201b009
> Hit any key to stop autoboot:  0
> SD/MMC found on device 0
> reading uEnv.txt
>
> ** Unable to read "uEnv.txt" from mmc 0:1 **
> reading uImage
>
> 3356520 bytes read
> Booting from mmc ...
> ## Booting kernel from Legacy Image at 82000000 ...
>    Image Name:   Linux-3.2.18-rt16-yocto-preempt-
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    3356456 Bytes = 3.2 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
> Yocto (Built by Poky 7.0) 1.2+snapshot-20120828
>  ttyO2
>
> overo login: root
> root@overo:~# uname -a
> Linux overo 3.2.18-rt16-yocto-preempt-rt #4 PREEMPT RT Tue Aug 28 22:36:26
> SAST 2012 armv7l GNU/Linux
>
>

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

Re: Kernel does not emit any boot-up messages

[Gary Thomas]

On 2012-08-29 05:04, Hartmut Behrens wrote:
> Hi All,
>
> A newbie question:
>
> After creating a new bsp for an Overo using the yocto-bsp script and modifying some kernel config's using menuconfig, I successfully created and loaded the image
> (core-image-minimal) onto an SD card and booted it.
>
> However, I do not see the kernel emitting any boot messages. Am I forgetting to include some recipes?
>
>
>     OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
>     OMAP3 Beagle board + LPDDR/NAND
>     I2C:   ready
>     DRAM:  512 MiB
>     NAND:  512 MiB
>     MMC:   OMAP SD/MMC: 0
>     *** Warning - bad CRC, using default environment
>
>     In:    serial
>     Out:   serial
>     Err:   serial
>     Beagle Rev Ax/Bx
>     No EEPROM on expansion board
>     Die ID #36be00029ff80000016071640201b009
>     Hit any key to stop autoboot:  0
>     SD/MMC found on device 0
>     reading uEnv.txt
>
>     ** Unable to read "uEnv.txt" from mmc 0:1 **
>     reading uImage
>
>     3356520 bytes read
>     Booting from mmc ...
>     ## Booting kernel from Legacy Image at 82000000 ...
>         Image Name:   Linux-3.2.18-rt16-yocto-preempt-
>         Image Type:   ARM Linux Kernel Image (uncompressed)
>         Data Size:    3356456 Bytes = 3.2 MiB
>         Load Address: 80008000
>         Entry Point:  80008000
>         Verifying Checksum ... OK
>         Loading Kernel Image ... OK
>     OK
>
>     Starting kernel ...
>
>     Uncompressing Linux... done, booting the kernel.
>
>     Yocto (Built by Poky 7.0) 1.2+snapshot-20120828
>       ttyO2
>
>     overo login: root
>     root@overo:~# uname -a
>     Linux overo 3.2.18-rt16-yocto-preempt-rt #4 PREEMPT RT Tue Aug 28 22:36:26 SAST 2012 armv7l GNU/Linux

Make sure your [U-Boot] bootargs contain 'console=ttyO2,115200'

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Kernel does not emit any boot-up messages

[Khem Raj]

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

What does your. Overo  machine.conf looks like ?

-Khem

On Aug 29, 2012, at 4:04 AM, Hartmut Behrens <hartmut.behrens@gmail.com> wrote:

> Hi All,
> 
> A newbie question:
> 
> After creating a new bsp for an Overo using the yocto-bsp script and modifying some kernel config's using menuconfig, I successfully created and loaded the image (core-image-minimal) onto an SD card and booted it.
> 
> However, I do not see the kernel emitting any boot messages. Am I forgetting to include some recipes?
> 
> 
>  
> OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  512 MiB
> NAND:  512 MiB
> MMC:   OMAP SD/MMC: 0
> *** Warning - bad CRC, using default environment
> 
> In:    serial
> Out:   serial
> Err:   serial
> Beagle Rev Ax/Bx
> No EEPROM on expansion board
> Die ID #36be00029ff80000016071640201b009
> Hit any key to stop autoboot:  0 
> SD/MMC found on device 0
> reading uEnv.txt
> 
> ** Unable to read "uEnv.txt" from mmc 0:1 **
> reading uImage
> 
> 3356520 bytes read
> Booting from mmc ...
> ## Booting kernel from Legacy Image at 82000000 ...
>    Image Name:   Linux-3.2.18-rt16-yocto-preempt-
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    3356456 Bytes = 3.2 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
> 
> Starting kernel ...
> 
> Uncompressing Linux... done, booting the kernel.
> 
> Yocto (Built by Poky 7.0) 1.2+snapshot-20120828 
>  ttyO2
> 
> overo login: root
> root@overo:~# uname -a
> Linux overo 3.2.18-rt16-yocto-preempt-rt #4 PREEMPT RT Tue Aug 28 22:36:26 SAST 2012 armv7l GNU/Linux
> 
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

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