[问答]

针对CentOS 7的Zynq FSBL和BSP项目的SDK错误

问答对人有帮助，内容完整，我也想知道答案 0 我已经安装了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 / fl_handoff.o“-mcpu = cortex-a9 -mfpu = vfpv3 -mfloat-abi = hard -I ../../ zynq_fl_bsp / ps7_cortexa9_0 / include -MMD -MP -MF”src / fl_handoff.d“-MT “src / fl_handoff.o” - o“src / fl_handoff.o”“../src/fl_handoff.S” cc1：错误：/home/user/Downloads/ad-hdl/projects/fmcomms2/zed/fmcomms2_zed.sdk/system_top_hw_platform_0：对于定义的数据类型，值太大 cc1：错误：../../ zynq_fl_bsp / ps7_cortexa9_0 / include：对于定义的数据类型，值太大 make： [src / fl_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/fl_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/fl_handoff.o" -mcpu=cortex-a9 -mfpu=vfpv3 -mfloat-abi=hard -I../../zynq_fl_bsp/ps7_cortexa9_0/include -MMD -MP -MF"src/fl_handoff.d" -MT"src/fl_handoff.o" -o "src/fl_handoff.o" "../src/fl_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_fl_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? 0
2018-12-27 10:58:11　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × asd008 该类别下有 32 个回答。邀请回答 aaaa321 该类别下有 27 个回答。邀请回答 doublelove 该类别下有 26 个回答。邀请回答 vynywrwr 该类别下有 21 个回答。邀请回答 hgjhgd 该类别下有 19 个回答。邀请回答 bwerwer 该类别下有 18 个回答。邀请回答 hanyan533 该类别下有 18 个回答。邀请回答 Jaionm 该类别下有 18 个回答。邀请回答 handsomelchcpp 该类别下有 17 个回答。邀请回答 wang2222222 该类别下有 17 个回答。邀请回答 ningee 该类别下有 16 个回答。邀请回答 binro 该类别下有 16 个回答。邀请回答 myf888 该类别下有 15 个回答。邀请回答 wznnzw 该类别下有 15 个回答。邀请回答 60user25 该类别下有 14 个回答。邀请回答 zcy615 该类别下有 14 个回答。邀请回答 wanglinhua2627 该类别下有 14 个回答。邀请回答 guotong1984 该类别下有 14 个回答。邀请回答 yhxc 该类别下有 14 个回答。邀请回答 armortech 该类别下有 14 个回答。邀请回答举报武文嘉相关推荐 • SDK构建失败 1721 • Vivado SDK BSP命令行怎么构建 3741 • 将Zynq项目导出到SDK时，如果找不到任何MIG，是否会出现问题？ 1601 • 如何在SDK中设置enable_mmc 1495 • Vivado 2013.2错误：AXI地址未导出到SDK中的system.xml定义 1520 • ZC706 BIST编译在Linux上失败 3023 • freeRTOS 如何移植到zynq芯片 2330 • 使用Zynq PL结构时钟驱动代码没有反应是为什么？ 2212 • Zynq FSBL src main.c在哪里是从QSPI加载比特流到Artix的PL的函数 1444 • CentOS上的PlanAhead 14.7无法将Bitstream导出到SDK 1138 2个回答

答案对人有帮助，有参考价值 0 看起来问题与我的硬盘驱动器的尺寸与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

2018-12-27 11:15:10 评论举报李欢

答案对人有帮助，有参考价值 0 看起来问题与我的硬盘驱动器的尺寸与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.

2018-12-27 11:32:26 评论举报李欢