[U-Boot] i.Mx6q u-boot stuck

[Fausto Sessego]

Ok.

The Kernel doesn't start.

U-Boot 2016.07 (May 24 2017 - 17:11:18 +0200)

CPU:   Freescale i.MX6Q rev1.2 at 792MHz
CPU:   Industrial temperature grade (-40C to 105C) at 20C
Reset cause: POR
Board: i.MX6Q TIBIDABO
Support: http://www.infomob.it/
I2C:   ready
DRAM:  gd->ram_size: 2147483648
DRAM test not implemented!
2 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Error: FEC address not set.

Hit any key to stop autoboot:  0
reading imx6q-tibidabo.dtb
29640 bytes read in 22 ms (1.3 MiB/s)
reading uImage
6621928 bytes read in 324 ms (19.5 MiB/s)
## Booting kernel from Legacy Image at 12000000 ...
   Image Name:   Linux-4.1.38
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6621864 Bytes = 6.3 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Can it depend on u-boot version?

I'm using u-boot 2016.07 and kernel 4.1-1.0.x.

I get u-boot and kernel directly from yocto, so i think the matching is
right.

I tried many procedures but i did'nt found any solution.

Thanks

------------------------------
*Ing. Fausto Sessego*
*R&D Hardware & Software Engineer*

info
mob
>
*Tecnologie Wireless per la logistica e la sicurezza*
*address:* Parco scientifico e tecnologico della Sardegna, Edificio 1 Loc.
Piscinamanna - 09010 Pula (CA)
<https://www.google.it/maps/place/Sardegna+Ricerche/@38.9899811,8.9280376,17z/data=!3m1!4b1!4m2!3m1!1s0x12e7274e0b4c4191:0x1a9e7f06456bbd3>
*phone:* +39 070 92432952
*email:* fausto.sessego at infomob.it
*skype:* fausto.sessego.infomob
*web:* www.infomob.it

2017-05-05 13:56 GMT+02:00 Fabio Estevam <festevam at gmail.com>:

>
>
> On Fri, May 5, 2017 at 8:51 AM, Fausto Sessego <fausto.sessego at infomob.it>
> wrote:
>
>> Ok.
>>
>> I have the problem the Kernel Stucks at startup "Starting Kernel .... "
>>
>> Could it depend on boot configuration (the macro  CONFIG_MMCROOT) ?
>>
>
> No, the rootfs will be mounted at a much later stage.
>
>