Incomplete boot of Yocto imx28evk core-image-minimal

[cmcqueen1975]

I'm building Yocto core-image-minimal for imx28evk, from denzil branch. It's building successfully. Then I'm trying to boot from SD card. As in a previous group post, it turns out that I must set the U-Boot parameter console=ttyAMA0.

Once I've done that, it starts to boot but doesn't get as far as a login prompt.

U-Boot 2012.04.01-00059-g4e6e824 (Sep 03 2012 - 13:54:58)

Freescale i.MX28 family at 454 MHz
BOOT:  SSP SD/MMC #0, 3V3
DRAM:  128 MiB
MMC:   MXS MMC: 0
In:    serial
Out:   serial
Err:   serial
Net:   FEC0, FEC1
Hit any key to stop autoboot:  0
reading boot.scr

** Unable to read "boot.scr" from mmc 0:2 **
reading uImage

2574616 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 42000000 ...
   Image Name:   Linux-2.6.35.3-11.09.01+yocto-20
   Created:      2012-09-03   3:20:45 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2574552 Bytes = 2.5 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.35.3-11.09.01+yocto-20120903 (craigm@fw-linux) (gcc version 4.6.4 20120303 (prerelease) (GCC) ) #1 PREEMPT Mon Sep 3 13:20:35 EST 2012
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Freescale MX28EVK board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttyAMA0,115200 root=/dev/mmcblk0p3 rw rootfstype=ext3 rootwait
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 124260k/124260k available, 6812k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xfde00000 - 0xffe00000   (  32 MB)
    vmalloc : 0xc8800000 - 0xf0000000   ( 632 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0030000   ( 160 kB)
      .text : 0xc0030000 - 0xc0503000   (4940 kB)
      .data : 0xc0504000 - 0xc05424a0   ( 250 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:288
Console: colour dummy device 80x30
console [ttyAMA0] enabled
Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)
pid_max: default: 32768 minimum: 301
Security Framework initialized
SELinux:  Initializing.
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
regulator: core version 0.5
NET: Registered protocol family 16
regulator: vddd: 800 <--> 1575 mV at 1500 mV fast normal
regulator: vdddbo: 800 <--> 1575 mV fast normal
regulator: vdda: 1500 <--> 2275 mV at 1800 mV fast normal
vddio = 3380000, val=10
regulator: vddio: 2880 <--> 3680 mV at 3380 mV fast normal
regulator: overall_current: fast normal
regulator: vbus5v:
regulator: mxs-duart-1: fast normal
regulator: mxs-bl-1: fast normal
regulator: mxs-i2c-1: fast normal
regulator: mmc_ssp-1: fast normal
regulator: mmc_ssp-2: fast normal
regulator: charger-1: fast normal
regulator: power-test-1: fast normal
regulator: cpufreq-1: fast normal
i.MX IRAM pool: 124 KB@0xc8820000
usb DR wakeup device is registered
IMX usb wakeup probe
audit: cannot initialize inotify handle
bio: create slab <bio-0> at 0
SCSI subsystem initialized
Freescale USB OTG Driver loaded, $Revision: 1.55 $
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource mxs clock source
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Bus freq driver module loaded
IMX usb wakeup probe
usb h1 wakeup device is registered
mxs_cpu_init: cpufreq init finished

Any suggestions on where it's stopping, why it's stopping, or how to go about debugging the boot procedure?

[Otavio Salvador]

On Mon, Sep 3, 2012 at 9:39 PM, cmcqueen1975
<google...@craig.mcqueen.id.au> wrote:
...

> mxs_cpu_init: cpufreq init finished
>
> Any suggestions on where it's stopping, why it's stopping, or how to go
> about debugging the boot procedure?

Seems mmc has not been found.

--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br

[Fabio Estevam]

On Mon, Sep 3, 2012 at 9:39 PM, cmcqueen1975
<google...@craig.mcqueen.id.au> wrote:

> IMX usb wakeup probe
> usb h1 wakeup device is registered
> mxs_cpu_init: cpufreq init finished
>
> Any suggestions on where it's stopping, why it's stopping, or how to go
> about debugging the boot procedure?

Looks like you are missing this patch:
https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-kernel/linux/linux-imx-2.6.35.3/mx28-removecpufreq.patch

Regards,

Fabio Estevam

[cmcqueen1975]

On Wednesday, 5 September 2012 06:51:53 UTC+10, Fabio Estevam wrote:

Looks like you are missing this patch:
https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-kernel/linux/linux-imx-2.6.35.3/mx28-removecpufreq.patch

With that advice, I can now boot to a login prompt on the imx28evk. Thank you for your help! It has been most valuable.

I added the reference to the patch as follows:

diff --git a/recipes-kernel/linux/linux-imx_2.6.35.3.bb b/recipes-kernel/linux/l
index c487cbc..64b9915 100644
--- a/recipes-kernel/linux/linux-imx_2.6.35.3.bb
+++ b/recipes-kernel/linux/linux-imx_2.6.35.3.bb
@@ -29,6 +29,7 @@ SRC_URI_append_mxs = " \
            file://mx23-do-not-use-safe-write.patch \
            file://mx23-dont-mange-IRQ_VDDA_BRNOUT.patch \
            file://mxs-duart-use-ttyAMA-for-device-name.patch \
+           file://mx28-removecpufreq.patch \
 "
 
 SRC_URI_append_mx5 = " \

But I'm not sure if that's the best way or place to do it. I'm fairly new to Yocto etc.

[Fabio Estevam]

On Wed, Sep 5, 2012 at 1:41 AM, cmcqueen1975
<google...@craig.mcqueen.id.au> wrote:

> With that advice, I can now boot to a login prompt on the imx28evk. Thank
> you for your help! It has been most valuable.

Glad it works.

>
> I added the reference to the patch as follows:
>
> diff --git a/recipes-kernel/linux/linux-imx_2.6.35.3.bb
> b/recipes-kernel/linux/l
> index c487cbc..64b9915 100644
> --- a/recipes-kernel/linux/linux-imx_2.6.35.3.bb
> +++ b/recipes-kernel/linux/linux-imx_2.6.35.3.bb
> @@ -29,6 +29,7 @@ SRC_URI_append_mxs = " \
> file://mx23-do-not-use-safe-write.patch \
> file://mx23-dont-mange-IRQ_VDDA_BRNOUT.patch \
> file://mxs-duart-use-ttyAMA-for-device-name.patch \
> + file://mx28-removecpufreq.patch \

Hmm, actually you don't need to apply this manually. The patch I
refereced is already part of meta-fsl-arm.

Maybe you missed a 'git pull' to update the tree?

It should work out-of-the box.

Regards,

Fabio Estevam

[cmcqueen1975]

The patch file is there, but I don't see it included in the kernel recipe. See:

https://github.com/Freescale/meta-fsl-arm/blob/denzil/recipes-kernel/linux/linux-imx_2.6.35.3.bb
https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-kernel/linux/linux-imx_2.6.35.3.bb

I don't see the patch referred to in there. Can you show me where it is?

Thanks,
Craig McQueen

[Otavio Salvador]

Hello,

My fault; I mistakenly dropped it when cleaning the recipe.

I am posting a patch to readd it. Please give it a try and ack it.

[cmcqueen1975]

I've tried the patch, and it looks fine to me, and boots properly. Thanks.

Regards,
Craig McQueen

[Otavio Salvador]

On Sun, Sep 9, 2012 at 9:27 PM, cmcqueen1975

I applied it.

Thanks by confirming it works.