4

我想知道如何设置正确的MACH_TYPEarch_id为内核。我搜索并找到了至少 2 个内核将挂在“正在启动内核...”的引用。这些都有相同的答案。正确设置您的机器类型。但随后都没有提到如何做到这一点。有人知道怎么做吗?

对挂起的很好的解释。另一个很好的描述。

当我尝试启动内核时,这两者都接近于我所经历的。它卡在“正在启动内核...”上并且不会继续。我已经从 .configs 构建了几次内核,这些 .configs 应该完全适合我的模型。

Timesys (LinuxLink) 提供了一个 .config,它应该与他们提供的免费构建服务的内核相匹配。但这也行不通。如果我使用他们预先构建的内核,它启动没有问题。所以我知道这不是我的 u-boot 或我如何配置我的 SD 卡。问题必须来自内核构建。

我运行我的 make like:make ARCH=arm CROSS_COMPILE=${PATH_TO_TOOLCHAIN}/bin/armv7l-timesys-linux-gnueabi- uImage并按如下方式制作我的图像:sudo mkimage -A arm -O linux -T kernel -C none -a 0x70800000 -e 0x70800000 -n "Linux-2.6.35-ts-armv7l" -d arch/arm/boot/uImage ../../uImage

我正在使用飞思卡尔 i.MX53 评估板。当我尝试运行内核时:

U-Boot 2009.08-dirty (Aug 02 2013 - 19:57:03)

CPU:   Freescale i.MX53 family 2.1V at 800 MHz
mx53 pll1: 800MHz
mx53 pll2: 400MHz
mx53 pll3: 432MHz
mx53 pll4: 455MHz
ipg clock     : 66666666Hz
ipg per clock : 33333333Hz
uart clock    : 66666666Hz
cspi clock    : 108000000Hz
ahb clock     : 133333333Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
emi_slow clock: 133333333Hz
ddr clock     : 400000000Hz
esdhc1 clock  : 80000000Hz
esdhc2 clock  : 80000000Hz
esdhc3 clock  : 80000000Hz
esdhc4 clock  : 80000000Hz
nfc clock     : 26666666Hz

Board: MX53-LOCO 1.0 Rev. B
Boot Reason: [POR]
Boot Device: SD
I2C:   ready
DRAM:   1 GB
MMC:   FSL_ESDHC: 0,FSL_ESDHC: 1
In:    serial
Out:   serial
Err:   serial
Serial reinitilized!
Net:   got MAC address from IIM: 00:04:9f:01:f7:ce
FEC0 [PRIME]
Hit any key to stop autoboot:  0
mmc0 is current device

MMC read: dev # 0, block # 2048, count 8192 ... 8192 blocks read: OK
## Booting kernel from Legacy Image at 70800000 ...
Image Name:   Linux-2.6.35-ts-armv7l
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    2999932 Bytes =  2.9 MB
Load Address: 70800000
Entry Point:  70800000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK

Starting kernel ...

u-boot环境:

bootdelay=3
baudrate=115200
netdev=eth0
ethprime=FEC0
uboot=u-boot.bin
kernel=uImage
nfsroot=/opt/eldk/arm
bootargs_base=setenv bootargs console=ttymxc0,115200
bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm
bootcmd=run bootcmd_mmc
ethact=FEC0
lcd=video=mxcdi0fb:RGB24,SEIKO-WVGA di0_primary
bootargs_mmc=setenv bootargs ${bootargs} gpu_nommu ${lcd} ip=dhcp root=/dev/mmcblk0p1 rootwait rw
bootargs=console=ttymxc0,115200 gpu_nommu video=mxcdi0fb:RGB24,SEIKO-WVGA di0_primary ip=dhcp root=/dev/mmcblk0p1 rootwait rw
bootcmd_mmc=run bootargs_base bootargs_mmc; mmc dev 0; mmc read ${loadaddr} 0x800 0x2000; bootm
loadaddr=0x70800000
stdin=serial
stdout=serial
stderr=serial
4

1 回答 1

3

The issue is that a double u-boot header has been applied to the image. As per unixsmurf.

于 2013-09-06T15:42:02.323 回答