打印
[i.MX]

android的kernel无法启动文件系统

[复制链接]
1738|3
手机看帖
扫描二维码
随时随地手机跟帖
跳转到指定楼层
楼主
nym521|  楼主 | 2016-2-22 15:37 | 只看该作者 回帖奖励 |倒序浏览 |阅读模式
本帖最后由 nym521 于 2016-2-22 17:13 编辑

参考飞思卡尔官方imx6dl_sabresd的开发板,自己layout一块板子.
在移植android4.3时,从sd卡启动.对fstab.freescale文件,已经做修改.

kernel启动后,仍无法启动文件系统.

下面是打印信息:
....此处省略
Board: i.MX6DL/Solo-SABRESD: unknown-board Board: 0x61013 [POR ]
Boot Device: SD
I2C:   ready
DRAM:   1 GB
MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3
In:    serial
Out:   serial
Err:   serial
i2c: I2C3 SDA is low, start i2c recovery...
I2C3 Recovery success
Net:   got MAC address from IIM: 00:00:00:00:00:00
FEC0 [PRIME]
Hit any key to stop autoboot:  0
kernel   @ 10808000 (4523468)
ramdisk  @ 11800000 (234098)
kernel cmdline:
        use uboot command line:
        console=ttymxc1,115200 init=/init video=mxcfb0:dev=lcd,if=RGB24,bpp=32 video=mxcfb1:dev=hdmi,1280x720M@60,if=RGB24,bpp=32 vid

Starting kernel ...

Initializing cgroup subsys cpu
Linux version 3.0.35 (root@fyh-ubuntu) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #2 SMP PREEMPT Mon Feb 22 14:06:20 CST6
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Freescale i.MX 6Quad/DualLite/Solo Sabre-SD Board
Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writealloc
CPU identified as i.MX6DL/SOLO, unknown revision
PERCPU: Embedded 7 pages/cpu @c1282000 s6592 r8192 d13888 u32768
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 191232
Kernel command line: console=ttymxc1,115200 init=/init video=mxcfb0:dev=lcd,if=RGB24,bpp=32 video=mxcfb1:dev=hdmi,1280x720M@60,if=RGBe
PID hash table entries: 2048 (order: 1, 8192 bytes)
......
......
......
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.3] using ADMA
mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using ADMA
mmc2: SDHCI controller on platform [sdhci-esdhc-imx.1] using ADMA
mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
VPU initialized
mxc_asrc registered
Galcore version 4.6.9.6622
revserved_memory_account:viv_gpu registerd
Thermal calibration data is 0x55a4d269
Thermal sensor with ratio = 176
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
Registered led device: chg_now_led
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 256K log 'log_main'
logger: created 256K log 'log_events'
logger: created 256K log 'log_radio'
logger: created 256K log 'log_system'
usbcore: registered new interface driver snd-usb-audio
mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
Cirrus Logic CS42888 ALSA SoC Codec Driver
i2c-core: driver [cs42888] using legacy suspend method
i2c-core: driver [cs42888] using legacy resume method
imx-hdmi-soc-dai imx-hdmi-soc-dai.0: Failed: Load HDMI-video first.
wm8962 0-001a: Failed to get supply 'DCVDD': -19
wm8962 0-001a: Failed to request supplies: -19
wm8962 0-001a: asoc: failed to probe CODEC wm8962.0-001a: -19
asoc: failed to instantiate card wm8962-audio: -19
imx_3stack asoc driver
Initialize HDMI-audio failed. Load HDMI-video first!
ALSA device list:
  No soundcards found.
oprofile: using arm/armv7-ca9
GACT probability NOT on
Mirror/redirect action on
u32 classifier
    Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (11776 buckets, 47104 max)
