AnsweredAssumed Answered

i.MX6 Sabreauto u-boot 2014.04 crash while loading the kernel image of type uImage.

Question asked by khandavalli on Mar 23, 2015
Latest reply on Mar 24, 2015 by igorpadykov

Hi All,


I am facing following crash while trying to boot kernel uImage:


U-Boot 2014.04-08643-gbec78ae-dirty (Mar 23 2015 - 18:32:51)


CPU:   Freescale i.MX6Q rev1.2 at 792 MHz

CPU:   Temperature 35 C, calibration data: 0x5c75227d

Reset cause: POR

Board: MX6-Sabreauto revA

I2C:   ready

DRAM:  2 GiB

NAND:  0 MiB


No panel detected: default to Hannstar-XGA

Display: Hannstar-XGA (1024x768)

In:    serial

Out:   serial

Err:   serial

Found PFUZE100! deviceid=10,revid=12

mmc1 is current device

Net:   FEC [PRIME]

Normal Boot

Hit any key to stop autoboot:  0

5587480 bytes read in 686 ms (7.8 MiB/s)

49698 bytes read in 47 ms (1 MiB/s)

## Booting kernel from Legacy Image at 12000000 ...

   Image Name:   Linux-3.10.72+

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    5587416 Bytes = 5.3 MiB

   Load Address: 12000000

   Entry Point:  12000000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 18000000

   Booting using the fdt blob at 0x18000000

   XIP Kernel Image ... OK

   Using Device Tree in place at 18000000, end 1800f221

arun changes

arunk hard-coding ldo_bypass

switch to ldo_bypass mode!


Starting kernel ...


undefined instruction

pc : [<12000008>]          lr : [<8ff473a8>]

sp : 8f542b10  ip : 0000000c     fp : 00000000

r10: 8f85cbac  r9 : 8f542efc     r8 : 00000000

r7 : 00000000  r6 : 12000000     r5 : 8ffa7da8  r4 : 00000000

r3 : 0000c222  r2 : 18000000     r1 : 00000dc9  r0 : 8f542fac

Flags: nZCv  IRQs off  FIQs off  Mode SVC_32

Resetting CPU ...


resetting ...


U-boot branch: imx_v2014.04_3.10.53_1.1.0_ga

Kernel: 3.10.72 (3.19.53_1.1.0_ga + Stable Updates)


I am successfully able to boot the zImage. The problem is only when trying to boot uImage.


Everything works fine when I use u-boot from branch imx_2014.04_3.10.31_1.1.0_beta branch. I have tried to root-cause the issue, I have tracked down to one-commit "404fd02 ENGR00326277-1: imx6: ldo_bypass: fix VDDARM voltage setting violate datasheet",  which might be causing the issue. Can you please help further debugging and root-causing the issue.