imx6q starting kernel hangs

taowang1 · ‎06-27-2016

Hi，all：

I encounter one problem recently.After power on, after uboot finishes, the kernel hangs..

I also try the method(chapter 1.1 and 1.2 ) by: Common Problems - Linux kernel doesnt boot - RidgeRun Developer Connection

but problem still exists.

Because the uboot is supplied by the third parner ,I don't know why the buled words occurs.

The platform information is as follows:

cpu: imx6q

board: customized board based on sabreAuto

os: android kk4.4.2_1.0.0,kernel:Linux 3.0.35

The following is the log(board is marked manualy on purpose ):

U-Boot 2014.04-00024-g5895096 (Apr 27 2016 - 23:57:08)

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

CPU: Temperature 16 C, calibration data: 0x5744d47d

Reset cause: POR

Board: XXXXXXXX Board ==>(note:XXXX is marked manually on purpose)

I2C: ready

DRAM: 2 GiB

MMC: FSL_SDHC: 0, FSL_SDHC: 1

SF: Detected S25FL164A with page size 256 Bytes, erase size 64 KiB, total 8 MiB

*** Warning - bad CRC, using default environment

No panel detected: default to Hannstar-XGA

Display: Hannstar-XGA (1024x768)

In: serial

Out: serial

Err: serial

unsupported boot devices

check_and_clean: reg 0, flag_set 0

Recovery key pressed

Fastboot: Recovery command file founded!

Unsupported bootup device for recovery: dev: 5

flash target is MMC:1

Net: Board Net Initialization Failed

No ethernet found.

Normal Boot

Hit '>' key to stop autoboot: 0

mmc1(part 0) is current device

MMC read: dev # 1, block # 2048, count 14336 ... 14336 blocks read: OK

booti 0x12000000

kernel @ 10808000 (4753788)

ramdisk @ 11800000 (499839)

kernel cmdline:

use boot.img command line:

console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=lc d,AT070-WVGA,if=RGB24,bpp=32 video=mxcfb1:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 video=mxcfb2:off fbme m=10M,28M fec_mac=1E:ED:19:27:1A:B3 androidboot.hardware=freescale androidboot.serialno=202091d4e3174 a01

No gpc device node -9, force to ldo-enable.

Starting kernel ...

waiting for your reply,Thanks!

taowang1 · ‎07-11-2016

Hi,all,

I knew the problem resides in the gpc,If I delete the gpc node in device tree for the image of the third partner

The same phenomenon occurs。The gpc node is defined as follows:

			gpc@020dc000 {
				compatible = "fsl,imx6q-gpc";
				reg = <0x20dc000 0x4000>;
				interrupts = <0x0 0x59 0x4 0x0 0x5a 0x4>;
				clocks = <0x2 0x7a 0x2 0x4a 0x2 0x79 0x2 0x1a 0x2 0x8f 0x2 0xa8 0x2 0x3e>;
				clock-names = "gpu3d_core", "gpu3d_shader", "gpu2d_core", "gpu2d_axi", "openvg_axi", "vpu_axi", "ipg";
				pu-supply = <0x12>;
				fsl,cpu_pupscr_sw2iso = <0xf>;
				fsl,cpu_pupscr_sw = <0xf>;
				fsl,cpu_pdnscr_iso2sw = <0x1>;
				fsl,cpu_pdnscr_iso = <0x1>;
			};

If I delete the "pu-supply = <0x12>",the kernel can walk to "atmel_mxt_ts 2-004a: Interrupt triggered but zero messages",so,android can't work.

so,where is the problem?can anybody give any ideas?

aravinthkumarja · ‎06-27-2016

Hi taowang1,

Can you try following bootargs,

bootcmd=booti mmc1

loadaddr=0x80800000

stdout=serial

stdin=serial

stderr=serial

Regards,

Aravinth

taowang1 · ‎06-27-2016

Hi,aravinthkumar jayaprakasam

Thank you for your reply and suggestions.

The following is the result :

=> setenv bootcmd 'booti mmc1'

=> setenv loadaddr 0x80800000

=> setenv stdout serial

=> setenv stdin serial

=> setenv stderr serial

=> pri

baudrate=115200

bootcmd=booti mmc1

bootcmd_mfg=run mfgtool_args;bootz ${loadaddr} ${initrd_addr} ${fdt_addr};

bootcmd_mmc=mmc dev ${mmcdev}; mmc read ${loadaddr} 0x800 0x3800; booti ${loadaddr}

bootdelay=0

fastboot_dev=mmc1

fdt_high=0xffffffff

initrd_addr=0x12C00000

initrd_high=0xffffffff

loadaddr=0x80800000

mfgtool_args=setenv bootargs console=ttymxc0,115200 rdinit=/linuxrc g_mass_storage.stall=0 g_mass_storage.removable=1 g_mass_storage.idVendor=0x066F g_mass_storage.idProduct=0x37FF g_mass_storage.iSerialNumber="" enable_wait_mode=off

mmcdev=1

splashpos=m,m

stderr=serial

stdin=serial

stdout=serial

Environment size: 642/8188 bytes

=> boot

booti mmc1

can't find partition: boot, dump the partition table

ptn 0 name=bootloader_nor start=0 len=393216 0x00000000~0x00060000

ptn 1 name=kernel_nor start=393216 len=3145728 0x00060000~0x00360000

ptn 2 name=dtb_nor start=3538944 len=262144 0x00360000~0x003A0000

ptn 3 name=recovery_nor start=3801088 len=4194304 0x003A0000~0x007A0000

ptn 4 name=burn_nor start=0 len=8388608 0x00000000~0x00800000

ptn 5 name=mbr start=0 len=1 0x000000000~0x000000200

ptn 6 name=bootloader start=2 len=2046 0x000000400~0x000100000

ptn 7 name=bootimg start=2048 len=14336 0x000100000~0x000800000

ptn 8 name=boottestsuit start=16384 len=6144 0x000800000~0x000B00000

ptn 9 name=bootparams start=22528 len=2048 0x000B00000~0x000C00000

ptn 10 name=bootreserved start=24576 len=8192 0x000C00000~0x001000000

ptn 11 name=recovery start=32768 len=32768 0x001000000~0x002000000

ptn 12 name=sdcard start=65536 len=18874368 0x002000000~0x242000000

ptn 13 name=system start=18939905 len=2097151 0x242000200~0x282000000

ptn 14 name=data start=21037057 len=2097151 0x282000200~0x2C2000000

ptn 15 name=cache start=23134209 len=262143 0x2C2000200~0x2CA000000

ptn 16 name=private start=23396353 len=4194303 0x2CA000200~0x34A000000

ptn 17 name=keyinfo start=27590657 len=32767 0x34A000200~0x34B000000

ptn 18 name=reserved start=27623425 len=131071 0x34B000200~0x34F000000

ptn 19 name=map start=27754497 len=33316863 0x34F000200~0x747C00000

booti: cannot find 'boot' partition

fastboot is in init......