完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
我已经安装了32位库来支持SDK(或者,至少我很确定我已经安装了所有指定的),但是当我尝试构建FSBL或BSP项目时,我会收到类似这样的错误
: make pre-build main-build A9-Linaro的 - 前累积步骤 构建文件:../ src /f***l_handoff.S 调用:ARM v7 gcc编译器 arm-none-eabi-gcc -Wall -O0 -g3 -I“/home/user/Downloads/ad-hdl/projects/fmcomms2/zed/fmcomms2_zed.sdk/system_top_hw_platform_0”-c -fmessage-length = 0 -MT“ src / f***l_handoff.o“-mcpu = cortex-a9 -mfpu = vfpv3 -mfloat-abi = hard -I ../../ zynq_f***l_bsp / ps7_cortexa9_0 / include -MMD -MP -MF”src / f***l_handoff.d“-MT “src / f***l_handoff.o” - o“src / f***l_handoff.o”“../src/f***l_handoff.S” cc1:错误:/home/user/Downloads/ad-hdl/projects/fmcomms2/zed/fmcomms2_zed.sdk/system_top_hw_platform_0:对于定义的数据类型,值太大 cc1:错误:../../ zynq_f***l_bsp / ps7_cortexa9_0 / include:对于定义的数据类型,值太大 make:*** [src / f***l_handoff.o]错误1 是否有其他人使用CentOS 7成功地在SDK中创建项目? 以上来自于谷歌翻译 以下为原文 I've installed the 32-bit libraries to support the SDK (or, at least I'm pretty sure I've installed all the ones specified), but when I try to build an FSBL or BSP project, I get errors like these: make pre-build main-build a9-linaro-pre-build-stepBuilding file: ../src/f***l_handoff.SInvoking: ARM v7 gcc compilerarm-none-eabi-gcc -Wall -O0 -g3 -I"/home/user/Downloads/ad-hdl/projects/fmcomms2/zed/fmcomms2_zed.sdk/system_top_hw_platform_0" -c -fmessage-length=0 -MT"src/f***l_handoff.o" -mcpu=cortex-a9 -mfpu=vfpv3 -mfloat-abi=hard -I../../zynq_f***l_bsp/ps7_cortexa9_0/include -MMD -MP -MF"src/f***l_handoff.d" -MT"src/f***l_handoff.o" -o "src/f***l_handoff.o" "../src/f***l_handoff.S"cc1: error: /home/user/Downloads/ad-hdl/projects/fmcomms2/zed/fmcomms2_zed.sdk/system_top_hw_platform_0: Value too large for defined data typecc1: error: ../../zynq_f***l_bsp/ps7_cortexa9_0/include: Value too large for defined data typemake: *** [src/f***l_handoff.o] Error 1Is anyone else using CentOS 7 having success in creating projects in the SDK? |
|
相关推荐
2个回答
|
|
看起来问题与我的硬盘驱动器的尺寸与Xilinx提供的工具相关。
文件的inode大于32位寻址可能支持的,并且SDK工具试图用32位来统计文件。 修复方法是构建一个32位友好的虚拟磁盘映像,将我的文件移入其中,然后运行SDK。 #Disk image fallocate -l 2G my_project.img mkfs -t ext4 my_project.img #当它询问不是块设备时,说“是”继续 #将原始项目目录移动到不同位置 mv my_project my_project.orig #制作一个挂载点,挂载img,获取所有权,将文件移入其中 mkdir my_project sudo mount my_project.img my_project sudo chown YOUR_NAME my_project mv my_project.orig / * my_project rmdir my_project.orig 此时,您将能够在该项目上运行SDK并构建您的FSBL或其他任何抱怨的内容。 在上面的示例中,我的虚拟磁盘大小为2 GB。 在原帖中查看解决方案 以上来自于谷歌翻译 以下为原文 It looks like the issue was tied to the size of my hard drive vs. the tooling that Xilinx provides. The inodes for the files were larger than 32-bit addressing could support, and the SDK tooling was trying to stat the files with 32-bit. A fix was to build a virtual disk image that was 32-bit friendly, move my files into it, and then run SDK. # Disk imagefallocate -l 2G my_project.imgmkfs -t ext4 my_project.img# say "yes" to continue when it asks about not being a block device# Move original project dir to different spotmv my_project my_project.orig# Make a mount point, mount the img, take ownership, move files into itmkdir my_projectsudo mount my_project.img my_projectsudo chown YOUR_NAME my_projectmv my_project.orig/* my_projectrmdir my_project.origAt that point you'll be able to run SDK on that project and build your FSBL or whatever else it was complaining about. In the above example, my virtual disk is 2 GB in size. View solution in original post |
|
|
|
看起来问题与我的硬盘驱动器的尺寸与Xilinx提供的工具相关。
文件的inode大于32位寻址可能支持的,并且SDK工具试图用32位来统计文件。 修复方法是构建一个32位友好的虚拟磁盘映像,将我的文件移入其中,然后运行SDK。 #Disk image fallocate -l 2G my_project.img mkfs -t ext4 my_project.img #当它询问不是块设备时,说“是”继续 #将原始项目目录移动到不同位置 mv my_project my_project.orig #制作一个挂载点,挂载img,获取所有权,将文件移入其中 mkdir my_project sudo mount my_project.img my_project sudo chown YOUR_NAME my_project mv my_project.orig / * my_project rmdir my_project.orig 此时,您将能够在该项目上运行SDK并构建您的FSBL或其他任何抱怨的内容。 在上面的示例中,我的虚拟磁盘大小为2 GB。 以上来自于谷歌翻译 以下为原文 It looks like the issue was tied to the size of my hard drive vs. the tooling that Xilinx provides. The inodes for the files were larger than 32-bit addressing could support, and the SDK tooling was trying to stat the files with 32-bit. A fix was to build a virtual disk image that was 32-bit friendly, move my files into it, and then run SDK. # Disk imagefallocate -l 2G my_project.imgmkfs -t ext4 my_project.img# say "yes" to continue when it asks about not being a block device# Move original project dir to different spotmv my_project my_project.orig# Make a mount point, mount the img, take ownership, move files into itmkdir my_projectsudo mount my_project.img my_projectsudo chown YOUR_NAME my_projectmv my_project.orig/* my_projectrmdir my_project.origAt that point you'll be able to run SDK on that project and build your FSBL or whatever else it was complaining about. In the above example, my virtual disk is 2 GB in size. |
|
|
|
只有小组成员才能发言,加入小组>>
2424 浏览 7 评论
2826 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2294 浏览 9 评论
3375 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2465 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
1253浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
590浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
453浏览 1评论
2008浏览 0评论
732浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-25 22:53 , Processed in 1.249756 second(s), Total 50, Slave 43 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号