IMX6Q-SDB NXP L5 core Android Image got Hangup

kumarasamypalan — Wed, 12 Apr 2017 04:02:06 GMT

Hello All,

I flashed L5 core image after Linux kernel got hang-up. Any one can help me to come out this problem .

Serial Port Logs:

U-Boot 2014.04-00201-g9d7bf9b (May 05 2015 - 10:14:54)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
CPU:   Temperature 65 C, calibration data: 0x53d4a47d
Reset cause: POR
Board: MX6-SabreSD
I2C:   ready
DRAM: 1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
No panel detected: default to Hannstar-XGA
Display: Hannstar-XGA (1024x768)
In:    serial
Out:   serial
Err:   serial
Found PFUZE100 deviceid=10,revid=21
check_and_clean: reg 0, flag_set 0
Fastboot: Normal
flash target is MMC:1
Net:   FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
=>
=>
=> editenv mmcargs
edit: setenv bootargs console=${console},${baudrate} ${smp} video=mxcfb1:off root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24
=> saveenv
Saving Environment to MMC...
Writing to MMC(1)... done
=> boot
booti mmc1
kernel   @ 14008000 (6819456)
ramdisk @ 15000000 (725617)
fdt      @ 14f00000 (51263)
kernel cmdline:
        use boot.img command line:
        console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off vmalloc=400M androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=freescale cma=384M androidboot.serialno=051fb9d4e3174029
switch to ldo_bypass mode!
   Using Device Tree in place at 14f00000, end 14f0f83e

Starting kernel ...

Printenv Logs:

U-Boot 2014.04-00201-g9d7bf9b (May 05 2015 - 10:14:54)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
CPU:   Temperature 66 C, calibration data: 0x53d4a47d
Reset cause: POR
Board: MX6-SabreSD
I2C:   ready
DRAM: 1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
No panel detected: default to Hannstar-XGA
Display: Hannstar-XGA (1024x768)
In:    serial
Out:   serial
Err:   serial
Found PFUZE100 deviceid=10,revid=21
check_and_clean: reg 0, flag_set 0
Fastboot: Normal
flash target is MMC:1
Net:   FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
=> printenv
baudrate=115200
bootcmd=booti mmc1
bootdelay=1
ethact=FEC
ethaddr=00:04:9f:04:18:5d
ethprime=FEC
fastboot_dev=mmc1
fdt_high=0xffffffff
initrd_high=0xffffffff
loadaddr=0x12000000
mmcargs=setenv bootargs console=${console},${baudrate} ${smp} video=mxcfb1:off root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24
splashpos=m,m

Environment size: 357/8188 bytes

Re: IMX6Q-SDB NXP L5 core Android Image got Hangup

joanxie — Mon, 17 Apr 2017 08:30:49 GMT

try to set the hdmi again:

Booting with single display: HDMI display
In the U-Boot prompt, set the U-Boot environment variables as shown below:
U-Boot > setenv bootcmd boota mmc2
U-Boot > setenv bootargs console=ttymxc0,115200 androidboot.console=ttymxc0 consoleblank=0
vmalloc=256M init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb1:off
video=mxcfb2:off video=mxcfb3:off androidboot.hardware=freescale cma=384M
U-Boot > saveenv
With the settings above, the Android platform does not start the shell console. It enables the default Android selinux and
dm_verity security features, which restrict users to change the system and detect the system's information. To avoid this,
"androidboot.selinux=disabled" and "androidboot.dm_verity=disabled" need to be appended to the U-Boot's bootargs. Boot
environment variables are as follows:
U-Boot > setenv bootcmd boota mmc2
U-Boot > setenv bootargs console=ttymxc0,115200 androidboot.console=ttymxc0 consoleblank=0
vmalloc=256M init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb1:off
video=mxcfb2:off video=mxcfb3:off androidboot.hardware=freescale cma=384M
androidboot.selinux=disabled androidboot.dm_verity=disabled
U-Boot > saveenv

i.MX Processors中的主题 IMX6Q-SDB NXP L5 core Android Image got Hangup

IMX6Q-SDB NXP L5 core Android Image got Hangup

Re: IMX6Q-SDB NXP L5 core Android Image got Hangup