|
发表于 2016-1-9 20:41:45
23074 浏览 8 回复
iTop4412_Kernel_3.0目录下make编译生成的zImage不能使用
每次在iTop4412_Kernel_3.0目录下使用make命令进行编译的生成zImage文件烧写到开发板,重启开发板,超级终端的时候一直出现5秒倒计时死循环,然后把ramdisk-uboot.img用android目录下的替换后,不死循环了,却又出现如下图的问题,怎么解决?
[ 4.670444] dm962x: ethernet MAC address 00:00:ff:ff:00:00 (chip)
[ 4.676554] dm962x: 9620 Mode = 128
[ 4.681047] init: cannot find '/system/bin/6620_launcher', disabling '6620_launcher'
[ 4.690248] init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
[ 4.695921] dm9620 1-3.2:1.0: eth0: register 'dm9620' at usb-s5p-ehci-3.2, Davicom DM9620 USB Ethernet, 00:00:ff:ff:00:00
[ 4.707725] init: cannot find '/system/bin/vold', disabling 'vold'
[ 4.713861] init: cannot find '/system/bin/netd', disabling 'netd'
[ 4.720041] init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
[ 4.727037] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
[ 4.733719] init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'
[ 4.741619] init: cannot find '/system/bin/app_process', disabling 'zygote'
[ 4.748562] init: cannot find '/system/bin/drmserver', disabling 'drm'
[ 4.755082] init: cannot find '/system/bin/mediaserver', disabling 'media'
[ 4.761931] init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
[ 4.768710] init: cannot find '/system/bin/installd', disabling 'installd'
[ 4.777250] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[ 4.784185] init: cannot find '/system/bin/keystore', disabling 'keystore'
[ 4.791037] init: cannot find '/system/bin/hald', disabling 'hald'
[ 4.797215] init: cannot find '/system/bin/cfg_audio', disabling 'cfg_audio'
[ 4.804223] init: property (null) has no value for writing to /sys/class/android_usb/android0/iManufacturer
[ 4.813936] init: property (null) has no value for writing to /sys/class/android_usb/android0/iProduct
[ 4.824273] android_work: did not send uevent (0 0 (null))
[ 4.829175] adb_bind_config
[ 4.831962] init: cannot execve('/system/bin/sh'): No such file or directory
[ 4.836322] adb_open
[ 4.836334] ADB open:
[ 4.837718] android_work: did not send uevent (0 0 (null))
[ 4.982639] android_work: sent uevent USB_STATE=CONNECTED
[ 5.053883] android_usb gadget: high speed config #1: android
[ 5.058968] android_work: sent uevent USB_STATE=CONFIGURED
[ 5.545192] CPU1: shutdown
[ 6.479156] CPU2: shutdown
[ 9.863311] init: cannot execve('/system/bin/sh'): No such file or directory
[ 11.721728] CPU3: shutdown
[ 14.883931] init: cannot execve('/system/bin/sh'): No such file or directory
[ 19.903627] init: cannot execve('/system/bin/sh'): No such file or directory
[ 24.923621] init: cannot execve('/system/bin/sh'): No such file or directory
[ 29.943586] init: cannot execve('/system/bin/sh'): No such file or directory
[ 34.962987] init: cannot execve('/system/bin/sh'): No such file or directory
|
|
|
|
|
|
|
|
发表于 2016-5-7 17:17:29
我也遇到同样问题,先去吧初始化配置文件用官方的替代一下 |
|
|
|
|
|
|
|
你这个是不是运行的最小系统?
先用我们提供的最小系统测试,然后再对比你自己的,测试出是不是zImage的问题
看打印信息,应该是你制作的最小系统有问题。
好好检查那几个初始化配置文件,不行就用我们提供的那几个文件测试
注意不要在window下打开那个几个问题,直接网盘下载然后拷贝到Ubuntu系统下,因为windows会将文件格式给转化,重新导致你这个问题出现。 |
|
|
|
|
|
|
|
发表于 2016-5-31 22:57:27
按楼上的操作试了,用迅为提供的最小系统,还是同样的情况
|
|
|
|
|
|
|
|
发表于 2016-6-24 23:10:11
你的ramdisk、system.img、zImage是不是配套的?用最小系统的ramdisk陪android的zImage估计会出错。 |
|
|
|
|
|
|
|
楼主|
发表于 2016-7-1 17:44:03
|
|
|
|
|
|
|
发表于 2016-8-30 14:22:16
|
|
|
|
|
|
|
发表于 2016-9-10 13:35:10
是不是编译的zImage是Android用的,而网盘的最小系统的system是qt的,所以不能用,要zImage,ramdisk,system都要为区分清楚,qt与Android,个人也遇到过这情款 |
|
|
|
|
|
|
|
记得更新高版本的手册~
不是make编译,是make zImage命令 |
|
|
|
|
|
|
登录或注册
扫一扫关注迅为公众号
|