解决qt移植中镜像过大问题
来源:互联网 发布:我是淘宝黑名单买家 编辑:程序博客网 时间:2024/05/16 01:28
启动情况如下:
U-Boot 2015.04 (Oct 28 2015 - 09:23:09)
DRAM: ECC disabled 512 MiB
MMC: 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 software
Gem.e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Gem.e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Gem.e000b000: No link.
Hit any key to stop autoboot: 0
Device: zynq_sdhci
Manufacturer ID: 1b
OEM: 534d
Name: 00000
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 14.9 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading image.ub
22243080 bytes read in 1856 ms (11.4 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: 22226754 Bytes = 21.2 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00008000
Entry Point: 0x00008000
Hash algo: crc32
Hash value: 135e9555
Verifying Hash Integrity ... crc32+ OK
## Loading fdt from FIT Image at 01000000 ...
Using 'conf@1' configuration
Trying 'fdt@1' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x02532918
Data Size: 15027 Bytes = 14.7 KiB
Architecture: ARM
Hash algo: crc32
Hash value: 6bbf9649
Verifying Hash Integrity ... crc32+ OK
Booting using the fdt blob at 0x2532918
Uncompressing Kernel Image ... Error: inflate() returned -5
Image too large: increase CONFIG_SYS_BOOTM_LEN
Must RESET board to recover
resetting ...
DRAM: ECC disabled 512 MiB
MMC: 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 software
Gem.e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Gem.e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Gem.e000b000: No link.
Hit any key to stop autoboot: 0
Device: zynq_sdhci
Manufacturer ID: 1b
OEM: 534d
Name: 00000
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 14.9 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading image.ub
22243080 bytes read in 1856 ms (11.4 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: 22226754 Bytes = 21.2 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00008000
Entry Point: 0x00008000
Hash algo: crc32
Hash value: 135e9555
Verifying Hash Integrity ... crc32+ OK
## Loading fdt from FIT Image at 01000000 ...
Using 'conf@1' configuration
Trying 'fdt@1' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x02532918
Data Size: 15027 Bytes = 14.7 KiB
Architecture: ARM
Hash algo: crc32
Hash value: 6bbf9649
Verifying Hash Integrity ... crc32+ OK
Booting using the fdt blob at 0x2532918
Uncompressing Kernel Image ... Error: inflate() returned -5
Image too large: increase CONFIG_SYS_BOOTM_LEN
Must RESET board to recover
resetting ...
解决方法:
1. petalinux-config/uboot - netstart offset change from hex 0x1000000 to desired value - my image.ub ~20M, but I set it to 0x4000000.
2. In your petalinux project config files for u-boot 'platform-auto.h' change CONFIG_SYS_BOOTM_LEN from 0x1000000 to same value 0x4000000.
rebuild the whole thing.
During u-boot start stop it and verify your u-boot settings loadaddr and netstart set to 0x4000000. If not - change them and save: "set loadaddr 0x4000000",..., "saveenv" and reboot.
0 0
- 解决qt移植中镜像过大问题
- 解决cookie过大问题
- 解决迅雷占用系统资源过大的问题
- 解决SharePoint_Config_log.ldf文件过大问题
- PHPExcel解决内存占用过大问题
- 解决VS2010工程体积过大问题
- 解决linux服务器内存占用过大问题
- 解决jsp 文件加载过大的问题
- poi解决内存消耗过大溢出问题
- 如何解决Mongodb内存过大问题
- Android解决图片上传过大问题
- 解决webpack打包文件过大的问题
- 解决webpack打包文件过大的问题
- tomcat 解决catalina.out过大的问题
- so 动态加载---解决sdk过大问题
- 《Angular4之解决构建包过大问题》
- qt移植问题
- qt移植问题
- 深入研究Android Handler机制
- 本地路径转换成URL相对路径
- linux目录介绍和文件操作
- 【旅游类APP源码】开发者案例开源,走过路过不可错过!
- 项目经验分享
- 解决qt移植中镜像过大问题
- iOS QQ第三方登实现
- How-to: resolve "java.io.NotSerializableException" issue during spark reading hbase table
- Android 编程下的代码混淆
- 海尔T520智能扫地机器人使用评测
- activiti与spring集成(maven)
- linux权限篇【一】
- MFC中获取各个窗体之间的句柄或者指针对象的方法 .
- WebLogic Tuxedo Connector 快速入门指南