新手上路
- 积分
- 40
- 金钱
- 40
- 注册时间
- 2019-10-19
- 在线时间
- 10 小时
|
自己编译了kernel和uboot,这两个都可以运行起来。硬件设置的从SD卡启动
uboot启动
- U-Boot 2016.03 (Oct 28 2019 - 21:21:43 +0800)
- CPU: Freescale i.MX6ULL rev1.0 528 MHz (running at 396 MHz)
- CPU: Industrial temperature grade (-40C to 105C) at 43C
复制代码
kernel启动
- Starting kernel ...
- Booting Linux on physical CPU 0x0
- Linux version 4.1.15 (jun@ubuntu) (gcc version 4.9.4 (Linaro GCC 4.9-2017.01) ) #4 SMP PREEMPT Mon Oct 28 21:24:51 CST 2019
- CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c53c7d
- CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
复制代码 问题出在文件系统,最后一部分报错信息
- mmcblk0: error -110 sending status command, retrying
- mmcblk0: error -110 sending status command, retrying
- mmcblk0: error -110 sending status command, aborting
- blk_update_request: I/O error, dev mmcblk0, sector 0
- Buffer I/O error on dev mmcblk0, logical block 0, async page read
- mmcblk0: unable to read partition table
- RAMDISK: gzip image found at block 0
- RAMDISK: incomplete write (18404 != 32768)
- write error
- VFS: Mounted root (ext2 filesystem) on device 1:0.
- devtmpfs: mounted
- Freeing unused kernel memory: 440K (80b18000 - 80b86000)
- EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=261, block=65541
- EXT2-fs (ram0): error: remounting filesystem read-only
- Starting init: /sbin/init exists but couldn't execute it (error -5)
- EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=327, block=81925
- EXT2-fs (ram0): error: remounting filesystem read-only
- Starting init: /bin/init exists but couldn't execute it (error -5)
- EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=327, block=81925
- EXT2-fs (ram0): error: remounting filesystem read-only
- Starting init: /bin/sh exists but couldn't execute it (error -5)
- Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
- ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
复制代码 看这个信息,像是ramdisk分配的不合理
修改uboot配置
- setenv bootargs 'console=ttymxc0,115200 ramdisk_size=40000000'
- setenv bootcmd 'mmc dev 0; fatload mmc 0:1 80800000 zImage; fatload mmc 0:1 81800000 ramdisk.img;fatload mmc 0:1 87800000 imx6ull-14x14-evk.dtb; bootz 80800000 81800000 87800000;'
- saveenv
复制代码
能跑起来了,但是读到的不是我加载到81800000这个地址的文件系统,这个被挂载的文件系统是我写到nand里面的那个
- mmcblk0: error -110 sending status command, retrying
- mmcblk0: error -110 sending status command, retrying
- mmcblk0: error -110 sending status command, aborting
- blk_update_request: I/O error, dev mmcblk0, sector 0
- Buffer I/O error on dev mmcblk0, logical block 0, async page read
- mmcblk0: unable to read partition table
- RAMDISK: gzip image found at block 0
- VFS: Mounted root (ext2 filesystem) on device 1:0.
- Please press Enter to activate this console.
- / #
- / # ls
- bin lib mnt root tmp
- dev linuxrc opt sbin usr
- etc lost+found proc sys var
- / #
复制代码
请问怎么运行我放在SD里面的文件系统?这个nand里面的文件系统在什么时候,自己读取到的?
终端打印信息太长,我做成文件上传。
终端打印信息.zip
(7.37 KB, 下载次数: 0)
|
|