sgannava
Occasional ContributorJoined 1 year ago
User Profile
Occasional Contributor
User Widgets
Contributions
Collection does not exist error while using Timing Analyzer with Intel Quartus Prime Pro 23.3
Hi Team, I have the timing query tcl script. If I run the tcl script in the timing analyzer of Intel Quartus Prime Pro 23.3, I am getting the below error Error (23035): Tcl error: can't read "slack": no such variable ###Tcl script create_timing_netlist read_sdc update_timing_netlist report_timing -append set worst_path [get_timing_paths -npaths 1 -setup] foreach_in_collection path $worst_path { set slack [get_path_info $path -slack] } puts $slack Few times I got below error also Error(23035): Tcl error: ERROR: Collection does not exist with name (:internal collection). Specify the collection name returned by a Tcl command that supports "foreach_in_collection." Note a valid collection name can become invalid if the variable holding the collection goes out of scope, as well as a result of some built-in TCL commands, for example, 'string length.' Thanks Sai G431Views0likes2CommentsRe: How to retrieve the deleted ip files from ip/system_soc/ folder
Got it. But in my case, I should share only .qsys and dependent files only, but not the .ip source files. In Quartus standard, I am sharing only those as above mentioned and we have few tcl commands to generate the .ip files under ip/system_soc. But it is not happening with Quartus Pro. Thos tcl commands are not generating the .ip files. Any idea on using tcl commands for this purpose would be helpful Thanks Sai G1.4KViews0likes0CommentsHow to retrieve the deleted ip files from ip/system_soc/ folder
Hi Team, I have created a platform designed (system_soc.qsys) for Arria10 using Intel Quartus Prime Pro 23.3 software. I have completed the design and saved the qsys file. But, unknowingly I have deleted the ip/system_soc folder where the IP's reside. Now, If I try to load my qsys file in platform designer, it is throwing the warnings like File not found: ip/system_soc/system_arria10_emif.ip I knew this is because I have deleted the IP path folder. Is there anyway I can retrieve the ip folder using any tcl commands or how can I proceed further Any help would be appreciated Thanks Sai G1.6KViews0likes10CommentsRe: Custom linux image build failure for Arri10 SoC development kit
Hi Jingyang, I am exactly following the same as mentioned in the documenatation. I am getting aforementioned error. I have also tried by changing the size of all the partitions, but still same error, but I can see the image built. But when I see the disk partition, I culd not see the FAT32 partition. As I said, in previous reply, "I assumed core-image-minimal-arria10.rootfs.tar.gz as core-image-minimal-arria10.tar.gz and proceeded further for creating an SD image" Could that be the problem? Thanks Sai5.5KViews0likes0CommentsRe: Custom linux image build failure for Arri10 SoC development kit
Hi Jingyang, Thanks for your response. Are you able to see core-image-minimal-arria10.tar.gz in the specified directory? Becuase I am not able to see that if I built rootfs using nanbield branch? FYI, I am able to build using nanbield branch only by removing linux-socfpga_6.6.bb file. But I cannot see core-image-minimal-arria10.tar.gz as mentioned in the documentation So, I assumed core-image-minimal-arria10.rootfs.tar.gz as core-image-minimal-arria10.tar.gz and proceeded further for creating an SD image. But while, creating SD image, I see the below error. But surprisingly, I can see the sdcard_a10.img file built with 80MB size. However this is not booting the board. Kindly, look into this as it is blocking my work. info: creating the image sdcard_a10.img image removed info: creating the partition table image_name set to sdcard_a10.img Partition return code [ 0 ] now delete loopback info: processing partitions... partition #3... do_partition entry partition #1... do_partition entry error: format: failed. Return code=1 params=['-F 32', '-I'], cmd=mkfs.vfat stdout=mkfs.fat 4.2 Bad FAT type : 32 stderr=Usage: mkfs.vfat [OPTIONS] TARGET [BLOCKS] Create FAT filesystem in TARGET, which can be a block device or file. Use only up to BLOCKS 1024 byte blocks if specified. With the -C option, file TARGET will be created with a size of 1024 bytes times BLOCKS, which must be specified. Options: -a Disable alignment of data structures -A Toggle Atari variant of the filesystem -b SECTOR Select SECTOR as location of the FAT32 backup boot sector -c Check device for bad blocks before creating the filesystem -C Create file TARGET then create filesystem in it -D NUMBER Write BIOS drive number NUMBER to boot sector -f COUNT Create COUNT file allocation tables -F SIZE Select FAT size SIZE (12, 16 or 32) -g GEOM Select disk geometry: heads/sectors_per_track -h NUMBER Write hidden sectors NUMBER to boot sector -i VOLID Set volume ID to VOLID (a 32 bit hexadecimal number) -I Ignore and disable safety checks -l FILENAME Read bad blocks list from FILENAME Thanks Sai5.6KViews0likes0CommentsRe: Custom linux image build failure for Arri10 SoC development kit
Hi Jingyang, Without adding custom recipes Following the steps mentioned in the documentation, I faced some errors and I have attached the screenshots Error-1: linux-socfpga-6.6+git-r0 do_compile: oe_runmake failed I have resolved this issue by removing linux-socfpga-6.6.bb file after cloning the repository Issue-2: After running the bitbake core-image-minimal In the documentation, it is mentioned that core-image-minimal-arria10.tar.gz will be generated under below path after running above bitbake command $ROOTFS_TOP/a10/build/tmp/deploy/images/arria10 But I cannot see the tarball with exact name. but instead, I could see core-image-minimal-arria10-rootfs.tar.gz. Hence, I used that and proceeded further. Finally I am able to created an .img file of size 84MB. When I load this onto board, I can see only blank screen on Putty. The conclusion is , without custom recipes also, booting not happening. I also checked that the shipping intel image is of size 1.02GB. I am not sure why the process is not creating the same. General Questions here: I have checked the SD partition after burning the SD with intel shipping image and image build from my side using Yocto. I can see the major difference in partition. I have attached then screenshots as well. Can I know why I am seeing such difference? With Custom recipes Error-1: I am getting the bitbake errors. I attached the screenshots with name recipe_bitbake_error1 Somehow, I overcome the error by Renaming u-boot-xlnx-scr.bbappend to u-boot-xlnx-scr.bb Renaming the petalinux-image-minimal.bbappend to core-image-minimal.bbappend Renaming libiio_%.bbappend to libiio_git.bb Added required license file also in layer.conf file Error - 2: But again, I have come up with another issue. Attached as withrecipe_bitbake_error2 I have tried cleaning the project as well and cleaning the particular script as well, but nothing happened With Regards, Sai6KViews0likes0Comments