嵌入式linux系统死机原因,嵌入式Linux引导卡死。如何调试?

在petalinux构建的嵌入式平台中,在引导期间(从u-boot),我看到的最后一个打印是(有时)mmcblk0boot1打印。

调试/跟踪/修复问题的好方法是什么?

正如您在日志末尾看到的,是另一个引导的开始

附加日志

=======================================================================

> U-Boot 2015.07 (Jul 22 2018 - 14:04:29 +0300)

> DRAM: ECC disabled 511 MiB

> MMC: Max clock 26000000, Min clock 0

> zynq_sdhci: 0

> SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 16 MiB

> *** Warning - bad CRC, using default environment

> In: serial

> Out: serial

> Err: serial

> Net: Gem.e000b000

> U-BOOT for AAS_TOP_V0_00_12

> Hit any key to stop autoboot: 4 3 2 1 0

> Device: zynq_sdhci

> Manufacturer ID: fe

> OEM: 14e

> Name: MMC04

> Tran Speed: 26000000

> Rd Block Len: 512

> MMC version 4.4.1

> High Capacity: Yes

> Capacity: 3.5 GiB

> Bus Width: 4-bit

> Erase Group Size: 512 KiB

> HC WP Group Size: 4 MiB

> User Capacity: 3.5 GiB

> Boot Capacity: 16 MiB ENH

> RPMB Capacity: 128 KiB ENH

> reading image.ub

> 7775932 bytes read in 750 ms (9.9 MiB/s)

> ## Loading kernel from FIT Image at 01000000 ...

> Using 'conf@1' configuration

> Verifying Hash Integrity ... OK

> Trying 'kernel@1' kernel subimage

> Description: PetaLinux Kernel

> Type: Kernel Image

> Compression: gzip compressed

> Data Start: 0x010000f0

> Data Size: 7760664 Bytes = 7.4 MiB

> Architecture: ARM

> OS: Linux

> Load Address: 0x00008000

> Entry Point: 0x00008000

> Hash algo: crc32

> Hash value: 53e3bbd8

> Verifying Hash Integrity ... crc32+ OK

> ## Loading fdt from FIT Image at 01000000 ...

> Using 'conf@1' configuration

> Trying 'fdt@1' fdt subimage

> Description: Flattened Device Tr