ctnetlink v0.93: registering with nfnetlink.
NF_TPROXY: Transparent proxy support initialized, version 4.1.0
NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
xt_time: kernel timezone is -0000
IPv4 over IPv4 tunneling driver
GRE over IPv4 demultiplexor driver
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
TCP cubic registered
NET: Registered protocol family 10
Mobile IPv6
ip6_tables: (C) 2000-2006 Netfilter Core Team
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
L2TP core driver, V2.0
PPPoL2TP kernel driver, V2.0
L2TP IP encapsulation support (L2TPv3)
L2TP netlink interface
L2TP ethernet pseudowire support (L2TPv3)
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'
lib80211_crypt: registered algorithm 'TKIP'
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Bus freq driver module loaded
Bus freq driver Enabled
mxc_dvfs_core_probe
DVFS driver module loaded
regulator_init_complete: SPKVDD: incomplete constraints, leaving on
snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
Freeing init memory: 240K
到此结束

曾经有一块正常启动的板子,启动过程,如下:
...此处省略
L2TP IP encapsulation support (L2TPv3)
L2TP netlink interface
L2TP ethernet pseudowire support (L2TPv3)
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'
lib80211_crypt: registered algorithm 'TKIP'
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Bus freq driver module loaded
Bus freq driver Enabled
DVFS driver module loaded
mmc1: new high speed SDHC card at address aaaa
regulator_init_complete: VDDD: incomplete constraints, leaving on
mmcblk1: mmc1:aaaa SS08G 7.40 GiB
rtc-pcf8563 2-0051: low voltage detected, date/time is not reliable.
rtc-pcf8563 2-0051: retrieved date/time is not valid.
rtc-pcf8563 2-0051: hctosys: invalid date/time
Freeing init memory: 236K
mmcblk1: p1 p2 p3 < p5 p6 p7 p8 > p4
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
root@sabresd_6dq:/ #
到此结束

发现卡在了system/core/init/init.c文件中的open_devnull_stdio()处,无法屏蔽标准的输入输出,为什么会出现这种问题呢?

路过的各位大侠,希望给给建议.!
谢谢!

相关帖子

沙发
nym521|  楼主 | 2016-2-23 14:48 | 只看该作者
文件系统起来了,是我的fstab.freescale文件修改的不正确导致的.

其中官方fstab.freescale内容如下:
/devices/platform/sdhci-esdhc-imx.2/mmc_host/mmc1 /mnt/extsd vfat defaults voldmanaged=sdcard:auto
/devices/platform/fsl-ehci /mnt/udisk vfat defaults voldmanaged=sdcard:auto
/dev/block/mmcblk0p5    /system      ext4    ro                                                                               wait
/dev/block/mmcblk0p6     /data        ext4    nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic    wait,encryptable=footer
/dev/block/mmcblk0p6    /cache       ext4    nosuid,nodev,nomblk_io_submit                                                    wait
/dev/block/mmcblk0p7    /device      ext4    ro,nosuid,nodev                                                                  wait
/dev/block/mmcblk0p1    /boot        emmc    defaults                                                                         defaults
/dev/block/mmcblk0p2    /recovery    emmc    defaults                                                                         defaults
/dev/block/mmcblk0p8    /misc        emmc    defaults                                                                         defaults
针对 fstab.freescale文件,存在以下几个问题:
1) sdhci-esdhc-imx.2中的数字2,从哪里而来,怎么确定?
2)mmc1 怎么确定是哪一个?  
3)/mmcblk0怎么确定的?

如果有知道的前辈,请不吝赐教.
谢谢!

使用特权

评论回复
板凳
mini1986| | 2016-2-23 16:42 | 只看该作者
你的跟官方的启动方式有区别吧......你所问的问题,得在启动打印信息里面找,具体我没详细研究......

使用特权

评论回复
地板
nym521|  楼主 | 2016-2-24 09:33 | 只看该作者
mini1986 发表于 2016-2-23 16:42
你的跟官方的启动方式有区别吧......你所问的问题,得在启动打印信息里面找,具体我没详细研究...... ...

启动方式跟官方的有点不一样

使用特权

评论回复
发新帖 我要提问
您需要登录后才可以回帖 登录 | 注册

本版积分规则

20

主题

46

帖子

1

粉丝