imx6dl run mfg kernel hung: Starting kernel ...

cancel
Showing results for 
Search instead for 
Did you mean: 

imx6dl run mfg kernel hung: Starting kernel ...

385 Views
Contributor I

BSP: android_M6.0.1_2.1.0,   android6.0.1-r22

ref platform: imx6dl-sabresd, uboot version: 2015.4, kernel: 4.1.15

our board doesn't have PMIC PFUZE100, we used imx6dl internal LDO.

our board can run the BSP Linux 3.0.101, and then we want to update to android6.

I undefine CONFIG_LDO_BYPASS_CHECK in uboot, so uboot is running OK from downloading by mfgtool.

Then i use make imx_v7_mfg_defconfig to build my mfg kernel, replace mfgtools zImage, the uart output information below:

 

U-Boot 2015.04-dirty (Nov 11 2017 - 17:20:17)

CPU: Freescale i.MX6DL rev1.2 at 792 MHz
CPU: Temperature 43 C
Reset cause: POR
Board: MX6-SabreSD
I2C: ready
DRAM: 1 GiB
board_init: setup_i2c(1) ret=0
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
flash target is MMC:2
Bad partition index:2 for partition:recovery
Bad partition index:5 for partition:system
Bad partition index:4 for partition:data
Net: FEC [PRIME]
Error: FEC address not set.

Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: run mfgtool_args;bootz ${loadaddr} ${initrd_addr} ${fdt_addr};
Hit any key to stop autoboot: 0
Kernel image @ 0x12000000 [ 0x000000 - 0x851c30 ]
## Loading init Ramdisk from Legacy Image at 12c00000 ...
Image Name: fsl-image-mfgtool-initramfs-imx6
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7565864 Bytes = 7.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK

Starting kernel ...

now, i open CONFIG_EARLY_PRINTK in kernel, i got one more line in console:

Uncompressing Linux... done, booting the kernel.

Labels (1)
0 Kudos
4 Replies

59 Views
Contributor II

Hello Gavin,

        Have solved this issue? I have found the same problem.

0 Kudos

61 Views
Contributor I

Thanks.

 更换官方的image,故障现象依旧.

综合来看,已经进入kernel的控制之下,并执行了代码,就是解压内核部分的那行提示,显示内核已经成功解压完成,在执行kernel的初始化过程时出现了问题,初步分析应该在两个地方:

1  uboot传递进来的参数不对, 根据附件的环境变量看,这里出问题的概率比较小

2  初始化dts的时候出错,也就是dts配置不对

第一次接触dts,很多地方不是很清楚,请帮忙检查下dts文件或者指出几个比较关键的参数.

之前运行linux-3.0.35 版本bsp的时候,几个初始化的.S文件,包含内存等参数都是官方原版的,没有做任何修改,只是对应调整了pin配置的几个初始化的地方,系统就跑起来了,因此分析问题大概率是出在dts配置上,请多指教这方面的问题.

0 Kudos

61 Views
NXP TechSupport
NXP TechSupport

Hello Gavin,

     please add "android.selinux=disabled" to bootargs of u-boot! Then try it again!


Have a great day,
TIC   weidong sun

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

0 Kudos

61 Views
Contributor I

Thanks.

附件是几个dts和启动参数相关文件,看电源配置部分是否正确。

换官方的kernel也都是一样的故障现象,是dts配置问题还是uboot初始化的问题呢,感觉不像是kernel的问题。

0 Kudos