imx6dl, "Starting kernel ..." hangs on SD3 with kernel 3.14

cancel
Showing results for 
Search instead for 
Did you mean: 

imx6dl, "Starting kernel ..." hangs on SD3 with kernel 3.14

616 Views
romaindubois
Contributor I

Hi everyone !

I'm working on a custom board (cubox like) with my IMX6DL.

My kernel is from Naoki Aizu (3.14.14,  GitHub - n-aizu/linux-linaro-stable-mx6: Linux kernel repository merging linux-linaro-stable and fre... ), and my low level debug options are enabled.

 

My problem is that I can't boot from a µSD on slot SD3, I get the (classic) "Starting kernel ... " hanging :

mmc0 is current device mmc_init: 0, time 84 ** Unable to read file /boot.scr ** 131 bytes read in 8 ms (15.6 KiB/s) Importing environment from mmc0 ... 4612368 bytes read in 219 ms (20.1 MiB/s) Booting from mmc ... 34901 bytes read in 16 ms (2.1 MiB/s) Loaded board.dtb Booting zImage Kernel image @ 0x10800000 [ 0x000000 - 0x466110 ] ## Flattened Device Tree blob at 18000000   Booting using the fdt blob at 0x18000000   Using Device Tree in place at 18000000, end 1800b854  Starting kernel ...

 

However I am not really understanding this error as :

- With my image, when removing my uboot patch (making me boot on SD2 instead of SD3) and using fused microsom to boot on SD2, it boots.

- With my image, when applying my uboot patch (making me boot on SD3 instead of SD2) and using fused microsom to boot on SD3, it does not boots.

- Coworker is using Boundary kernel 3.10.17 (same uboot, same patch, same device tree, same µSD, same uEnv), and it works (on SD3 with patch, on SD2 without).

 

 

Here is the boot log from my coworker :

mmc0 is current device ** Unable to read file /boot.scr ** 118 bytes read in 7 ms (15.6 KiB/s) Importing environment from mmc0 ... 4411512 bytes read in 209 ms (20.1 MiB/s) Booting from mmc ... 47250 bytes read in 17 ms (2.7 MiB/s) Loaded board.dtb Booting zImage Kernel image @ 0x10800000 [ 0x000000 - 0x435078 ] ## Flattened Device Tree blob at 18000000    Booting using the fdt blob at 0x18000000    Using Device Tree in place at 18000000, end 1800e891  Starting kernel ...  Booting Linux on physical CPU 0x0 Linux version 3.10.17-1.0.2_ga+yocto+g4da158a (gcc version 4.9.1 (GCC) ) #1 SMP Thu 6 CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache ... (booting)

 

So I am a bit confused toward what to do now, my guess is that the kernel is responsible for that mistake

 

Would you have any Idea why I would get such an error?

 

I thank you for your time,

 

Romain Dubois

Original Attachment has been moved to: Aizu_defconfig.zip

Original Attachment has been moved to: Boundary_defconfig.zip

Labels (3)
0 Kudos
3 Replies

57 Views
Yuri
NXP TechSupport
NXP TechSupport

Hello,

  Please try to get more information about the issue, using

recommendations in the following thread.

Stuck up at 'starting kernel'


Have a great day,
Yuri

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

57 Views
romaindubois
Contributor I

Thank you for your answer,

Unfortunately executing the memory dump in search of __log_buf did not give me any kind of infos .. (although it is entirely possible that i calculated the wrong addresses, i tried several plausible locations).

0 Kudos

57 Views
Yuri
NXP TechSupport
NXP TechSupport

Hello,

You may create request, so that I can forward You some recommendations

about JTAG Linux debugging.

How to submit a new question for NXP Support  

Regards,

Yuri.

0 Kudos